CN101277470B - A method and system for obtaining IP-CAN bearer - Google Patents

Abstract

The present invention provides a method of acquiring IP connection access network bearing, including: acquiring home type information corresponding to the IP-CAN bearing home network, obtaining IP-CAN bearing meeting the bearing home network requirement by utilizing the acquired home type information. The invention also provides a system of obtaining IP-CAN bearing, the system includes an acquisition module and an execution module. The application of the invention can utilize the existed IP-CAN bearing meeting the bearing home network requirement.

Description

A method and system for obtaining IP-CAN bearer

technical field

The invention relates to the field of mobile communication, in particular to a method and system for obtaining IP-CAN bearer.

Background technique

When the system needs to provide services, that is, when the IP connection access network (IP-CAN, IP-Connectivity Access Network) provides services for the user terminal (UE, Usersr Equipment), the user terminal or the network side needs to use the relevant signaling transmission Required IP-CAN bearer to transmit signaling or data. When the user terminal establishes the first bearer of the IP-CAN session, the gateway will assign an IP address to the user terminal and bring it to the user terminal in the bearer establishment response message, and when other bearers of the IP-CAN session are established , all bearer contexts in the IP-CAN session share the same context user terminal IP address, and bearers with the same user terminal IP have the same home network. Here, the IP-CAN network can be: General Packet Radio System (GPRS, Global Packet Radio System), Universal Mobile Telecommunications System (UMTS, Universal Mobile Telecommunication System), World Interoperability for Microwave Access (WiMAX, World Interoperability for Microwave Access ) system or long-term evolution/system architecture evolution (LTE/SAE, Long Term Evolution/System Architecture Evolution) network and other mobile communication networks.

When the UE is located at the home location, all IP-CAN bearers used to transmit signaling or data can be regarded as IP-CAN bearers of the local network. At this time, the home network is the local network; and when the UE is located at the visited location , the IP-CAN bearer used to transmit signaling or data can be divided into the IP-CAN bearer of the local network and the IP-CAN bearer of the remote network. At this time, the visited network is the local network, and the home network is the remote network. side network.

For some specific services, there are further requirements on the IP-CAN bearer for transmitting signaling or data. For example, for emergency services such as alarm calls and help calls, the IP-CAN bearer of the local network where the UE is located must be used to initiate an emergency service session request. That is, when the UE is located at the home location, the UE initiates an emergency service session request at the home location; when the UE is located at the visited location, the UE must initiate an emergency service session request at the visited location. For another example, for the non-emergency services that support route optimization initiated when the UE is located in the visited location, according to the policy configuration of the system, some services must use the IP-CAN bearer of the local network to complete at the visited location, while some services must return to the Attribution is accomplished by using the IP-CAN bearer of the remote network.

However, when the UE is in a visited location, there will usually be at least one IP-CAN bearer that can transmit signaling or data in the visited location and the home location respectively. For example, when the IP-CAN network is an SAE network, in order to ensure that the UE can normally initiate services at the home site and the visited site, the UE will establish bearers on the gateways of the home site and the visited site respectively, obtain two IP addresses, and use this The two IP addresses are respectively registered in the service system from the visited place and the home place, such as the IMS network, so that the UE has at least one available IP-CAN bearer in both the visited place and the home place.

At present, since there is no method for selecting the IP-CAN bearer, when the UE initiates some specific services at the visited location, it cannot determine whether the home network of the existing IP-CAN bearer is a local network or a remote network. Use the existing IP-CAN bearer; if the IP-CAN bearer is obtained through random selection, when the IP-CAN bearer that does not meet the specific service requirements is selected, the time for specific service processing will be increased. For example, for emergency services, if the IP-CAN bearer of the home network is selected, according to the current processing mechanism, the UE can only establish a special emergency bearer in the visited place to complete the emergency service request processing, instead of using the existing IP-CAN bearer belonging to the visited site. The IP-CAN bearer that satisfies the transmission requirements locally, thus increasing the processing time for emergency services.

To sum up, the current method for obtaining IP-CAN bearer cannot utilize the existing IP-CAN bearer that meets the requirements of the bearer home network, thus increasing the processing time for specific services.

Contents of the invention

An embodiment of the present invention provides a method for obtaining an IP-CAN bearer, which can utilize an existing IP-CAN bearer that meets the requirements of the bearer's home network.

An embodiment of the present invention provides a system for obtaining an IP-CAN bearer, which can utilize an existing IP-CAN bearer that meets the requirements of the bearer's home network.

In order to achieve the above-mentioned first purpose, the technical solutions of the embodiments of the present invention are specifically implemented as follows:

A method for obtaining an IP-CAN bearer, the method comprising: acquiring attribution type information corresponding to an IP-CAN bearer attribution network, and using the acquired attribution type information to obtain an IP-CAN bearer meeting the requirements of the bearer attribution network.

In order to achieve the above-mentioned second purpose, the technical solutions of the embodiments of the present invention are specifically implemented as follows:

A system for obtaining IP-CAN bearer, the system includes an obtaining module and an executing module;

The obtaining module is used to obtain the attribution type information corresponding to the IP-CAN bearer attribution network, and send the obtained attribution type information to the execution module;

The execution module is used to use the attribution type information input by the acquisition module to obtain the IP-CAN bearer that meets the requirements of the bearer attribution network.

It can be seen from the above technical solution that a method and system for obtaining an IP-CAN bearer provided by the embodiment of the present invention can use the attribution type information of the IP-CAN bearer to obtain an IP-CAN bearer that meets the requirements of the bearer attribution network, thereby making full use of The existing IP-CAN bearer can save bearer resources and processing time for specific services.

Description of drawings

FIG. 1 is a schematic flow chart of a method for obtaining the attribution type information of a default IP-CAN bearer by the SAE network in the first embodiment of the present invention.

Fig. 2 is a schematic flowchart of a method for the SAE network to acquire the attribution type information carried by the dedicated IP-CAN in the second embodiment of the present invention.

FIG. 3 is a schematic flowchart of a method for the GPRS network to obtain the attribution type information carried by the IP-CAN in the third embodiment of the present invention.

Fig. 4 is a schematic flowchart of a method for obtaining an IP-CAN bearer by using attribution type information in a fourth embodiment of the present invention.

Fig. 5 is a schematic flowchart of a method for obtaining an IP-CAN bearer by using attribution type information in a fifth embodiment of the present invention.

Fig. 6 is a schematic flowchart of a method for obtaining an IP-CAN bearer by using attribution type information in the sixth embodiment of the present invention.

Fig. 7 is a schematic flowchart of a method for updating attribution type information in the eighth embodiment of the present invention.

Fig. 8 is a schematic flowchart of a method for updating attribution type information in the ninth embodiment of the present invention.

FIG. 9 is a schematic structural diagram of a system for obtaining an IP-CAN bearer provided by an embodiment of the present invention.

Detailed ways

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and examples.

The main idea of the embodiments of the present invention is to obtain the attribution type information corresponding to the IP-CAN bearer network, and use the acquired attribution type information to select the IP-CAN bearer.

In order to enable the UE or the network side to use the attribution type information of the IP-CAN bearer to obtain the IP-CAN bearer, during the establishment of each IP-CAN bearer, the UE or the network side first obtains and saves the attribution type information of the bearer. Embodiment 1, Embodiment 2 and Embodiment 3 provide methods for UE or network side to obtain attribution type information, where attribution type information includes bearer attribution type information or address attribution information for user terminal IP address.

Embodiment one:

This embodiment takes the default IP-CAN bearer establishment process on the SAE network as an example to illustrate the method for the UE to obtain the address attribution type information of the default IP-CAN bearer. In this embodiment, the bearer attribution type information is obtained first, and then The address attribution type information is obtained according to the bearer attribution type information.

Fig. 1 is the schematic flow diagram of the method for obtaining the address attribution type information carried by the default IP-CAN in the first embodiment of the present invention, referring to Fig. 1, user equipment (UE, User Equipment) through an evolved radio access network (Evolved RAN) ) in the evolved base station (eNB, evolved Node Base), send an attach request to the evolved packet core network (Evolved Packet Core), and pass the mobile management entity (MME, Mobility Management Entity) and user plane entity (UPE, User PlaneEntity ), and send a default bearer establishment request to the access system anchor (IASA, Inter Access System Anchor). Wherein, the MME is separated from the UPE, and the session management module used for bearer establishment and management is set in the MME.

In this embodiment, during the establishment process of the default IP-CAN bearer, at this time, the UE has not allocated an IP address, and the MME includes the bearer attribution type information of the default IP-CAN bearer in the radio bearer request message and sends it to the eNB, and the eNB is performing During the radio resource connection process, the bearer attribution type information is included in the radio resource connection request message and transmitted to the UE, and the UE stores the bearer attribution type information.

In this embodiment, the MME may also include the address attribution type information of the IP address assigned to the UE in the radio bearer request message and pass it to the eNB, and the eNB includes the address attribution type information in the radio resource connection process during the radio resource connection process. The connection request message is sent to the UE, and the UE saves the address attribution type information.

Specifically include the following steps:

Step 101: UE sends an attach request to MME through eNB.

Step 102: the MME interacts with the HSS to complete the UE registration process.

Step 103: The MME sends a default bearer establishment request to the IASA through the UPE.

In this embodiment, the default bearer establishment request message sent by the MME to the IASA through the UPE includes bearer attribution type information of the default bearer. The bearer attribution type information of the default bearer is generated by the attribution type generation module set in the MME, and the bearer attribution type information can be generated according to the obtained gateway address of the IP-CAN bearer or according to a preset bearer attribution policy. In this embodiment, the method for generating bearer attribution type information is: obtain the gateway address of the IP-CAN bearer; judge whether the gateway address of the acquired IP-CAN bearer is the address of the local network, and if so, the IP-CAN bearer If it is a bearer of the local network, the generated bearer attribution type information is the local network; otherwise, the generated bearer attribution type information is the remote network. In this embodiment, the gateway address is the address of the access system anchor in the IASA.

Bearer attribution type information is a switch value. When the value is TRUE, it means that the IP-CAN bearer belongs to the local network; when the value is false (FALSE), it means that the IP-CAN bearer belongs to the remote network.

Step 104: The IASA returns a default bearer establishment request response to the MME through the UPE.

In this embodiment, as the network side, the IASA stores the obtained bearer attribution type information of the default bearer.

Step 105: the MME sends a radio bearer request to the eNB.

In this embodiment, the MME sends a radio bearer request carrying bearer attribution type information to the eNB.

In this embodiment, the radio bearer request sent by the MME to the eNB may also carry address attribution type information.

Step 106: the eNB sends a radio resource connection request to the UE.

In this embodiment, the eNB sends a radio resource connection request carrying bearer attribution type information to the UE.

In this embodiment, the radio resource connection request sent by the eNB to the UE may also carry address attribution type information.

Step 107: the UE saves the bearer attribution type information.

In this embodiment, the UE directly saves the bearer attribution type information together with the IP-CAN bearer context, and the UE can use the bearer attribution type information to select an appropriate IP-CAN bearer according to service requirements.

In this embodiment, after the UE receives the bearer attribution type information, it can also use the bearer attribution type as the address attribution type information of the user terminal IP address, so that when it is necessary to select an IP-CAN bearer, the UE can use the address attribution type information according to service requirements. Type information, select the appropriate IP address, and then select the appropriate IP-CAN bearer in the IP address.

In this embodiment, the UE may also directly save the received address attribution type information together with the IP address assigned to the user terminal.

Step 108: the UE sends a radio resource connection response to the eNB.

Step 109: the eNB sends a radio bearer request response to the MME.

Step 110: MME sends a default bearer establishment response to IASA.

If the bearer attribution type information is not carried in step 103, the bearer attribution type information may be included in the default bearer establishment response sent by the MME to the IASA.

Step 111: the MME sends an attach receive message to the UE through the eNB.

Step 112: the UE sends an attach complete message to the MME through the eNB.

This embodiment can also be implemented under other network architectures, such as the integration of the MME and the UPE, or the separation of the MME and the UPE, and the session management is implemented under the network architecture completed in the UPE. If the MME is separated from the UPE, but the session management is completed in the UPE, the bearer attribution type information needs to be brought to the UE in the radio bearer request message initiated by the UPE. In addition, in addition to the bearer attribution type information carried in the radio bearer request message, other messages sent to the UE may also be used, for example, the bearer attribution type information is carried in the attach receive message.

In addition, the address attribution type information of the IP address of the user terminal can also be obtained directly without the attribution type of the bearer. When the UE establishes the first bearer of the IP-CAN session, the gateway will assign an IP address to the UE. Therefore, in step In 103, the address attribution type information should be generated according to the gateway address that allocates the IP address of the user terminal or according to a preset address attribution policy. According to the gateway address of distributing user terminal IP address, the method for generating address attribution type information is: obtain the gateway address of distributing user terminal IP address; Judge whether the gateway address of distributing user terminal IP address obtained is the address of local network, if yes, Then the bearer of the IP address is the bearer of the local network, and the generated address attribution type information is the local network; otherwise, the generated address attribution type information is the remote network. Step 107 should be the storage address attribution type, and the bearer attribution type in other steps should be the address attribution type.

The generated address attribution type and the allocated IP address may also be included in the attach receiving message in step 111 . At this time, after receiving the message, the UE needs to add a step of saving the received IP address and address attribution type. So that when an IP-CAN bearer needs to be selected, the UE can use address attribution type information to select an appropriate IP address according to service requirements, and then select an appropriate IP-CAN bearer in the IP address.

Embodiment two:

This embodiment takes the establishment process of the dedicated IP-CAN bearer in the SAE network as an example to illustrate the method for the UE to obtain the attribution type information of the dedicated IP-CAN bearer. -Schematic diagram of the method flow of the attribution type information carried by CAN, see Figure 2, MME and UPE are jointly set as MME/UPE entities, in this embodiment, during the establishment process of proprietary IP-CAN bearer initiated by the network side, MME/UPE will bear the bearer The attribution type information is sent to the UE through a radio bearer request message. Since the dedicated bearer establishment procedure initiated by the network side is established under the condition that an IP address has been allocated to the UE, that is, the UE has established at least one bearer for the IP address. Therefore, the method for obtaining the bearer attribution class information of the newly created IP-CAN bearer is: according to the IP address allocated by the UE, search for the bearer established by the IP address, and use the bearer attribution type information of the established bearer of the IP address as the bearer attribution of the newly created bearer type information. After receiving the bearer attribution type information, use the attribution type information as the address attribution type information of the IP address of the user terminal. Referring to Figure 2, the specific steps include:

Step 201: IASA sends a bearer establishment request to MME/UPE.

In this embodiment, according to the IP address allocated by the UE, the IASA finds the bearer that has been established with the IP address, and uses the bearer with the IP address as the obtained bearer attribution type information, and includes it in the bearer establishment request message sent by the IASA. to MME.

Step 202: the MME/UPE sends a radio bearer request to the eNB.

In this embodiment, the MME/UPE sends a wireless IP-CAN bearer request carrying bearer attribution type information to the eNB. Bearer attribution type information is an enumerated value. If the value is 0, it means that the IP-CAN bearer belongs to the local network; if the value is 1, it means that the IP-CAN bearer belongs to the remote network; if the value is 2, it means other information.

Step 203: the eNB sends a radio resource connection request to the UE.

In this embodiment, the eNB sends a radio resource connection request carrying bearer attribution type information to the UE.

Step 204: the UE stores bearer attribution type information.

In this embodiment, the UE directly saves the bearer attribution type information together with the IP-CAN bearer context, and the UE can use the bearer attribution type information to select an appropriate IP-CAN bearer according to service requirements.

In this embodiment, after the UE receives the bearer attribution type information, it can save the attribution type information value in the address attribution type information of the IP address, so that when the IP-CAN bearer is required, the UE can use the address attribution type according to service requirements. Information, select the appropriate IP address, and then select the appropriate IP-CAN bearer in the IP address.

Step 205: UE sends a radio resource connection response to eNB.

Step 206: the eNB sends a radio bearer request response to the MME.

Step 207: The MME/UPE sends a resource request response to the IASA.

In this embodiment, the IASA on the network side obtains the bearer attribution type of the bearer according to the IP address of the UE, and the UE obtains the bearer attribution type information by analyzing the message carrying the bearer attribution type information sent by the MME/UPE. Of course, the UE can also obtain the bearer attribution type information according to The IP address of the UE obtains the bearer attribution type information of the bearer, and other network entities, such as the gateway, can also find the bearer that has been established with the IP address according to the IP address allocated by the UE, and use the bearer that has been established with the IP address as The obtained bearer attribution type information. In this embodiment, no processing is performed in step 201. After the MME receives the resource request message in step 201, it generates the bearer attribution type. The bearer attribution type of the bearer is used as the generated bearer attribution type information.

If the proprietary IP-CAN bearer process initiated by the UE is supported, the bearer attribution type information can also be sent to the eNB through the radio resource request message sent by the MME/UPE to the eNB, and then sent through the radio resource connection request message sent by the eNB to the UE to UE. The processing flow is similar.

Of course, it is not ruled out that the MME/UPE uses other messages sent to the UE to carry bearer attribution type information during the establishment of the IP-CAN bearer.

Embodiment three:

This embodiment takes the establishment of the IP-CAN bearer of the GPRS network as an example to illustrate, and Fig. 3 is a schematic flow diagram of the method for obtaining the attribution type information of the IP-CAN bearer by the GPRS network in the third embodiment of the present invention, referring to Fig. 3, general grouping The wireless service support node (SGSN, Serving GPRSSupporting Node) is used to realize functions such as route forwarding, mobility management, session management, and user information storage, and the gateway general packet wireless service support node (GGSN, Gateway GPRSSupporting Node) is the GPRS network and the external network The gateway is also responsible for the transmission of user plane data.

When the MS needs to perform services, it first initiates a packet data protocol (PDP, Packet Data Protocol) activation process to establish a PDP context. The bearer attribution type information is carried in the activation PDP context response message sent by the SGSN to the MS to mark whether the PDP bearer belongs to the local network or the remote network. Except that the IMS emergency service must be completed in the local network (when the MS is roaming, it is the visiting location, otherwise it is the home location), for other IMS services, it is necessary to consider whether to use the route optimization function according to the routing policy. The specific steps shown in Figure 3 are as follows:

Step 301: MS sends a PDP context activation request to SGSN through RNC.

Step 302: the SGSN authenticates the MS.

Step 303: SGSN sends a PDP context establishment request to GGSN.

Step 304: The GGSN sends a PDP context establishment response to the SGSN.

Step 305: Establish a radio access bearer between the SGSN and the MS.

Step 306: The SGSN sends a PDP context update request to the GGSN.

Step 307: The GGSN sends an update PDP context response to the SGSN.

Step 308: The SGSN sends an activation PDP context response to the MS through the RNC.

In this embodiment, the SGSN sends an activation PDP context response carrying bearer attribution type information to the MS through the RNC. The session management module in the SGSN produces bearer attribution type information, and the method that it produces is similar to that in embodiment one, promptly obtains the gateway address that IP-CAN bears the weight of, is GGSN address in the present embodiment; Whether the GGSN address is the address of the local network, if yes, the IP-CAN bearer is the bearer of the local network, and the generated bearer attribution type information is the local network; otherwise, the generated bearer attribution type information is the remote network. In this embodiment, the method for the SGSN to obtain the GGSN address is: the SGSN obtains a message carrying an Access Point Name (APN, Access Point Name), and performs DNS resolution according to the APN to obtain the GGSN address. It is judged whether the bearer belongs to the local network or the remote network according to whether the GGSN is the address of the local network, that is, if the GGSN belongs to the local network, the bearer is the local network; otherwise, the bearer is the remote network.

Bearer attribution type information is a special data that can be used for judgment. It can be used to represent the mobile network number + mobile country number (MNC+MCC, Mobile Network) in the information of a public land mobile phone network (PLMN, Public Land Mobile Network) Code/Mobile CountryCode), other information can also be added as needed.

Step 309: the MS saves the bearer attribution type information.

In this embodiment, the MS directly saves the bearer attribution type information together with the IP-CAN bearer context, and the MS can use the bearer attribution type information to select an appropriate IP-CAN bearer according to service requirements.

In this embodiment, after the MS receives the bearer attribution type information, the attribution type information value can be stored in the address attribution type information of the IP address, and the MS can use the address attribution type information to select a suitable IP address according to service requirements. , and then select the appropriate IP-CAN bearer in the IP address.

In this embodiment, the address attribution type information of the UE's IP address may be carried in step 308, and then in step 309, the UE may directly store the received address attribution type information and the UE's IP address together.

This embodiment provides a method for carrying bearer attribution type information in the processing flow of PDP activation in Iu mode. If in the processing flow of PDP activation in A/Gb mode, the bearer is also carried in the activation PDP context response message sent by the SGSN to the MS. For the attribution type information, only step 303 is changed to: the packet data context process is performed between the BSS and the SGSN.

If this embodiment is an IP-CAN bearer establishment process initiated by the network side, the SGSN will first send a PDP context establishment request message to the MS. After receiving the message, the MS completes the PDP context according to the IP-CAN bearer establishment process initiated by the MS. The establishment of the context, the remaining steps can be the same as step 302-step 309, that is, the SGSN can send the activation PDP context response message to the MS to carry the bearer attribution type information indicating whether the IP-CAN bearer belongs to the local network or the remote network, if In the case that the user terminal has been assigned an IP address, the method for obtaining bearer attribution type information according to the IP address adopted in the second embodiment may also be followed.

By analyzing the steps of Embodiments 1, 2 and 3 of the present invention, it can be seen that when the user terminal establishes the first bearer of the IP-CAN session, the gateway will assign an IP address to the user terminal, and set up an IP address in the bearer establishment response message. The user terminal will also use the bearer attribution type obtained during the bearer establishment process to mark the attribution type of the IP address. When a user terminal performs services, it usually selects an IP address that meets the requirements of the attribution type according to the service requirements, and then selects a suitable bearer according to the IP address, or establishes a new bearer to complete the service.

The bearer attribution type information can be sent to the UE or the network side during the establishment of each IP-CAN bearer, so the UE or the network side can obtain the bearer attribution type information of each IP-CAN bearer. It is also possible to only pass the bearer attribution type information to the UE in the first bearer establishment process of each IP-CAN session, and when other bearers of the IP-CAN session are established, all bearer contexts in the IP-CAN session share The same context IP address also shares the same bearer attribution type information and bearer location information.

When the UE or the network side needs to use the IP-CAN bearer for business, the UE or the network side will select the IP-CAN bearer according to the obtained bearer attribution type information. Embodiment 4, Embodiment 5 and Embodiment 6 give the UE Or the three application scenarios where the network side uses the acquired attribution type information to select the bearer for business, namely: when the UE cannot identify the IMS emergency service, use the acquired attribution type information to realize the IP-CAN bearer selection process; the UE can identify the IMS emergency service During service, use the obtained attribution type information to realize the process of IP-CAN bearer selection and when the UE is in the visited location, for non-emergency services that support the route optimization function, use the obtained attribution type information to realize the process of IP-CAN bearer selection.

Embodiment four:

Fig. 4 is a schematic flowchart of a method for obtaining an IP-CAN bearer by using attribution type information in a fourth embodiment of the present invention. In this embodiment, assuming that the UE cannot identify the IMS emergency service, when the UE needs to use the IMS service, the UE will randomly select the IP-CAN bearer after normally registering with the IMS system, and initiate a normal IMS session establishment request message to the local network The P-CSCF of the remote network or the P-CSCF of the remote network. When the UE just selects the IP-CAN bearer of the local network, according to the existing technology, the P-CSCF of the local network transfers the emergency service request to the E-CSCF of the local network for processing, which will not be repeated here. If the UE selects the IP-CAN bearer of the remote network, step 401 to step 409 are performed.

Step 401: UE sends an IMS session establishment request to a remote P-CSCF.

Step 402: The remote P-CSCF detects that the IMS session establishment request is for an emergency service.

Step 403: the remote P-CSCF sends a request message of denying IMS session establishment to the UE.

Because the IMS emergency service must be completed in the local network, that is, if the UE is in the roaming state, the IMS emergency service can only be performed in the visited location, so the P-CSCF in the home location rejects the session establishment request of the UE and notifies the UE to initiate an emergency call in the local network. business request.

Step 404: The UE judges whether there is an available IP-CAN bearer in the local network, and if so, selects the existing local network IP-CAN bearer as the IP-CAN bearer for sending the IMS emergency session request, and performs step 406; otherwise, executes step 405.

In this embodiment, the UE judges whether there is a local network IP-CAN bearer for transmitting IMS-related signaling by using the stored bearer attribution type information. In this embodiment, any one of the methods provided in Embodiments 1, 2 and 3 or any combination of the three methods may be used to obtain and save bearer attribution type information.

In this embodiment, the UE may also use the saved address attribution type information of the user terminal IP address to determine whether there is a user terminal IP address whose address attribution type meets the requirements of the bearer home network, and if so, select an IP address that meets the requirements of the bearer home network. After the address, select an IP-CAN bearer according to the IP address, otherwise, create a new IP-CAN bearer that meets the requirements of the bearer's home network.

Step 405: The UE initiates an IMS emergency bearer establishment procedure.

In this embodiment, the UE establishes an IP-CAN bearer dedicated to transmitting an IMS emergency session request by initiating an IMS emergency bearer establishment process.

Step 406: UE initiates IMS emergency registration.

If the UE has already registered in the local IMS network, this step does not need to be performed.

In this embodiment, the UE uses the local bearer to perform IMS emergency registration.

Step 407: the UE sends an IMS emergency session request to the P-CSCF of the local network.

In this embodiment, when there is a local network IP-CAN bearer for transmitting IMS-related signaling, the UE uses the existing IP-CAN bearer, and when there is no local network IP-CAN bearer, uses the newly created IMS emergency The IP-CAN bearer of the session request sends the IMS emergency session request to the P-CSCF of the local network.

In this embodiment, after step 407 is executed, the P-CSCF of the local network transfers the emergency service request to the local E-CSCF, and the local E-CSCF further processes the emergency service.

In this embodiment, the UE uses the attribution type information to preferentially select the existing IP-CAN bearer of the local network, which can make full use of the existing IP-CAN bearer resources, reduce the delay of signaling or data transmission, and improve user experience.

Embodiment five:

Fig. 5 is a schematic flowchart of a method for obtaining an IP-CAN bearer by using attribution type information in a fifth embodiment of the present invention. In this embodiment, it is assumed that the UE can recognize that the IMS emergency service is initiated, and when the UE needs to use the IMS service, step 501-step 505 are performed.

Step 501: UE judges whether there is an available IP-CAN bearer in the local network, and if yes, executes step 503; otherwise, executes step 502.

The UE uses the attribution type information to judge whether there is an IP-CAN bearer in the local network that meets the attribution requirements of the bearer network. If it exists, it directly selects an existing IP-CAN bearer in the local network that can be used to transmit IMS-related signaling as the bearer according to the attribution type information. IP-CAN bearer for sending IMS emergency session request.

In this embodiment, the UE judges whether there is an IP-CAN bearer of the local network by using the stored bearer attribution type information. In this embodiment, any one of the methods provided in Embodiments 1, 2 and 3 or any combination of the three methods may be used to obtain and save bearer attribution type information.

In this embodiment, the UE may also use the saved address attribution type information of the user terminal IP address to determine whether there is a user terminal IP address whose address attribution type meets the requirements of the bearer home network, and if so, select an IP address that meets the requirements of the bearer home network Finally, select an IP-CAN bearer according to the IP address, otherwise, create a new IP-CAN bearer that meets the requirements of the bearer's home network.

Step 502: UE initiates an IMS emergency IP-CAN bearer establishment procedure.

In this embodiment, the UE establishes an IP-CAN bearer dedicated to transmitting an IMS emergency session request by initiating an IMS emergency IP-CAN bearer establishment process.

Step 503: UE initiates IMS emergency registration.

If the UE has already registered in the local IMS network, this step does not need to be performed.

In this embodiment, the UE initiates an IMS emergency registration by using an existing IP-CAN bearer in the local network that can transmit IMS signaling or a newly created IP-CAN bearer dedicated to transmitting an IMS emergency session request.

Step 504: UE sends the IMS emergency session request to the P-CSCF of the local network.

In this embodiment, when there is a local network IP-CAN bearer for transmitting IMS-related signaling, the UE uses the existing IP-CAN bearer, and when there is no local network IP-CAN bearer, uses the newly created IMS emergency The IP-CAN bearer of the session request sends the IMS emergency session request to the P-CSCF of the local network.

In this embodiment, after step 504 is executed, the P-CSCF of the local network transfers the emergency service request to the E-CSCF, and the E-CSCF further processes the emergency service.

Embodiment six:

Fig. 6 is a schematic flowchart of a method for obtaining an IP-CAN bearer by using attribution type information in the sixth embodiment of the present invention. In this embodiment, it is assumed that the MS can judge whether the service needs the route optimization function. The judging method includes: after the MS registers to the IP-CAN bearer network, the MS can obtain a service list, and the list includes whether the service needs to be route optimized. In this embodiment, it is assumed that a service needs to perform a route optimization function, and the service is required to be performed on a local network. When the MS uses the IMS service, step 601 is executed.

Step 601: Obtain a suitable IP-CAN bearer according to the attribution type information.

In this embodiment, if the MS is in the home location, all IP-CAN bearers established by the MS will have the IP-CAN bearer type as the local network. Therefore, the service initiated by the MS can directly transmit the IMS service without judging the bearer attribution type information. session request.

If there is a local network bearer, a suitable bearer for transmitting the IMS session request is selected. When it is found that it does not exist, the MS initiates an IMS bearer establishment process to create a new bearer for transmitting the IMS session request.

The MS determines whether the local network has a bearer that can be used to transmit IMS-related signaling according to the attribution type information, and if so, selects a suitable bearer for transmitting the IMS session request. When it is found that it does not exist, the MS initiates a bearer establishment process to create a new bearer for transmitting the IMS session request. In this embodiment, any one of the methods provided in Embodiments 1, 2 and 3 or any combination of the three methods may be used to obtain and save bearer attribution type information.

In this embodiment, it is required that the currently initiated service request must be executed in the local network. If the MS is in a visited location, the MS selects the IP-CAN bearer for transmitting IMS-related signaling in the local network to transmit the IMS service session request according to the attribution type information.

If this embodiment requires that the currently initiated service request must be returned to the home site for completion, then the MS in the visited site can select the IP-CAN bearer for transmitting IMS-related signaling in the remote network to transmit the IMS service session request according to the home type information .

Step 602: The MS sends an IMS session request to the local P-CSCF.

After receiving the session service request, the P-CSCF of the IMS network will process it through the Serving-Call Session Control Function entity (S-CSCF, Serving-CallSession Control Function) in the IMS network according to the method in the prior art, and forward it to The destination end of the service, and then, after receiving the session response sent by the destination end of the service, the P-CSCF initiates an IP-CAN bearer establishment process required by the network side, and establishes a new IP-CAN bearer to transmit the service.

In this embodiment, when the UE is in a visited location, and there is at least one IP-CAN bearer that can transmit IMS-related signaling in the visited location and the home location, the bearer attribution type information can be used to select an appropriate IP-CAN bearer, In this way, different requirements of different services for IP-CAN bearer can be met, and the routing optimization function can be realized. Of course, it is also possible to use the address attribution type information to select an IP address that meets the requirements of the bearer home network, and then select a suitable bearer based on the IP address. When there is no IP address that meets the bearer home network requirements, a new IP-CAN bearer is established. To complete the IMS business.

In addition to IMS services, other services such as IP telephony (VoIP, Voice over IP), virtual private network (VPN, Virtual Private Network), Internet (Internet), etc. are similar to IMS services. Taking Internet services as an example, if UE When roaming, the UE initiates an Internet service request. If the service needs to be completed in the visited place, the UE selects an IP address whose attribution type is the local network, and selects a bearer that can transmit Internet service data to transmit data according to the IP address; If there is no IP address whose attribution type is the local network, the UE will initiate a bearer establishment request to the visited location, obtain an IP address of the visited location, and establish a bearer capable of Internet service data to transmit data.

In addition, when the UE switches between the visited location and the home location, the existing bearer connected to the original PLMN must be transferred to the new PLMN. Therefore, the attribution type information stored on the UE or the network side needs to be Update, when the UE arrives at a PLMN and restarts, the UE will initiate an attach process in the new PLMN, rebuild the IP-CAN bearer context, and reacquire new attribution type information. The processing steps are as in the first, second or third of the present invention The steps shown in the examples are similar.

However, when the UE is switched on and moves from one PLMN to another, or when roaming within the same PLMN occurs, handover processing is required. If the UE is in service, it needs to update the attribution type information for the currently activated IP-CAN bearer. Embodiments 7 to 8 give an example of a method for updating the stored attribution type information when the user terminal switches between the visited location and the home location, where the attribution type information is bearer attribution type information or address attribution type information.

Embodiment seven

This embodiment provides that when the user terminal switches between the visited location and the home location, the user terminal initiates a process of updating the stored attribution type information after the switching process is completed. In this embodiment, when the UE acquires the attribution type information during the establishment of the IP-CAN bearer, it also acquires and stores the bearer location information where the IP-CAN bearer is established, and the bearer location information may be PLMN information. The method of obtaining and storing the bearer location information when the IP-CAN bearer is established is: when the attribution type information is a local network, the stored bearer location information is the same as the location information of the MME; when the attribution type information is a remote network , according to the identifier of the UE, such as the International Mobile Station Identification Number (IMSI, International Mobile Station Identify), the home bearer location information of the UE is obtained as the bearer location information of the IP-CAN bearer.

In this way, after the UE switches between the visited location and the home location, it obtains the bearer location information where the IP-CAN bearer is currently located, and compares the bearer location information where the IP-CAN bearer is located when it is established with the bearer location information after switching. Comparison, if the comparison result is the same, update the attribution type information corresponding to the IP-CAN bearer to the local network, otherwise, update the attribution type information corresponding to the IP-CAN bearer to the remote network. For example, when the UE moves between different PLMNs, it only needs to update the attribution type information of the IP-CAN bearer according to the current PLMN information and the stored bearer location information when the IP-CAN bearer is established.

This embodiment takes the specific steps of the SAE network as an example:

Firstly: the UE receives a signaling message including new PLMN information from the evolved RAN after the handover.

For the UE, after the handover process is completed, it will receive a message including PLMN information sent by the evolved RAN, such as MNC+MCC in the RAI.

Next, the UE updates the attribution type information according to the stored PLMN information and the comparison result of the received PLMN information.

The UE checks the received PLMN information and compares it with the PLMN information when each IP-CAN bearer is established in the UE. If the PLMN information when the IP-CAN bearer is established is the same as the current PLMN information, the IP-CAN The attribution type information carried by the IP-CAN is updated to the local network, otherwise, the attribution type information carried by the IP-CAN is updated to the remote network.

Of course, if the representation method of the third embodiment is used for the attribution type information, that is, when the affiliation type information is represented by bearer location information, for example, when it is represented by PLMN information, then when UE handover occurs, it is not necessary to perform the attribution type information It is judged by update processing. The UE can save the PLMN information of the current network, so when selecting the IP-CAN bearer, it can judge which belongs to the local network and which belongs to the remote network by comparing the value of each attribution type information with the current network PLMN information.

Embodiment eight

When UE switches between visiting location and home location, the network side needs to perform user plane switching and routing area update process. The entity MME or UPE where the SM is located, or SGSN will initiate the context update process to the gateway device, such as gateway or GGSN, Complete the update of the relevant information of the user plane on the gateway, for example, complete the update of the address information of the device where the current SM is located and the identification of the context.

Fig. 7 is a schematic flow diagram of the method for updating the attribution type information in the eighth embodiment of the present invention. This embodiment provides the user plane handover in the GPRS network, and the PDP context update process initiated by the entity SGSN where the SM is located, so as to realize the The update of the established attribution type information, as shown in Figure 7, specifically includes the following steps:

Step 701: The source RNC (source RNC) decides to perform SRNS relocation

Step 702: the source RNC sends a relocation request to the old SGSN (Old SGSN).

Step 703: The old SGSN forwards the relocation request to the new SGSN (New SGSN).

Step 704: The new SGSN sends a relocation request to the target RNC (Target SGSN).

Step 705: The target RNC returns a relocation request response to the new SGSN.

In this embodiment, after the radio bearer is established between the new SGSN and the target RNC, the target RNC returns a relocation request response to the new SGSN.

Step 706: The new SGSN forwards the relocation request response to the old SGSN.

Step 707: The old SGSN sends a relocation command to the source RNC.

Step 708: the source RNC sends data to the target RNC.

Step 709: the source RNC sends a relocation confirmation to the target RNC.

Step 710: The target RNC sends a relocation detection to the new SGSN.

Step 711: the target RNC sends RAN mobility information to the MS.

Step 712: The MS sends a RAN mobile information confirmation to the target RNC.

Step 713: the target RNC sends a relocation complete message to the new SGSN.

Step 714: The new SGSN forwards the relocation complete message to the old SGSN.

Step 715: the old SGSN sends a relocation complete message response to the new SGSN.

Step 716: Determine whether the stored attribution type information needs to be modified, if yes, carry the modified attribution type information when executing step 717, otherwise, execute step 717 without carrying the modified attribution type information.

In this embodiment, the new SGSN judges whether the attribution type of the established IP-CAN bearer needs to be modified by comparing the PLMN location of the current user with the saved location information in the PDP context.

In order to meet the above processing, it is required that the entity where the PDP context exists (such as the UE, the MME or UPE where the SM resides, the gateway device such as GGSN or Anchor, etc.) retains the attribution type information, and at the same time, the MME or UPE where the SM resides The bearer location information of the context is reserved in the PDP context, and the bearer location information may be a PLMN number. When the attribution type information is obtained during the establishment of the IP-CAN bearer, the bearer location information when the IP-CAN bearer is established is obtained and stored at the same time. The method for obtaining and storing the bearer location information when the IP-CAN bearer is established is : When the attribution type information is a local network, the stored bearer location information is the same as the location information of the MME; when the attribution type information is a remote network, obtain the UE's home bearer location information according to the UE's identity, such as IMSI, as The location information of the bearer. In this way, when the UE switches between the visited site and the home site (Inter-PLMN/Intra-PLMN), the network side can initiate a process of modifying the home type information. As shown in Table 1.

UE SM (MME, UPE, SGSN) GGSN, SAE anchor, 3GPP anchor Attribution Type Information x x x bearer location information x

Table 1

Step 717: The new SGSN sends a PDP context update request to the GGSN.

In this embodiment, the new SGSN sends an update PDP context request carrying the modified attribution type information to the GGSN.

Step 718: The GGSN sends an update PDP context request response to the new SGSN.

Steps 719 to 720 are optional steps, which are executed when the affiliation type information stored in the MS needs to be modified.

Step 719: The new SGSN sends a PDP context update request to the MS.

In this embodiment, the new SGSN sends an update PDP context request carrying the modified attribution type information to the MS.

Step 720: The MS sends an update PDP context request response to the new SGSN.

If in this embodiment, the PDP context update process initiated by the gateway is notified by the entity SGSN where the SM is located, then after step 718 is executed, the GGSN judges whether to modify the step of the attribution type information. The method for judging is: the GGSN checks the If the attribution type information is inconsistent with the locally saved information, it is determined that the attribution type information needs to be modified. If the attribution type information is not included in the received context update message, the value is not checked.

After judging that the attribution type information needs to be modified, the GGSN initiates a PDP context modification process, and modifies the attribution type information stored in the UE to the latest value. That is, the GGSN sends the update PDP context request carrying the modified attribution type information to the new SGSN, and the new SGSN forwards the update PDP context request carrying the modified attribution type information to the MS.

Step 721: The old SGSN sends an Iu bearer release command to the source RNC.

Step 722: The source RNC sends an Iu bearer release complete message to the old SGSN.

After this step is executed, the user plane handover process is completed, and the network side will continue to update the routing area.

Embodiment nine

Fig. 8 is a schematic flowchart of a method for updating attribution type information in the ninth embodiment of the present invention. This embodiment shows that when the GPRS network performs user plane handover, the attribution type information is not updated, but in the routing area update process of the user, the stored attribution type information is updated, see Figure 8, the attribution location The user's subscription information is saved in the register (HLR, Home Location Register). Fig. 8 is that the entity SGSN where the SM is located notifies the gateway to initiate the PDP context update process, which specifically includes the following steps:

Step 801: MS sends a routing area update request to the new SGSN.

Step 802: Authentication is performed between the MS and the HLR.

Step 803: The new SGSN judges whether the attribution type of the established IP-CAN bearer needs to be modified, if so, execute step 804, otherwise, directly execute step 811.

In this embodiment, the new SGSN first compares the current bearer location information with the bearer location information retained in the bearer context at the time of establishment, and if the comparison results are the same, the attribution type information corresponding to the IP-CAN bearer is updated to the local network , otherwise, update the attribution type information corresponding to the IP-CAN bearer to the remote network. If the updated type attribution is inconsistent with the locally saved one, it is determined that the attribution type information needs to be modified, and step 804 needs to be executed; otherwise, step 811 is executed.

Step 804: The new SGSN sends a PDP context update request to the GGSN.

In this embodiment, the new SGSN sends an update PDP context request carrying the modified attribution type information to the GGSN. The new SGSN includes the modified attribution type information in the context update request message sent to the gateway. Of course, this embodiment may also include the latest attribution type information in the context update request message regardless of whether modification is required.

Step 805: The GGSN sends an update PDP context request response to the new SGSN.

Step 806: The GGSN judges whether to modify the attribution type information.

After receiving the modified attribution type information, the GGSN checks whether the attribution type information is inconsistent with the locally stored one, and if so, modifies the attribution type information stored in the UE to the latest value. Otherwise, go to step 807 directly. If the attribution type information is not included in the received context update message, the value is not checked.

Step 807: The GGSN sends a PDP context update request to the new SGSN.

In this embodiment, the GGSN sends an update PDP context request carrying the modified attribution type information to the new SGSN.

Step 808: The new SGSN sends a PDP context update request to the MS.

In this embodiment, the new SGSN sends an update PDP context request carrying the modified attribution type information to the MS.

Step 809: The MS sends an update PDP context request response to the new SGSN.

In this embodiment, the MS updates the bearer attribution type of the corresponding IP-CAN bearer and the address attribution type of the IP address according to the attribution type information parsed from the update PDP context request response message.

Step 810: The new SGSN sends an update PDP context request response to the GGSN.

Step 811: Perform location update processing between the new SGSN and the HLR.

Step 812: The new SGSN sends a routing area update reception message to the MS.

Step 813: The MS sends a routing area update complete message to the new SGSN.

If in this embodiment, the entity SGSN where the SM resides initiates the PDP context update process, then step 808 is directly executed after step 805 is executed.

In this embodiment, step 803-step 810 may also be performed after step 811 is completed.

Embodiment ten

FIG. 9 is a schematic structural diagram of a system for obtaining an IP-CAN bearer provided by an embodiment of the present invention. The system includes an acquisition module 920 and an execution module 930;

The acquisition module 920 acquires the attribution type information corresponding to the IP-CAN bearer attribution network, and sends the acquired attribution type information to the execution module 930;

The execution module 930 obtains the IP-CAN bearer that meets the requirements of the bearer's home network by using the attribution type information input by the acquisition module 920 .

The system also includes an attribution type generation module 910 ; the attribution type generation module 910 generates attribution type information when the user terminal establishes a bearer, and sends the attribution type information to the acquisition module 920 .

The system also includes an update module 940; the update module 940 updates or judges the attribution type information obtained in the acquisition module 920 when the user terminal switches between the visited place and the home place.

When the attribution type information is sent to the acquisition module 920 through a message carrying the attribution type information, the acquisition module 920 includes an input unit 921 and an analysis unit 922;

The input unit 921 is configured to receive a message carrying bearer attribution type or address attribution type information, and send the received message carrying bearer attribution type or address attribution type information to the parsing unit 922;

The parsing unit 922 is configured to parse the message carrying the bearer attribution type information or the address attribution type sent by the input unit 921 to obtain the attribution type information corresponding to the IP-CAN bearer attribution network.

In this embodiment, when the user terminal is assigned an IP address, the obtaining module 920 includes a storage unit and a determination unit;

The storage unit is configured to store the bearer attribution type of the bearer of the user terminal IP address or the address attribution type of the user terminal IP address;

The determination unit uses the stored bearer attribution type of the user terminal IP address that has established a bearer as the address attribution type or bearer attribution type of the user terminal IP address, or uses the stored address attribution type of the user terminal IP address as the bearer attribution type, and will determine The attribution type information is input to the execution module.

The execution module 930 includes a judgment unit 931 and an execution unit 932;

The judging unit is used to determine whether there is currently an IP-CAN bearer or user terminal IP address whose address attribution type meets the requirements of the bearer home network according to the service requirements for the bearer home network and the attribution type information input by the acquisition module, and input the result of the judgment to the execution unit;

The execution unit is used to select an IP-CAN bearer that meets the requirements of the bearer home network when the judgment result input by the judgment unit is that there is an IP-CAN bearer that meets the requirements of the bearer home network, and when the judgment result input by the judgment unit is that there is an IP-CAN bearer that meets the bearer home network requirements When the IP address of the user terminal required by the home network is selected, an IP-CAN bearer is selected according to the IP address; otherwise, an IP-CAN bearer that meets the requirements of the bearer home network is created.

The attribution type generation module 910 includes an address acquisition unit 912 and a generation unit 911;

The address obtaining unit 912 obtains the gateway address carried by the IP-CAN or the gateway address assigned to the user IP address, and sends the obtained gateway address to the generating unit 911;

The generation unit 911 judges whether the gateway address input by the address acquisition unit 912 is the address of the local network, if yes, the generated attribution type information is the bearer of the local network, otherwise, the generated attribution type information is the remote network.

The update module 940 includes a bearer location acquisition unit 941 and a bearer location comparison unit 942;

The bearer position acquisition unit 941 acquires and stores the bearer position information when the IP-CAN bearer is established; The bearer position information during establishment and after switching is input to the bearer position comparison unit 942;

The bearer position comparison unit 942 compares the set-up of the bearer position information input with the bearer position information after switching, and if the comparison result is the same, the attribution type information corresponding to the IP-CAN bearer is updated to the local network; The attribution type information corresponding to the IP-CAN bearer is updated to the remote network.

The attribution type generating module 910 can be set in the MME, UPE, an entity jointly established by the MME and the UPE in the SAE network, or in the SGSN entity in the GPRS network.

The obtaining module 920 may be set in a user terminal, a gateway or a GGSN.

The execution module 930 may be set in a user terminal, a gateway or a GGSN.

The update module 940 can be set in the MME, UPE, an entity jointly established by the MME and the UPE in the SAE network, or in the SGSN entity in the GPRS network.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims (29)

1. one kind obtains the method that IP connection access network IP-CAN carries; It is characterized in that; This method comprises: obtain with IP-CAN and carry the corresponding home type information of home network, utilize the home type information of obtaining, be met the IP-CAN that carries the home network requirement and carry.

2. method according to claim 1 is characterized in that, the said method of obtaining home type information comprises: carry the message of home type information through parsing, obtain and IP-CAN carries the corresponding home type information of home network.

3. method according to claim 2; It is characterized in that said message of carrying home type information comprises: the wireless IP-CAN in the IP-CAN loading establishing process carries and sets up request message, adheres to and receive message, or the activation packet data protocol PDP Context response message in the packet data protocol pdp context activation.

4. method according to claim 1; It is characterized in that; Said home type information is for characterizing the carrying home type information that IP-CAN carries home network; When user terminal had distributed the IP address, the said method of obtaining home type information comprised: according to the user terminal IP address allocated, search the carrying home type that this IP address has been set up carrying; The carrying home type of this IP address having been set up carrying is as the carrying home type information of obtaining, perhaps with the address home type of this IP address as the carrying home type information of obtaining.

5. method according to claim 1; It is characterized in that; Said home type information is for characterizing the address home type information of user terminal IP address home network; When user terminal had distributed the IP address and used the newly-built carrying in this IP address, the said method of obtaining home type information comprised: with the carrying home type of the newly-built carrying address home type information as this IP address.

6. method according to claim 1; It is characterized in that said home type information is for carrying home type, the home type information that said utilization is obtained; Being met the method that the IP-CAN that carries the home network requirement carries comprises: the carrying home type information of the requirement of carrying home network and the IP-CAN that obtains being carried according to business; Judge that the current IP-CAN that satisfies the requirement of carrying home network that whether exists carries, if select an IP-CAN to carry; Otherwise, a newly-built IP-CAN carrying of satisfying to carry the home network requirement.

7. method according to claim 1 is characterized in that, said home type information is the address home type, the home type information that said utilization is obtained, and the method that is met the IP-CAN carrying of carrying the home network requirement comprises:

According to the address home type information of business to the requirement of carrying home network and the user terminal IP address that obtains; Judge whether to exist the address home type to satisfy the user terminal IP address that carries the home network requirement; If after selecting to satisfy the IP address of carrying the home network requirement, an IP-CAN carries according to this IP address choice; Otherwise, a newly-built IP-CAN carrying of satisfying to carry the home network requirement.

8. method according to claim 1 is characterized in that, before the said step of obtaining home type information, this method further comprises: produce home type information.

9. method according to claim 8; It is characterized in that; Said home type information is for carrying home type; The method of said generation home type information comprises: the gateway address that carries according to the IP-CAN that obtains perhaps belongs to strategy according to the carrying that is provided with in advance, and home type information is carried in generation.

10. method according to claim 9 is characterized in that, the gateway address that the IP-CAN that said basis is obtained carries produces the method for carrying home type information and comprises: obtains the gateway address that IP-CAN carries; Whether the gateway address of judging the IP-CAN carrying of obtaining is the address of local network; If then this IP-CAN is carried as the carrying of local network, the carrying home type information of generation is local network; Otherwise the carrying home type information of generation is far-end network.

11. method according to claim 8 is characterized in that, said home type information is the address home type, and the method for said generation home type information comprises:

According to the gateway address of distributing user IP address of terminal or according to the address ownership strategy that is provided with in advance, produce address home type information.

12. method according to claim 11 is characterized in that, said gateway address according to the distributing user IP address of terminal, and the method that produces address home type information comprises: the gateway address that obtains the distributing user IP address of terminal; Whether the gateway address of judging the distributing user IP address of terminal that obtains is the address of local network; If, the then carrying that is carried as local network of this IP address, the address home type information of generation is local network; Otherwise the address home type information of generation is far-end network.

13. according to claim 1 or 8 described methods; It is characterized in that; When the switching between visit ground and the ownership place takes place in user terminal; Before the step that home type Information Selection IP-CAN that utilization is obtained carries, this method further comprises: the home type information of obtaining is upgraded or judged.

14. method according to claim 13 is characterized in that, saidly the home type information of obtaining is carried out method for updating comprises:

Obtain and storing IP-residing carrying positional information when CAN carrying is set up; After the switching that takes place between visit ground and ownership place; Obtain IP-CAN and carry present located carrying positional information; IP-CAN is carried when setting up the carrying positional information after the residing carrying positional information and switching compare, if comparative result is identical, then will carry corresponding home type information updating with IP-CAN is local network; Otherwise will carry corresponding home type information updating with IP-CAN is far-end network.

15. method according to claim 14 is characterized in that, the method that said obtain and storing IP-CAN carries residing carrying positional information when setting up comprises:

When the angelica type information was local network, the carrying positional information of storage was identical with the positional information at MME place; When the angelica type information was far-end network, according to the sign of UE, the ownership of obtaining this UE was carried positional information, as the positional information of this carrying.

16., it is characterized in that said carrying positional information comprises public land mobile network PLMN positional information according to claim 14 or 15 described methods.

17. method according to claim 13 is characterized in that, when home type information was represented to carry the positional information form, the said method that the home type information of obtaining is judged comprised:

Carrying positional information after switching preceding home type information and switching is compared,, judge that then carrying corresponding home type information with IP-CAN is local network if comparative result is identical, otherwise, be far-end network.

18. one kind obtains the system that IP-CAN carries, it is characterized in that this system comprises acquisition module and Executive Module;

Described acquisition module is used to obtain with IP-CAN and carries the corresponding home type information of home network, and the home type information of obtaining is sent to Executive Module;

Described Executive Module is used to utilize the home type information from acquisition module that receives, and is met the IP-CAN that carries the home network requirement and carries.

19. system according to claim 18 is characterized in that, said home type information is to send to acquisition module through the message of carrying home type information, and said acquisition module comprises input unit and resolution unit;

Described input unit is used to receive the message of carrying home type information, and the message of carrying home type information that receives is sent to resolution unit;

Described resolution unit is used for the message of carrying home type information that input unit sends, and obtains with IP-CAN and carries the corresponding home type information of home network.

20. system according to claim 18 is characterized in that, described acquisition module comprises memory cell and definite unit;

Described memory cell is used to store user terminal IP address and has set up the carrying home type of carrying or the address home type of user terminal IP address;

Described definite unit; Be used for user terminals stored IP address has been set up address home type or the carrying home type of the carrying home type of carrying as user terminal IP address; Perhaps with the address home type of user terminals stored IP address as carrying home type, the home type of confirming is sent to Executive Module.

21., it is characterized in that described acquisition module is arranged among user terminal, gateway or the GGSN according to claim 18,19 or 20 described systems.

22. system according to claim 18 is characterized in that, said Executive Module comprises judging unit and performance element;

Described judging unit; Be used for according to the home type information of business the requirement and the acquisition module input of carrying home network; Judge that the current IP-CAN that whether exists the address home type to satisfy the requirement of carrying home network carries or user terminal IP address, is input to performance element with the result who judges;

Described performance element; Be used for when the judged result of judging unit input is carried for the IP-CAN that exists satisfied carrying home network to require; Select an IP-CAN carrying of satisfying to carry the home network requirement; The judged result of importing when judging unit is when having the user terminal IP address that satisfies the requirement of carrying home network, according to IP-CAN carrying of this IP address choice, otherwise a newly-built IP-CAN carrying of satisfying to carry the home network requirement.

23., it is characterized in that described Executive Module is arranged among user terminal, gateway or the GGSN according to claim 18 or 22 described systems.

24. system according to claim 18 is characterized in that, this system further comprises the home type generation module;

Described home type generation module is used to produce home type information, and home type information is sent to acquisition module.

25. system according to claim 24 is characterized in that, said home type generation module comprises address acquisition unit and generation unit;

Described address acquisition unit is used to obtain the gateway address of IP-CAN carrying or the gateway address of distributing user IP address, and the gateway address that obtains is sent to generation unit;

Described generation unit is used to judge whether the gateway address of address acquisition unit input is the address of local network, if the home type information that then produces is the carrying of local network, otherwise the home type information of generation is far-end network.

26., it is characterized in that described home type generation module is arranged on MME, UPE, MME and UPE and closes in the entity of establishing or SGSN according to claim 24 or 25 described systems.

27., it is characterized in that this system further comprises update module according to claim 18 or 24 described systems;

Described update module is used for when the switching between visit ground and the ownership place takes place user terminal, and the home type information of obtaining in the acquisition module is upgraded or judged.

28. system according to claim 27 is characterized in that, described update module comprises: carry the position acquiring unit and carry the position comparing unit;

Described carrying position acquiring unit is used to obtain and storing IP-CAN carries residing carrying positional information when setting up; And after the switching that takes place between visit ground and ownership place, obtain IP-CAN and carry present located and carry positional information, with obtain set up the time with switch after the carrying positional information be input to and carry the position comparing unit;

Described carrying position comparing unit; When being used for carrying the setting up of positional information input with switch the back and carry positional information and compare; If comparative result is identical; Then will carry corresponding home type information updating with IP-CAN is local network, otherwise will carry corresponding home type information updating with IP-CAN is far-end network.

29. system according to claim 27 is characterized in that, described update module is arranged on MME, UPE, MME and UPE and closes in the entity of establishing or SGSN.

Images