CN101252782B - Method for obtaining terminal roam access mode - Google Patents
Method for obtaining terminal roam access mode Download PDFInfo
- Publication number
- CN101252782B CN101252782B CN2008100901869A CN200810090186A CN101252782B CN 101252782 B CN101252782 B CN 101252782B CN 2008100901869 A CN2008100901869 A CN 2008100901869A CN 200810090186 A CN200810090186 A CN 200810090186A CN 101252782 B CN101252782 B CN 101252782B
- Authority
- CN
- China
- Prior art keywords
- plmn
- information
- message
- session
- access
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
- 238000000034 method Methods 0.000 title claims abstract description 46
- GVVPGTZRZFNKDS-JXMROGBWSA-N geranyl diphosphate Chemical compound CC(C)=CCC\C(C)=C\CO[P@](O)(=O)OP(O)(O)=O GVVPGTZRZFNKDS-JXMROGBWSA-N 0.000 claims description 90
- 230000008569 process Effects 0.000 claims description 15
- 230000004044 response Effects 0.000 claims description 13
- 230000004927 fusion Effects 0.000 claims 1
- 238000013475 authorization Methods 0.000 description 6
- 238000007726 management method Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 230000000977 initiatory effect Effects 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 238000013468 resource allocation Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000011664 signaling Effects 0.000 description 1
- 238000012384 transportation and delivery Methods 0.000 description 1
Images
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The present invention provides a method for acquiring a terminal roaming access way. A terminal UE is accessed into a PDN network in 3GPP and initiates IP-CAN session service. The method comprises the following steps: an MME assigns P-GW for IP-CAN session, and preserves the PLMN ID information of the P-GW; the MME sends a loading request message to S-GW, and the preserved PLMN ID information of the P-GW is carried in the message; after receiving the message, the S-GW acquires the terminal roaming access way according to the comparison between the PLMN ID information of the P-GW and the PLMN ID information of the S-GW, and accomplishes the IP-CAN session establishment flow. The method of the invention ensures the loading binding and event reporting function entity resided in a service gateway or an access gateway to acquire the terminal roaming access way.
Description
Technical Field
The invention relates to the field of wireless networks, in particular to a method for acquiring a terminal roaming access mode by a bearing binding and event reporting functional entity.
Background
The architecture diagram of a 3GPP Evolved Packet System (EPS, Evolved Packet System) is shown in fig. 1, where the EPS System is composed of an Evolved UTRAN (E-UTRAN, Evolved universal Radio Access Network Evolved Terrestrial universal Radio Access Network), an MME (Mobility Management Entity), an S-GW (Serving Gateway), a PDN GW (P-GW, Packet Data Network Gateway), an HSS (Home Subscriber Server ), a 3GPP AAA Server (3GPP authentication and authorization accounting Server), a PCRF (Policy and Charging function), and other support nodes. Wherein,
the MME is responsible for control plane related work such as mobility management, processing of non-access stratum signaling, management of the mobility management context of a user and the like;
the S-GW is an access gateway device connected to the E-UTRAN, forwards data between the E-UTRAN and the PDN GW, and is responsible for caching paging waiting data.
The P-GW is a border gateway of an Evolved Packet System (EPS) and a PDN (Packet Data network) network in 3GPP, and is responsible for accessing the PDN, forwarding Data between the EPS and the PDN, and other functions.
The PCRF is a policy and charging rules function entity, which is connected with an operator IP service network interface through an Rx interface to acquire service information, and the other side of the PCRF is connected with gateway equipment in the network through S7/S7a/S7c and is responsible for initiating the establishment of IP load, ensuring the QoS of service data and carrying out charging control.
The EPS supports the intercommunication with the non-3 GPP network, the intercommunication with the non-3 GPP network is realized through an S2a/b interface, and the P-GW is used as an anchor point between the 3GPP and the non-3 GPP network. Wherein the non-3 GPP systems are divided into trusted non-3 GPP IP access and untrusted non-3 GPP IP access. The trusted non-3 GPP IP access can be directly interfaced with the P-GW through the S2 a; the untrusted non-3 GPP IP access needs to be connected to the P-GW through an ePDG (Evolved Packet Data Gateway), and an interface between the ePDG and the P-GW is S2 b.
In a conventional 3GPP network, Policy and Charging Enforcement Functions (PCEFs) exist only in a P-GW, a PCRF can complete control of all functions as long as it interfaces with the P-GW, and the PCRF exchanges information with the P-GW through an S7 interface (see fig. 1). However, when the user uses 3GPP access, and the interface between P-GW and S-GW goes PMIP (Proxy Mobile IP protocol) based on the S5 interface, the policy enforcement function part of the PCEF function also exists in S-GW; or when the user uses trusted non-3 GPP access, part of the policy enforcement function in the PCEF function also exists in the trusted non-3 GPP access gateway. The entities residing in these gateways are called Bearer Binding and Event Reporting Functions (BBERF). When a user accesses the 3GPP, information is exchanged between the S-GW and the PCRF through an S7c interface; when the user can access the trusted non-3 GPP, the trusted non-3 GPP access gateway interacts information with the PCRF through S2a (as shown in fig. 1).
When the user roams to a visited place, the PDN network can be accessed using both Home Routed (Home Routed) and Local BreakOut (LBO). By adopting a Home Routed manner (as shown in fig. 2), a user accesses a PDN network by using a P-GW of a Home network; in LBO mode (as shown in fig. 3), the user uses P-GW at the visited place to access the PDN network. The difference between the two is whether the P-GW is in the visited network or the home network. In a roaming scenario, in order to make an S9 interface (interface between vPCRF and hPCRF) simpler, when a user accesses the Home Routed manner, the BBERF/PCEF of a roaming location directly interacts with the hPCRF, without going through an S9 interface (as shown in fig. 2), which is different from the original technology; when a user accesses the network by using a Local Breakout method, the BBERF/PCEF of the roaming site directly performs message interaction with the vprf, and the interaction between the vprf (visited PCRF) and the hPCRF (home PCRF) uses an S9 interface (as shown in fig. 3, consistent with the prior art). When a user initiates an IP-CAN (IP Connectivity access network) session or performs handover (3GPP inter-network handover, 3GPP access is handed over to trusted non-3 GPP access, trusted non-3 GPP access is handed over to 3GPP access), the BBERF/PCEF needs to initiate a request pcc (policy and charging control) policy to the PCRF, and according to the difference between the user using Home Routed and Local Breakout modes, the BBERF/PCEF fills different destination addresses for the request message: if the user accesses in the Home Routed mode, the destination domain name of the request message filled by the BBERF/PCEF is the Home network (interacts with the hPCRF message of the Home network); if the Local Breakout mode is adopted, the destination domain name of the request message filled by the BBERF/PCEF is the visited network (interacting with the vPCRF message of the visited network). For the PCEF, the PCEF (PCEF residing in the P-GW) knows where the PCEF is located, and certainly, it is clear whether the user uses the Home Routed or Local Breakout mode for access. For the BBERF (residing in the S-GW or the trusted non-3 GPP access gateway), the BBERF cannot know whether the user accesses in Home Routed or Local Breakout manner.
Disclosure of Invention
The technical problem to be solved by the present invention is to provide a method for obtaining a terminal roaming access mode, so that a functional entity residing in a serving gateway or an access gateway for bearing binding and event reporting obtains the terminal roaming access mode.
In order to solve the above problems, the present invention provides a method for obtaining a terminal roaming access mode, wherein a terminal UE accesses a packet data network PDN network in 3GPP and initiates an IP convergence access network IP-CAN session service, the method comprising the following steps:
a1: a mobile management unit MME distributes a packet data network gateway P-GW for the IP-CAN session and stores public land mobile network identification PLMN ID information of the P-GW;
b1: MME sends a bearing request message to a service gateway S-GW, wherein the message carries the stored PLMN ID information of the P-GW;
c1: after receiving the message, the S-GW obtains the terminal roaming access mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the S-GW, and completes the IP-CAN session establishment process.
Further, if the IP-CAN session service is switched between 3GPP accesses and the MME changes, the step C1 further includes the following steps:
d1: the new MME sends an authentication request to the old MME, the old MME sends an authentication response to the new MME, and the message carries PLMN ID information of P-GW selected for IP-CAN session;
e1: the new MME stores the PLMN ID information of the P-GW according to the received information;
f1: and the new MME sends a request message for establishing default load to the S-GW, the message carries the stored related information of the P-GW, and after receiving the message, the S-GW acquires a terminal roaming access mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the S-GW to complete the session establishment process.
Further, if the IP-CAN session service is switched between 3GPP accesses and the S-GW is changed, the step C1 further includes the following steps: and the MME sends a request message for establishing default load to the new S-GW, the message carries PLMN ID information of the P-GW of the IP-CAN session, and after receiving the message, the new S-GW acquires a terminal roaming access mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the new S-GW to complete a session establishing process.
Further, in step a1, the MME allocates a P-GW for the IP-CAN session and sends a response message to the HSS, where the message carries the PLMN ID information of the selected P-GW, and the HSS stores the PLMN ID information of the P-GW selected by the IP-CAN session after receiving the response message; if the UE is switched from the 3GPP access to the trusted non-3 GPP access, the following steps are included after the step C1 or F1:
g1: a trusted non-3 GPP access gateway initiates authentication to an AAA server;
h1: AAA server judges the success of authentication, and obtains PLMN ID information of P-GW of the IP-CAN session from HSS;
i1: AAA stores PLMN ID information of P-GW of the IP-CAN session after receiving the message;
j1: the AAA server sends the related information of the P-GW to a trusted non-3 GPP access gateway, and the trusted non-3 GPP access gateway obtains a terminal roaming access mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the trusted non-3 GPP access gateway after receiving the information, and completes a switching access process.
Further, the access mode of terminal roaming refers to a home routing mode or a local breakout mode, the S-GW or the trusted non-3 GPP access gateway compares the PLMN ID information of the P-GW in the received message with the PLMN ID of the S-GW, and if the comparison result is the same, the UE is judged to be accessed by using the home routing mode; and if the UE is different from the local breakout mode, judging that the UE is accessed by using the local breakout mode.
In order to solve the above technical problem, the present invention further provides a method for obtaining a roaming access mode of a terminal, wherein when the terminal accesses a trusted non-3 GPP and initiates an IP-CAN session, the method comprises the following steps:
a2: after the AAA server successfully authenticates, the AAA server selects a P-GW for the IP-CAN session, sends PLMN ID information of the P-GW to a trusted non-3 GPP access gateway, or the AAA server sends related information of the P-GW, and the trusted non-3 GPP access gateway selects the P-GW;
b2: and the trusted non-3 GPP access gateway acquires a terminal roaming access mode and completes a session establishment process according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the gateway.
Further, in step a2, the message sent by the AAA server to the trusted non-3 GPP access gateway includes the APN and information on whether to allow the P-GW to be selected for access in the roaming area, and the trusted non-3 GPP access gateway selects the P-GW for the IP-CAN session according to the received message.
Further, step B2 is followed by the following steps:
c2: the trusted non-3 GPP access gateway already knows the address information of the P-GW and sends an agent binding update message to the P-GW;
d2: after receiving the message, the P-GW sends a message for updating the PDN GW address to the AAA server, wherein the message carries the PLMN ID of the P-GW;
e2: after AAA server receives the message, it stores the PLMNID information of P-GW selected by the IP-CAN session;
f2: AAA server sends message to HSS, the message contains PLMN ID information of P-GW, informs HSS to store PLMN ID information of P-GW selected by IP-CAN;
g2: after HSS receives the message, storing PLMN ID of P-GW selected by the IP-CAN session;
if the UE is switched from the trusted non-3 GPP access to the 3GPP access, the method further comprises the following steps:
h2: the MME authenticates to the HSS, and sends a message to the MME after the HSS successfully authenticates, wherein the message comprises the P-GW address of the IP-CAN session and the PLMN ID information of the P-GW;
i2: after receiving the message, the MME stores the PLMN ID information of the P-GW selected by the IP-CAN session;
j2: MME sends a request message for creating default load to S-GW, the message carries the stored PLMN ID information of the P-GW, after the S-GW receives the message, the S-GW acquires the terminal roaming access mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the S-GW.
Further, the access mode of terminal roaming refers to a home routing mode or a local breakout mode, the S-GW or the trusted non-3 GPP access gateway compares the PLMN ID information of the P-GW in the received message with the PLMN ID of the S-GW, and if the comparison result is the same, the UE is judged to be accessed by using the home routing mode; and if the UE is different from the local breakout mode, judging that the UE is accessed by using the local breakout mode.
The method for acquiring the terminal roaming access mode of the invention enables the bearing binding and event reporting functional entity residing in the service gateway or the access gateway to acquire the terminal roaming access mode by increasing the PLMN ID information transmission and storage on the basis of the original flow, and the method is simple and easy to realize.
Drawings
Fig. 1 is a non-roaming architecture diagram for a UE employing 3GPP access and non-3 GPP access.
Fig. 2 is a roaming architecture diagram for access by a UE in a home routing manner.
Fig. 3 is a roaming architecture diagram for UE access using local delivery and guidance.
Fig. 4 is a flowchart illustrating a UE initiating an attach procedure when a user accesses a 3GPP network according to an embodiment of the present invention.
Fig. 5 is a flowchart of UE completing attach and initiating a new IP-CAN session when a second user uses 3GPP to access in the embodiment of the present invention.
Fig. 6 is a flow chart of handover from a 3GPP network to another 3GPP network when a user uses 3GPP access according to the embodiment of the present invention.
FIG. 7 is a flowchart illustrating that when four users use trusted non-3 GPP access, UE initiates attachment and an AAA server selects a P-GW for an IP-CAN session of the user according to an embodiment of the present invention.
Fig. 8 is a flowchart illustrating that when a five-user uses a trusted non-3 GPP access, a UE initiates attachment, and the trusted non-3 GPP access gateway selects a P-GW for an IP-CAN session of the user according to the embodiment of the present invention.
FIG. 9 is a flowchart of a six-user handover from a trusted non-3 GPP network to a 3GPP network using a trusted non-3 GPP access according to an embodiment of the present invention.
Fig. 10 is a flowchart of a seven-user handover from a 3GPP network to a trusted non-3 GPP network using 3GPP access according to an embodiment of the present invention.
Detailed Description
The method for acquiring the terminal roaming access mode of the invention is a method for informing a bearer binding and event reporting function entity BBERF to acquire whether a user uses a Home Routed or Local Breakout mode for access, and the main idea of the invention is as follows:
when a terminal uses 3GPP to access a PDN Network in a roaming place, after an MME selects a P-GW for an IP-CAN session, a PLMN ID (Public Land Mobile Network ID) of the P-GW is stored and informed to the S-GW, wherein the PLMN ID is used for marking the Network position where the P-GW is located. And informing HSS of the PLMN ID of the P-GW, and storing the PLMN ID of the P-GW by the HSS. And the S-GW judges whether the user is accessed by the Home Routed or the LocalBreakout according to the received information.
When the terminal uses the non-3 GPP to access the PDN network in a roaming place, if the terminal can be trusted to access the P-GW selected by the gateway; or the P-GW selected by the AAA server informs a trusted non-3 GPP access gateway of the PLMN ID information of the P-GW; the trusted non-3 GPP access gateway judges whether the access is in a Home Routed or Local Breakout mode according to the PLMN ID information of the P-GW; when the P-GW reports the update message to the AAA server, the message carries the PLMNID information of the P-GW, and the AAA server stores the PLMN ID information of the P-GW selected by the IP-CAN session. The AAA server informs the HSS to store the PLMN ID information of the P-GW selected by the IP-CAN session.
When the IP-CAN session service of a user is switched from a 3GPP network to a trusted non-3 GPP network, the continuity of the session service is kept, and the AAA server acquires the PLMN ID of the P-GW of the IP-CAN session from the HSS and informs the trusted non-3 GPP access gateway. And the trusted non-3 GPP access gateway judges whether the access is Home Routed or Local Breakout according to the received PLMN ID information of the P-GW of the IP-CAN session.
When the IP-CAN session service of a user is switched from a trusted non-3 GPP network to a 3GPP network, the continuity of the session service is kept, and the MME acquires the PLMN ID of the P-GW of the IP-CAN session from the HSS and informs the S-GW. And the S-GW judges whether the access is Home Routed or Local Breakout according to the received PLMNID information of the P-GW of the IP-CAN session.
In addition, the basis of the application of the invention is that the terminal establishes an IP-CAN session in a roaming place, wherein MME are MME in the roaming place and AAA servers are AAA servers in a home network.
The method of the invention is described in further detail below with reference to the accompanying drawings.
Example one
This embodiment describes that when the UE is in a 3GPP access roaming scenario, and the 3GPP core network adopts an EPC architecture. When UE initiates an IP-CAN session in a roaming place, MME receives user subscription information from HSS, MME selects a P-GW for the IP-CAN session after receiving the information, and MME stores PLMN ID information of the selected P-GW. MME sends response message of user subscription information to HSS, and the message contains selected PLMN ID information of P-GW. And after receiving the message, the HSS stores the PLMN ID information of the P-GW selected by the IP-CAN session. And when the MME sends a request for creating the default bearer to the S-GW, the PLMN ID of the P-GW selected on the MME is brought to inform the S-GW of the PLMN ID of the P-GW selected by the IP-CAN session. Thus, the S-GW can compare the received PLMN ID information of the P-GW with the PLMN ID information of the S-GW: if the UE is the same as the Home Routed mode, judging that the UE is accessed in the Home Routed mode; if not, judging that the UE is accessed by using a Local BreakOut mode. The flowchart of this embodiment is shown in fig. 4, and the steps are described as follows:
402. and the HSS sends subscription information related to the user to the MME.
404. And the MME allocates a P-GW for the IP-CAN session according to the received information, and stores the PLMN ID information of the P-GW while storing the APN and the address of the P-GW.
406. MME sends response message of user subscription information to HSS, and the message contains selected PLMN ID information of P-GW.
408. And after receiving the response message, the HSS stores the PLMNID information of the P-GW selected by the IP-CAN session.
410. MME sends a request message for creating default load to S-GW, wherein the message has the stored PLMN ID information of the P-GW. Thus, after receiving the message, the S-GW can judge whether the user accesses in an LBO or Homerouted mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the S-GW, and accordingly the BBERF residing in the S-GW initiates a request PCC strategy to the PCRF to complete the session establishment process.
Example two
This embodiment describes that when the UE is in a 3GPP access roaming scenario, and the 3GPP core network adopts an EPC architecture. UE has already established and finished attaching in roaming the place, UE initiates a new IP-CAN conversation at this moment, MME chooses a P-GW for the IP-CAN conversation after receiving the message, MME keeps the PLMN ID information of P-GW chosen. MME sends message to HSS to inform HSS to save PLMN ID of selected P-GW. And after receiving the message, the HSS stores the PLMN ID information of the P-GW selected by the IP-CAN session. And when the MME sends a message for requesting bearer resource allocation to the S-GW, the PLMN ID of the selected P-GW is brought to inform the S-GW of the PLMN ID of the P-GW selected by the IP-CAN session. Thus, the S-GW can compare the received PLMN ID information of the P-GW with the PLMN ID information of the S-GW: if the UE is the same as the Home Routed mode, judging that the UE is accessed in the Home Routed mode; if not, judging that the UE is accessed by using a Local BreakOut mode. The flowchart of this embodiment is shown in fig. 5, and the steps are described as follows:
502. and the MME allocates a P-GW for the IP-CAN session according to the received information and stores the PLMN ID information of the P-GW.
504. The MME informs the HSS of the P-GW information for saving the IP-CAN session selection.
506. And after receiving the response message, the HSS stores the PLMNID information of the P-GW selected by the IP-CAN session.
508. MME sends a request bearing resource allocation message to S-GW, wherein the message has the stored PLMN ID information of the P-GW. Thus, after receiving the message, the S-GW can judge whether the user accesses in an LBO or Homerouted mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the S-GW, and accordingly the BBERF residing in the S-GW initiates a request PCC strategy to the PCRF to complete the session establishment process.
EXAMPLE III
This embodiment describes that when the UE is in a 3GPP access roaming scenario, the 3GPP core network adopts an EPC architecture. This embodiment describes that the UE is switched from the 3GPP access to another 3GPP access, that is, the IP-CAN session service of the UE is switched between 3GPP networks, at this time, the MME changes, the New MME sends an authentication request to the Old MME, the Old MME sends an authentication response to the New MME after receiving the request, and because the Old MME has stored the PLMN ID information of the P-GW selected for the IP-CAN session before, the Old MME is brought up in the response message to select the PLMN ID information of the P-GW for the IP-CAN session. And the New MME stores the PLMN ID information of the P-GW, carries the PLMN ID information of the P-GW when sending a request for creating a default bearer to the S-GW, and informs the S-GW of the PLMN ID information of the P-GW selected by the IP-CAN session. Thus, the S-GW can compare the received PLMN ID information of the P-GW with the PLMN ID information of the S-GW: if the UE is the same as the Home Routed mode, judging that the UE is accessed in the Home Routed mode; if not, judging that the UE is accessed by using a Local BreakOut mode. The flowchart of this embodiment is shown in fig. 6, and the steps are described as follows:
602. and the Old MME sends an authentication response to the New MME, and the message carries PLMN ID information of the P-GW selected for the IP-CAN session.
604. And the New MME stores the PLMN ID information of the P-GW according to the received information.
606. And the New MME sends a request message for creating default load to the S-GW, wherein the message has the stored PLMN ID information of the P-GW. Thus, after receiving the message, the S-GW can judge whether the user accesses in an LBO or Home Routed mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the user, and accordingly the BBERF residing in the S-GW initiates a request PCC strategy to the PCRF to complete the session establishment process.
The above is a scenario example in which the MME changes when the UE is switched in the 3GPP access environment. If the MME is not changed and only the switching between S-GWs occurs, the steps 602 and 604 are omitted, and the PLMN ID of the P-GW selected by the IP-CAN session is directly sent to the New S-GW by the MME through a message of establishing a default bearer request.
Example four
This embodiment describes that when the UE adopts a trusted non-3 GPP access roaming scenario, and the 3GPP core network adopts an EPC architecture. This embodiment describes that when a UE initiates an IP-CAN session, the UE and a trusted non-3 GPP Access gateway initiate an authentication and authorization request to an AAA server, the AAA server authenticates the UE and allows the UE to Access using the trusted non-3 GPP gateway, after obtaining subscription information of a user from an HSS, a P-GW is selected for the IP-CAN session, and relevant information of the P-GW (including an Access Point Name (APN), an address of the P-GW, and PLMN ID information) is sent to the non-3 GPP Access gateway. The non-3 GPP access gateway compares the received PLMN ID information of the P-GW with the PLMN ID information of the non-3 GPP access gateway: if the UE is the same as the Home Routed mode, judging that the UE is accessed in the Home Routed mode; if not, judging that the UE is accessed by using a Local BreakOut mode. And then the trusted non-3 GPP access gateway sends a proxy binding update message to the P-GW, and the P-GW sends the updated P-GW address information to the AAA server, wherein the message carries the PLMN ID of the P-GW. After receiving the message, AAA stores the PLMN ID and sends the message to HSS, wherein the message carries the PLMN ID. And after receiving the message, the HSS stores the PLMN ID information of the P-GW selected for the IP-CAN session. The flowchart of this embodiment is shown in fig. 7, and the steps are described as follows:
702. the trusted non-3 GPP access gateway initiates an authentication and authorization request to an AAA server, the AAA server successfully authenticates and selects a P-GW for an IP-CAN session, the address information of the P-GW is sent to the trusted non-3 GPP access gateway, and the message carries the PLMN ID of the P-GW. After receiving the message, the trusted non-3 GPP access gateway can judge whether the user accesses in an LBO or Home Routed mode according to the comparison between the PLMNID information of the P-GW and the PLMN ID of the user.
704. The trusted non-3 GPP access gateway already knows the address information of the P-GW and sends a proxy binding update message to the P-GW.
After the AAA server sends the information about the P-GW to the access gateway, the S-GW notifies the P-GW via this message, and the P-GW sends an update address message to the AAA server for authentication in step 706.
706. And after receiving the message, the P-GW sends a message for updating the PDN GW address to the AAA server, wherein the message carries the PLMN ID of the P-GW.
708. And after receiving the message, the AAA server stores the PLMN ID information of the P-GW selected by the IP-CAN session.
710. AAA server sends message to HSS, the message contains PLMN ID information of P-GW, informs HSS to store PLMN ID information of P-GW selected by IP-CAN.
712. And after receiving the message, the HSS stores the PLMN ID information of the P-GW selected by the IP-CAN session.
EXAMPLE five
This embodiment describes that when the UE adopts a trusted non-3 GPP access roaming scenario, and the 3GPP core network adopts an EPC architecture. This embodiment describes that when a UE initiates an IP-CAN session, the UE and a trusted non-3 GPP access gateway initiate an authentication and authorization request to an AAA server, the AAA server authenticates the UE and allows the UE to access, after obtaining subscription information of a user from an HSS, a P-GW is not selected for the IP-CAN session, relevant information (including an APN and whether to allow P-GW access to be selected in a roaming location) for selecting the P-GW is delivered to the non-3 GPP access gateway,
after receiving the message, the trusted non-3 GPP access gateway selects a P-GW for the IP-CAN session, compares the PLMN ID information of the selected P-GW with the PLMN ID information of the trusted non-3 GPP access gateway: if the UE is the same as the Home Routed mode, judging that the UE is accessed in the Home Routed mode; and if the UE is different from the local BreakOut mode, judging that the UE is accessed by using the LocalBreakOut mode. And then the trusted non-3 GPP access gateway sends a proxy binding update message to the P-GW, and the P-GW sends the updated P-GW address information to the AAA server, wherein the message carries the PLMN ID of the P-GW. After receiving the message, AAA stores the PLMN ID and sends the message to HSS, wherein the message carries the PLMN ID. And after receiving the message, the HSS stores the PLMN ID information of the P-GW selected for the IP-CAN session. The flowchart of this embodiment is shown in fig. 8, and the steps are described as follows:
802. the trusted non-3 GPP access gateway initiates an authentication and authorization request to the AAA server, the AAA server successfully authenticates, the P-GW is not selected for the IP-CAN session, and only the selected scope and policy (including the APN and whether the P-GW is allowed to be selected for access in roaming) are sent to the trusted non-3 GPP access gateway. And after receiving the message, the trusted non-3 GPP access gateway selects the P-GW for the IP-CAN session, compares the PLMN ID of the selected P-GW with the PLMN ID of the user, and judges whether the user accesses in an LBO or Home Routed mode.
804. And the trusted non-3 PP access gateway sends a proxy binding update message to the selected P-GW.
806. And after receiving the message, the P-GW sends a message for updating the PDN GW address to the AAA server, wherein the message carries the PLMN ID of the P-GW.
808. And after receiving the message, the AAA server stores the PLMN ID information of the P-GW selected by the IP-CAN session.
810. AAA server sends message to HSS, the message contains PLMN ID information of P-GW, informs HSS to store PLMN ID information of P-GW selected by IP-CAN.
812. And after receiving the message, the HSS stores the PLMN ID information of the P-GW selected by the IP-CAN session.
In embodiment 4, the AAA server selects the P-GW, and in embodiment 5, the access gateway selects the P-GW, and the two selection modes are compatible with the former networking mode.
EXAMPLE six
This embodiment describes that when the UE adopts a trusted non-3 GPP access roaming scenario, and the 3GPP core network adopts an EPC architecture. When UE is switched to 3GPP access from trusted non-3 GPP access, MME authenticates to HSS, HSS successfully authenticates, sends message containing P-GW address selected by IP-CAN session and PLMN ID information of P-GW (since HSS has saved the information before) to MME, when MME sends request of creating default bearer to S-GW, PLMN ID of P-GW selected is brought up, and S-GW is informed of PLMN ID of P-GW selected by IP-CAN session. Thus, the S-GW can compare the received PLMN ID information of the P-GW with the PLMN ID information of the S-GW: if the UE is the same as the Home Routed mode, judging that the UE is accessed in the Home Routed mode; if not, judging that the UE is accessed by using a Local BreakOut mode. The flowchart of this embodiment is shown in fig. 9, and the steps are described as follows:
902. and the MME authenticates to the HSS, and the HSS successfully authenticates and sends a message to the MME, wherein the message contains the PLMN ID information of the P-GW selected by the IP-CAN session.
904. And after receiving the message, the MME stores the PLMN ID information of the P-GW selected by the IP-CAN session.
906. MME sends a request message for creating default load to S-GW, wherein the message has the stored PLMN ID information of the P-GW. Thus, after receiving the message, the S-GW can judge whether the user accesses in an LBO or Homerouted mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the user.
EXAMPLE seven
This embodiment describes that when the UE adopts a roaming scenario of 3GPP access, and the 3GPP core network adopts an EPC architecture. When the UE is switched from 3GPP access to trusted non-3 GPP access, the UE and the trusted non-3 GPP access gateway initiate an authentication and authorization request to an AAA server, the AAA server acquires PLMN ID information of the P-GW selected by the IP-CAN session from an HSS (since the information is stored by the HSS before), and the AAA server authenticates the UE and allows the UE to access by using the trusted non-3 GPP gateway. The AAA server sends the relevant information of the P-GW to the non-3 GPP access gateway, and the relevant information of the P-GW comprises a P-GW address and a PLMN ID. Therefore, the trusted non-3 GPP access gateway can compare the received PLMN ID information of the P-GW with the PLMN ID information of the trusted non-3 GPP access gateway: if the UE is the same as the Home Routed mode, judging that the UE is accessed in the Home Routed mode; if not, judging that the UE is accessed by using a Local BreakOut mode. The flowchart of this embodiment is shown in fig. 10, and the steps are described as follows:
1002. the trusted non-3 GPP access gateway initiates authentication to the AAA server.
1004. AAA server judges the success of authentication, and obtains P-GW information related to the IP-CAN session from HSS, including PLMN ID information of P-GW.
1006. After receiving the message, AAA stores the P-GW related information selected by the IP-CAN session, including the PLMN ID information of P-GW.
1008. The AAA server sends the related information of the P-GW (including the PLMN ID information of the P-GW) to a trusted non-3 GPP access gateway. After receiving the message, the trusted non-3 GPP access gateway can judge whether the user accesses in an LBO or Home Routed mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the user.
In the above embodiment, the transmission and storage of the PLMN ID information are based on the original process, and the bearer binding and event reporting functional entity residing in the serving gateway or the access gateway learns the terminal roaming access mode by adding the PLMN ID information, and the changes to the existing system and process are very small.
The IP-CAN session includes all services based on IP, and at present, except that the functional entities that initiate IP-CAN session and switch, reside in the serving gateway or the access gateway, and report events need to know the access mode according to the information of the P-GW in the above embodiments, the present invention may also be applied if there is an application similar to the above embodiments.
Claims (9)
1. A method for obtaining terminal roaming access mode is characterized in that: the terminal UE accesses a packet data network PDN in 3GPP and initiates IP-CAN session service of an IP fusion access network, and the method comprises the following steps:
a1: a mobile management unit MME distributes a packet data network gateway P-GW for the IP-CAN session and stores public land mobile network identification PLMN ID information of the P-GW;
b1: MME sends a bearing request message to a service gateway S-GW, wherein the message carries the stored PLMN ID information of the P-GW;
c1: after receiving the message, the S-GW obtains the terminal roaming access mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the S-GW, and completes the IP-CAN session establishment process.
2. The method of claim 1, wherein: if the IP-CAN session service is switched between 3GPP accesses and the MME changes, the following steps are further included after step C1:
d1: the new MME sends an authentication request to the old MME, the old MME sends an authentication response to the new MME, and the message carries PLMN ID information of P-GW selected for IP-CAN session;
e1: the new MME stores the PLMN ID information of the P-GW according to the received information;
f1: and the new MME sends a request message for establishing default load to the S-GW, the message carries the stored related information of the P-GW, and after receiving the message, the S-GW acquires a terminal roaming access mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the S-GW to complete the session establishment process.
3. The method of claim 1, wherein: if the IP-CAN session service is switched between 3GPP accesses and the S-GW is changed, the following steps are further included after step C1: and the MME sends a request message for establishing default load to the new S-GW, the message carries PLMN ID information of the P-GW of the IP-CAN session, and after receiving the message, the new S-GW acquires a terminal roaming access mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the new S-GW to complete a session establishing process.
4. The method of any of claims 1 to 3, wherein: step A1, MME distributes P-GW for IP-CAN conversation and sends response information to home subscriber server HSS, the information carries PLMN ID information of selected P-GW, HSS stores PLMN ID information of P-GW selected by IP-CAN conversation after receiving response information; if the UE is switched from the 3GPP access to the trusted non-3 GPP access, the following steps are included after the step C1 or F1:
g1: a trusted non-3 GPP access gateway initiates authentication to an AAA server;
h1: AAA server judges the success of authentication, and obtains PLMN ID information of P-GW of the IP-CAN session from HSS;
i1: AAA stores PLMN ID information of P-GW of the IP-CAN session after receiving the message;
j1: the AAA server sends the related information of the P-GW to a trusted non-3 GPP access gateway, and the trusted non-3 GPP access gateway obtains a terminal roaming access mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the trusted non-3 GPP access gateway after receiving the information, and completes a switching access process.
5. The method of any of claims 1 to 3, wherein: the access mode of terminal roaming refers to a home routing mode or a local breakout mode, the S-GW or the trusted non-3 GPP access gateway compares the PLMN ID information of the P-GW in the received message with the PLMN ID of the S-GW, and if the comparison result is the same, the UE is judged to be accessed by using the home routing mode; and if the UE is different from the local breakout mode, judging that the UE is accessed by using the local breakout mode.
6. A method for obtaining terminal roaming access mode is characterized in that when a terminal accesses a trusted non-3 GPP and initiates an IP-CAN session, the method comprises the following steps:
a2: after the AAA server successfully authenticates, the AAA server selects a P-GW for the IP-CAN session, sends PLMN ID information of the P-GW to a trusted non-3 GPP access gateway, or the AAA server sends related information of the P-GW, and the trusted non-3 GPP access gateway selects the P-GW;
b2: and the trusted non-3 GPP access gateway acquires a terminal roaming access mode and completes a session establishment process according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the gateway.
7. The method of claim 6, wherein: the message sent by the AAA server to the trusted non-3 GPP access gateway in step a2 includes the APN and information on whether to allow the P-GW to be selected for access in the roaming location, and the trusted non-3 GPP access gateway selects the P-GW for the IP-CAN session according to the received message.
8. The method of claim 6 or 7, wherein: step B2 is followed by the steps of:
c2: the trusted non-3 GPP access gateway already knows the address information of the P-GW and sends an agent binding update message to the P-GW;
d2: after receiving the message, the P-GW sends a message for updating the P-GW address to the AAA server, wherein the message carries the PLMN ID of the P-GW;
e2: after AAA server receives the message, it stores the PLMNID information of P-GW selected by the IP-CAN session;
f2: AAA server sends message to HSS, the message contains PLMN ID information of P-GW, informs HSS to store PLMN ID information of P-GW selected by IP-CAN session;
g2: after HSS receives the message, storing PLMN ID of P-GW selected by the IP-CAN session;
if the UE is switched from the trusted non-3 GPP access to the 3GPP access, the method further comprises the following steps:
h2: the MME authenticates to the HSS, and sends a message to the MME after the HSS successfully authenticates, wherein the message comprises the P-GW address of the IP-CAN session and the PLMN ID information of the P-GW;
i2: after receiving the message, the MME stores the PLMN ID information of the P-GW selected by the IP-CAN session;
j2: MME sends a request message for creating default load to S-GW, the message carries the stored PLMN ID information of the P-GW, after the S-GW receives the message, the S-GW acquires the terminal roaming access mode according to the comparison between the PLMN ID information of the P-GW and the PLMN ID of the S-GW.
9. The method of claim 6 or 7, wherein: the access mode of terminal roaming refers to a home routing mode or a local breakout mode, the S-GW or the trusted non-3 GPP access gateway compares the PLMN ID information of the P-GW in the received message with the PLMN ID of the S-GW, and if the comparison result is the same, the UE is judged to be accessed by using the home routing mode; and if the UE is different from the local breakout mode, judging that the UE is accessed by using the local breakout mode.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100901869A CN101252782B (en) | 2008-04-14 | 2008-04-14 | Method for obtaining terminal roam access mode |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2008100901869A CN101252782B (en) | 2008-04-14 | 2008-04-14 | Method for obtaining terminal roam access mode |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101252782A CN101252782A (en) | 2008-08-27 |
| CN101252782B true CN101252782B (en) | 2011-12-07 |
Family
ID=39955934
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2008100901869A Expired - Fee Related CN101252782B (en) | 2008-04-14 | 2008-04-14 | Method for obtaining terminal roam access mode |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101252782B (en) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101668280B (en) * | 2008-09-01 | 2012-07-04 | 华为技术有限公司 | Network switching method, management equipment, terminal and home location server |
| CN101677437B (en) | 2008-09-18 | 2012-02-29 | 华为技术有限公司 | Method and system for implementing policy and charging control in multi-packet data network scenario |
| CN101437297B (en) * | 2008-12-16 | 2012-07-04 | 华为技术有限公司 | Method, apparatus and system for processing business |
| CN101784035B (en) * | 2009-01-16 | 2013-05-08 | 中兴通讯股份有限公司 | Method, system and user equipment for establishing correlation between business network element and MME |
| RU2628316C2 (en) * | 2013-05-24 | 2017-08-15 | Телефонактиеболагет Л М Эрикссон (Пабл) | Methods for providing plmn-identificator of network gateway of packet data transfer to ran node |
| CN104349297A (en) * | 2013-08-02 | 2015-02-11 | 中兴通讯股份有限公司 | Charging policy method of internetwork signing authorization and device thereof |
| CN103781087A (en) * | 2014-01-06 | 2014-05-07 | 联想(北京)有限公司 | Information processing method and mobile terminal |
| CN104994492B (en) | 2015-06-19 | 2017-05-17 | 广东欧珀移动通信有限公司 | Method and server for saving pages in standard format |
| CN106937276A (en) * | 2015-12-29 | 2017-07-07 | 中兴通讯股份有限公司 | Data gateway system of selection, device and mobility management entity |
| EP3573360B1 (en) | 2017-02-15 | 2022-11-30 | Huawei Technologies Co., Ltd. | Local breakout service data transmission method |
| CN109219099B (en) * | 2017-07-06 | 2021-07-20 | 北京佰才邦技术股份有限公司 | A network switching method, network controller, related server and PGW |
| CN109327869A (en) * | 2017-07-31 | 2019-02-12 | 中兴通讯股份有限公司 | Terminal network switching method, device, system and computer storage medium |
| CN112449337B (en) * | 2019-09-02 | 2023-10-31 | 中兴通讯股份有限公司 | Roaming control method and device, UDM (Universal description language) equipment and storage medium |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859776A (en) * | 2006-01-26 | 2006-11-08 | 华为技术有限公司 | Roaming user data route optimizing method in 3GPP evolution network |
-
2008
- 2008-04-14 CN CN2008100901869A patent/CN101252782B/en not_active Expired - Fee Related
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1859776A (en) * | 2006-01-26 | 2006-11-08 | 华为技术有限公司 | Roaming user data route optimizing method in 3GPP evolution network |
Non-Patent Citations (2)
| Title |
|---|
| 3GPP TSGSSA.Architecture enhancements for non-3GPP accesses.《3GPP TS 23.402 V8.1.1》.2008,全文. * |
| 3GPP TSGSSA.General Packet Radio Service (GPRS) enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access.《3GPP TS 23.401 V8.1.0》.2008,全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101252782A (en) | 2008-08-27 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101252782B (en) | Method for obtaining terminal roam access mode | |
| US9019890B2 (en) | Method for selecting a policy and charging rules function server on a non-roaming scene | |
| US9137652B2 (en) | Method for implementing policy and charging control in a roaming scene | |
| CN101646149B (en) | Method for deleting session messages in DRA | |
| US8817612B2 (en) | Method for implementing limited policy and charging control and system thereof | |
| US9351325B2 (en) | Policy control method and system for converged network | |
| US8943165B2 (en) | Method for reselecting bearer binding and event report function | |
| US8811342B2 (en) | Method and system for deleting redundant information of home policy and charging rules function | |
| CN102340866B (en) | A kind of method and system of reporting access information of fixed network | |
| CN101267319B (en) | A method for distributing control rule of policy billing | |
| US8463889B2 (en) | Method for provisioning and installing event triggers | |
| US20100281170A1 (en) | Method for selecting a policy and charging rules function entity in the non-roaming scenario | |
| WO2011015140A1 (en) | Method, system and apparatus for mobile telecommunication paging | |
| CN102340766B (en) | Home network obtains the method and system of net element information in visited network | |
| CN101998513B (en) | Method and system for controlling policy and charging rules function (PCRF) load balance and redirect diameter routing agent (DRA) | |
| CN102378143B (en) | A kind of method and system triggering fixed network mobile fusion policy conferring | |
| CN102378144B (en) | A kind of method and system setting up session, policy distribution | |
| CN102932915B (en) | A kind of method and system for establishing session | |
| HK1143906B (en) | A method for selecting a policy and charging rules function server on a non-roaming scene |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20111207 Termination date: 20200414 |
|
| CF01 | Termination of patent right due to non-payment of annual fee |