WO2006037268A1

WO2006037268A1 - A method for the service deregistering based on the IP access

Info

Publication number: WO2006037268A1
Application number: PCT/CN2005/001597
Authority: WO
Inventors: Wenlin Zhang; Jie Wang; Xiaoqin Duan
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2004-10-07
Filing date: 2005-09-29
Publication date: 2006-04-13
Also published as: CN1758635A; CN1758635B

Abstract

A method for the service deregistering based on the IP access, could cause the deregisting process by the user terminal, the AAA server or the IP gateway, and delete the dependent service registering information stored in the AAA server, the user information storage unit and the IP gateway during the deregistering process. The invention discloses three different solutions about causing the deregisting process by the different entities. Using this invention, the user information storage unit can timely get the information that the current user terminal could not use 3GPP network service, and the information registered in the IP gateway by the user terminal can be updated according to the changes of the user access network state. Therefore, when the other network entity requests for the address information of the user terminal, it does not return IP gateway address to avoid the error during next process.

Description

Service deregistration method based on IP access

The invention relates to a service deregistration technology, in particular to a service deregistration method based on IP access. Background of the invention

Due to the increasing demand for wireless access rates, wireless local area networks (WLANs) have emerged to provide high-speed wireless data access in a small range. Wireless LAN includes many different technologies. One of the most widely used technical standards is IEEE 802.11b, which uses the 2.4GHz band and the highest data transmission rate of 11Mbps. The IEEE 802.11g and Bluetooth technologies are also used. Among them, 802.11g has a maximum data transfer rate of 54Mbps. Other new technologies such as IEEE 802.11a and ETSI BRAN Hiperlan2 use the 5GHz band and the maximum transfer rate is 54Mbps.

Although there are many different wireless access technologies, most WLANs are used to transport Internet Protocol (IP) packet data packets. For a wireless IP network, the specific WLAN access technology used is transparent to the upper layer IP. The basic structure is to use the access point (AP) to complete the wireless access of the user terminal, and to form an IP transmission network through network control and connection of the connected devices.

With the rise and development of WLAN technology, WLAN and various wireless mobile communication networks, such as: GSM, Code Division Multiple Access (CDMA) systems, Wideband Code Division Multiple Access (WCDMA) systems, Time Division-synchronous Code Division Multiple Access (TD) -SCDMA) Interoperability of systems and CDMA2000 systems is becoming the focus of current research. In the 3rd Generation Partnership Project (3GPP) standardization organization, the user terminal can connect to the Internet (Internet), the intranet (Intranet) through the WLAN access network, and can also access the home network of the 3GPP system via the WLAN. Or access network connection of the 3GPP system, specifically, when the WLAN user terminal accesses locally, it is connected to the home network of 3GPP via the WLAN access network, as shown in FIG. 2; when roaming, via WLAN The access network is connected to the access network of the 3GPP, and some entities in the 3GPP access network are respectively interconnected with corresponding entities in the 3GPP home network, for example: 3GPP Authentication and Authorization Accounting (AAA) proxy and 3GPP home network in the 3GPP access network 3GPP Authentication and Authorization Accounting (AAA) server; 3GPP access network wireless LAN access gateway (WA^G) and 3GPP home network packet data gateway (PDG, Packet Data Gateway), etc., as shown in Figure 1. Show. FIG. 1 and FIG. 2 are schematic diagrams showing the networking structure of the WLAN system interworking with the 3GPP system in the case of roaming and non-roaming.

Referring to FIG. 1 and FIG. 2, in the 3GPP system, the primary packet belongs to the subscription subscriber server (HSS)/home location register (HLR), the 3GPP AAA server, the 3GPP AAA proxy, the WAG, the packet data gateway, and the offline charging system. (Offline Charging System) and Online Billing System (OCS). The user terminal, the WLAN access network, and all entities of the 3GPP system jointly construct a 3GPP-WLAN interaction network, and the 3GPP-WLAN interaction network can serve as a wireless local area network service system. The 3GPP AAA server is responsible for the user's rights, authorization, and charging. The charging information sent by the WLAN access network is collected and transmitted to the charging system; the packet data gateway is responsible for the user data from the WLAN access network to the 3GPP. The data transmission of the network or other packet network; the charging system mainly receives and records the user charging information transmitted from the network, and further includes the OCS, which instructs the network to periodically transmit the online charging information according to the cost of the online charging user, and performs Statistics and control.

In the case of roaming, when the WLAN user terminal wants to directly access the Internet/Intranet, after the user terminal completes the access authentication and authorization through the WLAN access network and the AAA server (AS), the user terminal can access through the WLAN access network. Intemet/Intranet. If the WLAN user terminal also wants to access the 3GPP packet-switched (PS) domain service, the service of the Scenario 3 can be applied to the 3GPP home network in one step, that is, the WLAN user terminal initiates the interworking scenario 3 to the AS of the 3GPP home network. The service authorization request, the AS of the 3GPP blame the network performs service authentication and authorization for the service authorization request. If successful, the AS sends an access permission message to the user terminal, and the AS allocates the corresponding PDG to the user terminal, and the user terminal and the device Assigned between PDGs After the tunnel is established, the 3GPP PS domain service can be accessed. At the same time, the offline charging system and the OCS record the charging information according to the network usage of the user terminal. In the case of roaming, when the WLAN terminal wants to directly access the Internet/Intranet, the user terminal can apply for access to the Internet/Intranet through the 3GPP access network to the 3GPP home network. If the user terminal also wants to apply for the interworking scenario 3 service and access the 3GPP PS domain service, the user terminal needs to initiate a service authorization process to the 3GPP home network through the 3GPP access network, and the service authorization process is also performed on the user terminal and the AS of the 3GPP home network. After the authorization is successful, the AS allocates a corresponding home PDG to the user terminal. After the user terminal establishes a tunnel between the WAG in the 3GPP access network and the allocated PDG, the user terminal can access the 3GPP PS domain of the home network. business.

According to the 3GPP protocol, in the existing 3GPP-WLAN interactive network, the authentication and authorization process of the WLA1ST user access network is as shown in FIG. 3, and includes the following steps:

Steps 301-302: The current WLAN terminal and the WLAN access network establish a wireless connection according to the procedure specified by the 3GPP protocol; and then initiate an access authentication process between the current WLAN user terminal and the 3GF»P AAA server, the access authentication Responsive to message interaction through the Extensible Authentication Protocol (EAP).

Steps 303 to 304: After receiving the access authentication request, the 3GPP AAA server determines whether there is authentication information for the current WLAN user terminal, and if not, obtains the authentication information of the current WLAN user terminal from the HSS, for example, : Authentication quintuple/triple. And, if the user signing letter of the current LAN user terminal does not exist in the 3GPP AAA server, for example, the authorization information and the user temporary identifier are also obtained from the HSS. That is to say, if the 3GPP AAA server does not have user information itself, it needs to be obtained from the HSS.

Step 305: The 3GPP AAA server may send the policy execution information to the WAG in the access public land mobile network (VPLMN) to which the current WT N user terminal roams. This step is optional.

Step 306: If the authentication and authorization are successful, the 3GPP AAA server accesses the WLAN. The network sends an access permit message, including the EAP Success message, which carries the connection authorization information, such as: access filtering rules, tunnel attributes, and the like.

Step 307: After receiving the allowed access message, the WLAN access network sends an authentication success message EAP Success to the current WLAN user terminal.

Step 308: If the current WLAN user terminal does not have registration information for the access authentication 3GPP AAA server currently provided in the HSS, the 3GPP AAA server that provides authentication for the current WLAN user terminal is registered in the HSS, and the registration message is based on the user. Temporary identity to identify the user.

When the WLAN user is not in the coverage of the WLAN network, the WLAN network may initiate a process for separating the WLAN user terminal from the 3GPP network. According to the 3GPP protocol, in the existing 3GPP-WLAN interaction network, the WLAN network actively initiates The process of separating the WLAN user terminal from the 3GPP network is as shown in FIG. 4, and includes the following steps:

Steps 401~402: The WLAN detects that a session of a WLAN user terminal needs to be terminated to the 3GPP AAA server/proxy. The IKE WLAN initiates a Wa session termination process to the AAA server/proxy. For example, when the WLAN user terminal leaves the coverage of the WLAN, the WLAN network side initiates a Wa session termination process.

Step 403: If the WLAN user terminal has established a tunnel connection with the one or more PDGs, the AAA server/proxy needs to delete the tunnel connection, and the AAA server/proxy initiates a tunnel deletion request to the PDG via the Wm interface, and the PDG deletes the previous WLAN. The tunnel established by the user terminal releases related resources.

Step 404: The AAA server/proxy deletes the filter established by the WAG for the tunnel by interacting with the WAG.

Step 405: When the AAA server determines that the registration information of the WLAN user terminal needs to be deleted, the AAA server sends a notification message to the HLR/HSS through the Wx interface, requesting the HLR/HSS to set the information of the WLAN user terminal to Purge, indicating that the WLAN user terminal registration message It has been deleted in the AAA, and then the HLR/HSS deletes the associated information of the stored WLAN user terminal and the AAA server, such as the address information of the AAA server associated with the WLAN user terminal.

The operator can also force a WLAN user to separate from the 3GPP network by setting data for the HLR/HSS. According to the 3GPP protocol, in the existing 3GPP-WLAN interactive network, the process of separating the WLAN user terminal from the 3GPP network due to the HLR/HSS is as shown in FIG. 5, and includes the following steps:

The 501.

Step 503: If the WLAN access connection of the user terminal currently exists, the AAA server initiates a session termination process to the WLAN network via the Wa interface.

Step 504: If a wireless connection exists, the WLAN network releases the wireless interface connection through the technology defined in the WLAN specification.

Step 505: If the WLAN user terminal has established a tunnel connection with one or more PDGs, the AAA server needs to delete the tunnel connections, and the AAA server initiates a tunnel deletion request to the PDG via the Wm interface, and the PDG deletes the previously established connection with the WLAN user terminal. Tunnel, release related resources.

Step 506: The AAA server deletes the filter established by the WAG for the tunnel by interacting with the WAG.

In addition, when the 3GPP network adopts online charging for the accessed WLAN user, the online charging system (OCS) can also initiate the process of separating the WLAN users accessing the 3GPP network when the user credit is exhausted. . According to the 3GPP protocol, in the existing 3GPP-WLAN interactive network, the process of separating the WLAN user terminal from the 3GPP network caused by the online charging system is as shown in FIG. 6, and includes the following steps:

Steps 601 to 603: The 3GPP AAA server performs online charging for the WLAN access of the user; if the credit of a WLAN user terminal is exhausted, the online charging system rejects the 3GPP AAA service. The server requests a credit request for the WLAN access of the user terminal; at this time, the AAA server initiates a session termination process to the WLAN network via the Wa interface.

Step 604: The WLAN network releases the wireless interface connection through the technology defined in the WLAN specification.

Step 605: If the WLAN user terminal has established a tunnel connection with one or more PDGs, the AAA server/proxy needs to delete the tunnel connections, and the AAA server/agent initiates a tunnel deletion request to the PDG via the Wm interface, and the PDG deletes the previous A tunnel established by a WLAN user terminal releases related resources.

Step 606: The AAA server/proxy deletes the filter established by the WAG for the tunnel by interacting with the WAG.

Step 607: If the session termination process is not initiated in step 603, that is, the purge process, the AAA server/proxy initiates a purge process to the HLR/HSS, and notifies the HLR/HSS that the registration information of the WLAN user terminal previously registered in the AAA server has been got canceled.

Currently, according to the discussion of the 3GPP protocol, the network architecture and process related to short message service (WLAN over WLAN) on the WLAN in 3GPP is as shown in FIG. 7. FIG. 7 is a short message support architecture based on IP access. As can be seen from FIG. 7, the UE can interact with the mobile switching center (GMSC/SMS-IWMSC) of the gateway mobile switching center/short message-interworking function through the MSC or SGSN. The UE may also interact with the GMSC/SMS-IWMSC through an IP short message gateway (IP-MESSAGE-GW), where the IP-MESSAGE-GW is a new network entity added to the existing 3GPP-WLAN interaction architecture. The transmission of short messages between the IP client (Client) and the GSM/UMTS network is provided, where the UE is the IP Client. That is, the IP-MESSAGE-GW can interact with the GMSC/SMS-IWMSC using the Mobile Application Protocol (MAP), receive short messages from the GMSC/SMS-IWMSC, or send to the GMSC/SMS-IWMSC. Short message; You can also use the IP bearer-based protocol to interact with the IP Client, receive short messages from the IP Client, or send short messages to the IP Client.

Short message origination in SMGPP (SM-MO, Short Message Mobile Origination) The process, that is, the sending process of the IP client to the Short Message Service Centre (SM-SC) is shown in Figure 8, which includes the following steps:

Step 801: The IP client establishes a tunnel with the PDG. Here, the IP client is a WLAN UE. Step 802: After the tunnel is established, the IP client registers with the IP-MESSAGE-GW.

Step 803: The IP client forwards the short message to the IP-MESSAGE-GW by using an IP bearer-based protocol, where the IP bearer-based protocol may be WAP, SMPP, MMPP, XML, SIP,

SMTP.

Step 804: The IP-MESSAGE-GW parses the short message from the IP message, and forwards the parsed short message to the SMS-IWMSC by using standard MAP signaling similar to that used by the MSC or the SGSN to send the short message to the SMS-IWMSC. The standard MAP signaling is defined in 3GPP TS 23.040.

Steps 805 to 806: After receiving the short message sent by the IP-MESSAGE-GW, the SMS-IWMSC forwards the short message to the SM-SC; after receiving the short message, the SM-SC sends a short message transmission report to the SMS-IWMSC. The forwarding process and the transmission reporting process are all defined in 3GPP TS 23.040.

Steps 807 to 808: After receiving the report, the SMS-IWMSC sends a short message transmission report to the IP-MESSAGE-GW; and the IP-MESSAGE-GW sends a short message transmission report to the IP client. The process by which the SMS-IWMSC sends a report to the IP-MESSAGE-GW is defined in 3GPP TS 23.040.

The existing 3GPP specifications only indicate that the WLAN IP client needs to register in the IP-MESSAGE-GW before using the short message service. Similarly, when the WLAN IP client does not need to use the short message service, the service registration process can also be initiated. . In addition, when the network detects that the WLAN IP Client actively leaves the WLAN network, or the network forces the WLAN IP Client to leave the WLAN network, for example, due to cost issues, the WLAN network may also initiate a service registration process, but currently The specification does not define the specific process of the service to register, nor does it define how to notify the HLR/HSS of the service registration information of the WLAN IP Client, so that the user status information of the IP-MESSAGE-GW and the HLR/HSS cannot be updated in time. Possible guidance The failure of the business process. It can be seen that there are imperfections in the prior art process, which affects the availability of the process. Summary of the invention

In view of this, the main purpose of the present invention is to provide a service deregistration method based on IP access, so that the user terminal can perform service registration through the IP gateway, and can notify the user information storage unit of the latest user status information in time.

Another object of the present invention is to provide a service deregistration method based on IP access, which can delete the service registration information currently saved by the deregistered user terminal in each network entity.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

A service deregistration method based on IP access, the method includes:

The IP gateway initiates a deregistration request to the user information storage unit, and notifies the user information storage unit to delete the stored related service registration information; and the IP gateway deletes the related service registration information stored by the IP gateway, the method further includes: the user terminal initiating the IP gateway The service de-registers the request, and the IP gateway initiates a registration request to the user information storage unit after receiving the de-registration request sent by the user terminal. The method further includes: the IP gateway returning a service deregistration response to the current user terminal.

In the foregoing solution, the initiating service deregistration request specifically includes the following steps:

The current user terminal sends a service deregistration request carrying the user terminal identification information to the packet data gateway;

Al2. The packet data gateway that received the service registration request forwards the received service deregistration request to the IP gateway.

The packet data gateway in the step a2 further includes: before checking the forwarding request to the registration request, the legality of the user terminal is checked according to the source IP address in the request sent by the current user terminal and the assigned tunnel identifier. After the check is passed, Then forward the service to the registration request. The method further includes: the IP gateway initiating a deregistration request to the AAA server to notify the AAA server to delete the stored related service registration information.

In the above solution, the service deregistration request carries the user terminal identifier, and the IP gateway notifying the user information storage unit to delete the related information includes:

Ml. The IP gateway carries the user terminal identifier carried in the request, parses the address information of the AAA server to which the current user terminal is registered, and then sends a logout user information request to the AAA server;

After receiving the request for canceling the user information, the AAA server sends a deregistration request to the user information storage unit according to the user terminal identifier carried in the request;

Bl3. After receiving the registration request, the user information storage unit deletes the related service registration information of the client previously stored by itself, and then returns a registration response to the AAA server. After receiving the response, the AAA service deletes the relevant information stored by the user terminal in itself. The business registration information is then returned to the IP gateway to log out the user information response.

After the user information storage unit receives the deregistration request, the step bl3 further includes: the user information storage unit notifying the application server that the user terminal cannot access the network service through the IP.

The related service registration information deleted by the user information storage unit in the step M3 includes at least: an IP-attached identifier, and an SS7 address information of the IP gateway.

The IP gateway receives the logout user information response, and the method further includes: the IP gateway *'J includes the related service including the correspondence between the permanent identifier of the user terminal and the IP address of the user terminal; The corresponding relationship is stored in a separate database, which is set in the IP gateway or is set in the AAA server, and the deletion process is initiated by the IP gateway or the AAA server to the database.

B21. The IP gateway parses the address information of the user information storage unit to which the current user terminal belongs according to the user terminal identifier carried in the request, and then sends the address information to the user information storage unit. already"

B22. After receiving the deregistration request, the user information storage unit deletes the related service registration information of the user terminal stored according to the user terminal identifier, and then returns a registration response to the IP gateway.

After receiving the deregistration request by the information storage unit, step b22 further includes: the user information storage list does not notify the application server that the user terminal cannot access the network service through the IP.

The related service registration information deleted by the user information storage unit in step b22 includes at least: an IP-attached identifier, and an SS7 address information of the IP gateway.

The IP gateway receives the deregistration response, and the method further includes: deleting, by the IP gateway, related service registration information that the user terminal does not identify the correspondence with the IP address of the user terminal. The corresponding relationship is stored in a separate database, which is set in the IP gateway or is placed in the AAA server, and the deletion process is initiated by the IP gateway or the AAA server to the database.

In the above, the user terminal is an IP client accessed through an IP network. The user information storage list is a home location register or a home subscription subscriber server.

The present invention provides a service deregistration method based on IP access, and the method includes:

The AAA server initiates a deregistration process to the IP gateway and the user information storage unit, notifying the user that the information storage unit and the IP gateway respectively delete the respective service registration information stored therein; after receiving the response, the AAA server deletes the self storage. Related business registration information.

The method body includes:

The AAA server sends a request for canceling the user information to the IP gateway, and the IP gateway deletes the related service registration information of the user terminal stored by the IP gateway, and then returns the logout user information response;

The AAA server sends a deregistration request to the user information storage unit, and after receiving the deregistration request, the user information storage unit deletes the related service registration information of the user terminal previously stored by itself, and then returns a registration response to the AAA ill server. .

Alternatively, the method specifically includes: A21. The AAA server sends a request for canceling the user information to the IP gateway, and after receiving the request for canceling the user information, the IP gateway sends a registration request to the HLR7HSS;

A22. After receiving the registration request, the HLR/HSS deletes the related service registration information of the previously stored IP gateway, and then returns a registration response to the IP gateway;

A23. After receiving the registration, the IP gateway deletes the relevant service registration information of the user terminal previously stored by itself, and then returns a logout user information response to the AAA server. After receiving the response, the AAA server deletes the stored information. Related service registration information of the user terminal.

In the above solution, after receiving the deregistration request, the user information storage unit further includes: the user information storage unit notifying the application server that the user terminal cannot access the network service through the IP.

In the above solution, the related service registration information deleted by the user information storage unit includes at least: an IP-attached identifier, and an SS7 address information of the IP gateway.

In the above solution, the deleting the related service registration information by the IP gateway includes: deleting the correspondence between the stored permanent identifier of the user terminal and the IP address; and deleting the correspondence between the stored port addresses registered by the user terminal.

In the above solution, the AAA server initiates a service deregistration request when the WLAN user terminal leaves the WLAN network; or, the AAA server initiates a service deregistration request when the user information storage unit is forced to be separated from the network by configuring the user information storage unit; or, the AAA server is When the user terminal runs out of credit, it initiates a service registration request.

In the above solution, the user terminal is an IP client accessed through an IP network. The user information storage unit is a home location register or a home subscription subscriber server.

The IP access-based service deregistration method provided by the present invention provides the IP access-based service de-registration process, and the user terminal that has accessed the 3GPP network and registered the service information in the IP-GW of the 3GPP network. The deregistration process is used to cancel the business information that has been registered. In addition, the present invention provides an application scenario in which multiple service information is to be registered, for example, when the user terminal does not want to use the service of the 3GPP network, the service may be initiated to the registration process; In the process of disconnecting the user terminal from the accessed IP network, the AAA server may also initiate a service registration process; for example: when the short message is sent to the user terminal, the IP-GW may also initiate a service to register. Process. Having passed the service deregistration process provided by the present invention, the IP-GW performs the status information of the user terminal in the user information storage unit to update the user terminal, so that the user information storage unit can know that the current service terminal cannot use the service of the 3GPP network. Information, so that the image registered by the IP client in the IP-GW can be updated according to the change of the state of the user access network, so that when other network entities request the address information of the WLAN IP client, the address of the IP-GW is not returned. , to avoid the subsequent process out of 3 errors. BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a schematic diagram of a network structure of a WLAN system and a 3GPP system:

2 is a schematic diagram of a networking structure of a WLAN operation network;

3 is a flow chart of the prior WLAN user terminal's right to answer and authorize; FIG. 5 is a schematic diagram of the existing WLAN user terminal separation process initiated by the HLR/HSS; FIG. 6 is an existing online charging system. Schematic diagram of the separation process of the initiated WLAN user terminal; FIG. 7 is a schematic diagram of the IP-based short message support architecture;

Figure 8 is a schematic diagram of the IP client transmitting to the SM-SC;

FIG. 9 is a flowchart of a process of a first embodiment of a user terminal actively initiating deregistration according to the present invention; FIG. 10 is a flowchart of a process of a second embodiment of a user terminal actively initiating registration according to the present invention; a processing flow chart of the book;

FIG. 12 is a flowchart of another process of initiating a deregistration by the AAA server according to the present invention;

FIG. 13 is a flowchart of a first embodiment of the AAA server initiating a de-mastered book according to the present invention; FIG. 14 is a flowchart of a second embodiment of the AAA server initiating a de-mastering book according to the present invention; The third embodiment is a flowchart of processing; FIG. 16 is a schematic flowchart of a process for initiating deregistration by the IP-MESSAGE-GW according to the present invention; FIG. 17 is a schematic diagram of a process for initiating registration of another process by the IP-MESSAGE-GW according to the present invention. Mode for carrying out the invention

The core idea of the present invention is: A user terminal that has accessed the 3GPP network and registered service information in the IP-GW of the 3GPP network may initiate a service registration process to the PDG, and after PDG verification, the PDG to the IP address. - The GW sends a service deregistration request carrying the user terminal identification information, and deletes the service registration information registered by the user terminal on the user information storage unit, the AA server, and the IP-GW; or, when the AAA server initiates the session termination process, Whether the user terminal has been registered on the IP-GW, and if so, the server initiates a deregistration process to the IP-GW, and deletes the service registration information registered by the user terminal on the user information storage unit, the AAA server, and the IP-GW. The corresponding resource is released; or the service registration process is initiated by the IP-GW, and the service registration information registered by the user terminal on the user information storage unit, the AAA_server, and the IP-GW is deleted. Here, the user terminal is an IP client, that is, a WLAN user terminal; the PDG is a PDG supporting the requested service; and the user information and the storage unit may be an HLR or an HSS.

The premise of the implementation of the present invention is: In the existing 3GPP-WLAN interactive network, there is a functional entity IP gateway (IP-GW), and when the user terminal accesses the 3GPP network through the IP network, the IP-GW is registered. And registering its own information on the IP-GW. At the same time, the IP-GW notifies the user information storage unit and the AAA server of its own related information, such as the address information of the IP-GW. The user information storage unit may be an HLR or an HSS.

Here, the IP-GW may be a logical function entity that only supports a certain service to register, for example: an IP-MESSAGE-GW that only supports short message service registration; or a logic that supports multiple services to register at the same time. Functional entity. The IP-GW may have one or more, and the IP-GW may exist independently or in an existing network device, such as: ^: in the AAA server.

The deregistration process mentioned in the present invention may be initiated by the user terminal or by AAA. The server initiates and can also be initiated by the IP-GW. The notification user information storage unit deletes the service registration information of the corresponding user terminal stored thereon, and the IP-GW may notify the user information storage unit to delete the corresponding information by using the AAA server, or may directly know by the IP-GW. The user information storage unit deletes the corresponding information. The specific implementation process of the active initiation zone registration process of the user terminal is described in detail below through two specific embodiments and their diagrams.

In this embodiment, the user terminal is an IP client, the IP-GW is an IP-MESSAGE-GW that supports short-message service registration, the user information storage unit is HL3⁄4/HSS, and the IP-MESSAGE-GW deletes the HLR through an AAA server. /HSS IP-MESSAGE-GW related information stored first. In this embodiment, the user terminal initiates a de-injection process, and the specific processing process is as shown in FIG. 9, and includes the following steps:

Step 901: The IP client that needs to be registered sends a service registration request message to the PDG, where the request message carries the IP-MESSAGE-GW identification information and the identity information of the IP client itself. The PDG is a PDG related to the service; the IP-MESSAGE-GW identification information may be sent in a domain name format, and the PDG obtains the address information of the IP-MESSAGE-G^V by using a domain name resolution manner; For identification information, a network access identifier ( ΓΑΙ ) can be used.

It should be noted that the IP-MESSAGE-GW identification information may not be carried in the service deregistration request sent by the IP client. The PDG directly uses the IP-MESSAGE-GW that it contacts to forward the service to the IP-MESSAGE-GW that it contacts. The registration request is sent by the PDG according to the IP client identification information carried in the service registration request, such as the NAI, parsing the IP-MESSAGE-GW to which the IP client belongs, and forwarding the service registration request to the parsed IP-MESSAGE-GW.

Steps 902 to 903: After receiving the service registration request, the PDG checks the correspondence between the source IP address and the assigned tunnel ID ( Tunnel ID) in the request sent by the IP client, and ensures that the IP client makes the registration request. After the check is passed, the PDG is based on the PDG. Obtained IP-MESSAGE-GW information information, to The corresponding IP-MESSAGE-GW forwards the service to the registration request, and the forwarded service registration request carries the IP Client identification information.

Here, the IP-MESSAGE-GW address information obtained by the PDG may be obtained according to the information in the service registration request, or may be obtained according to the IP-MESSAGE-GW information of the contact.

Step 904: Receive the service to register the IP-MESSAGE-GW request, according to the IP in the request

The client identification information is used to parse the address information of the AAA server to which the current IP client is registered. Then, the IP-MESSAGE-GW sends a logout user information request message to the AAA server according to the obtained address information, and the message may carry the IP client identification information, such as NAI.

Step 905: After receiving the logout user information request message, the AAA server obtains the HLR/HSS address information of the IP client according to the IP client identification information carried in the message, such as the NAI, and then initiates a deregistration process to the HLR/HSS, namely: The HLR/HSS sends a registration request, which carries the permanent identity of the IP Client, and notifies the HLR/HSS that the service information registered by the IP Client in the IP-MESSAGE-GW has been removed.

Here, the permanent identifier of the IP Client may be MSISDN or IMSL.

Step 906: The HLR/HSS deletes the information about the previously stored IP-MESSAGE-GW, for example, the SS7 address information of the IP-MESSAGE-GW, the IP-attached identifier, etc., thereby enabling the HLR/HSS to learn that the IP Client cannot pass. IP access to the 3GPP network, using the services of the 3GPP PS domain. The HLR/HSS then returns a registration response to the AAA server.

Here, optionally, the HLR/HSS may further notify the application server (AS, Application Server) that the user terminal cannot access the PS domain service through the IP, and the AS deletes the information stored in the previous registration, such as deleting the previously stored IP-MESSAGE-GW. Address information.

Step 907: After the AAA server receives the successful deregistration response returned by the HLR/HSS, the AAA server deletes the related service registration information of the IP client in the AAA server, such as IP-MESSAGE-GW address information, and then sends the IP-MESSAGE-GW to the IP-MESSAGE-GW. Return the logout user information response message;

After receiving the IP-MESSAGE-GW, delete the relevant information stored when the IP Client performs service registration.

15 Information, such as: Delete the correspondence between the stored permanent ID of the IP Client and the IP address of the IP Client, the address information of the stored AAA server registered by the IP Client, and the stored PDG address and the IP address of the IP Client. Correspondence.

Here, since the correspondence between the permanent identifier of the IP client and the IP address of the IP client can be stored in a separate database by the IP-MESSAGE-GW or the AAA server, the database can be opened to other network entities for access, therefore, The deletion of the correspondence between the permanent identifier of the IP client and the IP address of the IP client may be initiated by the IP-MESSAGE-GW or the AAA server to the database.

Steps 908 to 909: The IP-MESSAGE-GW returns a service registration response message to the PDG. After receiving the PDG, the PDG returns a service registration response message to the IP client. Embodiment 2:

In this embodiment, the user terminal is an IP client, the IP-GW is an IP-MESSAGE-GW that supports short message service registration, the user information storage unit is an HLR/HSS, and the IP-MESSAGE-GW passes the HLR/HSS Directly delete the IP-MESSAGE-GW related information previously stored by the HLR/HSS. In this embodiment, the user terminal initiates a deregistration process, and the specific processing process is as shown in FIG. 10, and includes the following steps:

Steps 1001-1003: The same is true for all the processing and description of step 901 903 in the first embodiment.

Step 1004: After receiving the service registration request, the IP-MESSAGE-GW parses the permanent identification information of the IP client, such as the IMSI, according to the IP client identification information in the request, and obtains the address of the HLR/HSS to which the IP client belongs according to the IMSI. The information, then the IP-MESSAGE-GW sends a registration request message to the HLR/HSS, which may carry the IP Client identification information, such as the IMSI obtained by the NAI parsing.

Step 1005: After receiving the de-registration request of the IP-MESSAGE-GW, the HLR/HSS deletes the phase stored by the IP client during the service registration according to the identifier information of the IP client, such as the IMSI. Off information, such as SS-address information of IP-MESSAGE-GW, IP-attached identifier, etc. In this way, the HLR/HSS can be made aware that the IP Client can no longer access the 3GPP network through the IP, and uses the services of the 3GPP PS domain.

Here, optionally, the HLR/HSS may further notify the application server that the user terminal cannot access the PS domain service through the IP, and the AS deletes the information stored in the previous registration, such as deleting the address information of the previously stored IP-MESSAGE-GW.

The HLR/HSS then returns a registration response to the IP-MESSAGE-GW.

Step 1006: The IP-MESSAGE-GW sends a registration request to the AAA server, and the IP client identifier information carried in the message, such as the MSISDN, the AAA server deletes the related service registration information of the IP client in the AAA server, for example: deleting the stored IP address. -MESSAGE-GW address information.

Step 1007: The IP-MESSAGE-GW deletes the information stored in the IP client for service registration, for example: deleting the correspondence between the stored permanent identifier MSIDSN of the IP client and the IP address of the IP client; deleting the stored IP Client The address information of the registered AAA server; and the correspondence between the stored PDG address and the IP address of the IP client.

Then, the IP-MESSAGE-GW returns a service registration response message to the PDG.

Step 1008: After receiving the service registration response sent by the IP-MESSAGE-GW, the PDG returns a service registration response message to the IP client.

When the WLAN user is not in the coverage of the WLAN network, the WLAN network will initiate a process of separating the WLAN user from the 3GPP network. In this case, the service information of the WLAN user terminal in the IP-MESSAGE-GW needs to be registered. When the operator sets data to the HLR/HSS to force a WLAN user terminal to be detached from the 3GPP network, the service information of the WLAN user terminal in the IP-MESSAGE-GW needs to be registered. Further, when the 3GPP network uses online charging for the accessed WLAN user terminal, the online charging system actively initiates a process of separating the WLAN user terminal accessing the 3GPP network when the user credit is exhausted, and is also required at this time. Performing a service to register a WLAN user terminal in IP-MESSAGE-GW Information. For the service deregistration process that needs to be performed in the above three cases, the service deregistration process may be initiated by the AAA server. The deregistration process initiated by the AAA server is as shown in Figure 11, and includes the following steps:

Step 1101: The AAA server initiates a service deregistration process, and sends a logout user information request message to the IP-MESSAGE-GW, where the message may carry the permanent identity information of the IP client, such as MSISDN or IMSI.

Step 1102: After receiving the request for canceling the user information, the IP-MESSAGE-GW deletes the related information stored when the IP client performs service registration according to the IP client identification information carried in the request, for example, deleting the permanent identifier and IP of the storage user. The correspondence between the addresses; the stored AAA address information registered by the IP client; and the correspondence between the stored IP client's IP address and the PDG address.

The IP-MESSAGE-GW then returns a logout user information response message to the AAA server. Step 1103: The AAA server initiates a deregistration process to the HLR/HSS, and carries a permanent identifier of the IP client, such as MSISDN or IMSI, to notify the HLR/HSS that the service information registered by the IP client in the IP-MESSAGE-GW has been removed.

Step 1104: After receiving the HLR/HSS, delete the information about the previously stored IP-MESSAGE-GW, such as the SS7 address information of the IP-MESSAGE-GW, the IP-attached identifier, etc., so that the HLR/HSS can learn the IP Client. The 3GPP PS domain service cannot be used to access the 3GPP network through IP.

The HLR/HSS then returns a registration response to the AAA server.

In the above process, the execution order of steps 1101, 1102 and steps 1103, 1104 may be interchanged, that is, the AAA server may initiate a deregistration process to the HLR/HSS, and then initiate a process of canceling the user information to the IP-MESSAGE-GW. . Finally, the AAA server deletes the related service registration information of the IP client in the AAA server, such as: deleting the stored IP-MESSAGE-GW address information.

The de-registration process initiated by the AAA server can also be implemented by the process shown in Figure 12, including the following steps:

Step 1201: The AAA server initiates a service deregistration process, and sends a logout user information request message to the IP-MESSAGE-GW, where the message may carry the permanent identity information of the IP client, such as MSISDN or IMSI.

Step 1202: After receiving the request for canceling the user information, the IP-MESSAGE-GW sends a deregistration process to the HLR/HSS according to the IP client identification information carried in the request, and carries the permanent identifier of the IP client, such as MSISDN or IMSI, to notify the HLR/ HSS The service information registered by the IP Client in the IP-MESSAGE-GW has been removed.

Step 1203: After receiving the registration request, the HLR/HSS deletes the related service registration information of the previously stored IP-MESSAGE-GW, such as the SS7 address information of the IP-MESSAGE-GW, and the IP-attached identifier, etc., so that the HLR7HSS can be made. It is known that the IP Client cannot access the 3GPP network through IP, and uses the services of the 3GPP PS domain.

Here, optionally, the HLR/HSS may further notify the AS user terminal that the PS domain service cannot be accessed through the IP, and the AS deletes the information stored in the previous registration, such as deleting the address information of the previously stored IP-MESSAGE-GW.

The HLR/HSS then returns a registration response to the IP-MESSAGE-GW.

Step 1204: After receiving the de-registration response returned by the HLR/HSS, the IP-MESSAGE-GW deletes the related information stored when the IP client performs service registration, such as deleting the correspondence between the stored permanent identifier and the IP address of the user; The stored IP client registers the AAA server address letter and then the IP-MESSAGE-GW returns a logout user information response message to the AAA server. After receiving the AAA server, the AAA server deletes related service registration information of the IP client in the AAA server, such as the stored IP-MESSAGE-GW address information. The detailed process of the de-registration process initiated by the AAA server caused by three different reasons is specifically described below through three embodiments and their drawings. Embodiment 3:

In this embodiment, the user terminal is an IP client, and the IP-GW supports the short message service: the IP-MESSAGE-GW of the main book, and the user information storage unit is the HLR/HSS. In this embodiment, when the WLA user terminal is not in the coverage of the WLAN network, the WLAN network actively initiates a process of separating the WLAN user terminal from the 3GPP network, and registers the processing of the service information of the WLAN user terminal in the IP-MESSAGE-GW. The process shown in FIG. 13 includes the following steps: Steps 1301 to 1304: The entire processing and description of steps 401 to 404 in the process of separating the WLAN user terminal from the 3GPP network initiated by the WLAN network in the prior art are completely the same.

Step 1305: If the WLAN user terminal has performed service registration in the IP-MESSAGE-GW, the AAA server initiates a service deregistration process, and the AAA server sends a logout user information request message to the IP-MESSAGE-GW, and the IP-MESSAGE-GW deletes The service registration information of the corresponding IP Client stored by itself.

Step 1306: If the AAA server determines that the registration information of the WLAN user terminal needs to be deleted, the AAA server sends a notification message to the HLR/HSS through the Wx interface, and requests the information sent by the HLR/HSS 4 to the WLAN user terminal to be set to Purge, indicating that the WLAN user The registration information of the terminal has been deleted in the AAA server. After receiving the HLR/HSS, the HLR/HSS deletes the association information of the WLAN user terminal and the AAA server, such as the address information of the AAA server associated with the WLAN user terminal.

In addition, if the WLAN user has performed service registration in the IP-MESSAGE-GW, the AAA server initiates a service deregistration process, and the AAA server sends a registration request message to the HLR/HSS, and the HLR/HSS deletes the corresponding IP Client stored by itself. Business registration information. Then, the AAA server deletes the service registration information of the previously stored IP Client, such as deleting the stored IP-GW. Address information.

In the process of this embodiment, the order of step 1305 can be interchanged with steps 1303, 1304, 1306. That is, the deregistration process initiated by the AAA server to the IP-MESSAGE-GW may be performed before step 1303, or at any time between steps 1303 and 1306, or after step 1306.

In addition, since the HLR/HSS deletes the registration information of the WLAN user terminal, the service registration information of the stored IP Client may be deleted in the HLR/HSS, so the AAA server initiates the service to the HLR/HSS in step 1306. The registration process and the corresponding processing part may not be executed.

Embodiment 4:

In this embodiment, the user terminal is an IP client, the IP-GW is an IP-MESSAGE-GW that supports short message service registration, and the user information storage unit is an HLR/HSS. In this embodiment, when the operator performs data setting on the HLR/HSS to force a WLAN user terminal to be separated from the 3GPP network, the process of processing the service information of the WLAN user terminal in the IP-MESSAGE-GW is registered. As shown in Figure 14, the following steps are included:

Steps 1401~1402: The 3GPP user deletes its WLAN attribute in the HSS; the HSS initiates the process of canceling the user's WLAN registration information through the Wx interface AAA server, and the cancellation of the registration information uses a permanent identifier to indicate the corresponding user.

If the WI N user has registered the service in the IP-MESSAGE-GW, the IKE server initiates the service registration process, and the AAA server sends a registration request message to the HLR/HSS, the HLR/HSS book! Business registration information of the IP Client.

Steps 1403~1404: If the WLAN access connection of the user terminal currently exists, the AAA server initiates a session termination process to the WLAN network via the Wa interface; if the wireless connection exists, the LAN network releases the wireless interface connection through the technology defined in the WLAN specification. .

Step 1405: If the WLAN user has already registered the service in the IP-MESSAGE-GW, Then, the AAA server initiates a service registration process, and the AAA server sends a logout user information request to the IP-MESSAGE-GW, and the IP-MESSAGE-GW deletes the service registration information of the corresponding IP client stored by itself. Then, the AAA server deletes the service registration information of the previously stored IP client, such as deleting the stored IP-GW address information.

Step 1406: If the W AN user has established a tunnel connection with one or more PDGs, the AAA server/proxy needs to delete the tunnel connections, and the AAA server/proxy initiates a tunnel deletion request to the PDG via the Wm interface, and the PDG deletes the previous WLAN user. The tunnel established by the terminal releases related resources.

Step 1407: The AAA server deletes the filter established by the WAG for the tunnel by interacting with the WAG.

In this embodiment, the order of step 1405 can be interchanged with steps 1406 and 1407. That is to say, the deregistration process initiated by the AAA server to the IP-MESSAGE-GW can be performed at any time before and after steps 1406 and 1407.

When the registration information of the WLAN user terminal is deleted in the HLR/HSS, the service registration information of the stored IP client may be deleted in the HLR/HSS. Therefore, in step 1402, the AAA server initiates a service registration process and corresponding processing to the HLR7HSS. Some can not be executed. Embodiment 5:

In this embodiment, the user terminal is an IP client, the IP-GW is an IP-MESSAGE-G V that supports short message service registration, and the user information storage unit is an HLR/HSS. In this embodiment, when the user credit is exhausted, the online charging system actively initiates a separation process of the WLAN user terminal accessing the 3GPP network, and processes the service information of the WLAN user terminal in the IP-MESSAGE-GW. As shown in Figure 15, the following steps are included:

Steps 1501 to 1504: The entire processing and description of steps 601 to 604 in the process of separating the WLAN user terminal from the 3GPP network caused by the online charging system in the prior art are completely the same. Step 1505: If the WLAN user has already registered the service in the IP-MESSAGE-GW, the AAA server initiates the service to register: The AAA server sends a logout user information request message to the IP-MESSAGE-GW, and the IP-MESSAGE-GW deletes the service registration information of the IP client stored by itself.

Step 1506: If the WLAN user establishes a tunnel connection through the same or multiple PDGs, the AAA server/proxy needs to delete the tunnel il_connection, and the AAA server/proxy initiates a tunnel deletion request to the PDG via the Wm interface, PDG deletes! A tunnel established with the WLAN user terminal releases related resources.

Step 1507: The AAA server/proxy deletes the filter established by the WAG for the tunnel through interaction with the WAG. .

Step 1508: If the process of terminating the process is terminated in step 1503, that is, the purge process, the AAA server/proxy initiates a purge process to the HLR/HSS to notify the HLR/HSS to register the WLAN user terminal previously registered in the AAA server. The information has been cancelled.

In addition, if the WLAN user has already registered the service in the IP-MESSAGE-GW, the AAA server initiates a service deregistration process, and the AAA server sends a registration request message to the HLR/HSS, and the HLR/HSS deletes its own storage^ corresponding IP Client. Business registration information. Then, the AAA server deletes the service registration information of the previously stored IP client, such as deleting the stored IP-GW address information.

In the process of this embodiment, the sequence of step 1 505 may be interchanged with steps 1506, 1507, 1508, that is, the deregistration process initiated by the AAA server to the IP-MESSAGE-GW may be any before or after steps 1506 to 1508. When the bird 'j performs.

In addition, since the HLR/HSS deletes the registration information of the user terminal, the service registration information of the stored IP Client may be deleted in the HLR/HSS, so in step 1508, the AAA server initiates the service to the HLR/HSS. The registration process and the corresponding processing part may not be executed. '

For the third embodiment, the fourth embodiment, and the fifth embodiment, the deregistration process may be The IP-MESSAGE-GW notifies the HLR/HSS to delete the service registration information of the current IP client on the HLR/HSS through the AAA server, as described in Embodiments 3 and 5, and may also initiate the registration process by the IP-MESSAGE-GW. The direct access port HLR/HSS deletes the service registration information of the current IP client on the HLR/HSS. For the above embodiment, after the IP client completes the service deregistration process in the IP-MES SAGE-GW, and subsequently performs the MO process of the short message service, the IP client also sends a short message to the IP-MESSAGE-GW via the PDG, IP. After the MESSAGE-GW receives the short message from the IP client, the IP-MESSAGE-GW returns a failure message to the IP client, and rejects the MO short message process initiated by the IP client. Carry the corresponding failure reason further.

For the SMS MT process, when the IP-MESSAGE-GW fails to send a short message to the IP client, the IP-MESSAGE-GW can initiate the service registration process. The specific processing is shown in Figure 16, which includes the following steps:

Step 1601: The IP-MESSAGE-GW initiates a service deregistration process, and sends a registration request to the HLR/HSS, where the request carries a permanent identifier of the IP client, such as an MSISDN or an IMSI, and notifies the HLR/HSS that the IP Client is in the IP-MESSAGE- The service information registered in the GW has been removed.

Step 1602: After receiving the registration request, the HLR/HSS deletes the related service registration information of the previously stored IP-MESSAGE-GW, such as the SS7 address information of the IP-MESSAGE-GW, and the IP-attached identifier, etc., so that the HLR can be made. The HSS knows that the IP Client cannot access the 3GPP network through IP, and uses the services of the 3GPP PS domain.

Here, optionally, the HLR/HSS may further notify the A_S user terminal that the PS domain service cannot be accessed through the IP, and the AS deletes the rest information stored in the previous registration, such as deleting the address information of the previously stored IP-MESSAGE-GW.

The HLR/HSS then returns a registration response to the IP-MESSAGE-GW.

Step 1603: After receiving the deregistration response returned by the HLR/HSS, the IP-MESSAGE-GW The AAA server sends a registration request, and after receiving the AAA server, deletes the related service registration information of the IP client in the AAA server, such as the stored IP-MESSAGE-GW address information. Then, the IP-MESSAGE-GW deletes the key information stored in the IP client for service registration, such as: deleting the correspondence between the permanent identifier of the storage user and the IP address; deleting the stored AAA address information of the IP client; and deleting Correspondence between the IP address of the stored IP client and the PDG address.

De-registration initiated by IP-MESSAGE-GW can also be implemented through the process shown in Figure 17, including the following steps:

Step 1701: The IP-MESSAGE-GW initiates a service deregistration process, sends a registration request to the AAA, and carries a permanent identifier of the IP client, such as MSISDN or IMSI.

Step 1702: After receiving the deregistration request, the AAA server initiates a deregistration process to the HLR HSS according to the IP Client identification information carried in the request, and the HLR/HSS clerk j stores the related information of the IP-MESSAGE-GW, such as The SS-address information of the IP-MESSAGE-GW and the IP-attached identifier, etc., enable the HLR/HSS to know that the IP Client does not access the 3GPP domain through IP, and uses the services of the 3GPP PS domain.

Here, optionally, the HLR/HSS may further notify the AS user terminal that the PS domain service can be accessed through the IP, and the AS deletes the information stored in the previous registration, such as deleting the address information of the previously stored IP-MESSAGE-GW.

Then, the AAA server deletes the IP client's registration information in the AAA server, such as the stored IP-MESSAGE-GW address information, and goes back to the IP-MESSAGE-GW to register the response.

Step 1703: After receiving the de-registration response returned by the AAA server, the IP-MESSAGE-GW deletes the related service registration information stored when the IP client performs service registration, for example, deleting the correspondence between the permanent identifier of the storage user and the IP address; Stored IP Client's AAA address is inflated after the IP Client completes the service in the IP-MESSAGE-GW to register the flow test, followed by When the MT process of the short message service is performed, when the GMSC obtains the routing information of the IP client from the HLR/HSS, since the HLR/HSS does not have the IP-MESSAGE-GW address information of the IP client, the HLR/HSS can only return to the GMSC. The MSC or SGSN address information of the IP client, the GMSC sends a short message to the IP client via the MSC or the SGSN, and cannot send a short message to the IP client via the IP-MESSAGE-GW.

In the process flow of the foregoing embodiment, the IP-MESSAGE-GW is a service gateway for the WLAN IP Client to access the SMS service in the 3GPP PS domain. In practical applications, since the deregistration process of other services, such as the LCS service, is similar to the deregistration process of the short message service described above, the IP-MESSAGE-GW can be replaced with an IP-GW that supports different services to be registered. The process can also be used by the WLAN IP Client to register various service information previously registered in the 3GPP network.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for deregistering a service based on IP access, characterized in that the method comprises:

The IP gateway initiates a deregistration request to the user information storage unit to notify the user information storage unit to delete the stored related service registration information; and, the IP gateway deletes the related service registration information stored by itself.

2. The method according to claim 1, wherein the method further comprises: the user terminal initiating a service deregistration request to the IP gateway, the IP gateway receiving the deregistration request sent by the user terminal The user information storage unit initiates a deregistration request.

3. The method of claim 2, wherein the method further comprises: the IP gateway returning a service deregistration response to the current user terminal.

The method according to claim 2 or 3, wherein the initiating service deregistration request specifically comprises the following steps:

The method according to claim 4, wherein the packet data gateway in step a2 further comprises: before the forwarding service deregistration request, according to: the source IP address in the request sent by the current user terminal and the assigned tunnel identifier check After the validity of the user terminal is checked, the service is forwarded to the registration request.

6. The method according to claim 1, wherein the method further comprises:

The IP gateway initiates a registration request to the AAA server, informing the AAA server to delete the stored related service registration information.

The method according to claim 2, 3 or 6, wherein the service deregistration request carries a user terminal identifier, and the IP gateway notifies the user information storage unit to delete the phase The specific information includes:

Bl. The IP gateway parses the address information of the AAA server to which the current user terminal is registered according to the user terminal identifier carried in the request, and then sends a logout user information request to the AAA server;

After receiving the registration request, the user information storage unit deletes the related service registration information of the user terminal previously stored by itself, and then returns a registration response to the AAA server. After receiving the response, the AAA server deletes the user terminal and stores the information in the user terminal. Related business registration information, and then return the logout user information response to the IP gateway.

The method according to claim 7, wherein after the user information storage unit receives the deregistration request, the step bl3 further comprises: the user information storage unit notifying the application server that the user terminal cannot access the network service through the IP.

The method according to claim 7, wherein the related service registration information deleted by the user information storage unit in step M3 comprises at least: an IP-attached identifier, and SS7 address information of the IP gateway.

The method according to claim 7, wherein the IP gateway receives the logout user information response, and the method further includes: deleting the IP gateway, including the correspondence between the permanent identifier of the user terminal and the IP address of the user terminal. Related business registration information.

The method according to claim 10, wherein the corresponding relationship is stored in a separate database, the database is set in an IP gateway or set in an AAA server, and the deletion process is performed by an IP gateway or AAA. The server initiates to the database.

12. The method according to claim 7, wherein the user terminal is an IP client accessed through an IP network.

The method according to claim 7, wherein the user information storage unit is a home location register or a home subscription user server.

The method according to claim 2, 3 or 6, wherein the service deregistration request carries a user terminal identifier, and the IP gateway notifying the user information storage unit to delete the related information specifically includes:

B21. The IP gateway parses the address information of the user information storage unit to which the current user terminal belongs according to the user terminal identifier carried in the request, and then sends the address information to the user information storage unit;

The method according to claim 14, wherein after the user information storage unit receives the registration request, the step b22 further comprises: the user information storage unit notifying the application server that the user terminal cannot access the network service through the IP.

The method according to claim 14, wherein the related service registration information deleted by the user information storage unit in step b22 includes at least: an IP-attached identifier, and SS7 address information of the IP gateway.

The method according to claim 14, wherein the IP gateway receives the deregistration response, the method further comprising: deleting the IP gateway, including the correspondence between the permanent identifier of the user terminal and the IP address of the user terminal. Related business registration information.

The method according to claim 17, wherein the corresponding relationship is stored in a separate database, the database is set in an IP gateway or is set in an AAA server, and the deletion process is performed by an IP gateway or AAA. The server initiates to the database.

The method according to claim 14, wherein the user terminal is an IP client accessed through an IP network.

The method according to claim 14, wherein the user information storage unit is a home location register or a home subscription subscriber server.

A method for deregistering a service based on IP access, the method comprising: the AAA server initiating a deregistration process to the IP gateway and the user information storage unit, notifying the user The information storage unit and the IP gateway respectively delete the related service registration information stored by the AAA server; after receiving the response, the AAA server deletes the related service registration information stored by itself.

The method according to claim 21, wherein the method specifically includes: the AAA server sends a request for canceling the user information to the IP gateway, and after receiving the request for canceling the user information, the IP gateway deletes the stored information. The relevant service registration information of the user terminal, and then returning the logout user information response;

The AAA server sends a deregistration request to the user information storage unit. After receiving the deregistration request, the user information storage unit deletes the related service registration information of the user terminal previously stored by itself, and then returns a deregistration response to the AAA server.

The method according to claim 21, wherein the method specifically comprises: a21. The AAA server sends a request for canceling the user information to the IP gateway, and after receiving the request for canceling the user information, the IP gateway sends the request to the HLR/ The HSS sends a registration request;

A23. After receiving the registration response, the IP gateway deletes the related service registration information of the user terminal previously stored by itself, and then returns a response to the logout user information to the AAA server. After receiving the response, the AAA server deletes the related information of the user terminal stored by itself. Business registration information.

The method according to claim 22 or 23, wherein after the user information storage unit receives the deregistration request, the method further comprises: the user information storage unit notifying the application server that the user terminal cannot access the network service through the IP.

The method according to claim 22 or 23, wherein the related service registration information deleted by the user information storage unit comprises at least: an IP-attached identifier, and SS7 address information of the IP gateway.

The method according to claim 22 or 23, wherein the deleting the related service registration information by the IP gateway comprises: deleting the correspondence between the stored permanent identifier of the user terminal and the IP address; deleting the stored user terminal Registered AAA server address information; and delete Correspondence between the stored IP address of the user terminal and the packet data gateway address.

The method according to claim 22 or 23, wherein the AAA server initiates a service deregistration request when the WLAN user terminal leaves the WLAN network; or, the AAA server forces the user terminal to be separated from the network by configuring the user information storage unit. The service is initiated to register the request; or, the AAA server initiates a service deregistration request when the user terminal is exhausted.

The method according to claim 22 or 23, wherein the user terminal is an IP client accessed through an IP network.

The method according to claim 22 or 23, wherein the user information storage unit is a home location register or a home subscription subscriber server.