WO2016026145A1 - Procédé de configuration d'identité, serveur de gestion de dispositif, et nœud d'infrastructure - Google Patents

Procédé de configuration d'identité, serveur de gestion de dispositif, et nœud d'infrastructure Download PDF

Info

Publication number
WO2016026145A1
WO2016026145A1 PCT/CN2014/085035 CN2014085035W WO2016026145A1 WO 2016026145 A1 WO2016026145 A1 WO 2016026145A1 CN 2014085035 W CN2014085035 W CN 2014085035W WO 2016026145 A1 WO2016026145 A1 WO 2016026145A1
Authority
WO
WIPO (PCT)
Prior art keywords
ext
target node
node
identifier
network entity
Prior art date
Application number
PCT/CN2014/085035
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 CN201480080213.8A priority Critical patent/CN106471788B/zh
Priority to PCT/CN2014/085035 priority patent/WO2016026145A1/fr
Publication of WO2016026145A1 publication Critical patent/WO2016026145A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications

Definitions

  • the present invention relates to the field of communications, and in particular, to an identity configuration method, a terminal management server, and a base node.
  • the device trigger function Prior art, Institute of Electrical and Electronics Engineers (Institute of Electrical and Electronics The public service function defined in the Engineers, IEEE) technology includes the device trigger function.
  • the implementation principle of the device trigger function is: the target node is in the base node (Infrastructure) When Node, IN) is registered, it is the public service entity identifier of the target node (Common Service) Entity-Identity, CSE-ID) External communication with machine communication (M2M-External
  • M2M-External External communication with machine communication
  • M2M-External The correspondence between the identity, the M2M-Ext-ID is provided to the base node, so that the base node selects the underlying network entity according to the M2M-Ext-ID, and then the base node can send the device to the selected underlying network entity.
  • Trigger request (Device Triggering Request message, the message carries the M2M-Ext-ID, and the M2M-Ext-ID is a representation identifier that can be identified by the underlying network entity, so that the underlying network entity can route the trigger message to the corresponding target node according to the M2M-Ext-ID; Among them, the CSE-ID obtained by the base node is used to implement the business layer function.
  • the M2M-Ext-ID is allocated by the underlying network entity to the target node.
  • the target node cannot obtain the M2M-Ext-ID, so that the target node cannot register the CSE-ID and the M2M- at the time of registration.
  • the mapping relationship of the Ext-ID is provided to the base node, so that the underlying network entity cannot route the trigger message to the target node.
  • the embodiment of the present invention provides an identifier configuration method, a terminal management server, and a base node, which can implement an underlying network entity to route a trigger message to a target node.
  • an embodiment of the present invention provides a terminal management server DMS, including:
  • a receiving unit configured to receive an identifier of a terminal where the target node is sent by the target node
  • a sending unit configured to send, to the underlying network entity, an identifier of the terminal where the target node is located, so that the underlying network entity obtains the machine communication external identifier M2M-Ext-ID of the target node according to the identifier of the terminal where the target node is located ;
  • the receiving unit is further configured to receive an M2M-Ext-ID of the target node sent by the underlying network entity;
  • the sending unit is further configured to send the M2M-Ext-ID to the target node, so that the target node obtains the location according to the M2M-Ext-ID and a preset public service entity identifier CSE-ID. Corresponding relationship between the M2M-Ext-ID and the CSE-ID, where the correspondence relationship is sent to the base node when the target node initiates registration with the base node.
  • an embodiment of the present invention provides a basic node, including:
  • a sending unit configured to send the terminal identifier and the service information to the underlying network entity, so that the underlying network entity obtains the machine communication external identifier M2M-Ext-ID of the target node according to the terminal identifier and the service information;
  • a receiving unit configured to obtain an M2M-Ext-ID of the target node from the underlying network entity
  • the sending unit is further configured to send the M2M-Ext-ID to the target node, so that the target node obtains the location according to the M2M-Ext-ID and a preset public service entity identifier CSE-ID. Corresponding relationship between the M2M-Ext-ID and the CSE-ID;
  • the receiving unit is further configured to receive the correspondence that is sent when the target node initiates registration with the base node.
  • the receiving unit is specifically configured to:
  • the service information includes at least one of the following information: at least one of an identifier of the M2M service providing device, an identifier of the base node, an application type, a service type, and a location.
  • the sending unit is specifically configured to: store the M2M-Ext-ID, and send the M2M-Ext-ID to the target node; or After receiving the reclaiming instruction sent by the target node, the receiving unit sends a response message to the target node, where the response message carries the M2M-Ext-ID.
  • the base node further includes:
  • a processing unit configured to obtain a resource for storing the M2M-Ext-ID, where the resource of the M2M-Ext-ID is created by the target node after initiating registration with the base node.
  • an embodiment of the present invention further provides an identifier configuration method, including:
  • the embodiment of the present invention further provides an identifier configuration method, including:
  • the base node sends the terminal identifier and the service information to the underlying network entity, so that the underlying network entity obtains the machine communication external identifier M2M-Ext-ID of the target node according to the terminal identifier and the service information;
  • the base node receives the correspondence that is sent when the target node initiates registration with the base node.
  • the base node obtains the M2M-Ext-ID of the target node from the underlying network entity, including:
  • the base node receives an M2M-Ext-ID of the target node from a machine communication M2M service providing device; the M2M-Ext-ID is obtained by the M2M service providing device from the underlying network entity.
  • the service information includes at least one of the following information: at least one of an identifier of the M2M service providing device, an identifier of the base node, an application type, a service type, and a location.
  • the sending, by the base node, the M2M-Ext-ID to the target node includes:
  • the base node stores the M2M-Ext-ID, and sends the M2M-Ext-ID to the target node;
  • the base node After receiving the revocation instruction sent by the target node, the base node sends a response message to the target node, where the response message carries the M2M-Ext-ID.
  • the base node obtains a resource for storing the M2M-Ext-ID, where the resource of the M2M-Ext-ID is the target node
  • the base node is created at the base node after it initiates registration.
  • the terminal management server (Device Management The server, DMS) or the base node can obtain the M2M-Ext-ID configured by the underlying network entity for the target node, and provide the obtained M2M-Ext-ID to the target node, so that the target node can register M2M-Ext at the time of registration.
  • the mapping between the ID and the CSE-ID is provided to the base node, so that the base node can carry the M2M-Ext-ID in the device trigger request sent to the underlying network entity, and the underlying network entity can route the trigger message according to the M2M-Ext-ID.
  • the corresponding target node is provided. Therefore, the technical solution provided by the embodiment of the present invention can implement the device triggering mechanism in the OneM2M technology.
  • FIG. 1 is a functional block diagram of a terminal management server according to an embodiment of the present invention.
  • FIG. 2 is a schematic structural diagram of a system used by a technical solution provided by an embodiment of the present invention.
  • FIG. 3 is a schematic structural diagram of a terminal management server according to an embodiment of the present invention.
  • FIG. 4 is a functional block diagram of a base node according to an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of a base node according to an embodiment of the present invention.
  • FIG. 6 is a schematic flowchart of a method 1 for configuring identity according to an embodiment of the present invention.
  • FIG. 7 is a schematic flowchart of a second method for configuring identity according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart diagram of Embodiment 1 of an identifier configuration method according to an embodiment of the present disclosure
  • FIG. 9 is a schematic flowchart of Embodiment 2 of an identifier configuration method according to an embodiment of the present disclosure.
  • Embodiment 10 is a schematic flowchart of Embodiment 3 of a method for configuring an identifier provided by an embodiment of the present invention
  • FIG. 11 is a schematic flowchart diagram of Embodiment 4 of an identifier configuration method according to an embodiment of the present invention.
  • the word “if” as used herein may be interpreted as “when” or “when” or “in response to determining” or “in response to detecting.”
  • FIG. 1 is a functional block diagram of a terminal management server according to an embodiment of the present invention.
  • the DMS includes:
  • the receiving unit 10 is configured to receive an identifier of a terminal where the target node is sent by the target node;
  • the sending unit 11 is configured to send, to the underlying network entity, an identifier of the terminal where the target node is located, so that the underlying network entity obtains the machine communication external identifier M2M-Ext- of the target node according to the identifier of the terminal where the target node is located. ID;
  • the receiving unit 10 is further configured to receive an M2M-Ext-ID of the target node sent by the underlying network entity;
  • the sending unit 11 is further configured to send the M2M-Ext-ID to the target node, so that the target node obtains according to the M2M-Ext-ID and a preset public service entity identifier CSE-ID. Corresponding relationship between the M2M-Ext-ID and the CSE-ID, where the correspondence relationship is sent to the base node when the target node initiates registration with the base node.
  • the underlying network entity may be a 3rd Generation Partnership (3rd Generation Partnership) Project, 3GPP) Network entity.
  • 3rd Generation Partnership 3rd Generation Partnership
  • 3GPP 3rd Generation Partnership
  • the M2M-Ext-ID may include: a domain identifier (Domain ID) and a region identifier (Local ID); wherein the domain identifier is different according to the service provided; the international mobile subscriber identity of the terminal where the target node is located may be obtained according to the area identifier (International Mobile Subscriber Identification Number (IMSI), and the area identifier is unique in the service domain corresponding to the domain identifier.
  • Domain ID domain identifier
  • Local ID region identifier
  • IMSI International Mobile Subscriber Identification Number
  • the target node may be an application service node (Application Service) Common Service Entity (ASN-CSE) in Node), or intermediate node (Middle) Common Service Entity (MN-CSE) in Node, MN).
  • Application Service Application Service
  • ASN-CSE Application Service Common Service Entity
  • MN-CSE Middle Common Service Entity
  • the basic node may be a public service entity in the basic node (Common Service) Entity, IN-CSE).
  • FIG. 2 is a schematic structural diagram of a system used by the technical solution provided by the embodiment of the present invention.
  • the ASD can be connected to the base node through the MN, and the ASN can also be connected to the base node by using the reference point Mcc.
  • the system used in the technical solution provided by the embodiment of the present invention may include: IN-CSE, Application Entity (IN-AE) in the base node, MN-CSE, and application entity in the intermediate node (Application) Entity, MN-AE), application entity in Application Dedicated Node (ADN) Entity, ADN-AE), ASN-CSE, application entity in the application service node (Application Entity, ASN-AE). Also included in the figure are the Mcc interface, the Mca interface, and the Mcn interface.
  • each target node can obtain at least one M2M-Ext-ID.
  • the identifier of the terminal where the target node is located may be a terminal identifier (Device ID), the terminal identifier may include: an international mobile device identification code (International Mobile Equipment) Identity, IMEI), Universally Unique Identifier (UUID), Electronic Serial Number (Electronic) Serial Number (ESN) or Mobile Equipment Identifier (MEID).
  • IMEI International Mobile Equipment
  • UUID Universally Unique Identifier
  • ESN Electronic Serial Number
  • MEID Mobile Equipment Identifier
  • FIG. 3 is a schematic structural diagram of a terminal management server according to an embodiment of the present invention.
  • the terminal management server includes:
  • a receiver 30 configured to receive an identifier of a terminal where the target node is sent by the target node
  • the transmitter 31 is configured to send, to the underlying network entity, an identifier of the terminal where the target node is located, so that the underlying network entity obtains the machine communication external identifier M2M-Ext- of the target node according to the identifier of the terminal where the target node is located. ID;
  • the receiver 30 is further configured to receive an M2M-Ext-ID of the target node sent by the underlying network entity;
  • the transmitter 31 is further configured to send the M2M-Ext-ID to the target node, so that the target node obtains according to the M2M-Ext-ID and a preset public service entity identifier CSE-ID. Corresponding relationship between the M2M-Ext-ID and the CSE-ID, where the correspondence relationship is sent to the base node when the target node initiates registration with the base node.
  • a memory 32 for storing information including a program routine
  • the processor 33 is coupled to the memory 32, the transmitter 31, and the receiver 30, respectively, for controlling execution of the program routine.
  • FIG. 4 is a functional block diagram of a base node according to an embodiment of the present invention.
  • the base node includes:
  • the sending unit 40 is configured to send the terminal identifier and the service information to the underlying network entity, so that the underlying network entity obtains the machine communication external identifier M2M-Ext-ID of the target node according to the terminal identifier and the service information;
  • the receiving unit 41 is configured to obtain an M2M-Ext-ID of the target node from the underlying network entity;
  • the sending unit 40 is further configured to send the M2M-Ext-ID to the target node, so that the target node obtains according to the M2M-Ext-ID and a preset public service entity identifier CSE-ID. Corresponding relationship between the M2M-Ext-ID and the CSE-ID;
  • the receiving unit 41 is further configured to receive the correspondence that is sent when the target node initiates registration with the base node.
  • the receiving unit 41 is specifically configured to:
  • the underlying network entity may send all M2M-Ext-IDs corresponding to the service type to the M2M service providing device according to the service type, and when the M2M service providing device allocates the CSE-ID to the target node, the CSE-ID and the M2M are used.
  • the correspondence of -Ext-ID is stored in the base node.
  • the service information includes at least one of the following information: at least one of an identifier of the M2M service providing device, an identifier of the base node, an application type, a service type, and a location.
  • the terminal identifier may include an IP address of the target node or an IMSI of the terminal where the target node is located.
  • the underlying network entity may allocate at least one M2M-Ext-ID to the target node according to the terminal identifier and the service information.
  • the identifier of the base node may be a machine type communication interaction function (Machine-Type Communication) Interworking Function, MTC-IWF) Service Capability that the entity can identify Server, SCS) logo.
  • MTC-IWF Machine-Type Communication Interworking Function
  • the sending unit 40 is specifically configured to: store the M2M-Ext-ID, and send the M2M-Ext-ID to the target node; or send the target node to send at the receiving unit After the reclaiming instruction, a response message is sent to the target node, and the response message carries the M2M-Ext-ID.
  • the storing, by the base node, the M2M-Ext-ID includes: the base node may store the obtained M2M-Ext-ID in a ⁇ remoteCSE> resource corresponding to the target node, where the ⁇ remoteCSE> resource may be stored.
  • the existing attribute you can also create a new attribute in the ⁇ remoteCSE> resource, and then use the new attribute in the ⁇ remoteCSE> resource to store the M2M-Ext-ID.
  • the base node further includes:
  • the processing unit 42 is configured to obtain a resource for storing the M2M-Ext-ID, where the resource of the M2M-Ext-ID is created by the target node after starting registration with the base node. .
  • the target node may create a ⁇ remoteCSE> resource in the base node, and the ⁇ remoteCSE> resource is used to store the M2M-Ext-ID obtained by the target node.
  • FIG. 5 is a schematic structural diagram of a base node according to an embodiment of the present invention.
  • the base node includes:
  • the transmitter 50 is configured to send the terminal identifier and the service information to the underlying network entity, so that the underlying network entity obtains the machine communication external identifier M2M-Ext-ID of the target node according to the terminal identifier and the service information;
  • a receiver 51 configured to obtain an M2M-Ext-ID of the target node from the underlying network entity
  • the transmitter 50 is further configured to send the M2M-Ext-ID to the target node, so that the target node obtains according to the M2M-Ext-ID and a preset public service entity identifier CSE-ID. Corresponding relationship between the M2M-Ext-ID and the CSE-ID;
  • the receiver 51 is further configured to receive the correspondence that is sent when the target node initiates registration with the base node.
  • a memory 52 for storing information including a program routine
  • the processor 51 is coupled to the memory 52, the transmitter 50, and the receiver 51, respectively, for controlling the execution of the program routine.
  • Embodiments of the present invention further provide an embodiment of a method for implementing each unit in the foregoing apparatus embodiment.
  • An embodiment of the present invention provides a method for configuring an identifier.
  • FIG. 6 it is a schematic flowchart of a method for configuring an identifier provided by an embodiment of the present invention, which is a method for implementing identity configuration on a terminal management server side; The method includes the following steps:
  • Step 601 The terminal management server DMS receives the identifier of the terminal where the target node is sent by the target node.
  • Step 602 The identifier of the terminal where the target node is sent by the DMS to the underlying network entity, so that the underlying network entity obtains the machine communication external identifier M2M-Ext- of the target node according to the identifier of the terminal where the target node is located. ID.
  • Step 603 The DMS receives an M2M-Ext-ID of the target node sent by the underlying network entity.
  • Step 604 The DMS sends the M2M-Ext-ID to the target node, so that the target node obtains the M2M according to the M2M-Ext-ID and a preset public service entity identifier CSE-ID. a correspondence between the Ext-ID and the CSE-ID, where the correspondence is used when the target node initiates registration with the base node and sends the registration to the base node.
  • An embodiment of the present invention provides a method for configuring an identifier.
  • FIG. 7 it is a schematic flowchart of a method for configuring an identifier provided by an embodiment of the present invention, which is a method for implementing identity configuration on a base node side; The method includes the following steps:
  • Step 701 The base node sends the terminal identifier and the service information to the underlying network entity, so that the underlying network entity obtains the machine communication external identifier M2M-Ext-ID of the target node according to the terminal identifier and the service information.
  • the service information includes at least one of the following information: at least one of an identifier of the M2M service providing device, an identifier of the base node, an application type, a service type, and a location.
  • Step 702 The base node obtains an M2M-Ext-ID of the target node from the underlying network entity.
  • the method for the base node to obtain the M2M-Ext-ID of the target node from the underlying network entity may include the following two types:
  • the base node receives an M2M-Ext-ID of the target node sent by the underlying network entity.
  • the base node receives the M2M-Ext-ID of the target node from the machine communication M2M service providing device; the M2M-Ext-ID is obtained by the M2M service providing device from the underlying network entity.
  • Step 703 The base node sends the M2M-Ext-ID to the target node, so that the target node obtains the according to the M2M-Ext-ID and a preset public service entity identifier CSE-ID. The correspondence between the M2M-Ext-ID and the CSE-ID.
  • the method for the base node to send the M2M-Ext-ID to the target node may include the following two types:
  • the base node stores the M2M-Ext-ID and sends the M2M-Ext-ID to the target node.
  • the second type after receiving the reclaiming instruction sent by the target node, the basic node sends a response message to the target node, where the response message carries the M2M-Ext-ID.
  • Step 704 The base node receives the correspondence that is sent when the target node initiates registration with the base node.
  • the foregoing method may further include:
  • the base node obtains a resource for storing the M2M-Ext-ID, and the resource of the M2M-Ext-ID is created at the base node after the target node initiates registration with the base node.
  • FIG. 8 is a schematic flowchart of Embodiment 1 of an identifier configuration method according to an embodiment of the present invention.
  • an underlying network entity passes an Open Mobile Alliance (Open Mobile). Alliance, OMA) Device Management mode configures the M2M-Ext-ID for the target node; as shown in Figure 8, the method includes the following steps:
  • Step 801 the target node uses the terminal ID (Device ID) for boot loading (Boot) Trapped) operation, wherein the terminal identifier may include an IMEI, a UUID, an ESN, or an MEID.
  • the terminal ID may include an IMEI, a UUID, an ESN, or an MEID.
  • Step 802 The DM client in the terminal where the target node is located is initialized to obtain the terminal identifier, and the target node sends the obtained terminal identifier to the DMS.
  • Step 803 The DMS obtains the IMEI of the terminal where the target node is located according to the received terminal identifier, and then sends the IMEI of the terminal where the target node is located to the underlying network entity.
  • Step 804 The underlying network entity allocates an M2M-Ext-ID to the target node in the terminal corresponding to the IMSI according to the IMSI sent by the DMS, and then returns the allocated M2M-Ext-ID to the DMS.
  • step 805 the DMS sends the M2M-Ext-ID received from the underlying network entity to the target node.
  • the target node stores the M2M-Ext-ID received from the DMS.
  • the target node provides the correspondence between the M2M-Ext-ID and the preset CSE-ID to the base node, and the base node may store the correspondence.
  • the base node can be at the access point of the ⁇ remoteCSE> resource (Point The corresponding relationship is stored in the Access, PoA) attribute, and a new attribute may also be created in the ⁇ remoteCSE> resource to store the correspondence.
  • the target node and the DMS can pass through the OMA.
  • the DM-1 interface or the DM-2 interface defined in the DM protocol is connected; and the private interface is not defined between the DMS and the underlying network entity, and no standardization is required.
  • Both the DMS and the underlying network entity belong to the mobile network operator (Mobile Network Operator, MNO).
  • FIG. 9 is a schematic flowchart of Embodiment 2 of an identifier configuration method according to an embodiment of the present invention.
  • an underlying network entity configures an M2M-Ext-ID for a target node by using a base node; The method includes the following steps:
  • Step 901 The target node registers with the base node, and creates a ⁇ remoteCSE> resource in the base node, where the ⁇ remoteCSE> resource is used to store related information of the target node, such as the M2M-Ext-ID and the CSE-ID of the target node. Correspondence relationship.
  • Step 902 The base node sends an identity request to the underlying network entity (M2M-Ext-ID)
  • the request message carries the terminal identifier (Device ID); wherein the terminal identifier may be an IP address of the target node or an IMEI of the terminal where the target node is located.
  • the identifier request message may further include service information, where the service information may include at least one of the following information: an identifier of the M2M service providing device, an identifier of the base node, and an application type (Application Type), business type (Service Type) and location (Location).
  • the identifier of the basic node may be an identifier of the service capability server (SCS) that the MTC-IWF entity can identify. ID).
  • SCS service capability server
  • Step 903 The underlying network entity allocates a corresponding M2M-Ext-ID to the target node according to the received terminal identifier, or according to the received terminal identifier and service information; where the underlying network entity may allocate at least one M2M to the target node.
  • -Ext-ID the underlying network entity sends an identity response (M2M-Ext-ID) to the underlying node
  • the Response message carries the assigned M2M-Ext-ID in the identity response message.
  • Step 904 The base node obtains a correspondence between the M2M-Ext-ID and the CSE-ID according to the received M2M-Ext-ID, and stores the corresponding relationship in the ⁇ remoteCSE> resource of the target node corresponding to the M2M-Ext-ID.
  • Medium which can be stored in the existing attribute of the ⁇ remoteCSE> resource, or in the new attribute created in the ⁇ remoteCSE> resource.
  • the base node may allocate a CSE-ID to the target node corresponding to the received M2M-Ext-ID. After the CSE-ID is allocated, the base node may obtain the correspondence between the M2M-Ext-ID and the CSE-ID.
  • Step 905 the target node sends a create subscription request to the base node (Create Subscription) Request) message or retrieve instruction.
  • Step 906 The base node sends a response message to the target node, where the response message includes the M2M-Ext-ID of the target node.
  • Step 907 The target node stores the M2M-Ext-ID received from the base node in its own ⁇ CSEBase> resource, and the target node associates the M2M-Ext-ID with the CSE-ID when the next time the registration is initiated to the base node. Provided to the base node.
  • FIG. 10 is a schematic flowchart of Embodiment 3 of an identifier configuration method according to an embodiment of the present invention.
  • multiple target nodes are registered to the same basic node, and the underlying network entity passes the basic node at the same time.
  • the M2M-Ext-ID is configured for multiple target nodes; as shown in FIG. 10, the method includes the following steps:
  • Step 1001 At least two target nodes are registered to the same base node, and a ⁇ remoteCSE> resource is created in the base node, where the ⁇ remoteCSE> resource is used to store related information of the target node, such as the M2M-Ext-ID of the target node. Correspondence with CSE-ID.
  • Step 1002 The base node sends an identity request to the underlying network entity (M2M-Ext-ID Request) message, the identifier request message carries the terminal identifier (Device
  • the ID) list may include at least two terminal identifiers in the terminal identifier list, where the terminal identifier may be an IP address of a target node registered to the base node or an IMEI of a terminal where the target node is located.
  • the identifier request message may further include service information, where the service information may include at least one of the following information: an identifier of the M2M service providing device, an identifier of the base node, and an application type (Application Type), business type (Service Type) and location (Location).
  • the identifier of the base node may be an identifier (SCS ID) of the service capability server that the MTC-IWF entity can identify.
  • Step 1003 The underlying network entity allocates an M2M-Ext-ID to the target node corresponding to each terminal identifier in the terminal identifier list according to the received terminal identifier list or according to the received terminal identifier list and service information;
  • the underlying network entity may allocate at least one M2M-Ext-ID for each target node;
  • the underlying network entity sends an identity response (M2M-Ext-ID to the base node)
  • the response message carries the identifier list, where the identifier list includes an M2M-Ext-ID allocated by the underlying network entity to the target node corresponding to each terminal identifier in the terminal identifier list.
  • the identifier list may include each terminal identifier and a corresponding M2M-Ext-ID, such as (Device The ID, M2M-Ext-ID, may also include only the M2M-Ext-ID, and the order of the M2M-Ext-ID is consistent with the order of the terminal identifiers in the terminal identifier list to ensure one-to-one correspondence.
  • Step 1004 The base node obtains a correspondence between the M2M-Ext-ID and the CSE-ID according to each of the M2M-Ext-IDs according to the received identifier list, and stores the corresponding relationship in the M2M-Ext-ID.
  • the ⁇ remoteCSE> resource of the target node which can be stored in the existing attribute of the ⁇ remoteCSE> resource, or can be stored in the new attribute created in the ⁇ remoteCSE> resource.
  • Step 1005 If a target node needs to obtain its own M2M-Ext-ID, if the target node needs to obtain the M2M-Ext-ID of the base node, the target node sends a create subscription request to the base node. Subscription Request message or retrieve command.
  • Step 1006 The base node sends a response (Response) message to the target node, where the response message includes the M2M-Ext-ID of the target node.
  • Step 1007 The target node stores the M2M-Ext-ID received from the base node in its own ⁇ CSEBase> resource, and the target node associates the M2M-Ext-ID with the CSE-ID when the next time the registration is initiated to the base node. The relationship is provided to the base node.
  • FIG. 11 is a schematic flowchart of Embodiment 4 of an identifier configuration method according to an embodiment of the present invention.
  • multiple target nodes are registered to the same basic node, and the underlying network entity simultaneously uses the basic node.
  • the M2M-Ext-ID is configured for multiple target nodes; as shown in FIG. 11, the method includes the following steps:
  • Step 1101 the base node sends an identity request to the underlying network entity (M2M-Ext-ID) Request) message, the identifier request message carries the terminal identifier (Device
  • the ID) list may include at least two terminal identifiers in the terminal identifier list, where the terminal identifier may be an IP address of a target node of the base node or an IMEI of a terminal where the target node is located.
  • the at least two terminal identifiers may be configured on the basic node in advance.
  • the identifier request message may further include service information, where the service information may include at least one of the following information: an identifier of the M2M service providing device, an identifier of the base node, and an application type (Application Type), business type (Service Type) and location (Location).
  • the identifier of the base node may be an identifier (SCS ID) of the service capability server that the MTC-IWF entity can identify.
  • Step 1102 The underlying network entity allocates an M2M-Ext-ID to the target node corresponding to each terminal identifier in the terminal identifier list according to the received terminal identifier list, or according to the received terminal identifier list and service information;
  • the underlying network entity may allocate at least one M2M-Ext-ID for each target node;
  • the underlying network entity sends an identity response (M2M-Ext-ID to the base node)
  • the response message carries the identifier list, where the identifier list includes an M2M-Ext-ID allocated by the underlying network entity to the target node corresponding to each terminal identifier in the terminal identifier list.
  • the identifier list may include each terminal identifier and a corresponding M2M-Ext-ID, such as (Device The ID, M2M-Ext-ID, may also include only the M2M-Ext-ID, and the order of the M2M-Ext-ID is consistent with the order of the terminal identifiers in the terminal identifier list to ensure one-to-one correspondence.
  • Step 1103 At least two target nodes are registered to the foregoing base node, and a ⁇ remoteCSE> resource is created in the base node, where the ⁇ remoteCSE> resource is used to store related information of the target node, such as the M2M-Ext-ID of the target node. Correspondence with CSE-ID.
  • Step 1104 The base node selects an M2M-Ext-ID from the identifier list as the M2M-Ext-ID of the target node according to the service information of the target node, and then obtains a correspondence between the M2M-Ext-ID and the CSE-ID, and The corresponding relationship is stored in the ⁇ remoteCSE> resource of the target node corresponding to the M2M-Ext-ID, where the existing attribute of the ⁇ remoteCSE> resource may be stored, or the new one created in the ⁇ remoteCSE> resource may be stored. In the attribute.
  • Step 1105 If a target node needs to obtain its own M2M-Ext-ID, if the target node needs to obtain the M2M-Ext-ID of the base node, the target node sends a create subscription request to the base node. Subscription Request message or retrieve command.
  • Step 1106 The base node sends a response (Response) message to the target node, where the response message includes the M2M-Ext-ID of the target node.
  • Step 1107 the target node stores the M2M-Ext-ID received from the base node in its own ⁇ CSEBase> resource, and the target node associates the M2M-Ext-ID with the CSE-ID when the next time the registration is initiated to the base node.
  • the relationship is provided to the base node.
  • a terminal management server (Device Management The server, DMS) or the base node can obtain the M2M-Ext-ID configured by the underlying network entity for the target node, and provide the obtained M2M-Ext-ID to the target node, so that the target node can register M2M-Ext at the time of registration.
  • the mapping between the ID and the CSE-ID is provided to the base node, so that the base node can carry the M2M-Ext-ID in the device trigger request sent to the underlying network entity, and the underlying network entity can route the trigger message according to the M2M-Ext-ID.
  • the corresponding target node is provided. Therefore, the technical solution provided by the embodiment of the present invention can implement the device triggering mechanism in the OneM2M technology.

Landscapes

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

Abstract

L'invention concerne un procédé et un équipement de configuration d'identité. Le procédé comprend : la réception, par un serveur de gestion de dispositif (DMS), d'une identité d'un dispositif dans lequel se trouve un nœud cible, l'identité étant envoyée par le nœud cible; l'envoi, par le DMS, de l'identité du dispositif dans lequel se trouve le nœud cible, à une entité de réseau sous-jacent, pour permettre à l'entité de réseau sous-jacent d'obtenir une identité externe de machine à machine (M2M-Ext-ID) du nœud cible d'après l'identité du dispositif dans lequel se trouve le nœud cible; la réception, par le DMS, de l'identité M2M-Ext-ID du nœud cible, qui est envoyée par l'entité de réseau sous-jacent; et l'envoi, par le DMS, de l'identité M2M-Ext-ID, au nœud cible, pour permettre au nœud cible d'obtenir une correspondance entre l'identité M2M-Ext-ID et une identité d'entité de service commune prédéfinie (CSE-ID) d'après l'identité M2M-Ext-ID et l'identité CSE-ID, la correspondance étant ensuite envoyée à un nœud d'infrastructure lorsque le nœud cible initie un enregistrement auprès du nœud d'infrastructure. La solution technique des modes de réalisation de la présente invention garantit la capacité de l'entité de réseau sous-jacent à acheminer un message de commande au nœud cible.
PCT/CN2014/085035 2014-08-22 2014-08-22 Procédé de configuration d'identité, serveur de gestion de dispositif, et nœud d'infrastructure WO2016026145A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201480080213.8A CN106471788B (zh) 2014-08-22 2014-08-22 标识配置方法、终端管理服务器及基础节点
PCT/CN2014/085035 WO2016026145A1 (fr) 2014-08-22 2014-08-22 Procédé de configuration d'identité, serveur de gestion de dispositif, et nœud d'infrastructure

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/085035 WO2016026145A1 (fr) 2014-08-22 2014-08-22 Procédé de configuration d'identité, serveur de gestion de dispositif, et nœud d'infrastructure

Publications (1)

Publication Number Publication Date
WO2016026145A1 true WO2016026145A1 (fr) 2016-02-25

Family

ID=55350130

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/085035 WO2016026145A1 (fr) 2014-08-22 2014-08-22 Procédé de configuration d'identité, serveur de gestion de dispositif, et nœud d'infrastructure

Country Status (2)

Country Link
CN (1) CN106471788B (fr)
WO (1) WO2016026145A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101902681A (zh) * 2010-07-21 2010-12-01 中兴通讯股份有限公司 M2m平台业务处理的方法和m2m平台
CN101932068A (zh) * 2009-06-19 2010-12-29 华为技术有限公司 实现机器对机器业务的方法、系统和装置
US20130227036A1 (en) * 2012-02-23 2013-08-29 Kt Corporation Providing machine-to-machine service
CN103618800A (zh) * 2013-12-05 2014-03-05 华为技术有限公司 订阅通知的实现方法和装置

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011025876A1 (fr) * 2009-08-27 2011-03-03 Interdigital Patent Holdings, Inc. Procédé et appareil pour résoudre le manque d'espace d'adressage dans des environnements de communication entre machines (m2m)
CN102014144A (zh) * 2009-09-04 2011-04-13 华为技术有限公司 一种终端数据上报方法和装置
CN102148863A (zh) * 2011-01-27 2011-08-10 华为技术有限公司 一种m2m业务消息传递的方法及装置
US8819649B2 (en) * 2011-09-09 2014-08-26 Microsoft Corporation Profile guided just-in-time (JIT) compiler and byte code generation

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101932068A (zh) * 2009-06-19 2010-12-29 华为技术有限公司 实现机器对机器业务的方法、系统和装置
CN101902681A (zh) * 2010-07-21 2010-12-01 中兴通讯股份有限公司 M2m平台业务处理的方法和m2m平台
US20130227036A1 (en) * 2012-02-23 2013-08-29 Kt Corporation Providing machine-to-machine service
CN103618800A (zh) * 2013-12-05 2014-03-05 华为技术有限公司 订阅通知的实现方法和装置

Also Published As

Publication number Publication date
CN106471788B (zh) 2019-07-23
CN106471788A (zh) 2017-03-01

Similar Documents

Publication Publication Date Title
WO2016024695A1 (fr) Procédé et appareil de téléchargement de profil de dispositifs de groupe
WO2016111600A1 (fr) Authentification mutuelle entre équipement utilisateur et cœur de réseau paquet évolué
WO2012141556A2 (fr) Procédure d'annulation pour des noeuds de communication entre machines
WO2014148859A1 (fr) Méthode et équipement utilisateur permettant de mettre en œuvre des communications dispositif à dispositif entre ue
WO2015157942A1 (fr) Dispositif et procédé d'accès à un réseau sans fil
WO2015016627A1 (fr) Procédé et dispositif permettant de connecter un seul dispositif ap parmi de multiples dispositifs ap dans le même réseau sur un terminal
WO2015137787A1 (fr) Procédé pour supporter une commande d'accès d'ue
WO2017030399A1 (fr) Procédé et appareil d'accès d'ue
WO2018147711A1 (fr) Appareil et procédé de contrôle d'accès de esim
WO2016195199A1 (fr) Procédé de traitement de requête par un canal d'interrogation dans un système de communication sans fil et appareil associé
WO2015037909A1 (fr) Procédé et appareil de fourniture d'un service de diffusion sélective dans un système de communication
WO2011155733A2 (fr) Procédé de communication entre un dispositif et un autre dispositif
WO2018038412A1 (fr) Procédé et équipement utilisateur permettant la connexion au moyen d'une pluralité d'accès dans un réseau de nouvelle génération
WO2018184302A1 (fr) Procédé de transmission de données, système, équilibreur de charge virtuelle et support de stockage lisible
WO2015020488A1 (fr) Procédé et appareil pour obtenir des informations d'authentification
WO2015002436A1 (fr) Procédé et appareil permettant d'optimiser un trajet de données dans un système de communications mobiles
WO2014205778A1 (fr) Procédé et passerelle de transmission de données
WO2015096040A1 (fr) Nœud d'accès, élément réseau de gestion mobile et procédé de traitement de message d'appel radio
WO2015100537A1 (fr) Dispositif de transmission, nœud de plan utilisateur et nœud de plan de commande, et procédé de transmission de données
WO2015053602A1 (fr) Procédé et système pour prendre en charge des informations associées à la sécurité pour un service basé sur la proximité dans un environnement de système de communication mobile
WO2017003255A1 (fr) Procédé de sélection de réseau et station de base
WO2019194412A1 (fr) Appareil de réseau et son procédé de commande
WO2022102949A1 (fr) Serveur de configuration de bord, serveur de validation de bord et procédé de commande associé
WO2015035640A1 (fr) Procédé, dispositif et système d'accès au réseau
WO2016026145A1 (fr) Procédé de configuration d'identité, serveur de gestion de dispositif, et nœud d'infrastructure

Legal Events

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

Ref document number: 14899973

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: 14899973

Country of ref document: EP

Kind code of ref document: A1