WO2011032316A1 - Method, device and system for implementing registration - Google Patents

Abstract

A method, device and system for implementing registration are provided in the embodiments of the present invention, said method includes: a gateway device receiving a request message transmitted from a mobility management network element; the gateway device obtaining the application server information used by said user device according to said request message; the gateway device registering said user device with said application server. The application of the present invention, by registering the user device with the application server by the gateway device, avoids the user device registering to the application server, and makes the functions of the user device simple to realize, and makes the user device not need to obtain the information of the application server, thereby improves the security of the network.

Description

 TECHNICAL FIELD The present invention relates to the field of communications technologies, and in particular, to a method, an apparatus, and a system for implementing registration. Background technique

In order to meet the challenges of wireless broadband technology, maintain 3GPP ( 3 ^rd Generation Partnership

Project, 3rd Generation Partnership Project) The leading edge of the network, 3GPP developed LTE (Long Term Evolution) at the end of 2004. Under the guidance of the evolution plan, a new mobile communication network architecture is defined, which is flatter than the current GPRS (General Packet Radio Service)/UMTS (Universal Mobile Telecommunication System). And only the packet domain is reserved, so it can be called EPS (evolved packet system).

In the existing communication system, there are two main applications: H2H (Human to Human) application, M2M (Machine to Machine) application. In the H2H application, when the user equipment UE is attached to the network, the network side (such as PGW (PDN Gateway), packet data network gateway) will assign an IP address to the UE, and the UE will obtain the IP address and then apply to the AF (Application Function, application). The server initiates the registration process, and registers its user equipment identification information and the IP address assigned to it by the network side to the AF. The manner in which the UE obtains the IP address may be: when the UE is attached to the network (E-UTRAN (Evolved Universal Terrestrial Radio Access Network)) or the UE initiates a PDP context activation process (GERAN (GSM EDGE) After the Radio Access Network ) / UTRAN network, the network side (eg, PGW or GGSN (Gateway GPRS Support Node)) will assign an IP address to the UE and will display the AF information (eg, AF address information). It is carried to the UE in the Create Default Bearer Accept message or the PDP Context Activation Accept message. However, because the M2M application (refers to the network communication between one or more network elements without human intervention, such as traffic control and management, factory monitoring, remote meter reading, etc.) has a business application order and The MTC (Machine Type Communication) Device has a large number of features. The 3GPP network assigns an IP address to the MTC Device and notifies the MTC Device of the MTC Server information. This may result in complex MTC Device functions and reduced network. Security. Summary of the invention

To meet the challenges of wireless broadband technology, keeping 3GPP (3 ^rd Generation Partnership Project, Third Generation Partnership Project) lead the network, 3GPP has developed LTE (Long Term Evolution, Long Term Evolution) at the end of 2004. Under the guidance of the evolution plan, a new mobile communication network architecture is defined, which is flatter than the current GPRS (General Packet Radio Service)/UMTS (Universal Mobile Telecommunication System). And only the packet domain is reserved, so it can be called EPS (evolved packet system).

 In the existing communication systems, there are two main applications: H2H (Human to Human) applications, and M2M (Machine to Machine) applications. In the H2H application, when the user equipment UE is attached to the network, the network side (such as PGW (PDN Gateway), packet data network gateway) will assign an IP address to the UE, and the UE will obtain the IP address and then apply to the AF (Application Function, application). The server initiates the registration process, and registers its user equipment identification information and the IP address assigned to it by the network side to the AF. The manner in which the UE obtains the IP address may be: when the UE is attached to the network (E-UTRAN (Evolved Universal Terrestrial Radio Access Network)) or the UE initiates a PDP context activation process (GERAN (GSM EDGE) After the Radio Access Network ) / UTRAN network, the network side (eg, PGW or GGSN (Gateway GPRS Support Node)) will assign an IP address to the UE and will display the AF information (eg, AF address information). It is carried to the UE in the Create Default Bearer Accept message or the PDP Context Activation Accept message. However, because the M2M application (refers to the network communication between one or more network elements without human intervention, such as traffic control and management, factory monitoring, remote meter reading, etc.) has a business application order and The MTC (Machine Type Communication) Device has a large number of features. The 3GPP network assigns an IP address to the MTC Device and notifies the MTC Device of the MTC Server information. This may result in complex MTC Device functions and reduced network. Security. BRIEF DESCRIPTION OF DRAWINGS FIG. 1 is a schematic flowchart of a method for implementing registration according to an embodiment of the present invention;

 2 is a schematic flowchart of another method for implementing registration according to an embodiment of the present invention;

FIG. 3 is a schematic diagram of a corresponding relationship between an APN and an MTC Server according to an embodiment of the present disclosure; Figure 3b is a schematic diagram of the correspondence between the MTC Device identifier and the MTC Server according to the embodiment of the present invention;

 FIG. 3 is a schematic diagram of an MTC Device list in an MTC Server according to an embodiment of the present invention; FIG. 3 is a schematic diagram of a corresponding relationship between an MTC Server and an MTC Device identifier segment according to an embodiment of the present invention;

 3e is a schematic diagram of a correspondence between an industry user identifier and an MTC Server according to an embodiment of the present invention;

 4 is a schematic flowchart of a method for reselecting an application server for a user equipment according to an embodiment of the present invention;

 FIG. 5 is a schematic diagram of an apparatus for implementing registration according to an embodiment of the present invention; FIG.

 FIG. 6 is a schematic diagram of another apparatus for implementing registration according to an embodiment of the present invention; FIG.

 FIG. 7 is a schematic diagram of another apparatus for implementing registration according to an embodiment of the present invention; FIG.

 FIG. 8 is a schematic diagram of a system for implementing registration according to an embodiment of the present invention.

detailed description

 The specific configuration can be MTC Device, and the application server is specifically MTC Server. The following describes an M2M application scenario as an example. However, those skilled in the art can understand that the embodiment of the present invention is not limited to the M2M application scenario.

As shown in FIG. 2, another method for implementing registration according to an embodiment of the present invention includes: Step 201: An MTC Device sends an access request message to a mobility management network element, where the access request message includes an MTC Device At least one of an identifier, an APN (Access Point Name) information carried by the MTC Device, and an industry user identifier to which the MTC Device belongs. The industry user ID of the MTC Device refers to the identifier of the user equipment group (group) to which the MTC Device belongs, the identifier of the M2M industry user (MTC User) to which the MTC Device belongs, and the M2M application subscription user to which the MTC Device belongs (MTC) The identifier of the Subscriber, other indication group, or the identifier of the industry user. For example, the APN identifies the group to which the user equipment belongs, the user group, or the industry user. The APN is the group to which the user equipment belongs or the identifier of the user group or the industry user. The specific implementation method is not limited in this patent. It should be noted that, in a specific application, for the GERAN/UTRAN network, the mobility management network element is an SGSN, and the access request message may be a PDP context activation request message (Active PDP Context Request); For the E-UTRAN network, the mobility management network element is the MME, and the access request message may be an attach request message or a PDN connection request message (Attach Request or PDN Connectivity Request).

 Step 202: The mobility management network element initiates a session request message to the gateway device according to the received access request message (it is to be noted that the embodiment of the present invention is not limited to the session request message), the session The request message includes at least one of an identifier of the MTC Device, an APN information carried by the MTC Device, and an industry user identifier to which the MTC Device belongs. It should be noted that, in the embodiment of the present invention, the gateway device may be a PGW or a GGSN. For example, for the E-UTRAN network, the gateway device is a PGW, and the mobility management network element sends a session request message to the gateway device to send a Create Session Request message to the SGW, and then the SGW sends the message to the SGW. The PGW sends a Create Session Request message; or, for the GERAN/UTRAN network, the gateway device is a GGSN, and the mobility management network element sends a session request message to the gateway device to specifically send a PDP context for the SGSN. Request (Create PDP Context Request) message to the GGSN.

 Optionally, the MTC used by the MTC Device may be signed in the subscription data (the subscription data may be the subscription data of the MTC Device, or the subscription data of the group, the industry user, the MTC User, or the MTC Subscriber to which the MTC Device belongs). Server information (such as the MTC Server information that can be used by this APN in the PDN Subscribe Context). The mobility management network element may obtain the MTC Server information used by the MTC Device in the subscription data, and may carry the MTC Server information used by the MTC Device in the session request message to notify the gateway device.

 Step 203: The gateway device obtains application server information used by the MTC Device according to the received request message (specifically, a session request message).

 Specifically, the gateway device queries the configuration information of the gateway device according to the MTC Device identifier, the APN information carried by the MTC device, or the industry user identifier of the MTC Device, and obtains the MTC Server information used by the MTC Device. Further, the gateway device can select an appropriate MTC Server for the MTC Device from the MTC Server information used by the obtained MTC Device according to the weight information of the MTC Server.

It should be noted that for M2M applications, all MTC devices under one industry user are used. The MTC Server can be fixed. The operator can configure the address of the MTC Server used by the MTC Device among the industrial users on the gateway device (PGW/GGSN).

 In addition, the MTC Server used by the MTC Device may also be signed in the subscription data (the subscription data may be the subscription data of the MTC Device, or the subscription data of the group, the industry user, the MTC User, or the MTC Subscriber to which the MTC Device belongs). Information (such as the MTC Server information that can be used by this APN in the PDN Subscribe Context). The mobility management network element may obtain the MTC Server information used by the MTC Device in the subscription data (for example, the mobility management network element in the attach procedure or the tracking area update or the routing area update process to the HLR (Home Location Register) Or the HSS (Home Subscriber Server) sends a Location Update Request (Update Location Request) message, and the HLR or HSS carries the MTC Server information used by the MTC Device in the Update Location Ack message. The mobility management network element may carry the MTC Server information used by the MTC Device in the session request message, and notify the gateway device.

 Another method for obtaining the information of the MTC Server used by the MTC Device may be the identifier of the MTC Device, the APN information carried by the MTC Device, or the industry user identifier to which the MTC Device belongs. Querying a DNS (Domain Name System) server, where the MTC Server information used by the MTC Device is configured according to the identifier of the MTC Device, the APN information carried by the MTC Device, or the industry user ID of the MTC Device. After receiving the query request sent by the mobility management network element or the gateway device, the DNS server returns a query response message according to the query request information and the configuration information, where the query response message carries the MTC Server information used by the MTC Device. If the mobility management network element obtains the MTC Server information used by the MTC Device by querying the DNS server, the mobility management network element may carry the MTC Server information used by the MTC Device in the session request message, and notify the gateway device.

 The gateway device can obtain the MTC Server information used by the MTC Device in the following ways:

Manner 1: Configure the mapping between the APN and the MTC server. As shown in Figure 3a, the mapping between the APN and the MTC Server is as follows. Specifically, the operator can sign a specific APN for the industry user, which is in the HSS (Home Subscriber Server) / HLR (Home Location Register, The specific APN is included in the subscription data of the MTC Device of the industry user in the Home Location Register. The MTC Server information corresponding to the specific APN is configured in the gateway device (the GGSN or the PGW) (that is, the MTC Server information used by the industry user corresponding to the specific APN is configured in the gateway device). The gateway device can learn the MTC Server information used by the MTC Device according to the APN corresponding to the MTC Device.

 Manner 2: Configure the mapping between the MTC Device and the MTC Server.

 As shown in FIG. 3b, for the mapping table A of the MTC Device and the MTC Server, each MTC Device identifier is configured in the gateway device (for example, the identifier is an IMSI (International Mobile Subscriber Identifier) or ΙΜΕΙ ( International Mobile Equipment Identity (International Mobile Equipment Identity)) corresponding MTC Server information; or, as shown in Figure 3c, for the MTC Device List B under the configured MTC Server, the MTC Device that each MTC Server can serve is configured in the gateway device. List of identifiers; or,

 As shown in Figure 3d, the MTC Server is configured with the MTC Device identifier segment corresponding to the MTC Server. For example, an MTC Server can be an industry user IMSI number segment 460350789123000 to 460350789123999. MTC Device provides services;

 After obtaining the MTC Device identifier, the gateway device can obtain the MTC Server information used by the MTC Device by querying the table A or the table B. Alternatively, the table C can be obtained according to the identifier segment to which the MTC Device identifier belongs, and the MTC Device is used. MTC Server information.

As shown in Figure 3e, it is a correspondence table between the configured industry users and the MTC Server. The gateway device configures the correspondence between the industry user ID (eg, the group ID) and the MTC Server information used by users in this industry. After the gateway device obtains the industry user ID (for example, the group ID) to which the MTC Device belongs, the MTC Server information used by the MTC Device can be obtained according to the configuration table. The method for the gateway device to obtain the industry user identifier to which the MTC device belongs may be: The MTC Device carries the industry user identifier to which the user information belongs in the access message (for example, the attached message), and is forwarded by the mobility management network element to the gateway device (GGSN). Or PGW); or, another method may be that the mobility management network element (for example, SGSN/MME) obtains the MTC Device subscription data, and obtains the industry user identifier to which the MTC Device belongs from the MTC Device subscription data, and the mobility management network The industry user ID to which the MTC Device belongs will be forwarded to the gateway device (GGSN or PGW) in the session request message. Implementation of the invention There is no limitation on how to obtain the industry user ID of the MTC Device.

 Manner 3: Sign the MTC Server information used by the MTC Device in the subscription data of the MTC Device (for example, the MTC Server information that can be used by the APN in the PDN Subscribe Context). The mobility management network element may obtain the MTC Server information used by the MTC Device in the subscription data. The specific manner is as described above, and is not described here. The mobility management network element may carry the MTC in the session request message. The MTC Server information used by the Device is notified to the gateway device. When the session request message includes the MTC Server information used by the MTC Device, the gateway device receives the session request message, and extracts information about the MTC Server used by the MTC Device.

 Method 4: The mobility management network element or the gateway device (GGSN or PGW) queries the DNS server according to the identifier of the MTC device, the APN information carried by the MTC device, or the industry user identifier to which the MTC Device belongs, according to the MTC Device in the DNS server. The identifier of the APN, the APN information carried by the MTC Device, or the industry user ID of the MTC Device is configured with the MTC Server information used by the MTC Device. After receiving the query request sent by the mobility management network element or the gateway device, the DNS server receives the query request. The request information and the configuration information return a query response message, where the query response message carries the MTC Server information used by the MTC Device. If the mobility management network element obtains the MTC Server information used by the MTC Device by querying the DNS server, the mobility management network element may carry the MTC Server information used by the MTC Device in the session request message, and notify the gateway device.

 The method for the gateway device to obtain the information of the MTC server used by the MTC device may belong to any one of the foregoing four modes, but is not limited to the foregoing four modes. The patent device obtains the information of the MTC Server used by the MTC Device by the gateway device. The method is not limited.

The gateway device obtains the MTC Server information used by the MTC device by using any of the foregoing four methods. It should be noted that the MTC Server may use one or more MTC Servers, and the MTC Server uses more MTC Servers. The MTC Server information may be a list of MTC Servers, for example, an MTC Server IP address list or a MTC Server FQDN (Fully Qualified Domain Name, the MTC Server FQDN refers to the MTC Server domain name information) list. Further, the gateway device may select the MTC Server in the MTC Server information list for the MTC Device according to the weight information of the MTC Server. The specific technical solutions are as follows: Configure the weight information of each MTC Server in the MTC Server information list on the gateway device. The weight information of the MTC Server is related to the access capability of the MTC Server (for example, the maximum number of MTC devices that can be accessed). For example, the MTC Server1 and the MTC Server2 belong to one MTC Server information list, and the access capability of the MTC Server1 is 5. If the access capability of the MTC Server2 is 10,000 MTC Devices, the weight of the MTC Server1 can be 5 on the gateway device, and the weight of the MTC Server 2 is 1. When the gateway device selects the MTC Server for the MTC Device, the MTC Server may be selected according to the weight information. As described above, the gateway device can select the MTC Server 1 and the MTC Server 2 according to the probability of 5:1, so that the ratio of the selected MTC Server1 to the MTC Server 2 is 5:1, thereby ensuring load balancing of the MTC Server1 and the MTC Server2. .

 Step 204: After the gateway device determines the MTC server used by the MTC device, the registration information of the user terminal (for example, the identifier information of the MTC device (the identification information of the MTC Device is the MTC Server or the M2M user, in order to identify the M2M device, Is the username of the M2M device) or the IP address assigned to the MTC Device on the network side) Registered to the selected MTC Server. The specific method is as follows:

 Manner 1: The gateway device sends the registration information (such as address information or identification information) of the MTC Device to the MTC Server by using registration signaling, where the registration signaling can be delivered to the MTC Server by using an IP packet. After obtaining the IP data packet containing the registration signaling, the MTC Server obtains the registration signaling by parsing the IP data packet, and obtains the identification information or IP address of the MTC Device by parsing the registration signaling. In order to achieve the purpose of the MTC Server to verify the MTC Device, the registration signaling may include the password of the MTC Device;

 Manner 2: An interface is added between the gateway device and the MTC server. For example, the interface uses the Diameter protocol to notify the MTC Server of the MTC Device address information or identification information through a new message, such as a Subscribe Request message. To achieve the purpose of checking the MTC Device by the MTC Server, the newly added message may include the password of the MTC Device. The protocol type and the newly added message name adopted by the interface between the gateway device and the MTC Server are not limited.

Step 204a: Corresponding to the second registration scheme described in Embodiment 1, an interface is added between the GGSN/PGW and the MTC Server. For example, the interface uses the Diameter protocol to set the address of the MTC Device. The information and identification information is notified to the MTC Server by a new message request request (Subscribe Request) message.

 Step 204b: The MTC Server returns a registration confirmation message (Subscribe Ack) to the GGSN/PGW. Step 205: The gateway device returns a session request response message to the mobility management network element (for example, the MME sends a Create Session Response message to the PGW; or the SGSN sends a Create PDP Context Response message to the GGSN. ). Optionally, the session request response message may carry the information of the MTC server selected by the gateway device for the MTC device, notify the mobility management network element, and the network side has registered the MTC Device with the MTC Server. The gateway device constructs the TFT information of the MTC Device according to the information of the MTC Server selected by the MTC Device (the traffic flow template, which is mainly used to match the monthly traffic data stream), for example, the address information of the MTC Server is used as the destination address of the TFT. . The purpose of the TFT is to match the service data stream. As described above, the gateway device constructs the TFT information of the MTC Device according to the information of the MTC server selected by the MTC device, and the gateway device can restrict the MTC Device from accessing other MTCs according to the TFT information. Server. The GGSN/PGW also sends the TFT information to the mobility management network element in the session request response message.

 It should be noted that, in some specific application scenarios, the MTC Device can be registered to the MTC Server by default on the network side. In this case, the gateway device does not need to notify the MTC Device of the registration through the mobility management NE. .

 Step 206: The mobility management network element sends an access response message to the MTC Device. If the mobility management network element obtains the TFT information allocated by the gateway device for the MTC device, the mobility response network element carries the information to the MTC Device in the access response message. Optionally, the mobility management network element carries an indication cell in the access response message, where the indication information is used to indicate whether the MTC Device has registered the MTC Device information to the network side. If the indication cell identifies that the gateway device has registered the information of the MTC Device to the network side, the MTC Device does not need to initiate the registration process to the MTC Server. The access response message may be: an Active PDP Context Accept or a Default Bearer Request/Attach accept message.

An embodiment of the present invention provides a method for implementing registration, by using a gateway device to select an MTC Server for an MTC Device, and the gateway device registers the information of the MTC Device to the MTC Server. In this way, the MTC Device does not need to support the SIP protocol, and the function realizes the billing, which reduces the delay of the MTC Device registration, and does not need to send the information of the MTC Server to the MTC Device, thereby improving the security of the network. In addition, the network side can dynamically select the MTC server according to the weight information of the MTC server, which can ensure the load sharing of the MTC server and avoid the downtime caused by the unbalanced load of the MTC Server. It should be noted that the embodiment of the present invention is described by using the communication system of the M2M application as an example. However, those skilled in the art can understand that the M2M application environment is only a specific application scenario of the present invention, and the embodiment of the present invention further It can be applied to other communication systems (such as the communication system of H2H), which is not limited by the embodiment of the present invention.

 As shown in FIG. 4, a method for reselecting an application server for a user equipment according to an embodiment of the present invention needs to be described. After the user equipment is registered to the application server, if the registered application server is overloaded (Overload), the fault occurs. Down) or restart (Reset). In this case, you need to re-select the application server for registration with the user equipment without affecting the access of the user equipment. The embodiment of the present invention is described by the M2M application. The user equipment is specifically an MTC Device, and the application server is specifically an MTC Server, and the gateway device is specifically a GGSN/PGW. It can be understood by those skilled in the art that the embodiments of the present invention can be applied not only to an M2M application environment but also to other communication systems, such as an H2H communication system. The embodiment of the invention does not limit this. The method for reselecting an application server for a user device includes:

Step 401: The gateway device detects whether the MTC Server (which is the Source MTC Server) is overloaded, faulty, or restarted. The specific detection method may be the following two methods. One method is that the gateway device periodically sends a detection message (which may be a detection data packet) to the Source MTC Server (source MTC Server), and the source MTC Server receives the detection sent by the gateway device. The message needs to be acknowledged when the message is sent (a reply packet can be returned to the gateway device). When the gateway device sends a detection message to the Source MTC Server for the first time, the Source MTC Server responds to the detection message, and the Source MTC Server indicates a Counter in the detection response message, and the value of the Counter may be an initial value. . When the subsequent gateway device periodically sends a detection message to the Source MTC Server, the Source MTC Server replies with a detection response message. If the Source MTC Server works normally, the Counter value in the detection response message does not change. If the Source MTC Server is overloaded, faulty, or restarted. Then, the value of the Counter in the response message is changed, for example, the value of the Counter is increased by 1. The gateway device can determine whether the Source MTC Server has passed according to the Counter value in the Source MTC Server detection response message. Load, fault or restart. In addition, the gateway device may also determine whether the Source MTC Server is overloaded, faulty, or restarted according to whether a response message returned by the Source MTC Server is received within a certain period of time. For example, the gateway device can determine whether the Source MTC Server is overloaded, faulty, or restarted according to the length of time that the response message of the Source MTC Server is not received. For example, if the response message of the Source MTC Server is not received within the T1 duration and the response message of the Source MTC Server is received within the T2 duration (T2>T1), the gateway device may consider the Source MTC Server to be overloaded. If the response message of the source MTC server is not received within the T2 duration, the GGSN/PGW may consider that the source MTC server is faulty or restarted. The specific T1 and Τ2 may be set according to the system requirements, which is not limited by the embodiment of the present invention. . Another detection method is that the Source MTC Server can send an indication message to the GGSN/PGW to overload, fault or restart through an interface with the gateway device.

 Step 402: When the gateway device detects that the MTC Server is overloaded, faulty, or restarts, the gateway device reselects the MTC Server in the MTC Server information list described in the embodiment corresponding to FIG. 2 for accessing the MTC Device of the MTC Server.

First, the gateway device needs to learn, according to the saved MTC Device context information, the MTC Device that is connected to the overloaded, faulty, or restarted MTC Server. The gateway device needs to learn to access the overload, fault, or restart according to the saved MTC Device context information. The specific method of the MTC device of the MTC server may be: the MTC Server information is included in the MTC Device context information, and the gateway device may learn, by using the MTC Server information in the MTC Device context information, the MTC Server that is connected to the overload, fault, or restart. MTC Device. Another method for the gateway device to learn to access the MTC Device of the overloaded, faulty, or restarted MTC Server according to the saved MTC Device context information may be that the gateway device identifies the MTC Device according to the MTC Device context information, and the MTC. The industry user identification information of the Deice or the mapping between the APN information used by the MTC Device and the MTC Server information, and the MTC Device that accesses the overloaded, failed, or restarted MTC Server. After the gateway device learns to access the MTC Device of the overloaded, faulty or restarted MTC Server, the gateway device (GGSN or PGW) reselects the MTC Server for the MTC Device (may be selecting other ones in the MTC Server information list) The MTC Server can also select the source MTC Server. For example, in the scenario where the source MTC Server is restarted, the gateway device can select the source MTC Server for the MTC Device, according to the system requirements and the importance of the MTC Device (for example, high reliability (High Availability ) M2M application The MTC Device), the gateway device can reselect the MTC Server for some or all of the MTC Device. For example, the gateway device can learn the M2M application feature (MTC Feature) of the MTC Device according to the MTC Device context information. If the M2M application feature of the MTC device is high reliability, the gateway device can re-create the high reliability MTC Device. The method for selecting the MTC server to obtain the M2M application characteristics of the MTC device according to the MTC Device context information may be that the gateway device may learn the M2M application characteristics of the MTC Device or the gateway device according to the MTC according to the M2M application characteristics in the MTC Device context information. The identification information of the MTC Device in the Device Context Information, the industry user ID information to which the MTC Deice belongs, or the APN information used by the MTC Device, the identification information of the MTC Device configured on the gateway device, the industry user ID information of the MTC Deice, or the MTC. The M2M application characteristics corresponding to the APN information used by the device are used to learn the M2M application characteristics of the MTC Device. In addition, the gateway device may also determine to reselect the MTC Device of the MTC Server according to the identifier of the MTC Device in the MTC Device context or the industry user identifier to which the MTC Device belongs, that is, the gateway device can ensure that the specific MTC Device or the MTC Device of the specific industry is re-established. registered. In addition, the gateway device may also select a processing manner according to the state of the MTC Server. For example, when the MTC Server is overloaded, the gateway device may reselect the MTC Server for the part of the MTC Device (for example, the gateway device is based on the Gi interface (the gateway device and the MTC Server). Whether there is data transmission on the data interface established for each MTC Device, and whether to reselect the MTC Server for a certain MTC Device. When there is data transmission on a certain Gi interface, in order not to affect business continuity, the gateway device The MTC Server may not be reselected for the MTC Device corresponding to the Gi interface. When there is no data transmission on a Gi interface, the gateway device may reselect the MTC Server „ MTC Device corresponding to the Gi interface, when the MTC Server fails or When restarting, the gateway device can re-select the MTC Server for all the MTC devices mentioned above. After the gateway device selects the MTC Server for the MTC Device, the gateway device needs to register the information of the MTC Device to the selected MTC Server, and specifically select the MTC Server. And the registration method can refer to the description of the second embodiment (for example, the gateway device The user equipment transmits the registration information to the application server, registering the user equipment to the application server), the present embodiment not repeated embodiment.

The above description is that in the case that the MTC Server is overloaded, faulty or restarted, the gateway device reselects the MTC Server for the MTC Device (may be selected in the MTC Server information list) The other MTC Servers may also be selected from the source MTC Server. For example, in the scenario where the source MTC Server is restarted, the gateway device may select the source MTC Server for the MTC Device. Optionally, after the gateway device reselects the MTC Server for the MTC Device (either by selecting another MTC Server in the MTC Server information list or the source MTC Server), the gateway device is configured according to the information of the new MTC Server. The MTC Device constructs the TFT information. For example, the GGSN/PGW described in the second embodiment uses the address information of the newly selected MTC Server as the destination address of the TFT. The GGSN/PGW may initiate the bearer modification or update process to send the TFT information to the MTC Device. If the address assigned to the MTC Device changes, the MTC Device address information may be sent to the MTC Device in the bearer modification process. Another method for notifying the MTC Device address may be to notify the address or TFT information to the MTC Device by using the OMA DM (Open Mobile Alliance Device Mangement). The specific GGSN/PGW initiated bearer modification procedure and the OMA DM mechanism are all existing. The technology is not described in this embodiment.

 With the method described in this embodiment, the network side can re-select the application server for the user equipment according to the load information of the application server, without affecting the access of the user equipment, effectively achieving load balancing of the application server, and effectively reducing The impact on the user equipment due to overload, failure or restart of the application server.

As described above, in the case that the MTC Server is overloaded, faulty, or restarted, after the gateway device reselects the MTC Server for the MTC Device, optionally, the gateway device may initiate a process of tampering or updating the modified TFT information. Or the MTC Device address information is sent to the MTC Device. In the bearer modification or update process, the gateway device may also instruct the MTC Device to re-initiate the process of registering with the MTC Server. The specific implementation is as follows: after the gateway device (GGSN or PGW) selects the MTC Server for the MTC Device, the gateway device may use the MTC Server information in an Update Bearer Request (Update Bearer Request or Update PDP Context Request) (for example, Sending to the mobility management network element (SGSN or MME) by the existing cell PCO (Property configuration), optionally carrying the indication that the MTC Device initiates registration with the MTC Server in the update bearer (PDP) request message The indication of the process, for example, the carrying cause value (Casuse), instructs the MTC Device to initiate a registration process to the MTC Server. The mobility management network element sends a modify bearer request message (Modify default Bearer Request or Modify dedicate Bearer Request or Modify PDP Context Request) to the MTC Device. The message includes the information about the MTC server. Optionally, the message may carry indication information indicating that the MTC Device initiates a registration process to the MTC Server, for example, carrying a cause value (Casuse) to instruct the MTC Device to the MTC Server. Initiate the registration process. After receiving the message, the MTC Device initiates a registration process to the MTC Server according to the MTC Server information or the MTC Server information and the indication information carried in the message. Another method for informing the MTC Device to initiate the registration process to the MTC Server may be to notify the MTC Device of the MTC Server information or the MTC Server information and the indication information indicating the MTC Device initiation registration process by using the OMA DM. After receiving the OMA DM message, the MTC Device initiates a registration process to the MTC Server according to the MTC Server information or the MTC Server information and the indication information carried in the message. The OMA DM mechanism is a prior art, and is not described in this embodiment. The process of initiating the registration of the MTC Device is also a prior art, and is not described in this embodiment.

 With the method described in this embodiment, the network side can re-select the application server for the user equipment according to the load information of the application server, and can effectively load balance the application server. In addition, the user equipment is instructed to initiate a registration process to the application server to ensure that the user equipment initiates a registration process to the application server. An effective connection between the user device and the application server.

 Corresponding to the above-described method embodiments provided by the present invention, the present invention also provides an apparatus and system for implementing registration.

 As shown in FIG. 5, an apparatus for implementing registration according to an embodiment of the present invention includes: a receiving unit 501, configured to receive a request message sent by a mobility management network element;

 The obtaining unit 502 is configured to acquire, according to the request message, application server information used by the user equipment corresponding to the request message;

 The first registration unit 503 is configured to register the user equipment to the application server.

 More preferably, FIG. 6 is a schematic diagram of another apparatus for implementing registration according to an embodiment of the present invention. Further, the request message received by the receiving unit 501 includes a user equipment identifier, an APN of the user equipment, and a user equipment. At least one of the industry user IDs.

 The obtaining unit 502 is specifically configured to acquire application server information used by the user equipment according to the request message and configuration information; or

 The request message includes application server information used by the user equipment, and the acquiring unit

502 is specifically configured to obtain, from the request message, application server information used by the user equipment; or The obtaining unit 502 is specifically configured to query the DNS server for the application server information used by the user equipment according to the user equipment identifier, the APN of the user equipment, or the industry user identifier to which the user equipment belongs.

 The device may further include: a storage unit 504, configured to store configuration information of the user equipment, where the acquiring unit 502 is specifically used when the configuration information of the user equipment is a correspondence between the user equipment identifier and the application server information. Querying, according to the user equipment identifier included in the request message, a corresponding relationship between the user equipment identifier and the application server information, and acquiring application server information corresponding to the user equipment;

 Or,

 When the configuration information of the user equipment is the corresponding relationship between the APN and the application server information, the obtaining unit 502 is specifically configured to query the correspondence between the APN and the application server information according to the APN of the user equipment included in the request message. Relationship, acquiring application server information corresponding to the user equipment;

 Or,

 When the configuration information of the user equipment is the corresponding relationship between the user equipment identification segment and the application server information, the obtaining unit 502 is specifically configured to query the user according to the user equipment identification segment to which the user equipment identifier included in the request message belongs. Corresponding relationship between the device identification segment and the application server information, and acquiring application server information corresponding to the user equipment;

 Or,

 When the configuration information of the user equipment is the corresponding relationship between the industry user identifier and the application server information, the obtaining unit 502 is specifically configured to query, according to the industry user identifier that the user equipment belongs to in the request message, Corresponding relationship between the industry user identifier and the application server information, and acquiring application server information corresponding to the user equipment.

 The device further includes: a first selecting unit 505, configured to select an application server from the application server information corresponding to the user equipment according to the weight information of the application server.

 The first registration unit 503 is specifically configured to send registration information of the user equipment to the selected application server, and register the user equipment to the selected application server.

The device further includes: a generating unit 506, configured to generate data flow template information according to the selected server; As shown in FIG. 7 , an apparatus for implementing registration according to an embodiment of the present invention includes: a second selecting unit 701, configured to be part or all users corresponding to the application server when an application server is overloaded, faulty, or restarted. The device selects an application server;

 The second registration unit 702 is configured to register the user equipment to the selected application server. Further, the second selecting unit further includes: a determining module 703, and a selecting submodule 704. a determining module 703, configured to determine, according to context information of the user equipment, a user equipment corresponding to the application server when the application server is overloaded, faulty, or restarted;

 a sub-module 704, configured to select an application server for a part or all of the user equipments determined by the gateway device according to an application feature of the user equipment, or a sub-module 704, configured to identify, according to the user equipment identifier, the gateway The part or all of the user equipments determined by the device selects an application server; or, the selection sub-module 704 is configured to select an application server for some or all of the user equipments determined by the gateway device according to the industry user identifier to which the user equipment belongs.

 The determining module 703 is specifically configured to: when the user equipment context information stored by the gateway device includes the application server information, determine the user equipment corresponding to the application server according to the context information; or

 The determining module 703 is specifically configured to query the configuration information of the user equipment according to the user equipment context information, and obtain the user equipment corresponding to the application server.

 The selection sub-module 704 is further configured to acquire the user equipment application feature from the context information of the user equipment; or the selection sub-module 704 is further configured to acquire the user equipment identification information and the industry configured by itself. User identification information or application characteristics corresponding to the access point name APN information.

 As shown in FIG. 8, a system for implementing registration according to an embodiment of the present invention includes: a mobility management network element 801, configured to send a request message to a gateway device 802;

 The gateway device 802 is configured to receive the request message sent by the mobility management network element 801, obtain the application server information corresponding to the user equipment according to the request message and the configuration information, and register the user equipment to the application server.

The embodiment of the invention provides a method, a device and a system for implementing registration. The gateway device receives the request message sent by the mobility management network element, obtains the application server information corresponding to the user equipment according to the configuration information, and registers the user equipment on the application server. The registration of the user equipment to the application server is avoided, so that the user equipment function is implemented, and the user equipment does not need to obtain the information of the application server. And improve the security of the network.

 It should be noted that, in the prior art, the UE may not be assigned an IP address by the 3GPP network, but the UE sends a DHCP REQUEST message to the DHCP (Dynamic Host Configuration Protocol), and the DHCP allocates an IP address to the UE, and this will be The IP address and AF information is sent to the UE in a DHCP ACK message. When the MTC device obtains the IP address and the MTC server (the AF in the H2H application) from the DHCP server, the DHCP load is increased due to the large number of MTC devices. As a result, the network is congested and the registration delay is increased. Correspondingly, the above embodiments provided by the present invention can reduce the DHCP load and avoid network congestion, so that the user equipment does not need to obtain the information of the MGC Server, thereby improving the security of the network.

 One of ordinary skill in the art will appreciate that all or part of the steps in implementing the above-described embodiments may be accomplished by a program instructing associated hardware, which may be stored in a computer readable storage medium. The storage medium is, for example, a ROM/RAM, a magnetic disk, an optical disk, or the like.

 The above description is only a preferred embodiment of the present invention, and it should be noted that those skilled in the art can also make several improvements and retouchings without departing from the principles of the present invention. It is considered as the scope of protection of the present invention.

Claims

Rights request  A method for implementing registration, characterized in that it comprises:  The gateway device receives the request message sent by the mobility management network element;  The gateway device acquires application server information used by the user equipment corresponding to the request message according to the request message;  The gateway device registers the user device to the application server.  The method according to claim 1, wherein the request message includes at least one of a user equipment identifier, an access point name APN of the user equipment, and an industry user identifier to which the user equipment belongs.  The method of claim 1, wherein the obtaining, by the gateway device, the application server information used by the user equipment corresponding to the request message according to the request message includes:  The gateway device acquires application server information used by the user equipment corresponding to the request message according to the request message and the configuration information; or  The request message includes application server information used by the user equipment, and the gateway device obtains, from the request message, application server information used by the user equipment corresponding to the request message.  The method of claim 2, wherein the obtaining, by the gateway device, the application server information used by the user equipment corresponding to the request message according to the request message includes:  The gateway device queries the domain name system DNS server for the application server information used by the user equipment according to the user equipment identifier, the APN of the user equipment, or the industry user identifier to which the user equipment belongs.  5. The method of claim 3, wherein the method further comprises:  The gateway device stores configuration information of the user equipment.  6. The method of claim 3 or 5, wherein  When the configuration information of the user equipment is the corresponding relationship between the user equipment identifier and the application server information, the gateway device acquires the application server information used by the user equipment corresponding to the request message according to the request message and the configuration information, including: The gateway device queries the corresponding relationship between the user equipment identifier and the application server information according to the user equipment identifier included in the request message, and obtains application server information corresponding to the user equipment;  Or, When the configuration information of the user equipment is a correspondence between the APN and the application server information, The acquiring, by the gateway device, the application server information used by the user equipment corresponding to the request message according to the request message and the configuration information includes: the gateway device querying the APN and the application server according to the APN of the user equipment included in the request message. Corresponding relationship of the information, acquiring application server information corresponding to the user equipment;  Or,  When the configuration information of the user equipment is the corresponding relationship between the user equipment identification segment and the application server information, the application, by the gateway device, the application server information used by the user equipment corresponding to the request message according to the request message and the configuration information includes: The gateway device queries the correspondence between the user equipment identification segment and the application server information according to the user equipment identification segment to which the user equipment identifier is included in the request message, and obtains the application server information corresponding to the user equipment;  Or,  When the configuration information of the user equipment is the correspondence between the industrial user identifier and the application server information, the gateway device acquires the application server information used by the user equipment corresponding to the request message according to the request message and the configuration information, including: The gateway device queries the corresponding relationship between the industry user identifier and the application server information according to the industry user identifier of the user equipment that is included in the request message, and obtains the application server information corresponding to the user equipment.  The method of claim 3, wherein when the request message includes application server information used by the user equipment, the gateway device obtains, from the request message, the request message corresponding to Before the application server information used by the user equipment, the method further includes:  The subscription data in the home location register or the home subscription server includes application server information used by the user equipment, and the mobility management network element acquires an application server used by the user equipment from the home location register or the home subscription server. Information; or,  The DNS server includes the application server information used by the user equipment. The mobility management network element obtains the application server information used by the user equipment from the DNS server according to the user equipment identifier, the APN of the user equipment, or the industry user identifier to which the user equipment belongs.  The method of claim 1, wherein the method further includes: before the gateway device registers the user equipment with the application server, the method further includes: The gateway device selects an application server from the application server information corresponding to the user equipment according to the weight information of the application server. 9. The method of claim 8, wherein the registering, by the gateway device, the user equipment to the application server comprises:  The gateway device sends the registration information of the user equipment to the selected application server, and registers the user equipment to the selected application server.  The method of claim 9, wherein the method further comprises:  The gateway device generates data flow template information according to the selected server.  The method of claim 1, wherein the method further comprises: before the gateway device receives the request message sent by the mobility management network element, the method further includes:  The mobility management network element receives an access request message sent by the user equipment, where the access request message includes at least one of a user equipment identifier, an APN of the user equipment, and an industry user identifier to which the user equipment belongs.  12. A method for implementing registration, characterized in that it comprises:  When the application server is overloaded, faulty, or restarted, the gateway device selects an application server for some or all of the user equipments corresponding to the application server;  The gateway device registers the user device to the selected application server.  The method of claim 12, wherein the selecting, by the gateway device, the application server for some or all of the user equipments corresponding to the application server includes:  The gateway device determines, according to the context information of the user equipment, the user equipment corresponding to the application server;  The gateway device selects an application server for some or all of the user equipments determined by the gateway device according to the application characteristics of the user equipment; or, the gateway device selects an application according to the user equipment identifier for some or all user equipments determined by the gateway device. The server device selects an application server for some or all of the user equipments determined by the gateway device according to the industry user identifier to which the user equipment belongs.  The method according to claim 13, wherein the determining, by the gateway device, the user equipment corresponding to the application server according to the context information of the user equipment includes:  The user equipment context information stored by the gateway device includes application server information, and the gateway device determines the user equipment corresponding to the application server according to the context information; or The gateway device queries the configuration information of the user equipment according to the user equipment context information, and obtains the User equipment corresponding to the application server.  The method of claim 13, wherein the method further comprises: the gateway device acquiring the user equipment application feature from the context information of the user equipment; or  The gateway device acquires an application feature that is configured by itself and corresponding to the user equipment identification information, the industry user identification information, or the access point name APN information.  The method of claim 11, wherein the registering, by the gateway device, the user equipment to the selected application server comprises:  The gateway device sends the registration information of the user equipment to the application server, and registers the user equipment to the application server; or  The mobility management network element receives an update bearer request message sent by the gateway device, where the update bearer request message includes information of the selected application server, and the mobility management network element sends a modify bearer request message to the user equipment, where And modifying, in the bearer request message, the information of the selected application server, where the user equipment registers with the selected application server according to the modify bearer request message.  17. A device for implementing registration, characterized in that it comprises:  a receiving unit, configured to receive a request message sent by the mobility management network element;  An obtaining unit, configured to acquire, according to the request message, application server information used by the user equipment corresponding to the request message;  a first registration unit, configured to register the user equipment to the application server.  The device according to claim 17, wherein the request message includes at least one of a user equipment identifier, an APN of the user equipment, and an industry user identifier to which the user equipment belongs.  The obtaining unit is specifically configured to acquire application server information used by the user equipment according to the request message and configuration information; or The request message includes the application server information used by the user equipment, where the acquiring unit is specifically configured to acquire the application server information used by the user equipment from the request message; or, the acquiring unit is specifically configured to use The user equipment identifier, the APN of the user equipment, or the industry user ID to which the user equipment belongs is queried to the domain name system DNS server for the application server information used by the user equipment. The device according to claim 17, wherein the device further includes: a storage unit, configured to store configuration information of the user equipment,  20. Apparatus according to claim 19 wherein:  When the configuration information of the user equipment is the corresponding relationship between the user equipment identifier and the application server information, the acquiring unit is specifically configured to query the user equipment identifier and the application server information according to the user equipment identifier included in the request message. Corresponding relationship, obtaining application server information corresponding to the user equipment;  Or,  When the configuration information of the user equipment is the mapping between the APN and the application server information, the acquiring unit is specifically configured to query the correspondence between the APN and the application server according to the APN of the user equipment included in the request message. Obtaining application server information corresponding to the user equipment; or  When the configuration information of the user equipment is a correspondence between the user equipment identification segment and the application server information, the acquiring unit is specifically configured to query the user equipment according to the user equipment identification segment to which the user equipment identifier included in the request message belongs Corresponding relationship between the identifier segment and the application server, and acquiring application server information corresponding to the user equipment;  Or,  When the configuration information of the user equipment is the corresponding relationship between the industry user identifier and the application server information, the acquiring unit is specifically configured to query the industry according to the industry user identifier to which the user equipment is included in the request message. Corresponding relationship between the user identifier and the application server information, and acquiring application server information corresponding to the user equipment.  The device according to claim 17, wherein the device further comprises: a first selecting unit, configured to select an application server from the application server information corresponding to the user equipment according to the weight information of the application server.  The device according to claim 21, wherein the first registration unit is specifically configured to send registration information of the user equipment to a selected application server, and register the user equipment to the selected On the application server. The device according to claim 17, wherein the device further comprises: a generating unit, configured to generate data flow template information according to the selected server. 24. A device for implementing registration, characterized in that it comprises:  a second selecting unit, configured to select an application server for some or all user equipments corresponding to the application server when the application server is overloaded, faulty, or restarted;  And a second registration unit, configured to register the user equipment to the selected application server.  The device according to claim 24, wherein the second selecting unit comprises: a determining module, configured to determine, according to context information of the user equipment, that the application server corresponds to when the application server is overloaded, faulty, or restarted User equipment;  a sub-module, configured to select an application server for a part or all of the user equipments determined by the gateway device according to an application feature of the user equipment; or, selecting a sub-module, configured to determine, according to the user equipment identifier, the gateway device The part or all of the user equipments select an application server; or, the selection submodule is configured to select an application server for some or all of the user equipments determined by the gateway device according to the industry user identifier to which the user equipment belongs.  26. Apparatus according to claim 25 wherein:  The determining module is configured to: when the user equipment context information stored by the gateway device includes the application server information, determine, according to the context information, the user equipment corresponding to the application server; or  The determining module is configured to query the configuration information of the user equipment according to the user equipment context information, and obtain the user equipment corresponding to the application server.  The device according to claim 25, wherein the selection sub-module is further configured to acquire the user equipment application feature from context information of the user equipment; or, the selection sub-module is further used to: Obtaining an application feature that is configured by itself and corresponding to the user equipment identification information, the industry user identification information, or the access point name APN information.  28. A system for implementing registration, characterized in that it comprises:  a mobility management network element, configured to send a request message to the gateway device;  The gateway device is configured to receive the request message sent by the mobility management network element, obtain the application server information corresponding to the user equipment according to the request message and the configuration information, and register the user equipment to the application server.