WO2004112319A1 - Method of querying route information in the environment of wlan interacting with mobile network - Google Patents

Abstract

The invention discloses a method of querying route information in the environment of WLAN interacting with mobile network, which includes the following steps: storing the IP address of user device and user id in packet data network gateway, and setting up the mapping of IP address and user id; according the IP address in the received data packet data network gateway looks up the corresponding user id of this IP address in itself, sends router query request with user id in it to the routing register device ; according the mapping of the user id of signed user device and the attributive authentication server routing information in itself, the routing register device queries the attributive authentication server routing information of current target user device , and returns the results. This invention realizes the query of the attributive authentication server routing information of UE in WLAN-3 GPP interacting network.

Description

 Method for querying routing under wireless LAN and mobile network interworking

Technical field

 The present invention relates to a route query technology in wireless communication, and in particular, to a method for querying a route in the case of interworking between a wireless local area network and a Third Generation Partnership Project (WLAN-3GPP) network. Background of the invention

 With the rise and development of WLAN technology, WLAN and wireless mobile communication networks include the Global System for Mobile Communications (GSM), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Synchronous Code Division Multiple Access (TD) -SCDMA) and the integration of CDMA2000 and other networks are becoming the focus of current research. Among them, GSM, CDMA, WCDMA, TD-SCDMA have been included in 3GPP, and CDMA 2000 belongs to 3GPP2.

 3GPP TS23.234 defines the WLAN-3GPP interworking scenario 3 as follows: After the UE is authorized by the 3GPP home network service, a tunnel establishment process is performed between the UE and the PDG. At this time, the PDG's subscription information and tunnel information are stored in the PDG. And other related information, this process is a mobile station initiated (MO) process. The non-roaming situation and roaming situation for interworking scenario 3 are described as follows:

Referring to FIG. 1, a simplified network structure diagram in a non-roaming scenario where a WLAN and a 3GPP network interworking scenario 3 is not shown. The WLAN access network 102 is directly connected to the external Internet (intranet) or intranet (intranet) 104, and the user equipment (UE) 101 and the 3GPP home network (3GPP Home Network) 3GPP authentication and authorization plan respectively through the WLAN access network 102 A charge server (AS, 3GPP AAA Server) 103 is connected to a packet data gateway (PDG, Packet Data Gateway) 105, and the PDG 105 is connected to a packet data network (PDN, Packet Data Network) that is part of an external network through a Wi interface. Generally, , When the UE 101 wishes to directly access the Internet / Intranet 104 through the WLAN access network 102, it may apply for a service of the interworking scenario 2 to the 3GPP home network. If the UE 101 also wants to access 3GPP packet switching (PS) domain services, and accesses the PDN through the WLAN-3GPP network, it may further apply to the 3GPP home network for an interworking scenario 3 service. That is, the UE 101 initiates a service authorization process request for the interworking scenario 3 to the AS 103 of the 3GPP home network. The AS 103 of the 3GPP home network performs service authentication and authorization on the service request. If successful, the AS 103 sends an access permission message to the user. The AS 103 allocates the corresponding PDG 105 to the UE 101, and a tunnel is established between the UE 101 and the allocated PDG 105. In addition, the charging gateway (CGw) 107a / charging information collection system (CCF) 107a / online charging system (OCS) 107b records charging information according to the network usage of the UE 101. The tunnel established for non-roaming situations is UE-WLAN-PDG. At this time, the UE 101 can access the 3GPP PS domain services, and the UE 101 can communicate with the PDN belonging to the external network through the tunnel with the PDG 105. The PDN includes all packet data networks other than mobile networks such as Intemet and Intranet.

The roaming situation in the WLAN access network and 3GPP interworking scenario 3 is similar to the non-roaming situation, and its tube network structure is shown in FIG. 2. In the case of roaming, the WLAN access network 102 is connected to the 3GPP home network through a 3GPP Visited Network. The WLAN access network 102 is connected to a UE 101, a 3GPP AAA server proxy (AS Proxy) 201, an Internet / Intranet 104, and a wireless access gateway (WAG) 202. The UE 101 may apply to the 3GPP home network for the interworking scenario 2 service access to the Internet / Intranet 104 through the 3GPP access network. If the UE 101 also wishes to apply for the interworking scenario 3 service and access the 3GPP PS domain service, the UE 101 needs to initiate a service authorization process to the 3GPP home network through the 3GPP access network. This process is also between the UE 101 and the AS 103 of the 3GPP home network. When the authorization is successful, the AS 103 allocates the corresponding home PDG 105 to the UE 101, and the UE 101 establishes a tunnel between the WAG 202 and the allocated PDG 105 through the 3GPP access network. For roaming, the established tunnel is UE-WLAN-WAG-PDG. At this time, UE 101 can access 3GPP PS domain services of the home network.

 In the above two cases, after the tunnel between the UE and the PDG is established, the UE can access the 3GPP PS domain services through the PDG, that is, after the data sent by the UE reaches the PDG through the tunnel, the PDG decapsulates the data. The data is then sent to the external network via the Wi interface. However, whether in roaming or non-roaming situations, when an external network initiates a mobile station termination (MT) procedure to send data to the UE, if no tunnel is established between the UE and the PDG, service data sent from the external network reaches the PDG Later, the PDG needs to know the authentication server to which the target UE belongs, that is, the AS address, in order to establish a tunnel between the UE and the PDG through the AS, and then send service data to the user. However, a method for how the PDG obtains routing information of the AS to which the target UE belongs has not yet been proposed. Summary of the Invention

 In view of this, the main object of the present invention is to provide a method for querying a route in a WLAN-3GPP interworking network, so that the PDG device can easily query the route to the authentication server to which the target UE belongs.

 A method for querying routing in the case of wireless local area network and mobile network interworking includes the following steps: a) storing an IP address and a user identification of a user equipment in a packet data gateway, and establishing a mapping relationship between the IP address and the user identification;

 b) the data of the external network reaches the packet data gateway and triggers a routing query, and the packet data gateway searches for the user ID corresponding to the IP address in itself according to the IP address of the target user equipment contained in the received data;

 c) the packet data gateway sends a routing query request including the user identity to the routing storage device;

d) The routing registration device searches for the authentication service to which the current target user equipment belongs according to the mapping relationship between the user identifier of the contracted user equipment established by itself and the routing information of the associated authentication server. The router routes information and returns the search results.

 In the method, the user identity of the user equipment is an international mobile subscription user identity (IMSI) of the user equipment, or a wireless local area network temporary mobile subscription user identity (WTMSI).

 In the method, the route registration device is a home subscription user service device. Step a) further includes: establishing a communication connection between the packet data gateway and the route registration device.

 The routing storage device in this method is a home subscription user service device;

 Step c) further includes: the packet data gateway sends a routing query request to an authentication server connected to the packet data gateway, and the authentication server forwards the query request to the routing storage device;

 Step d) further includes: the routing registration device sends the search result to the authentication server, and the authentication server forwards the search result to the packet data gateway.

 The routing storage device in the method is a home subscription user service device and an authentication server connected to the packet data gateway; and further includes:

 cdl) the packet data gateway sends a routing query request to the authentication server, and the authentication server searches for the routing information of the authentication server to which the current target user equipment belongs in itself, and if found, returns the packet server to the packet data gateway. The response information of the routing information ends the routing query process; otherwise, the authentication server forwards the routing query request to the home subscription user service device;

 cd2) the home subscription user service device searches itself for the routing information of the authentication server to which the current target user equipment belongs, and if found, returns the response information containing the routing information of the authentication server to the authentication server; otherwise, returns to the authentication server Carry response information with error reason;

 cd3) the authentication server forwards the received response information to the packet data gateway.

After the authentication server receives the routing information returned from the home subscription user service device, the method further includes: the authentication server includes the target user equipment included in the response message The own authentication server route is saved.

 In the method, the route registration device is an authentication server connected to the packet data gateway. Step a) further includes: storing in the authentication server the routing information of the authentication servers to which all contracted user equipment belongs, and establishing each contracted user. The mapping relationship between the device user ID and the routing information of the authentication server to which it belongs.

 In this method, the authentication server is a 3GPP authentication, authorization and accounting server (AS), and the routing information of the authentication server is an address of the AS.

 In this method, the home subscription user service device is a home subscription user server (HSS). In the method, the home subscription user service device is a home location register (HLR), and step a) further includes: saving the routing information of the authentication server to which the subscription user device belongs in the home location register, and establishing the user identity and belonging of the subscription user device. Mapping relationship of authentication server routing information.

 As can be seen from the above solution, the method for querying routing in the interworking network of the present invention implements the WLAN-3GPP interworking network by configuring related information of the contracted mobile user equipment in the packet data gateway and querying the routing storage device. The query on the routing of the authentication server to which the target UE belongs, thereby laying a foundation for the external network data to be sent to the user equipment through the WLAN-3GPP interworking network. Brief description of the drawings

 FIG. 1 is a schematic structural diagram of a non-roaming scenario in a WLAN and 3GPP network interworking scenario; FIG. 2 is a schematic structural diagram of a roaming situation in a WLAN and 3GPP network interworking scenario; FIG. 3 is a schematic structural diagram of a network structure according to Embodiment 1 of the present invention;

 4 is a working flowchart of Embodiment 1 of the present invention;

 5 is a schematic diagram of a network structure according to Embodiments 2 and 3 of the present invention;

6 is a working flowchart of Embodiment 2 of the present invention; 7 is a working flowchart of Embodiment 3 of the present invention;

 8 is a schematic diagram of a network structure according to Embodiment 4 of the present invention;

 FIG. 9 is a working flowchart of Embodiment 4 of the present invention. Mode of Carrying Out the Invention

 The present invention will be described in further detail below with reference to the drawings and specific embodiments.

 At present, for ordinary mobile users, the information about the UE stored in the home subscription service device of the 3GPP network, that is, the HLR or HSS includes: the user identity of the UE, the subscription information of the UE, and the security parameters of the UE. After the UE has passed the access authentication of the AS, the address of the AS to which the UE belongs is also stored in the HLR / HSS, and it is stored in the 3GPP AS: the user identity of the UE, the HLR / HSS address, the status information of the UE, and the UE's subscription Information, UE authentication, authorization parameters and other information. The user identifier may be the IMSI or WTMSI of the user.

 In view of this situation, the present invention configures parameters such as the IP address of the UE and the user identifier in the PDG in advance, and establishes a mapping relationship between the IP address of the UE and the user identifier. The data sent from the external network arrives at the PDG and triggers a routing query. The PDG finds the user ID of the user based on the IP address of the target user in the data, and then sends a query request containing the user ID to the routing storage device to query the target UE's ownership. AS routing. The route registration device may be a home subscription user service device. The home subscription user service device has stored the user identifier of the UE, the address of the AS to which the UE belongs, and the mapping relationship between the user identifier of the UE and the address of the own AS. Convenience. In addition, the route registration device may also use an AS adjacent to the PDG. Since the user identity of the UE already exists in the AS, it is necessary to add the address of the AS to which the UE belongs in the AS serving as the route registration device.

 The following are four schemes for querying the routing information of the AS to which the current UE belongs according to the present 3GPP home network structure of the roaming or non-roaming situation of the present invention:

Solution 1: The PDG directly queries the HLR / HSS for routing: first, the PDG and the HLR, or A direct interface is established between the PDG and the HSS. The PDG directly sends a routing query message to the HLR / HSS, and the HLR / HSS returns the routing information of the AS to which the UE belongs.

 In this solution, since there is no direct interface connection between the PDG and the home subscriber service equipment in the existing WLAN-3GPP network structure, firstly, an interface needs to be added between them to establish a connection. Referring to FIG. 3, different interfaces are added according to different network structures used. As shown in FIG. 3a, for a network using HSS 106a as a home subscriber service device, Wc is added between PDG 105 and HSS 106a. Interface; as shown in FIG. 3b, for a network using HLR 106b as a home subscriber service device, a Gc, interface is added between PDG 105 and HLR 106b.

 Refer to the message flow of the first scheme shown in FIG. 4.

 The process of implementing route query using HSS includes:

 Step 401: The PDG sends a request message to the HSS to query the AS routing information of the UE through the Wc interface. The request message includes the HSS address, the PDG address, and the UE's user identifier.

 Step 402: After receiving the request message, the HSS searches for the routing information of the AS to which the requested UE belongs according to the user identifier of the request message, and returns a response message to the requested PDG. If the HSS finds the requested routing information, The response message includes the user identifier of the UE and the address of the AS to which the UE belongs; if the HSS cannot find the requested routing information, the response message returned contains the corresponding error cause.

For the case of using HLR to implement route query, since the traditional HLR does not involve AS-related services, there is no AS routing entry in the HLR routing table. Existing parameters and signaling of General Packet Radio Service (GPRS) are not involved. AS part. In order to make the best use of existing resources, this solution uses Gc. The interface connects PDG and HLR. This interface still uses the existing parameters and signaling of GPRS. At the same time, the routing information of AS will be saved in the form of MSC / SGSN routing in HLR That is, save the AS's route as the route of a certain MSC or SGSN in The routing position of the MSC or SGSN, so that the PDG queries the routing information of the AS to which the UE belongs through this interface.

 Then, during the route query process:

 In step 401, the AS routing query request message sent by the PDG may use the existing MAP_SEND_ROUTING_IP_FOR_ GPRS request message to be sent to the HLR through the Gc interface to query the AS routing information to which the UE belongs. The UE is represented by a user identifier IMSI or WTMIS.

 In step 402, the HLR receives the message, and after the search is completed in itself, the existing MAP_SEND_ROUTING_INFO JFOR_GPRS response message is used as a response message to return the query result to the PDG. If the search is successful, it is included in the message. Contains the user identity of the UE and the address of the AS to which the UE belongs. Among them, the information element (IE) "GSN Address" of the MAP_SEND_ ROUTING_ INFO_ FOR_ GPRS response message is used to place the address identifying the AS to which the UE belongs. If the HLR cannot query the routing information of the AS to which the UE belongs, the response message contains the corresponding error cause.

 In the second scheme, the PDG queries the HLR / HSS for routing through the AS forwarding request: Unlike the first scheme, the PDG sends the route query message to the AS connected to it, and then the AS forwards the route query message to the HLR7HSS. After the route search is completed, , HLR7HSS returns a route query response message to the PDG via the AS.

 This solution uses the HLR / HSS address stored in the AS, and the interworking messages between PDG and HLR / HSS are forwarded through the AS. Therefore, this solution can use the existing network structure without adding interfaces. Referring to FIG. 5, FIG. 5a is a network using HSS 106a as a home subscriber service device, and PDG 105 and HSS 106a are indirectly connected through AS 103. FIG. 5b is a network using HLR 106 b as a home subscriber service device, PDG 105 It is indirectly connected to HLR 106b through AS 103.

Refer to the message flow of the second scheme shown in FIG. 6. The situation of using HSS to query the route includes:

 Step 601: The PDG sends a PDG query message to the AS through the Wm interface to query the routing information of the AS to which the target UE belongs. The destination address of the request message is the HSS address, the source address is the PDG address, and the UE identifier is included.

 Step 602: The request message is first sent to the AS via the Wm interface. After receiving the request message, the AS performs protocol conversion on the message and forwards the message to the HSS through the Wx interface.

 Step 603: After receiving the request message, the HSS searches for AS routing information of the requested UE in itself and returns a response message to the PDG. The source address of the response message is the HSS address and the destination address is the PDG. If the HSS finds the requested routing information, the response message contains the user ID of the UE and the address of the AS to which the UE belongs; if the HSS does not find the requested routing information, the response message returned contains the corresponding error cause. This step The same as described in step 402.

 Step 604, the response message is sent to the AS via the Wx interface, and the AS performs protocol conversion on the received response message and returns it to PDGo.

 For the case of using HLR to implement route query, the method of saving AS routes in HLR and HLR using query response signaling is the same as scheme one, that is, when AS passes D, interface or Gr, the interface forwards PDG to HLR to query the route of AS to which the UE belongs For information messages, use MAP_SEND_ ROUTING_ INFO_ FOR_ GPRS request message as the routing information message for the PDG to query the AS of the UE, and use MAP_SEND_ ROUTING_ INFO_ FOR_ the GPRS response message as the PDG to query the routing information for the AS of the UE. Response message. Use the IE "GSN Address" of the MAP-SEND- ROUTING- INFO- FOR- GPRS response message to place the address identifying the AS to which the UE belongs. The other processes are the same as in the case of HSS.

Solution 3: The PDG queries the AS for the route, and the AS queries the HLR / HSS for the route: The PDG directly queries the AS for the routing information of the AS to which the UE belongs through the Wm interface, and the AS then The HLR / HSS queries the routing information of the AS to which the UE belongs, and then the AS returns the routing information returned from the HLR / HSS to the PDG.

 This solution still uses the existing network structure, and its network structure is the same as that in solution 2 and is still the structure shown in Figure 5.

 The message flow of this solution is shown in Figure 7.

 For the case of using HSS query routing:

 Step 701: The PDG queries the AS for the routing information of the AS to which the UE belongs. The PDG sends a PDG query routing information message to the AS through the Wm interface to the AS to which the target UE belongs. The destination address in the message is the AS address, the source address is the PDG address, and the user identifier of the UE is included.

 Step 702: After receiving the request message, the AS first searches the AS route to which the target UE belongs in itself. If the AS finds the routing information of the AS to which the requested target UE belongs, it returns a corresponding message containing the routing information to the PDG. Find the AS route to which the target UE of the request belongs, and then perform protocol conversion on the message, and forward the request message to the HSS through the Wx interface according to the HSS address stored in the AS. In the forwarded message, the destination address is changed to an HSS address, and the source address is an AS address.

 Step 703: After receiving the request message, the HSS searches for the requested routing information and returns a response message to the AS. The destination address of the response information is the AS address and the source address is the HSS address. If the HSS finds the requested routing information, the response message contains the user ID of the UE and the address of the AS to which the UE belongs. If the routing query fails, the response message contains the corresponding error cause.

In step 704, the AS receives the response message, performs protocol conversion on the response message, and returns it to the PDG. The destination address of the response message is changed to the PDG address, and the source address is the AS address. At this time, the AS can also save the AS address of the target UE in the response message. When the PDG next queries the AS for the AS address of the target UE, the AS can directly return the AS address to the PDG without Need to check with HSS again.

 For the interworking network using HLR, it is the same as scheme 1 and scheme 2, that is, when the AS forwards the PDG query routing information message of the AS to which the UE belongs to the HLR via the D 'interface or Gr, the interface adopts MAP_SEND_ROUTING_INFO — FOR— The GPRS request message is used as the routing information message for the PDG query ΌΈ owning AS, and the MAP_SEND — ROUTING — INFO — FOR — GPRS response message is used as the PDG query routing information response message for the AS to which the UE belongs. Use the IE "GSN Address" of the MAP_SEND_ ROUTING_ INFO_ FOR_ GPRS response message to identify the address of the AS to which the UE belongs. The other processes are the same as in the case of HSS.

 In the fourth solution, the PDG queries the AS for routing: The PDG directly sends routing query information to the AS through the Wm interface, and the AS directly returns the routing information to the PDG.

 In this solution, in addition to the information such as the user identifier of the UE and the subscription information of the UE, the AS adjacent to the PDG should also store at least the AS addresses of all authorized interworking network users. See Figure 8 for its network structure. PDG 105 is directly connected to AS 103, which is a route registration device. Since this solution does not involve the HLR / HSS part, it can be connected or not connected with the HLR / HSS. Any structure shown in Figures 3 and 5 can be used.

 Refer to the message flow of the fourth scheme shown in FIG. 9.

 Step 901: The PDG queries the AS for routing information of the AS to which the UE belongs. The PDG sends a PDG query to the AS for the routing information message of the AS to which the UE belongs. The destination address of the message is the AS address, the source address is the PDG address, and the UE identifier is included.

Step 902: After receiving the message, the AS searches for the AS routing information of the requested target UE according to the user identifier of the request message, and then returns a response message to the PDG. If the AS finds the AS routing information of the requested target user, it responds The message contains the user identifier of the UE and the address of the AS to which the UE belongs. If the query routing process fails, the response message contains the corresponding error cause. The above are only preferred embodiments of the present invention and are not intended to limit the present invention. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention shall be included in the present invention. Within the scope of protection.

Claims

Claim  1. A method for querying routing in the case of wireless local area network and mobile network interworking, comprising the following steps:  a) save the IP address and user identification of the user equipment in the packet data gateway, and establish a mapping relationship between the IP address and the user identification;  b) the data of the external network reaches the packet data gateway and triggers a routing query, and the packet data gateway searches for the user ID corresponding to the IP address in itself according to the IP address of the target user equipment contained in the received data;  c) the packet data gateway sends a routing query containing the user identity to the routing storage device;  d) The routing registration device searches for the routing information of the authentication server to which the current target user equipment belongs, and returns the search result according to the mapping relationship between the user identifier of the contracted user equipment established by itself and the routing information of the associated authentication server.  2. The method according to claim 1, wherein the user identity of the user equipment is an International Mobile Subscriber Identity (IMSI) of the user equipment, or a WLAN temporary mobile subscriber identity (WTMSI).  3. The method according to claim 1, wherein the routing storage device is a home subscription user service device, and step a) further comprises: establishing a communication connection between the packet data gateway and the routing storage device.  4. The method according to claim 1, characterized in that the routing storage device is a home good service device for home subscribers; Step c) further includes: the packet data gateway sends a routing query request to an authentication server connected to the packet data gateway, and the authentication server forwards the query request to the routing storage device; Step d) further includes: the routing registration device sends the search result to the authentication server, and the authentication server forwards the search result to the packet data gateway.  5. The method according to claim 1, wherein the route registration device is a home subscription user service device and an authentication server connected to the packet data gateway;  Steps c) and d) further include:  cdl) the packet data gateway sends a routing query request to the authentication server, the authentication server searches itself for the routing information of the authentication server to which the current target user equipment belongs, and if found, returns the packet server to the packet data gateway The response information of the routing information ends the routing query process; otherwise, the authentication server forwards the routing query request to the home subscription user service device;  cd2) the home subscription user service device searches itself for the routing information of the authentication server to which the current target user equipment belongs, and if found, returns the response information containing the routing information of the authentication server to the authentication server; otherwise, returns to the authentication server Carry response information with error reason;  cd3) the authentication server forwards the received response information to the packet data gateway.  6. The method according to claim 5, wherein after the authentication server receives the routing information returned from the home subscription user service device, the method further comprises: the authentication server including the target user equipment included in the response message. The own authentication server route is saved.  7. The method according to claim 1, wherein the routing storage device is an authentication server connected to a packet data gateway, and step a) further comprises: storing, in the authentication server, all the subscription user equipments to which they belong. The routing information of the authentication server, and a mapping relationship between the user identity of each contracted user equipment and the routing information of the associated authentication server is established. 8. The method according to claim 1, 4, 5, 6, or 7, characterized in that the authentication server is a 3GPP authentication, authorization and accounting server (AS), and the path of the authentication server The message is the address of the AS.  9. The method according to claim 3, 4, 5 or 6, wherein the home subscriber service device is a home subscriber server (HSS).  10. The method according to claim 3, 4, 5, or 6, characterized in that the home subscription user service device is a home location register (HLR), and step a) further comprises: saving the subscription user in the home location register. The routing information of the authentication server to which the device belongs, and the mapping relationship between the user identity of the subscribed user device and the routing information of the authentication server to which it belongs.