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

Method, device and system for implementing registration Download PDF

Info

Publication number
CN102177757B
CN102177757B CN2009801100767A CN200980110076A CN102177757B CN 102177757 B CN102177757 B CN 102177757B CN 2009801100767 A CN2009801100767 A CN 2009801100767A CN 200980110076 A CN200980110076 A CN 200980110076A CN 102177757 B CN102177757 B CN 102177757B
Authority
CN
China
Prior art keywords
user equipment
application server
information
request message
gateway
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
CN2009801100767A
Other languages
Chinese (zh)
Other versions
CN102177757A (en
Inventor
周汉
吴问付
陈中平
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of CN102177757A publication Critical patent/CN102177757A/en
Application granted granted Critical
Publication of CN102177757B publication Critical patent/CN102177757B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/06—Authentication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/71—Hardware identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/60—Context-dependent security
    • H04W12/69—Identity-dependent
    • H04W12/72—Subscriber identity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/16—Gateway arrangements

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)

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

Method, device and system for realizing registration
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
To address the challenges of wireless broadband technology, 3GPP (3 GPP) is maintainedrdGeneration partnership project, third Generation partnership project) the leading edge of the network, LTE (Long Term Evolution) was established by 3GPP in 2004. Under the guidance of the evolution plan, a new architecture of mobile communication network is defined, which is compatible with the current GPRS (Ge)A random Packet Radio Service (gprs)/UMTS (Universal Mobile telecommunications System) is more flat and only a Packet domain is reserved, and thus may be referred to as an EPS (evolved Packet network).
In the existing communication system, two applications can be mainly divided: H2H (Human to Human) application, M2M (Machine to Machine) application. In H2H Application, after a UE attaches to a network, a network side (e.g., a pgw (pdn gateway)) may allocate an IP address to the UE, and after obtaining the IP address, the UE may initiate a registration procedure to an AF (Application Function, Application server), and register its UE identification information and the IP address allocated by the network side in the AF. The method for the UE to obtain the IP address may be as follows: when the UE attaches to a Network (E-UTRAN (Evolved Universal Radio Access Network)) or the UE initiates a PDP context activation procedure (geran (gsm edge Radio Access Network)/UTRAN Network), a Network side (e.g., a PGW or a GGSN (gateway GPRS Support Node)) allocates an IP address to the UE, and carries AF information (e.g., address information of the AF) to the UE in a default bearer creation acceptance message or a PDP context activation acceptance message. However, since the M2M application (which refers to network communication between one or more network elements without human involvement, such as applications of traffic control and management, factory monitoring, remote meter reading, etc.) has the characteristics of simple service application and a large number of MTC (machine Type communication) devices (M2M terminal devices), the 3GPP network allocates an IP address to the MTC Device and notifies the MTC Device of information of the MTC Server, which may cause the MTC Device to have a complex function and reduce the security of the network.
Disclosure of Invention
To address the challenges of wireless broadband technology, 3GPP (3 GPP) is maintainedrd Generation PartnershipProject，Third generation partnership project) the leading edge of networks, LTE (Long Term Evolution) was established by 3GPP in 2004. Under the guidance of the evolution plan, a new architecture of a Mobile communication network is defined, which is more flat than the current GPRS (General Packet Radio Service)/UMTS (Universal Mobile telecommunications System) and only reserves a Packet domain, and thus may be referred to as EPS (evolved Packet network).
In the existing communication system, two applications can be mainly divided: H2H (Human to Human) application, M2M (Machine to Machine) application. In H2H Application, after a UE attaches to a network, a network side (e.g., a pgw (pdn gateway)) may allocate an IP address to the UE, and after obtaining the IP address, the UE may initiate a registration procedure to an AF (Application Function, Application server), and register its UE identification information and the IP address allocated by the network side in the AF. The method for the UE to obtain the IP address may be as follows: when the UE attaches to a Network (E-UTRAN (Evolved Universal Radio Access Network)) or the UE initiates a PDP context activation procedure (geran (gsm edge Radio Access Network)/UTRAN Network), a Network side (e.g., a PGW or a GGSN (gateway GPRS Support Node)) allocates an IP address to the UE, and carries AF information (e.g., address information of the AF) to the UE in a default bearer creation acceptance message or a PDP context activation acceptance message. However, since the M2M application (which refers to network communication between one or more network elements without human involvement, such as applications of traffic control and management, factory monitoring, remote meter reading, etc.) has the characteristics of simple service application and a large number of MTC (machine Type communication) devices (M2M terminal devices), the 3GPP network allocates an IP address to the MTC Device and notifies the MTC Device of information of the MTC Server, which may cause the MTC Device to have a complex function and reduce the security of the network.
Drawings
Fig. 1 is a schematic flowchart of a method for implementing registration according to an embodiment of the present invention;
fig. 2 is a schematic flowchart of another method for implementing registration according to an embodiment of the present invention;
fig. 3a is a schematic diagram of a correspondence relationship between an APN and an MTC Server according to an embodiment of the present invention;
fig. 3b is a schematic diagram illustrating a correspondence relationship between an MTC Device identity and an MTC Server according to an embodiment of the present invention;
fig. 3c is a schematic diagram of an MTC Device list under the MTC Server according to an embodiment of the present invention;
fig. 3d is a schematic diagram of a correspondence relationship between the MTC Server and the MTC Device identification segment according to the embodiment of the present invention;
fig. 3e is a schematic diagram of a correspondence relationship between an industry user identifier and an MTC Server according to an embodiment of the present invention;
fig. 4 is a flowchart illustrating 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. 6 is a schematic diagram of another apparatus for implementing registration according to an embodiment of the present invention;
fig. 7 is a schematic diagram of another apparatus for implementing registration according to an embodiment of the present invention;
fig. 8 is a schematic diagram of a system for implementing registration according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
As shown in fig. 1, a method for implementing registration provided in an embodiment of the present invention includes:
step 101: the gateway equipment receives a request message sent by a mobility management network element;
step 102: the gateway equipment acquires the application server information used by the user equipment corresponding to the request message according to the request message;
step 103: the gateway device registers the user device with the application server.
In the embodiment of the invention, the gateway equipment receives the request message sent by the mobility management network element, acquires the information of the application server used by the user equipment according to the request message, and registers the user equipment on the application server, so that the user equipment is prevented from registering to the application server, the function of the user equipment is simple to realize, and the user equipment does not need to acquire the information of the application server, thereby improving the network security.
It should be noted that the embodiment of the present invention may be applied to an M2M scenario, where the user equipment may specifically be an MTC Device, and the application Server may specifically be an MTC Server. In the following embodiments, an M2M application scenario is taken as an example for explanation, but it is understood by those skilled in the art that the embodiments of the present invention are not limited to the M2M application scenario.
As shown in fig. 2, another method for implementing registration provided in the embodiment of the present invention includes:
step 201: the MTC Device sends an Access request message to a mobility management network element, wherein the Access request message comprises at least one of an identifier of the MTC Device, APN (Access Point Name) information carried by the MTC Device and an industry user identifier of the MTC Device. The industry User identifier of the MTCDevice refers to an identifier of a User equipment group (group) to which the MTC Device belongs, an identifier of an M2M industry User (MTC User) to which the MTC Device belongs, an identifier of an M2M application Subscriber (MTC Subscriber) to which the MTC Device belongs, and information indicating the group or industry User identifier, for example, if the group, User group or industry User to which the User equipment belongs is identified by an APN, the APN is the identifier of the group or User group or industry User to which the User equipment belongs, and the specific implementation manner of the present invention is not limited. It should be noted that, in a specific application, for a GERAN/UTRAN network, the mobility management element is an SGSN, and the access Request message may be a PDP Context activation Request message (ActivePDP Context Request); for an E-UTRAN network, the mobility management network element is an MME, and the access Request message may be an Attach Request message or a PDN Connectivity 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 should be noted that the embodiment of the present invention is not limited to the session request message), where the session request message includes at least one of an identifier of the MTC Device, APN information carried by the MTC Device, and an industry user identifier of the mtcc Device. 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 an E-UTRAN network, the gateway device is a PGW, the mobility management element sends a Session Request message to the gateway device, specifically, an MME sends a Create Session Request (Create Session Request) message to the SGW, and then the SGW sends the Create Session Request (Create Session Request) message to the PGW; or, for the GERAN/UTRAN network, the gateway device is the GGSN, and the mobility management element sends the session Request message to the gateway device, specifically, the SGSN sends a Create PDP Context Request (Create PDP Context Request) message to the GGSN.
Optionally, the information of the MTC Server used by the MTC Device (for example, the information of the MTC Server that can be used by the APN signed in the PDN subscription context) 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 industrial User, the MTC User, or the MTC subscription to which the MTC Device belongs). The mobility management network element may obtain the MTC Server information used by the MTC Device in the subscription data, and may notify the gateway Device of the MTC Server information used by the MTC Device carried in the session request message.
Step 203: the gateway device obtains the application server information used by the MTCDevice according to the received request message (specifically, session request message).
Specifically, the gateway Device queries configuration information on the gateway Device according to the identifier of the MTC Device, APN information carried by the MTC Device, or the industry user identifier to which the MTC Device belongs, and obtains MTC Server information used by the MTC Device. Further, the gateway Device may select a suitable mtserver for the MTC Device from the obtained MTC Server information used by the MTC Device according to the weight information of the MTC Server.
It should be noted that, for the M2M application, the mtcservers used by all MTC devices under one industry user may be fixed, and the operator may configure the addresses of the MTC servers used by the MTC devices in the industry users on the gateway Device (PGW/GGSN).
In addition, the information of the MTC Server used by the MTC Device (for example, the information of the MTC Server that can be used by the APN signed in the PDN subscription context) 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 industrial User, the MTC User, or the MTC subscription to which the MTC Device belongs). The mobility management network element may obtain MTC Server information used by the MTC Device in the subscription data (for example, the mobility management network element sends a Location Update Request (Update Location Request) message to an HLR (Home Location Register) or an HSS (Home subscription Server) in an attach procedure or a tracking area Update or routing area Update procedure, and the HLR or the HSS carries the MTC Server information used by the MTC Device in a Location Update acknowledgement (Update Location Ack) message), so that the mobility management network element may carry the mtserver information used by the MTC Device in the session Request message and notify the MTC Server information to the gateway Device.
Another method for acquiring the information of the MTC Server used by the MTC Device may be that a mobility management network element or a gateway Device (GGSN or PGW) queries a DNS (Domain name system) Server according to an identifier of the MTC Device, APN information carried by the MTC Device, or an industry user identifier to which the MTC Device belongs, configures MTC Server information used by the MTC Device in the DNS Server according to the identifier of the MTC Device, APN information carried by the mtcc Device, or the industry user identifier to which the MTC Device belongs, and after receiving a 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 MTC Server information used by the MTC Device is carried in the query response message. 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 session request message to the gateway Device.
The gateway Device may acquire the MTC Server information used by the MTC Device in several ways:
the first method is as follows: the corresponding relationship between the APN and the MTC Server is configured, as shown in fig. 3a, as a corresponding relationship table between the APN and the mtserver. Specifically, the operator may subscribe to a specific APN for the industrial user, and the specific APN is included in the subscription data of the MTC Device of the industrial user in the HSS (Home subscription Server)/HLR (Home location Register). The gateway device (GGSN or PGW) configures the MTC Server information corresponding to the specific APN (i.e. the MTC Server information used by the industry user corresponding to the specific APN is configured in the gateway device). The gateway equipment can acquire the MTC Server information used by the MTC Device according to the APN corresponding to the MTC Device;
the second method comprises the following steps: and configuring the corresponding relation between the MTC Device and the MTC Server.
As shown in fig. 3b, in the correspondence table a of MTC devices and MTC servers, MTC Server information corresponding to each MTC Device Identifier (for example, the Identifier is an IMSI (International mobile subscriber Identifier) or an IMEI (International mobile equipment Identifier)) is configured in the gateway Device; or,
as shown in fig. 3c, for the configured MTC Device list B under the MTC Server, an MTC Device identification list that each MTC Server can serve is configured in the gateway Device; or,
as shown in fig. 3d, in order to configure a correspondence table C between MTC servers and MTC Device identification segments, the gateway Device configures the MTC servers corresponding to the MTC Device identification segments, for example, a certain MTC Server may provide services for MTC devices in IMSI number segments 460350789123000 to 460350789123999 of industry users;
after the gateway Device acquires the MTC Device identifier, the MTC Server information used by the MTCC Device can be acquired by querying the table A or the table B; or, the MTC Server information used by the MTC Device may be obtained according to the identifier segment lookup table C to which the MTC Device identifier belongs.
As shown in fig. 3e, it is a corresponding relationship table between configured industry users and MTC servers. The gateway device configures a corresponding relationship between an industry user identifier (e.g., a group identifier) and MTC Server information used by the industry user. After the gateway Device obtains the industry user identifier (e.g., group identifier) 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 acquiring the industry user identifier to which the MTC Device belongs by the gateway Device may be: the MTC Device carries the industry user identification of the MTC Device in an access message (such as an attachment message), and the MTC Device forwards the industry user identification to gateway equipment (GGSN or PGW) through a mobility management network element; or, another method may be that the mobility management network element (e.g., SGSN/MME) obtains MTC Device subscription data, obtains an industry user identifier to which the MTC Device belongs from the MTC Device subscription data, and forwards the obtained industry user identifier to the gateway Device (GGSN or PGW) in the session request message. The embodiment of the invention does not limit the method for obtaining the industry user identification of the MTCD device.
The third method comprises the following steps: information of the MTC Server used by the MTC Device is signed in the subscription data of the MTC Device (e.g. information of the MTC Server that can be used by this APN is signed in the PDN subscription Context). The mobility management network element may obtain, in the subscription data, MTC Server information used by the MTC Device (the specific manner is as described above, and is not described herein again), and then the mobility management network element may carry, in the session request message, the MTC Server information used by the MTC Device and notify the session request message to the gateway Device. When the session request message contains the MTC Server information used by the MTC Device, the gateway Device receives the session request message and extracts the information of the MTC Server used by the MTC Device.
The method is as follows: a mobility management network element or gateway Device (GGSN or PGW) queries a DNS Server according to an identifier of an MTC Device, APN information carried by the MTC Device or an industry user identifier to which the MTC Device belongs, and configures MTC Server information used by the MTC Device in 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, and after receiving a query request sent by the mobility management network element or gateway Device, the DNS Server returns a query response message according to the query request information and the configuration information, wherein the query response message carries the MTC Server information used by the MTCC 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 session request message to 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 four manners, but is not limited to the four manners.
The gateway Device obtains information of the MTC Server used by the MTC Device in any one of the four manners, where it is noted that there may be one or more MTC servers used by the MTC Device, and when there are multiple MTC servers used by the MTC Device, the information of the MTC Server may be an mtserver list, for example, an MTC Server IP address list or an MTC Server FQDN (FullyQualified Domain Name, where the MTC Server FQDN refers to Domain Name information of the MTC Server) 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 scheme is as follows:
and configuring the weight information of each MTC Server in the MTC Server information list on the gateway equipment. The weight information of the MTC Server is related to the access capability of the MTC Server (e.g., how many MTC devices can be accessed at maximum), for example, if the MTC Server1 and the MTC Server2 belong to an MTC Server information list, and the access capability of the MTC Server1 is 5 ten thousand MTC devices, and the access capability of the MTC Server2 is 1 ten thousand MTC devices, the weight of the MTC Server1 configured on the gateway Device is 5, and the weight of the MTC Server2 is 1. And when the gateway equipment selects the MTC Server for the MTC Device, the MTC Server can be selected according to the weight information. As described above, the gateway device may select the MTC Server1 and the MTC Server2 according to a probability of 5: 1, so as to ensure that the ratio of the selected MTC Server1 to the MTC Server2 is 5: 1, thereby ensuring that the MTC Server1 and the MTC Server2 are load balanced.
Step 204: after the gateway Device determines the MTC Server used by the MTC Device, register information of the user terminal (for example, identification information of the MTC Device (the identification information of the MTC Device is MTCServer or M2M user may be a user name of M2M Device for identifying the M2M Device) or an IP address allocated to the MTC Device by the network side) is registered in the selected MTC Server. The specific method comprises the following steps:
the first method is as follows: the gateway Device sends the registration information (such as address information or identification information) of the MTC Device to the MTC Server through registration signaling, wherein the registration signaling can be transmitted to the MTC Server through an IP data packet. After the MTC Server obtains the IP data packet containing the registration signaling, the MTC Server obtains the registration signaling by analyzing the IP data packet, and obtains the identification information or the IP address of the MTC Device by analyzing the registration signaling. In order to achieve the purpose that the MTC Server checks the MTC Device, the registration signaling can contain a password of the MTCD Device;
the second method comprises the following steps: an interface is added between the gateway Device and the MTC Server, for example, the interface uses a Diameter protocol, and notifies the MTC Server of address information or identification information of the MTC Device through a Subscribe Request message by adding a message, such as a Subscribe Request message. In order to achieve the purpose of checking the MTC Device by the mtserver, the new message may include a 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 in this patent.
Step 204 a: corresponding to the second registration scheme described in embodiment 1, an interface is added between the GGSN/PGW and the MTCServer, for example, the interface uses a Diameter protocol, and notifies the MTCServer of address information and identification information of the MTC Device through a new message registration Request (Subscribe Request) message.
Step 204 b: the MTC Server returns a registration acknowledgement message (Subscribe Ack) to the GGSN/PGW.
Step 205: the gateway device returns a Session request Response message to the mobility management element (e.g., MME sends Create Session Response message to PGW, or SGSN sends Create PDP Context Response message to GGSN). Optionally, the session request response message may carry information of an MTC Server selected by the gateway Device for the MTC Device, and notify the mobility management network element that the network side has registered to the MTC Server for the MTC Device. The gateway Device constructs TFT information (traffic flow Template, mainly used for matching service data flow) of the MTC Device according to the information of the MTC Server selected for the MTC Device, for example, using address information of the MTC Server as a destination address of the TFT. The purpose of the TFT is to match service data streams, and as described above, the gateway Device constructs the TFT information of the MTC Device according to the information of the MTC Server selected for the MTC Device, so that the gateway Device can restrict the MTC Device from accessing other mtcservers according to the TFT information. And the GGSN/PGW sends the TFT information to a mobility management network element in a session request response message.
It should be noted that, in some specific application scenarios, the network side may be set as default to register the MTCDevice on the MTC Server, and at this time, the gateway Device does not need to notify the MTC Device of the performed registration through the mobility management network element.
Step 206: and the mobility management network element sends an access response message to the MTC Device. And if the mobility management network element obtains the TFT information distributed by the gateway equipment for the MTC Device, carrying 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 cell is used to indicate whether the MTC Device has registered the MTC Device information to the network side. If the information of the MTC Device is registered to the network side by the indicating cell identification gateway equipment, the MTC Device does not need to initiate a registration process to the MTC Server. The access response message may specifically be: PDP Context activation Accept message (Active PDP Context Accept) or Default bearer setup request message or Attach Accept message (Active Default bearer request/Attach Accept).
The embodiment of the invention provides a method for realizing registration, wherein the gateway equipment selects the MTC Server for the MTC Device, and registers the information of the MTC Device into the MTC Server, so that the MTC Device does not need to support an SIP protocol, the function is simple to realize, the time delay of registering the MTC Device is reduced, the information of the MTC Server does not need to be sent to the MTC Device, and the network security is improved. In addition, the network side can dynamically select the MTC Server according to the weight information of the MTC Server, so that the load sharing of the MTCMOS Server can be ensured, and the problem of paralysis caused by unbalanced load of the MTC Server is avoided. It should be noted that, in the embodiment of the present invention, a communication system applied to M2M is taken as an example for illustration, but it is understood by those skilled in the art that an application environment of M2M is only a specific application scenario of the present invention, and the embodiment of the present invention may also be applied to other communication systems (for example, a communication system of H2H), and the embodiment of the present invention is not limited to this.
As shown in fig. 4, for a method for reselecting an application server for a user equipment according to an embodiment of the present invention, it should be noted that, after the user equipment registers to the application server, if the registered application server is overloaded (Overload), failed (Down), or restarted (Reset), the application server needs to be reselected for the user equipment to register without affecting access of the user equipment. The embodiment of the present invention is described with an M2M application, where the user equipment is specifically an MTC Device, the application server is specifically an MTCServer, and the gateway Device is specifically a GGSN/PGW. It will be appreciated by those skilled in the art that the embodiments of the present invention may be applied not only to M2M application environment, but also to other communication systems, such as H2H communication system. The embodiments of the present invention are not limited in this regard. The method for reselecting the application server for the user equipment comprises the following steps:
step 401: the gateway equipment detects whether the MTC Server is overloaded, failed or restarted. The specific detection method may be two, one is that the gateway device periodically sends a detection message (which may be a detection packet) to a Source MTC Server, and when the Source MTC Server receives the detection message sent by the gateway device, the Source MTC Server needs to respond to the detection message (a response packet may 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 replies to the detection message, and the Source MTCServer indicates a Counter, whose value may be an initial value, in the detection reply message. When the subsequent gateway equipment periodically sends a detection message to the Source MTC Server, the Source MTC Server replies a detection response message, if the Source MTC Server works normally, the Counter value in the detection response message is unchanged, and if the Source MTC Server is overloaded, has a fault or is restarted, the Counter value in the detection response message is changed, for example, the Counter value is increased by 1. The gateway device can judge whether the Source MTC Server is overloaded, failed or restarted according to the Counter value in the Source MTC Server detection response message. In addition, the gateway device can also judge whether the Source MTC Server is overloaded, failed or restarted according to whether a response message returned by the Source MTC Server is received within a certain time. For example, the gateway device may determine whether the Source MTC Server is overloaded, failed, or restarted according to the duration of not receiving the response message of the Source MTC Server. For example, if the response message of the Source MTC Server is not received within the time duration T1 but is received within the time duration T2 (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 duration of T2, the GGSN/PGW may consider that the Source MTC Server fails or restarts, and the specific T1 and T2 may be set according to the system requirements, which is not limited in the embodiment of the present invention. Another detection method is that the Source MTC Server may send an indication message to notify the GGSN/PGW of overload, failure, or restart through an interface with the gateway device.
Step 402: when the gateway Device detects that the MTC Server is overloaded, failed, or restarted, the gateway Device reselects the MTC Server in the mtserver information list described in the embodiment corresponding to fig. 2 for the MTC Device accessing the MTC Server.
Firstly, the gateway Device needs to know the MTC Device accessed to the overloaded, failed or restarted MTC Server according to the stored MTC Device context information, and the specific method that the gateway Device needs to know the mtcc Device accessed to the overloaded, failed or restarted MTC Server according to the stored mtcc Device context information may be that the MTC Device context information includes MTC Server information, and the gateway Device may know the MTC Device accessed to the overloaded, failed or restarted MTC Server through the MTC Server information in the MTC Device context information. Another method for the gateway Device to acquire the mtcc Device accessed to the overloaded, failed or restarted MTC Server according to the stored mtcc Device context information may be that the gateway Device acquires the MTC Device accessed to the overloaded, failed or restarted MTC Server according to the mtcc Device identification information, the industry user identification information to which the MTC Device belongs, or the correspondence between the APN information used by the MTC Device and the MTC Server information in the MTC Device context information. After the gateway Device learns the MTC Device accessing the overloaded, failed or restarted MTC Server, the gateway Device (GGSN or PGW) reselects the MTC Server for the MTC Device (may select another MTC Server in the MTC Server information list, or may select a source MTC Server, for example, in a scenario where the source MTC Server is restarted, the gateway Device may select the source MTC Server for the MTC Device), and according to system requirements and importance of the MTC Device (for example, an MTC Device applied by M2M with High reliability), the gateway Device may reselect the MTC Server for part or all of the MTC devices. For example, the gateway Device may learn an M2M application characteristic (MTC Feature) of the MTC Device from the mtcc Device context information, and if the M2M application characteristic of the mtcc Device is high reliability, the gateway Device may reselect an MTC Server for the high reliability mtcc Device. The method for the gateway Device to obtain the M2M application characteristics of the mtcc Device according to the MTC Device context information may specifically be that the gateway Device may obtain the M2M application characteristics of the MTC Device according to the M2M application characteristics in the MTC Device context information, or the gateway Device obtains the M2M application characteristics of the MTC Device according to the identification information of the MTC Device, the industry user identification information to which the MTC Device belongs, or the APN information used by the MTC Device in the MTC Device context information, and the M2M application characteristics corresponding to the identification information of the MTC Device, the industry user identification information to which the MTC Device belongs, or the APN information used by the MTC Device, configured on the gateway Device. In addition, the gateway Device may also determine, according to the identifier of the MTC Device in the context of the MTC Device or the industry user identifier to which the MTC Device belongs, the MTC Device that reselects the MTC Server, that is, the gateway Device may ensure that the MTC Device of a specific mtcc or the MTC Device of a specific industry performs re-registration. In addition, the gateway Device may select a processing mode according to a state of the mtcc Server, for example, when the MTC Server is overloaded, the gateway Device may reselect the MTC Server for some of the MTC devices (e.g., the gateway Device may determine whether to reselect the MTC Server for a certain MTC Device according to whether there is data transmission on a Gi interface (a data interface established between the gateway Device and the MTC Server for each MTC Device), when there is data transmission on a Gi interface, the gateway Device may not reselect the MTC Server for the MTC Device corresponding to the Gi interface, so as not to affect service continuity, when there is no data transmission on a Gi interface, the gateway Device may reselect the MTC Server for the MTC Device corresponding to the Gi interface, and when the MTC Server fails or restarts, the gateway Device may reselect the MTC Server for all of the MTC devices. After the gateway Device selects the MTC Server for the mtcc Device, the gateway Device needs to register information of the MTC Device in the selected MTC Server, and the specific method for selecting the MTC Server and registering may refer to the description of the second embodiment (for example, the gateway Device sends the registration information of the user equipment to the application Server, and registers the user equipment to the application Server), which is not described in this embodiment again.
The above description is a method for the gateway Device to reselect the MTC Server for the MTCDevice under the condition that the MTC Server is overloaded, failed or restarted (it may be to select another MTC Server in the MTC Server information list, or to select the source MTC Server, for example, in the scenario of restarting the source MTC Server, 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 (may select another MTC Server in the MTC Server information list, or may select a source MTC Server), the gateway Device constructs TFT information for the MTC Device according to information of a new MTC Server, for example, the GGSN/PGW described in embodiment two uses address information of the newly selected MTC Server as a destination address of the TFT. The GGSN/PGW may initiate a bearer modification or update procedure to send the TFT information to the MTC Device. If the address allocated for the MTC Device changes, the MTC Device address information may be sent to the MTC Device in a procedure of bearer modification. Another method for notifying the MTC Device address may be to notify the MTC Device of the address or TFT information by using an Open Mobile alliance Device management (OMA DM). The specific GGSN/PGW initiated bearer modification procedure and OMA DM mechanism are all prior art, and are not described in this embodiment.
By the method described in this embodiment, the network side can reselect the application server for the user equipment according to the load information of the application server without affecting the access of the user equipment, so that the load balance of the application server can be effectively achieved, and the influence on the user equipment due to overload, failure or restart of the application server is effectively reduced.
As described above, under the condition that the MTC Server is overloaded, failed, or restarted, after the gateway Device reselects the MTC Server for the mtcc Device, optionally, the gateway Device may initiate a bearer modification or update procedure to send the modified TFT information or MTC Device address information to the MTC Device, and in the bearer modification or update procedure, the gateway Device may further instruct the MTC Device to re-initiate a procedure of registering with the MTC Server. Specifically, after the gateway Device (GGSN or PGW) selects the MTCs Server for the MTC Device, the gateway Device may send information of the MTC Server to a mobility management element (SGSN or MME) in an Update Bearer (PDP) Request message (Update Bearer Request or Update PDP Context Request) (for example, transmitted through an existing cell pco (protocol configuration options)), optionally, the Update Bearer (PDP) Request message carries indication information indicating that the MTCs Device initiates a registration procedure to the MTC Server, and for example, the Update Bearer (PDP) Request message carries a cause value (case) indicating that the MTC Device initiates the registration procedure 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, where the message includes information of the MTCServer, and optionally, the message may carry indication information indicating that the MTC Device initiates a registration procedure to the MTC Server, for example, a cause value (case) indicating that the MTC Device initiates the registration procedure to the MTCServer. And after the MTC Device receives the message, initiating a registration process to the MTC Server according to the MTCServer information or the MTC Server information and the indication information carried in the message. Another method for notifying the MTC Device to initiate the registration procedure to the MTC Server may be to notify the MTC Device of the information of the MTC Server or the information of the MTC Server and the indication information indicating that the MTC Device initiates the registration procedure by using an OMA DM method. And after the MTC Device receives the OMA DM message, initiating 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 the prior art, and the details are not described in this embodiment. The MTC Device initiates a registration procedure is also in the prior art, and this embodiment is not described again.
By the method described in this embodiment, the network side can reselect the application server for the user equipment according to the load information of the application server, so that load balancing of the application server can be effectively achieved, and in addition, effective connection between the user equipment and the application server is ensured by instructing the user equipment to initiate a registration process to the application server.
Corresponding to the method embodiment provided by the invention, the invention also provides a device and a system for realizing registration.
As shown in fig. 5, an apparatus for implementing registration provided in an embodiment of the present invention includes:
a receiving unit 501, configured to receive a request message sent by a mobility management network element;
an obtaining unit 502, configured to obtain, according to the request message, application server information used by the user equipment corresponding to the request message;
a first registering unit 503, configured to register the user equipment with the application server.
Preferably, as shown in fig. 6, a schematic diagram of another apparatus for implementing registration according to an embodiment of the present invention is provided:
further, the request message received by the receiving unit 501 includes at least one of the user equipment identity, the APN of the user equipment, and the industry subscriber identity to which the user equipment belongs.
The obtaining unit 502 is specifically configured to obtain, according to the request message and the configuration information, application server information used by the ue; or,
the request message includes information of an application server used by the ue, and the obtaining unit 502 is specifically configured to obtain the information of the application server used by the ue from the request message; or,
the obtaining unit 502 is specifically configured to query, according to the user equipment identifier, the APN of the user equipment, or the industry user identifier to which the user equipment belongs, the DNS server for the application server information used by the user equipment.
The apparatus may further include: a storage unit 504, configured to store configuration information of the user equipment, and when the configuration information of the user equipment is a corresponding relationship between a user equipment identifier and application server information, the obtaining unit 502 is specifically configured to query, according to the user equipment identifier included in the request message, the corresponding relationship between the user equipment identifier and the application server information, and obtain application server information corresponding to the user equipment;
or,
when the configuration information of the ue is a corresponding relationship between an APN and application server information, the obtaining unit 502 is specifically configured to query the corresponding relationship between the APN and the application server information according to the APN of the ue included in the request message, and obtain the application server information corresponding to the ue;
or,
when the configuration information of the user equipment is a corresponding relationship between a user equipment identifier segment and application server information, the obtaining unit 502 is specifically configured to query, according to the user equipment identifier segment to which the user equipment identifier included in the request message belongs, a corresponding relationship between the user equipment identifier segment and the application server information, and obtain application server information corresponding to the user equipment;
or,
when the configuration information of the user equipment is a corresponding relationship between an industry user identifier and application server information, the obtaining unit 502 is specifically configured to query the corresponding relationship between the industry user identifier and the application server information according to the industry user identifier to which the user equipment belongs, which is included in the request message, and obtain the application server information corresponding to the user equipment.
The device further comprises: 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 registering unit 503 is specifically configured to send registration information of the user equipment to a selected application server, and register the user equipment on the selected application server.
The device further comprises: a generating unit 506, configured to generate data stream template information according to the selected server;
fig. 7 shows an apparatus for implementing registration according to an embodiment of the present invention, which includes:
a second selecting unit 701, configured to select an application server for a part or all of user equipment corresponding to the application server when the application server is overloaded, failed, or restarted;
a second registering unit 702, configured to register the user equipment with the selected application server.
Further, the second selecting unit further includes: a determination module 703 selects a sub-module 704.
A determining module 703, configured to determine, when an application server is overloaded, failed, or restarted, a user equipment corresponding to the application server according to context information of the user equipment;
a selecting submodule 704, configured to select an application server for some or all of the user devices determined by the gateway device according to application characteristics of the user devices; or, the selecting submodule 704 is configured to select an application server for some or all of the user devices determined by the gateway device according to the user device identifier; or, the selecting sub-module 704 is configured to select an application server for some or all of the user devices determined by the gateway device according to the industry user identifier to which the user device belongs.
The determining module 703 is specifically configured to determine, when the context information of the user equipment stored in the gateway device includes application server information, the user equipment corresponding to the application server according to the context information; or,
the determining module 703 is specifically configured to query configuration information of the user equipment according to the context information of the user equipment, and obtain the user equipment corresponding to the application server.
The selecting sub-module 704 is further configured to obtain the application characteristics of the user equipment from the context information of the user equipment; or, the selecting sub-module 704 is further configured to obtain application characteristics configured by itself and corresponding to the user equipment identification information, the industry user identification information, or the access point name APN information.
As shown in fig. 8, a system for implementing registration provided in an embodiment of the present invention includes:
a mobility management network element 801, configured to send a request message to the gateway device 802;
the gateway device 802 is configured to receive a request message sent by the mobility management network element 801, obtain 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 realizing registration, wherein gateway equipment receives a request message sent by a mobility management network element, acquires application server information corresponding to user equipment according to configuration information, and registers the user equipment on an application server, so that the user equipment is prevented from registering on the application server, the function of the user equipment is simple to realize, and the user equipment does not need to acquire the information of the application server, thereby improving the network security.
In the prior art, instead of allocating an IP address to the UE by the 3GPP network, the UE may send a DHCP REQUEST message to a DHCP (dynamic Host Configuration protocol), and the DHCP may allocate an IP address to the UE and send information of the IP address and AF to the UE in a DHCP ACK message. When the MTC Device acquires the IP address and the MTC Server (equivalent to AF in H2H application) information from DHCP in the above manner, the number of MTC devices may cause heavy DHCP load, which may result in network congestion and increase registration delay. Correspondingly, the embodiment of the invention can reduce DHCP load, avoid network congestion, make user equipment not need to acquire MGC Server information, and improve network security.
Those skilled in the art will appreciate that all or part of the steps in the method according to the above embodiments may be implemented by hardware related to instructions of a program, and the program may be stored in a computer readable storage medium. The storage medium, such as: ROM/RAM, magnetic disk, optical disk, etc.
The foregoing is only a preferred embodiment of the present invention, and it should be noted that those skilled in the art can make various improvements and modifications without departing from the principle of the present invention, and these improvements and modifications should also be construed as the protection scope of the present invention.

Claims (21)

1. A method for implementing registration, comprising:
the gateway equipment receives a request message sent by a mobility management network element;
the gateway equipment acquires the application server information used by the user equipment corresponding to the request message according to the request message;
the gateway equipment selects an application server from the application server information corresponding to the user equipment;
the gateway equipment generates data flow template information according to the selected server;
the gateway equipment registers the user equipment to the application server;
wherein the registering, by the gateway device, the user device with the application server comprises:
and the gateway equipment sends the registration information of the user equipment to a selected application server and registers the user equipment to the selected application server.
2. The method of claim 1, wherein the request message contains at least one of a user equipment identity, an access point name, APN, of the user equipment, and an industry subscriber identity to which the user equipment belongs.
3. The method of claim 1, wherein the gateway device obtaining, according to the request message, application server information used by the user equipment corresponding to the request message comprises:
the gateway equipment acquires the 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 contains the information of the application server used by the user equipment, and the gateway equipment acquires the information of the application server used by the user equipment corresponding to the request message from the request message.
4. The method of claim 2, wherein the gateway device obtaining, according to the request message, application server information used by the user equipment corresponding to the request message comprises:
and the gateway equipment queries the information of the application server used by the user equipment from a Domain Name System (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.
5. The method of claim 3, wherein the method further comprises:
the gateway device stores configuration information of the user device.
6. The method of claim 3 or 5,
when the configuration information of the user equipment is a corresponding relationship between the user equipment identifier and the application server information, the gateway equipment obtaining, according to the request message and the configuration information, the application server information used by the user equipment corresponding to the request message includes: the gateway equipment inquires the corresponding relation between the user equipment identification and the application server information according to the user equipment identification contained 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 a corresponding relationship between the APN and the application server information, the gateway equipment obtaining 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 equipment queries the corresponding relation between the APN and the information of the application server according to the APN of the user equipment contained in the request message, and acquires the information of the application server 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 gateway equipment obtaining 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 equipment inquires the corresponding relation between the user equipment identification segment and the application server information according to the user equipment identification segment to which the user equipment identification contained in the request message belongs, and obtains the application server information corresponding to the user equipment;
or,
when the configuration information of the user equipment is a corresponding relationship between an industry user identifier and application server information, the gateway equipment obtaining, according to the request message and the configuration information, application server information used by the user equipment corresponding to the request message includes: and the gateway equipment inquires the corresponding relation between the industry user identification and the application server information according to the industry user identification to which the user equipment belongs, and the application server information corresponding to the user equipment is acquired.
7. The method according to claim 3, wherein when the request message includes the application server information used by the user equipment, before the gateway device obtains the application server information used by the user equipment corresponding to the request message from the request message, the method further includes:
the subscription data in the home location register or the home subscription server comprises the information of the application server used by the user equipment, and the mobile management network element acquires the information of the application server used by the user equipment from the home location register or the home subscription server; or,
the DNS server comprises information of an application server used by the user equipment, and the mobility management network element acquires the information of the application server 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.
8. The method of claim 1, wherein before the gateway device receives the request message sent by the mobility management network element, the method further comprises:
the method comprises the steps that a mobility management network element receives an access request message sent by user equipment, wherein the access request message comprises at least one of user equipment identification, APN of the user equipment and industry user identification to which the user equipment belongs.
9. A method for implementing registration, comprising:
when the application server is overloaded, fails or restarted, the gateway equipment selects the application server for part or all of the user equipment corresponding to the application server;
the gateway equipment registers the user equipment to the selected application server;
wherein the selecting, by the gateway device, an application server for part or all of the user devices corresponding to the application server includes:
the gateway equipment determines the user equipment corresponding to the application server according to the context information of the user equipment;
the gateway equipment selects an application server for part or all of the user equipment determined by the gateway equipment according to the application characteristics of the user equipment; or the gateway equipment selects an application server for part or all of the user equipment determined by the gateway equipment according to the user equipment identifier; or the gateway equipment selects an application server for part or all of the user equipment determined by the gateway equipment according to the industry user identification of the user equipment.
10. The method of claim 9, wherein the determining, by the gateway device, the user device corresponding to the application server according to the context information of the user device comprises:
the context information of the user equipment stored by the gateway equipment comprises application server information, and the gateway equipment determines the user equipment corresponding to the application server according to the context information; or,
and the gateway equipment inquires the configuration information of the user equipment according to the context information of the user equipment and acquires the user equipment corresponding to the application server.
11. The method of claim 9, wherein the method further comprises:
the gateway equipment acquires the application characteristics of the user equipment from the context information of the user equipment; or,
and the gateway equipment acquires the self-configured application characteristics corresponding to the user equipment identification information, the industry user identification information or the access point name APN information.
12. The method of claim 9, wherein the gateway device registering the user device with the selected application server comprises:
the gateway equipment sends the registration information of the user equipment to the application server, and registers the user equipment on the application server; or,
a mobility management network element receives an update bearer request message sent by gateway equipment, wherein the update bearer request message contains information of the selected application server; a mobility management network element sends a load modification request message to the user equipment, wherein the load modification request message contains the information of the selected application server; and the user equipment registers to the selected application server according to the load modification request message.
13. An apparatus for enabling registration, comprising:
a receiving unit, configured to receive a request message sent by a mobility management network element;
an obtaining unit, configured to obtain, 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 with the application server;
and the generating unit is used for generating the data flow template information according to the selected server.
14. The apparatus of claim 13, wherein the request message contains at least one of a user equipment identity, an APN of a user equipment, and an industry subscriber identity to which the user equipment belongs,
the obtaining unit is specifically configured to obtain, according to the request message and the configuration information, application server information used by the user equipment; or,
the request message includes information of an application server used by the user equipment, and the obtaining unit is specifically configured to obtain the information of the application server used by the user equipment from the request message; or,
the acquiring unit is specifically configured to query, according to a user equipment identifier, an APN of the user equipment, or an industry user identifier to which the user equipment belongs, a domain name system DNS server for application server information used by the user equipment.
15. The apparatus of claim 13, wherein the apparatus further comprises:
and the storage unit is used for storing the configuration information of the user equipment.
16. The apparatus of claim 15,
when the configuration information of the user equipment is a corresponding relationship between a user equipment identifier and application server information, the obtaining unit is specifically configured to query 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 obtain the application server information corresponding to the user equipment;
or,
when the configuration information of the user equipment is a corresponding relationship between the APN and the application server information, the acquiring unit is specifically configured to query the corresponding relationship between the APN and the application server information according to the APN of the user equipment contained in the request message, and acquire the 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 is specifically configured to query the corresponding relationship between the user equipment identification segment and the application server information according to the user equipment identification segment to which the user equipment identification contained in the request message belongs, and obtain the application server information corresponding to the user equipment;
or,
when the configuration information of the user equipment is a corresponding relationship between an industry user identifier and application server information, the obtaining unit is specifically configured to query the corresponding relationship between the industry user identifier and the application server information according to the industry user identifier to which the user equipment belongs, which is included in the request message, and obtain the application server information corresponding to the user equipment.
17. The apparatus of claim 13, wherein the apparatus further comprises:
and the first selection unit is used for selecting the application server from the application server information corresponding to the user equipment according to the weight information of the application server.
18. The apparatus of claim 17, wherein the first registering unit is specifically configured to send registration information of the user equipment to a selected application server, and register the user equipment on the selected application server.
19. An apparatus for enabling registration, comprising:
the second selection unit is used for selecting the application server for part or all of the user equipment corresponding to the application server when the application server is overloaded, failed or restarted;
a second registration unit, configured to register the user equipment with a selected application server;
wherein the second selection unit includes:
the determining module is used for determining the user equipment corresponding to the application server according to the context information of the user equipment when the application server is overloaded, fails or restarted;
the selection submodule is used for selecting an application server for part or all of the user equipment determined by the gateway equipment according to the application characteristics of the user equipment; or, the selection submodule is used for selecting an application server for part or all of the user equipment determined by the gateway equipment according to the user equipment identifier; or, the selection submodule is used for selecting the application server for part or all of the user equipment determined by the gateway equipment according to the industry user identification of the user equipment.
20. The apparatus of claim 19,
the determining module is specifically configured to determine, when the context information of the user equipment stored in the gateway device includes application server information, the user equipment corresponding to the application server according to the context information; or,
the determining module is specifically configured to query configuration information of the user equipment according to the context information of the user equipment, and obtain the user equipment corresponding to the application server.
21. The apparatus of claim 19, wherein the selection sub-module is further configured to obtain the ue application characteristic from context information of the ue; or, the selection sub-module is further configured to obtain application characteristics configured by the selection sub-module and corresponding to the user equipment identification information, the industry user identification information, or the access point name APN information.
CN2009801100767A 2009-09-18 2009-09-18 Method, device and system for implementing registration Active CN102177757B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2009/074026 WO2011032316A1 (en) 2009-09-18 2009-09-18 Method, device and system for implementing registration

Publications (2)

Publication Number Publication Date
CN102177757A CN102177757A (en) 2011-09-07
CN102177757B true CN102177757B (en) 2013-08-14

Family

ID=43758019

Family Applications (1)

Application Number Title Priority Date Filing Date
CN2009801100767A Active CN102177757B (en) 2009-09-18 2009-09-18 Method, device and system for implementing registration

Country Status (2)

Country Link
CN (1) CN102177757B (en)
WO (1) WO2011032316A1 (en)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104683289A (en) * 2013-11-26 2015-06-03 中兴通讯股份有限公司 Common service entity (CSE) registering method and system
CN113543132B (en) * 2021-07-15 2022-08-05 中国电信股份有限公司 Network access method and device of node equipment, storage medium and electronic equipment
CN117643118A (en) * 2022-06-23 2024-03-01 北京小米移动软件有限公司 Information processing method, apparatus, communication device and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1829337A (en) * 2005-03-01 2006-09-06 中兴通讯股份有限公司 Mobile soft switching server disaster recovery method
CN101087200A (en) * 2006-08-18 2007-12-12 中兴通讯股份有限公司 Method for establishing context in multicast service of mobile communication system
CN101087249A (en) * 2006-08-25 2007-12-12 中兴通讯股份有限公司 Method for establishing control side tunnel in mobile communication system multicast service

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090217038A1 (en) * 2008-02-22 2009-08-27 Vesa Petteri Lehtovirta Methods and Apparatus for Locating a Device Registration Server in a Wireless Network

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1829337A (en) * 2005-03-01 2006-09-06 中兴通讯股份有限公司 Mobile soft switching server disaster recovery method
CN101087200A (en) * 2006-08-18 2007-12-12 中兴通讯股份有限公司 Method for establishing context in multicast service of mobile communication system
CN101087249A (en) * 2006-08-25 2007-12-12 中兴通讯股份有限公司 Method for establishing control side tunnel in mobile communication system multicast service

Also Published As

Publication number Publication date
WO2011032316A1 (en) 2011-03-24
CN102177757A (en) 2011-09-07

Similar Documents

Publication Publication Date Title
CN114424508B (en) Method and apparatus for local application server discovery in mobile edge computing
US10873563B2 (en) IP address allocation method, and device
US9432960B2 (en) Method of handling proximity service in wireless communication system
US9654954B2 (en) Providing an IMS voice session via a packet switch network and an emergency voice session via a circuit switch network
US8661137B2 (en) Network-based information processing method and system, and mobility management network element
CN104871600B (en) A kind of network selecting method and equipment of the core network
CN107079353B (en) Low latency service connection setup in new service areas
US10757645B2 (en) Access control in communications network comprising slices
US9451594B2 (en) Method and apparatus for associating service provider network identifiers with access network identifiers
US9749306B2 (en) Method, device and communications system for network convergence
US9848359B2 (en) Method for obtaining serving gateway, mobility management node, data gateway, and system
US9667481B2 (en) Correlation identifier for user plane congestion and other use cases
KR101974022B1 (en) Service redundancy method and related devices
WO2012068728A1 (en) Methods and network entities for acquiring ip address of user
US20150296445A1 (en) Method, device and system for managing packet data network type
US20160353366A1 (en) Apparatus and method for acquiring ipv6 domain name system server and sip server address
US9445256B1 (en) Binding update forwarding between packet gateways
US10616764B2 (en) Methods and devices for selecting network partition in untrusted WLAN access
US11356887B2 (en) Systems and methods for selecting a core network slice for user plane communications
Kunz et al. Machine type communications in 3GPP: From release 10 to release 12
CN102177757B (en) Method, device and system for implementing registration
CN108235428B (en) Method for realizing registration of UE (user equipment) with P-CSCF (proxy Call Session control function), MME (mobility management entity) equipment and PGW (packet gateway) equipment
US20170048897A1 (en) Methods and Apparatuses for Notifying or Updating ProSe Temporary Identifier
WO2011134370A1 (en) Machine type communication event reporting method and system thereof
WO2011069287A1 (en) Method and device for user equipment management

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant