A method and system for implementing the data routing of the roaming user

FIELD OF THE INVENTION

0001The invention relates to mobile communication, and more particularly, to a method and system for implementing data routing of a roaming mobile user.

BACKGROUND

0002In order to guarantee that an evolved mobile communication system may satisfy the continuously increasing requirements of users in a long term of future, the ability of possessing rapid increasing IP (Internet Protocol) data service by the evolved mobile communication system should be enhanced, and the employment of packet technology in the mobile communication system should be further improved. The most important parts in this kind of technology evolution include: reducing time-delay and latency time, increasing user data rate, increasing system capacity, enlarging coverage area, and decreasing overall cost of the operator. Besides, the backward compatibility of the evolved network architecture to the existing network is also an important consideration.

0003In a 3GPP (3^rd Generation Partnership Project) system prior to the evolved network, an attaching process and a Packet Data Protocol (PDP) context activating process are two separated processes. Once powered on, a terminal firstly performs a General Packet Radio Service (GPRS) attaching process, which mainly includes a security process and a location updating process. When the attaching process is completed, the terminal does not simultaneously acquire an IP bearer. Only when the terminal further initiates the PDP context activating process, the terminal may be provided with an IP address and corresponding configuration parameters. This is to say, it is necessary for a user to perform the PDP context activating process before service communication, resulting in a relatively long time-delay for the user to turn from an idle state to a data communication state, this definitely does not meet the requirements of the evolved network.

0004In order to reduce the latency time for a mobile terminal to turn from the idle state into the data communication state, a network registration and a default IP bearer establishment are performed together in a System Architecture Evolution (SAE) /long-term evolution (LTE) system proposed in a Specification, i.e., during the mobile terminal attaches to the network for the first time, the network allocates an IP address and some corresponding bearer resources to the mobile terminal. In this case, it is not specified whether or not the air-interface resource should be allocated. Thus, it is realized that the mobile terminal is always online, so as to provide service more quickly and rapidly by the network when the mobile terminal needs to perform data service. In short, it is at the time a user in the evolved network performs a network attaching process that a default IP bearer should be established. As illustrated in <figref idref="f0001">Fig. 1</figref>, the 3GPP Technology Report (TR) 23.882 made by 3GPP SA2 group provides a possible process of network attaching suggested by the current 3GPP TR (23.882) as follows:

0005(1) Network Discovery and Access System Selection: a terminal of a mobile user discovers SAE/LTE access systems and then performs access system and network selection.

0006(2) Attaching Request: the terminal initiates an Attaching Request, which includes old registration information of the user (for example, temporary ID), to a Mobility Management Entity/User Plane Entity (MME/UPE). The Attaching Request includes a permanent ID (identification) of the user if the terminal does not report the old registration information of the user. The Attaching Request may include information for default IP bearer (for example, IP address or APN (Access Point Name) selected by the user).

0007(3) a. Sending old registration information: if the old registration information of the user is reported by the terminal, the MME/UPE derives the address of an old MME/UPE registered last time from the old registration information of the user, and sends the registration information of the user to the old MME/UPE so as to ask for the information of the user.

0008b. Sending user context information: the old MME/UPE sends the context information of the user to the new MME/UPE, and the context information includes the permanent ID of the user, security context parameters, and so on.

0009(4) Security Functions (this step is optional): the new MME/UPE performs security authentication on the mobile user and equipment according to system configuration.

0010(5) MME Registration Updating: the new MME/UPE initiates a registration updating request toward a Home Subscriber Server (HSS), and registers as the MME/UPE currently serving the mobile user.

0011(6) Deleting user registration information: the HSS instructs the old MME/UPE to delete the context information of mobile user.

0012(7) Registration Confirmation: the HSS confirms the registration of the new MME/UPE. The subscription information for the default IP bearer, the relevant Quality of Service (QoS) strategy and the charging control information are also sent to the MME/UPE.

0013(8) Selection of Intersystem Mobility Anchor: An Inter AS Anchor is selected, and the selection mechanism is not specified. The IP address configuration is determined based on user's preference or subscribed data, or based on the strategy of Public Land Mobile Network (PLMN) or VPLMN (Visited Public Land Mobile Network).

0014(9) User Plane Routing Configuration: the Inter AS Anchor performs the IP layer configuration according to the determined IP address of the user. The User Plane is established and the basic strategies and charging rules are applied. It is not specified whether the establishment of the User Plane is initiated by the terminal or by the MME/UPE.

0015(10) IP Bearer QoS Configuration: the MME/UPE provides QoS Configuration of a default IP bearer (for example, the upper limit of data rate) to an evolved RAN (Radio Access Network). It is not specified whether a trigger mechanism is needed for this QoS Configuration (for example, it is needed when sending uplink or downlink data).

0016(11) Attachment Accept: the MME/UPE sends an attachment accept message indicating the acceptance of the terminal, and allocates a temporary ID for the terminal, the user's IP address is also sent to the terminal. In a roaming scene, roaming restrictions are checked, and the attachment is denied if the restrictions are violated.

0017(12) Attachment Confirmation: the terminal confirms the success of the attachment.

0018In the evolved network, the default IP bearer established during the user attaching process may bear IP-based protocol signalling, such as SIP (Session Initiation Protocol) protocol used by IP Multimedia Subsystem (IMS), as well as other potential services which may adopt default QoS controlling strategy and charging strategy. The QoSs required by upper layer application services are different largely from each other, and usually cannot be satisfied by the QoS provided by the default IP bearer. But the mobile user may continuously adopt the secondary PDP activating process which is similar to the existing process, based on the default IP bearer which has already been established, to accelerate the subsequent establishment processes for other service bearers and enhance the reaction speed of the system. Since the services established by the secondary activating process needs to share the IP address used by the first activating process, the IP address allocation strategy for the default IP bearer acquired in the registering process of the mobile user is very important, in that the strategy directly decides the data plane routing of the services of default IP address.

0019In order to improve the service quality for a roaming user, the evolved network requires the ability for optimizing the user plane routing of the roaming user. For example, the data of the roaming user are transmitted to the destination directly through the roaming network, rather than being routed back to the home network. Practically, the optimization of the user plane routing need be controllable for the home network of the user, so as to guarantee the benefits of the home network operator. However, there are no definite strategy and method to realize this optimization at present.

SUMMARY

0020Embodiments of the invention provide a method and system for implementing data routing of a roaming user, so as to control the IP address allocation for the default IP bearer of the roaming user and establish a user plane data routing of the roaming user which is controllable by the home network operator.

0021Embodiments of the invention provide a method for implementing data routing for a roaming user, including:

0022configuring a roaming protocol between a home network and a roaming network;

0023during a registering process of the user in the roaming network, performing an interactive negotiation between the home network and the roaming network, so as to determine one of the home network and the roaming network to allocate an IP address according to the roaming protocol between the home network and the roaming network;

0024establishing a default IP bearer with the IP address over the network.

0025Embodiments of the invention further provide a system for implementing data routing of a roaming user, including a roaming network element and a Home Subscriber Server (HSS),

0026the HSS, on which a roaming protocol is stored, is adapted to determine an IP address allocation strategy according to the roaming protocol;

0027the roaming network element is adapted to select one of the home network and the roaming network to allocate an IP address according to the IP address allocation strategy determined by the HSS, and establish a default IP bearer.

0028Embodiments of the invention further provide a Home Subscriber Server (HSS) adapted to:

0029determine whether the roaming network is allowed to provide the IP address of the default IP bearer according to a mobile user ID and the roaming protocol of the roaming network where the user currently is located; and

0030return a registration response message to a roaming network element.

0031Embodiments of the invention further provide a roaming network element adapted to:

0032send a PLMN ID of roaming network where the user currently located to a Home Subscriber Server (HSS);

0033receive an IP address allocation strategy determined by the HSS according to the PLMN ID,

0034select one of the home network and the roaming network to allocate an IP address according to the IP address allocation strategy; and

0035establish a default IP bearer.

0036In the solutions provided by the embodiments of the invention, the home network operator may comprehensively consider various relevant factors, such as the maturity of the roaming interconnection between the home network operator and the roaming network operator and so on, during the registering process of the mobile user in the roaming network, so as to control the allocation strategy of the default IP bearer address, i.e., so as to determine which one of the home network and the roaming network is to allocate the IP address for the default IP bearer. Embodiments of the invention implement the data plane routing optimization of the roaming user under the control of the home network operator, i.e., when the home network operator determines that the IP address for the default IP bearer may be allocated by the roaming network based on above mentioned factors, the IP address for the default IP bearer is allocated by the roaming network, so as to optimize the routing of the data plane for the roaming user to bear services by the default IP bearer.

0037Through the embodiments of the invention, while guaranting the benefit and dominant control right of the home network operator, the IP address of the default IP bearer for the roaming user may be allocated by the roaming network as much as possible, so as to optimize the routing of the data plane for the roaming user, improve the performance of the data service, and bring a better service experience to the roaming user.

BRIEF DESCRIPTION OF THE DRAWINGS

0038<figref idref="f0001">Fig.1</figref> shows a flowchart for network attaching in 3GPP TR 23.882;

0039<figref idref="f0002">Fig.2</figref> shows a architecture diagram of a radio evolved network;

0040<figref idref="f0003">Fig.3</figref> shows a flowchart for network attaching of a roaming user according to an embodiment of the invention;

0041<figref idref="f0004">Fig.4</figref> shows a flowchart for network attaching of a roaming user according to another embodiment of the invention

DETAILED DESCRIPTION

0042In order to make principles, features and advantages of the invention more apparent, a further detailed description for the technical solutions of the invention is given below with respect to embodiments and with reference to the accompany drawings.

0043Embodiment one

0044As shown in <figref idref="f0002">Fig.2</figref> a core network of a radio evolved network mainly includes three logic function entities: Mobility Management Entity (MME), User Plane Entity (UPE), and Inter AS Anchor (Inter AS Anchor is a user plane anchor for mobility between different access systems). The MME corresponds to a control plane part of a Serving GPRS Support Node (SGSN) inside a current Universal Mobile Telecommunication System (UMTS), and is responsible for the mobility management of the control plane, including the management of user context and mobility states as well as the allocation of user contemporary ID and security functions. The UPE corresponds to a data plane part of a GGSN (Gateway GPRS Support Node) and SGSN inside the current UMTS system, and is responsible for initiating a paging for downlink data under the idle state, managing and saving IP bearer parameters and intra network route information. The Inter AS Anchor acts as a user plane anchor for mobility between difference access systems. The functions of each interface in <figref idref="f0002">Fig.2</figref> and whether or not these interfaces exist are not finally specified. In <figref idref="f0002">Fig.2</figref>, GERAN is GSM (Global System for Mobile) EDGE (Enhanced Data rates for GSM Evolution) Radio Access Network; UTRAN is UMTS Terrestrial Radio Access Network; CN is Core Network; MS is Mobile Subscriber; UE is User Equipment; PCRF is Policy and Charging Rules Function.

0045As shown in <figref idref="f0003">Fig. 3</figref>, based on interactive negotiation between a home network and a roaming network during the network registering process, the home network operator controls the allocation of IP address of the default IP bearer for the roaming user. If capabilities of an element phone need to be taken into consideration during the interactive negotiation, the element phone needs to carry such information about its capabilities in an attaching request message, and the information about its capabilities is included in a registration updating request sent to the HSS by the MME/UPE of the roaming network. Based on the mobile subscriber ID and the visited PLMN where the user currently is located as well as taking the capabilities of the element phone into consideration, the HSS inquires the strategy configuration of the operator and determines whether or not the roaming network of the PLMN is allowed to allocate the IP address of the default IP bearer. The details are shown as follows:

0046A flow of network attaching process for optimizing data routing of a roaming user, including the following steps:

0047S101, Network Discovery and Access system selection: a terminal of a mobile user discovers SAE/LTE access systems and then selects an access system and network.

0048S102, Attaching Request: the terminal initiates an Attaching Request, which includes old registration information of the user (for example, temporary ID), to an MME/UPE. The Attaching Request includes a permanent ID of the user if the terminal does not report the old registration information of the user.

0049The Attaching Request may include information for default IP bearer (for example, IP address or APN selected by the user).

0050S103, a) Sending old registration information: if the old registration information of the user is reported by the terminal, the MME/UPE derives the address of an old MME/UPE registered last time from the old registration information of the user, and sends the registration information of the user to the old MME/UPE so as to ask for the information of the user.

0051b) Sending user context information: the old MME/UPE sends the context information of the user to the new MME/UPE, and the context information includes the permanent ID of the user, security context parameters, and so on.

0052S104, Security Functions (this step is optional): the new MME/UPE performs security authentication on the mobile user and equipment according to the system configuration.

0053S105, MME Registration Updating (PLMN ID): the new MME/UPE initiates a registration updating request toward an HSS, and registers as the MME/UPE currently serving the mobile user. The registration updating request message includes the PLMN ID of the PLMN where the user is located currently.

0054S106, Deleting user registration information: the HSS instructs the old MME/UPE to delete the context information of the mobile user.

0055S107, Registration Confirmation (VPLMN Default IP Address Allowed): the operator to which the user belongs may in advance configure different roaming strategies for each user or certain class of users with respect to different PLMNs, and save the strategies in a database. For example, the strategies may allow the default IP address of a class A user to be allocated by VPLMN1, the default IP address of a class B user to be allocated by VPLMN2, and the default IP address of a class C user to be only allocated by the home network. Based on the mobile user ID and the visited PLMN where the user currently is located, the HSS inquires the above mentioned strategy configuration of the operator and determines whether or not the roaming network of the PLMN is allowed to provide the IP address allocation for the default IP bearer.

0056The HSS confirms the successful registration of the new MME/UPE. The subscribed data of the user are sent to the new MME/UPE. The subscription information related to the default IP bearer, the relevant QoS strategy, the charging rules information and so on are also sent to the new MME/UPE. The registration response message returned by the HSS includes a information element, i.e., VPLMN IP Address Allowed, for indicating whether or not the roaming network is allowed to allocate the IP address for the default IP bearer:

0057a. VPLMN IP Address Allowed = TRUE, the roaming network is allowed to allocate the IP address for the default IP bearer;

0058b. VPLMN IP Address Allowed = FALSE, the roaming network is not allowed to allocate the IP address for the default IP bearer, and the IP address needs to be allocated by the home network.

0059S108, Default IP bearer Establishment: According to the indication of the information element (VPLMN IP Address Allowed) included in the registration response message returned by the HSS, the MME/UPE selects one of the home network and the roaming network to allocate the IP address, then the network performs IP layer configuration for the default IP address, the User Plane is established and the basic QoS strategy and charging rules are applied. It is not discussed herein as to which network element allocates the IP address, the IP bearer establishing process may be similar to that as illustrated in <figref idref="f0002">Fig. 2</figref>.

0060S109, Attachment Accept: the MME/UPE informs the terminal that its attaching request is accepted, and allocates a contemporary ID for the terminal, the allocated user's IP address is also sent to the terminal. In a roaming scene, roaming restrictions are checked, and the attachment is denied if the restrictions are violated.

0061S110, Attachment Confirmation: the terminal confirms the success of the attachment.

0062Embodiment two

0063If the service of default IP bearer in a future evolved network is not necessarily transparent to access network equipments (such as Evolved RAN (access network of future evolved network), MME/UPE, and Inter AS Anchor in <figref idref="f0002">fig.2</figref>), the above negotiation process may need to consider the supporting capability of the roaming network with respect to these non-transparent services. According to this respect, <figref idref="f0004">Fig. 4</figref> shows another embodiment of the invention.

0064First, for the non-transparent services (such as IMS service, which is not transparent to the access network equipments when the IMS service needs support from the roaming network equipments) of default IP bearer, a series of service IDs or service types are defined, and a TLV (type-length-value) format may be adopted as follows: <tables id="tabl0001" num="0001"><table frame="all"><tgroup cols="8" colsep="0" rowsep="0"><colspec colnum="1" colname="col1" colwidth="19mm" /><colspec colnum="2" colname="col2" colwidth="19mm" /><colspec colnum="3" colname="col3" colwidth="19mm" /><colspec colnum="4" colname="col4" colwidth="16mm" /><colspec colnum="5" colname="col5" colwidth="16mm" /><colspec colnum="6" colname="col6" colwidth="16mm" /><colspec colnum="7" colname="col7" colwidth="16mm" /><colspec colnum="8" colname="col8" colwidth="16mm" colsep="1" /><tbody><row><entry align="center">8</entry><entry align="center">7</entry><entry align="center">6</entry><entry align="center">5</entry><entry align="center">4</entry><entry align="center">3</entry><entry align="center">2</entry><entry align="center">1</entry></row><row><entry namest="col1" nameend="col4" align="center">Service ID List Type</entry><entry namest="col5" nameend="col8" align="center">Service ID List Length</entry></row><row><entry align="center">Reserved</entry><entry align="center">Reserved</entry><entry align="center">Reserved</entry><entry align="center">Service</entry><entry align="center">Service</entry><entry align="center">Service</entry><entry align="center">Service</entry><entry align="center">Service</entry></row><row><entry align="center" /><entry align="center" /><entry align="center" /><entry align="center">5</entry><entry align="center">4</entry><entry align="center">3</entry><entry align="center">2</entry><entry align="center">1</entry></row><row rowsep="1"><entry align="center">...</entry><entry align="center">...</entry><entry align="center">...</entry><entry align="center">...</entry><entry align="center">...</entry><entry align="center">...</entry><entry align="center">...</entry><entry align="center">...</entry></row><row><entry align="center">8</entry><entry align="center">7</entry><entry align="center">6</entry><entry align="center">5</entry><entry align="center">4</entry><entry align="center">3</entry><entry align="center">2</entry><entry align="center">1</entry></row><row><entry namest="col1" nameend="col4" align="center">Service Type List Type</entry><entry namest="col5" nameend="col8" align="center">Service Type List Length</entry></row><row><entry align="center">Reserved</entry><entry align="center">Reserved</entry><entry align="center">Reserved</entry><entry align="center">Service</entry><entry align="center">Service</entry><entry align="center">Service</entry><entry align="center">Service</entry><entry align="center">Service</entry></row><row><entry align="center" /><entry align="center" /><entry align="center" /><entry align="center">5</entry><entry align="center">4</entry><entry align="center">3</entry><entry align="center">2</entry><entry align="center">1</entry></row><row rowsep="1"><entry align="center">...</entry><entry align="center">...</entry><entry align="center">...</entry><entry align="center">...</entry><entry align="center">...</entry><entry align="center">...</entry><entry align="center">...</entry><entry align="center">...</entry></row></tbody></tgroup></table></tables>

0065The Service ID List Type or Service Type List Type is the identification of the whole information element for identifying the appearance of the information element.

0066The Service ID List Length or Service Type List Length is the length of the whole information element in unit of bytes.

0067Each service ID occupies one bit or employs a service ID value; or each service type occupies one bit or employs a service type value.

0068Referring to <figref idref="f0004">Fig. 4</figref>, a flow for network attaching of a roaming user is specifically described as below:

0069A method for optimizing data routing of a roaming user, including the following steps:

0070S201, Network Discovery and Access system selection: a terminal of a mobile user discovers SAE/LTE access systems and then selects an access system and network.

0071S202, Attaching Request (Service ID List): the terminal initiates an Attaching Request, which includes old registration information of the user (for example, temporary ID), to an MME/UPE. The Attaching Request includes a permanent ID of the user if the terminal does not report the old registration information of the user.

0072The Attaching Request may include information for default IP bearer (for example. IP address or APN selected by the user).

0073The Attaching Request carries a service ID list or a service type list of non-transparent services of the default IP bearer for the mobile terminal. For example, if the terminal requires the default IP bearer to bear IMS service, the bit corresponding to IMS in the Service ID List information element of the Attaching Request message is set to 1, and all the other bits are set to 0; alternatively, the service ID value in the Service ID List information element or the bit corresponding to IMS in the Service Type List information element of the Attaching Request message is set to 1 and all the other bits are set to 0 or values corresponding to service types in the Service Type List information element.

0074S203, a) Sending old registration information: if the old registration information of the user is reported by the terminal, the MME/UPE derives the address of an old MME/UPE registered last time from the old registration information of the user, and sends the registration information of the user to the old MME/UPE so as to ask for the information of the user.

0075b) Sending user context information: the old MME/UPE sends the context information of the user to the new MME/UPE, and the context information includes the permanent ID of the user, security context parameters, and so on.

0076S204, Security Functions (this step is optional): the new MME/UPE performs security authentication on the mobile user and equipment.

0077S205, MME Registration Updating (PLMN ID, Service ID List/Service Type List): the new MME/UPE matches the Service ID List or Service Type List reported by the user with the capabilities of the system itself for supporting these services, so as to acquire an intersection set of the capabilities supported by the system and the requirements of the user. The new MME/UPE initiates a registration updating request toward the HSS, and registers as the MME/UPE currently serving the mobile user. The registration updating request includes the PLMN ID of the PLMN where the user is located currently and the updated Service ID List or Service Type List, which indicates the service list of the default IP bearer for the mobile user in the current roaming network; i.e., the intersection set service list allowed by the default IP bearer, which are both requested by the user and supported by the system.

0078For example, when the registration by an IMS is not transparent to network equipments (for example, a core network is required to inform the mobile user of the P-CSCF (Proxy-Call Session Control Function) address), the user reports that the default IP bearer needs to bear the IMS. If the roaming network supports the IMS service, the bit corresponding to IMS in the Service ID List information element of the Register Updating Request sent from the MME/UPE to the HSS is set to 1 or the service ID value in the information element is set to 1, alternatively, the bit corresponding to IMS in the Service Type List information element of the Register Updating Request is set to 1 or the service type value in the information element is set to 1. In contrast, when the roaming network can not support the IMS service, the bit corresponding to IMS is set to 0, or the service ID value is set to 0, or the service type value is set to 0.

0079S206, Deleting user registration information: the HSS instructs the old MME/UPE to delete the context information of mobile user.

0080S207, Registration Confirmation (VPLMN Default IP Address Allowed, Service ID List/Service Type List): the operator to which the user belongs may in advance configure different roaming strategies for each user or certain class of users with respect to different PLMNs, and save the strategies in a database. Based on the mobile user ID and the visited PLMN where the user currently is located, the HSS inquires the above mentioned strategy configuration of the operator to acquire the services which may be borne by the default IP bearer provided by the roaming PLMN network, and matches the services with the received service list of the default IP bearer in the current roaming network. According to the result of matching, the HSS determines whether or not the roaming network is allowed to provide the IP address allocation for the default IP bearer. If the default IP address is allocated by the roaming network, the HSS further determines the services which may be borne by the IP allocated by the roaming network.

0081The HSS confirms the successful registration of the new MME/UPE, and the subscribed data of the user are transmitted to the new MME/UPE. The subscription information of the default IP bearer, relevant QoS strategy and charging control information are also transmitted to the new MME/UPE.

0082According to the matching result in step S207:

0083a. If the roaming network is determined to allocate the IP address of the default IP bearer, the registration response message returned from the HSS should include an information element (VPLMN IP Address Allowed = TRUE) to indicate that the IP address of the default IP bearer is provided by the roaming network and an information element (Service ID List/Service Type List) to indicate the service list of the default IP bearer.

0084b. If the home network is determined to allocate the IP address of the default IP bearer, the registration response message returned from the HSS should include an information element (VPLMN IP Address Allowed = FALSE) to indicate that the roaming network is not allowed to allocate the IP address of the default IP bearer and the IP address needs to be allocated by the home network.

0085S208, Default IP bearer Establishment: According to the indication of the information element (VPLMN IP Address Allowed) included in the registration response message returned from the HSS, the MME/UPE selects one of the home network and the roaming network to allocate the IP address; then the network performs IP layer configuration for the default IP address, the User Plane is established and the basic QoS strategy and charging rules are applied. It is not discussed herein as to which network element allocates the IP address, the IP bearer establishing process may be similar to that as illustrated in <figref idref="f0002">Fig. 2</figref>.

0086S209, Attachment Accept (Service ID List): the MME/UPE informs the terminal that its attaching request is accepted, and allocates a contemporary ID for the terminal, the allocated user's IP address is also sent to the terminal.

0087In a roaming scene, roaming restrictions are checked, and the attachment is denied if the restrictions are violated.

0088If the IP address of the default IP bearer is allocated by the roaming network, the MME/UPE further informs the mobile user, via the Attachment Accept message, the service list allowed by the default IP bearer and the service list is returned from the HSS.

0089S210, Attachment Confirmation: the terminal confirms the success of the attachment.

0090Once the network registration is completed, based on the established default IP bearer, the mobile user may initiates IMS registration and other services that may be borne by the default IP bearer. If the mobile terminal receives the service list allowed by the default IP bearer returned by the network, the mobile terminal determines whether or not a service to be initiated subsequently belongs to the above mentioned service list. If the service does not belong to the service list, the mobile terminal needs to initiate a process which is similar to the existing fist PDP activating process, so as to establish a new default IP bearer for the service. The IP address of the established new default IP bearer is different from the IP address of the default IP bearer. Assuming that, in the embodiment, the HSS indicates that the IP address of the default IP bearer may be allocated by the roaming network and only IMS services may be borne by the default IP bearer. In this case, if the terminal initiates a IMS registration in a later time, the default IP bearer established during the network registering process may be used directly; if the terminal initiates a non-IMS service such as a VPN (Virtual Private Network) service in a later time, the terminal needs to initiate a process which is similar to the fist PDP activating process of the existing 3GPP, so as to acquire a new IP address.

0091It should be understood that, although the MME and UPE are drawn together as a single unit in the schematic diagram, the MME and UPE may be separated in practice. In addition, the location of Inter AS Anchor in a network does not influence the adaptability of the invention. For example, the Inter AS Anchor and the UPE may be located in a same network node.

0092Through the embodiments of the invention, while guaranteeing the benefit and dominant control right of the home network operator, the IP address of the default IP bearer for the roaming user may be allocated by the roaming network as much as possible, so as to optimize the data plane routing of the roaming user, enhance the performance of data service, and bring better service experience for the roaming user.

0093The embodiments described herein are only to illustrate the invention, and are not intended to limit the scope of the invention. Any modification, equivalent substitution and improvement may be made to these embodiments without departing from the scope of the invention.