WO2011032316A1 - Procédé, dispositif et système de mise en œuvre d'enregistrement - Google Patents

Procédé, dispositif et système de mise en œuvre d'enregistrement Download PDF

Info

Publication number
WO2011032316A1
WO2011032316A1 PCT/CN2009/074026 CN2009074026W WO2011032316A1 WO 2011032316 A1 WO2011032316 A1 WO 2011032316A1 CN 2009074026 W CN2009074026 W CN 2009074026W WO 2011032316 A1 WO2011032316 A1 WO 2011032316A1
Authority
WO
WIPO (PCT)
Prior art keywords
user equipment
application server
information
request message
gateway device
Prior art date
Application number
PCT/CN2009/074026
Other languages
English (en)
Chinese (zh)
Inventor
周汉
吴问付
陈中平
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2009/074026 priority Critical patent/WO2011032316A1/fr
Priority to CN2009801100767A priority patent/CN102177757B/zh
Publication of WO2011032316A1 publication Critical patent/WO2011032316A1/fr

Links

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

Definitions

  • 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
  • LTE Long Term Evolution
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunication System
  • EPS evolved packet system
  • H2H Human to Human
  • M2M Machine to Machine
  • the network side such as PGW (PDN Gateway), packet data network gateway
  • PGW Packet Data Network Gateway
  • AF Application Function, application
  • 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.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • GERAN GSM EDGE
  • the network side eg, PGW or GGSN (Gateway GPRS Support Node)
  • PGW or GGSN Gateway GPRS Support Node
  • 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.
  • 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
  • 3GPP 3 rd Generation Partnership Project, Third Generation Partnership Project
  • LTE Long Term Evolution, Long Term Evolution
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunication System
  • EPS evolved packet system
  • H2H Human to Human
  • M2M Machine to Machine
  • the network side such as PGW (PDN Gateway), packet data network gateway
  • PGW Packet Data Network Gateway
  • AF Application Function, application
  • 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.
  • E-UTRAN Evolved Universal Terrestrial Radio Access Network
  • GERAN GSM EDGE
  • the network side eg, PGW or GGSN (Gateway GPRS Support Node)
  • PGW or GGSN Gateway GPRS Support Node
  • 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. 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
  • FIG. 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. 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.
  • 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.
  • 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 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.
  • 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);
  • 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.
  • the gateway device may be a PGW or a GGSN.
  • 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
  • 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).
  • 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.
  • 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).
  • 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.
  • the DNS server 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.
  • 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.
  • 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,
  • the MTC Server is configured with the MTC Device identifier segment corresponding to the MTC Server.
  • an MTC Server can be an industry user IMSI number segment 460350789123000 to 460350789123999.
  • MTC Device provides services;
  • the gateway device can obtain the MTC Server information used by the MTC Device by querying the table A or the table B.
  • 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.
  • 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).
  • 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.
  • GGSN or PGW gateway 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.
  • 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.
  • the DNS server 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.
  • 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.
  • 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).
  • 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.
  • the gateway device selects the MTC Server for the MTC Device, the MTC Server may be selected according to the weight information.
  • 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 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:
  • 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.
  • the MTC Server 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.
  • 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.
  • 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.
  • 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.
  • Subscribe Request a new message request request
  • 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. ).
  • 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.
  • 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.
  • the GGSN/PGW also sends the TFT information to the mobility management network element in the session request response message.
  • the MTC Device can be registered to the MTC Server by default on the network side.
  • 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.
  • 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.
  • 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.
  • the embodiment of the present invention is described by using the communication system of the M2M application as an example.
  • 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.
  • a method for reselecting an application server for a user equipment 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
  • the application server is specifically an MTC Server
  • the gateway device is specifically a GGSN/PGW.
  • 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).
  • 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
  • the Source MTC Server indicates a Counter in the detection response message, and the value of the Counter may be an initial value. .
  • the Source MTC Server 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.
  • 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.
  • 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 gateway device 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.
  • 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.
  • 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 M2M application characteristics corresponding to the APN information used by the device are used to learn the M2M application characteristics of the MTC Device.
  • 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.
  • 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.
  • the gateway device may reselect the MTC Server angry 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.
  • the gateway device needs to register the information of the MTC Device to the selected MTC Server, and specifically select the MTC Server.
  • 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 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.
  • the gateway device may select the source MTC Server for the MTC Device.
  • the gateway device is configured according to the information of the new MTC Server.
  • the MTC Device constructs the TFT information.
  • 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).
  • OMA DM Open Mobile Alliance Device Mangement
  • 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.
  • 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 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
  • Update Bearer Request Update Bearer Request or Update PDP Context Request
  • PDP Packety configuration
  • 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.
  • 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.
  • 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.
  • the MTC Device 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.
  • 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.
  • 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.
  • the present invention also provides an apparatus and system for implementing registration.
  • an apparatus for implementing registration 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.
  • FIG. 6 is a schematic diagram of another apparatus for implementing registration according to an embodiment of the present invention.
  • 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
  • the obtaining 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;
  • 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;
  • 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;
  • 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;
  • a generating unit 506 configured to generate data flow template information according to the selected server;
  • 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.
  • a system for implementing registration 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.
  • 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.
  • 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.
  • 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.
  • the storage medium is, for example, a ROM/RAM, a magnetic disk, an optical disk, or the like.

Landscapes

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

Abstract

Les modes de réalisation de la présente invention portent sur un procédé, un dispositif et un système de mise en œuvre d'enregistrement, ledit procédé comprenant les opérations suivantes : un dispositif de passerelle reçoit un message de requête envoyé par un élément de réseau de gestion de mobilité; le dispositif de passerelle obtient les informations de serveur d'application utilisées par ledit dispositif utilisateur conformément audit message de requête; le dispositif de passerelle enregistre ledit dispositif utilisateur auprès dudit serveur d'application. L'application de la présente invention, par enregistrement du dispositif utilisateur auprès du serveur d'application par le dispositif de passerelle, évite au dispositif utilisateur de s'enregistrer auprès du serveur d'application, et rend les fonctions du dispositif utilisateur simples à réaliser, et permet au dispositif utilisateur de ne pas avoir besoin d'obtenir les informations du serveur d'application, ce qui améliore la sécurité du réseau.
PCT/CN2009/074026 2009-09-18 2009-09-18 Procédé, dispositif et système de mise en œuvre d'enregistrement WO2011032316A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2009/074026 WO2011032316A1 (fr) 2009-09-18 2009-09-18 Procédé, dispositif et système de mise en œuvre d'enregistrement
CN2009801100767A CN102177757B (zh) 2009-09-18 2009-09-18 一种实现注册的方法、装置和系统

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2009/074026 WO2011032316A1 (fr) 2009-09-18 2009-09-18 Procédé, dispositif et système de mise en œuvre d'enregistrement

Publications (1)

Publication Number Publication Date
WO2011032316A1 true WO2011032316A1 (fr) 2011-03-24

Family

ID=43758019

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/074026 WO2011032316A1 (fr) 2009-09-18 2009-09-18 Procédé, dispositif et système de mise en œuvre d'enregistrement

Country Status (2)

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

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104683289A (zh) 2013-11-26 2015-06-03 中兴通讯股份有限公司 公共业务实体注册方法和系统
CN113543132B (zh) * 2021-07-15 2022-08-05 中国电信股份有限公司 节点设备的入网方法及装置、存储介质、电子设备
CN117643118A (zh) * 2022-06-23 2024-03-01 北京小米移动软件有限公司 信息处理方法、装置、通信设备及存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1829337A (zh) * 2005-03-01 2006-09-06 中兴通讯股份有限公司 一种移动软交换服务器的容灾方法
CN101087200A (zh) * 2006-08-18 2007-12-12 中兴通讯股份有限公司 移动通信系统组播业务中建立上下文的方法
CN101087249A (zh) * 2006-08-25 2007-12-12 中兴通讯股份有限公司 移动通信系统组播业务中建立控制面隧道的方法
WO2009103621A1 (fr) * 2008-02-22 2009-08-27 Telefonaktiebolaget L M Ericsson (Publ) Procédés et appareil localisant un serveur d'enregistrement de dispositif dans un réseau sans fil

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1829337A (zh) * 2005-03-01 2006-09-06 中兴通讯股份有限公司 一种移动软交换服务器的容灾方法
CN101087200A (zh) * 2006-08-18 2007-12-12 中兴通讯股份有限公司 移动通信系统组播业务中建立上下文的方法
CN101087249A (zh) * 2006-08-25 2007-12-12 中兴通讯股份有限公司 移动通信系统组播业务中建立控制面隧道的方法
WO2009103621A1 (fr) * 2008-02-22 2009-08-27 Telefonaktiebolaget L M Ericsson (Publ) Procédés et appareil localisant un serveur d'enregistrement de dispositif dans un réseau sans fil

Also Published As

Publication number Publication date
CN102177757B (zh) 2013-08-14
CN102177757A (zh) 2011-09-07

Similar Documents

Publication Publication Date Title
US10873563B2 (en) IP address allocation method, and device
US11641620B2 (en) Access control in communications network comprising slices
JP5793812B2 (ja) データオフロードをトリガするための方法、ネットワーク側デバイス、ユーザ機器、およびネットワークシステム
US9094839B2 (en) Evolved packet core (EPC) network error mapping
US8661137B2 (en) Network-based information processing method and system, and mobility management network element
US9654954B2 (en) Providing an IMS voice session via a packet switch network and an emergency voice session via a circuit switch network
US9313094B2 (en) Node and method for signalling in a proxy mobile internet protocol based network
CN107079353B (zh) 新服务区中的低等待时间服务连接设立
US10567216B2 (en) Fault detection method, gateway, user equipment, and communications system
US9473877B2 (en) Uplink/downlink transmission method for small amount of data, and corresponding terminal and mobility management unit
WO2015062098A1 (fr) Procédé de sélection de réseau et dispositif de réseau central
WO2011140884A1 (fr) Procédé destiné à un groupe de communication de type machine sélectionnant une passerelle de réseau de données par paquets, et élément de réseau de gestion de mobilité
WO2012068728A1 (fr) Procédés et entités de réseau pour l'acquisition d'une adresse ip d'utilisateur
WO2011020435A1 (fr) Procédé et système permettant de transmettre des paquets de données au niveau d'un serveur d'application de machine à machine (m2m)
WO2013163945A1 (fr) Procédé pour rapporter un événement de communication de type de machine et dispositif associé
WO2011134370A1 (fr) Procédé de rapport d'événement de communication de type machine et système associé
TWI572176B (zh) 處理目標行動裝置之延遲信令之方法
WO2011032316A1 (fr) Procédé, dispositif et système de mise en œuvre d'enregistrement
WO2011050723A1 (fr) Procédé, système et dispositif de sélection d'entité de gestion de mobilité (mme) cible durant un processus de commutation de terminal mobile
WO2016019559A1 (fr) Appareil, système, et procédé d'identification d'équipement d'utilisateur de réseau partagé
WO2013152545A1 (fr) Procédé d'établissement de connexion et unité de passerelle
WO2011110022A1 (fr) Procédé, dispositif et système destinés à transmettre des données
WO2011137582A1 (fr) Procédé, système et équipement de passerelle d'initiation de service
CN108235428B (zh) 实现ue注册p-cscf的方法、mme设备及pgw设备
WO2013060214A1 (fr) Procédé et appareil de signalement d'informations d'application

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200980110076.7

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09849369

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09849369

Country of ref document: EP

Kind code of ref document: A1