WO2016026145A1 - Identity configuration method, device management server and infrastructure node - Google Patents

Identity configuration method, device management server and infrastructure node 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
French (fr)
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/en
Priority to PCT/CN2014/085035 priority patent/WO2016026145A1/en
Publication of WO2016026145A1 publication Critical patent/WO2016026145A1/en

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

Provided are an identity configuration method and equipment. The method comprises: receiving, by a device management server (DMS), an identity of a device where a target node is located, wherein the identity is sent by the target node; sending, by the DMS, the identity of the device where the target node is located to an underlying network entity to enable the underlying network entity to obtain a machine-to-machine external identity (M2M-Ext-ID) of the target node according to the identity of the device where the target node is located; receiving, by the DMS, the M2M-Ext-ID of the target node, which is sent by the underlying network entity; and sending, by the DMS, the M2M-Ext-ID to the target node to enable the target node to obtain a correspondence between the M2M-Ext-ID and a pre-set common service entity-identity (CSE-ID) according to the M2M-Ext-ID and the CSE-ID, wherein the correspondence is sent to an infrastructure node when the target node initiates a registration to the infrastructure node. The technical solution provided by the embodiments of the present invention is used for ensuring that the underlying network entity can route a trigger message to the target node.

Description

标识配置方法、终端管理服务器及基础节点 Identification configuration method, terminal management server, and base node
【技术领域】[Technical Field]
本发明涉及通信领域，尤其涉及一种标识配置方法、终端管理服务器及基础节点。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.
【背景技术】 【Background technique】
现有技术中，电器和电子工程师协会（Institute of Electrical and Electronics Engineers，IEEE）技术中定义的公共服务功能中包括装置触发功能，该装置触发功能的实现原理为：目标节点在向基础节点（Infrastructure Node，IN）注册时，是需要将目标节点的公共服务实体标识（Common Service Entity-Identity，CSE-ID）与机器通信外部标识（M2M-External Identity，M2M-Ext-ID）的对应关系提供给基础节点的，使得基础节点依据该M2M-Ext-ID，进行底层网络实体的选择后，然后该基础节点能够向选出的底层网络实体发送装置触发请求（Device Triggering Request）消息，该消息中携带M2M-Ext-ID，M2M-Ext-ID是底层网络实体可以识别的表示标识，从而底层网络实体可以依据M2M-Ext-ID将触发消息路由给对应的目标节点；而其中，基础节点获得的CSE-ID用于实现业务层功能。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 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.
上述机制中，M2M-Ext-ID是由底层网络实体为目标节点分配的，然而现有技术中，目标节点无法获得M2M-Ext-ID，使得目标节点不能在注册时将CSE-ID与M2M-Ext-ID的对应关系提供给基础节点，导致底层网络实体不能将触发消息路由给目标节点。In the above mechanism, the M2M-Ext-ID is allocated by the underlying network entity to the target node. However, in the prior art, 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.
【发明内容】 [Summary of the Invention]
有鉴于此，本发明实施例提供了一种标识配置方法、终端管理服务器及基础节点，可以实现底层网络实体能够将触发消息路由给目标节点。In view of this, 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.
第一方面，本发明实施例提供了一种终端管理服务器DMS，包括：In a first aspect, 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;
发送单元，用于向底层网络实体发送的目标节点所在终端的标识，以使得所述底层网络实体依据所述目标节点所在终端的标识，获得所述目标节点的机器通信外部标识M2M-Ext-ID；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 ;
所述接收单元，还用于接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID；The receiving unit is further configured to receive an M2M-Ext-ID of the target node sent by the underlying network entity;
所述发送单元，还用于向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系，所述对应关系用于所述目标节点向基础节点发起注册时发送给所述基础节点。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.
第二方面，本发明实施例提供了一种基础节点，包括：In a second aspect, an embodiment of the present invention provides a basic node, including:
发送单元，用于向底层网络实体发送终端标识和业务信息，以使得所述底层网络实体依据所述终端标识和所述业务信息，获得目标节点的机器通信外部标识M2M-Ext-ID；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;
接收单元，用于从所述底层网络实体获得所述目标节点的M2M-Ext-ID；a receiving unit, configured to obtain an M2M-Ext-ID of the target node from the underlying network entity;
所述发送单元，还用于向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系；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.
在第二方面的第一种可能的实现方式中，所述接收单元，具体用于：In a first possible implementation manner of the second aspect, the receiving unit is specifically configured to:
接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID；或者，Receiving an M2M-Ext-ID of the target node sent by the underlying network entity; or
从机器通信M2M业务提供设备接收所述目标节点的M2M-Ext-ID；所述M2M-Ext-ID为所述M2M业务提供设备从所述底层网络实体获得的。Receiving, by the machine communication M2M service providing device, an M2M-Ext-ID of the target node; the M2M-Ext-ID being obtained by the M2M service providing device from the underlying network entity.
在第二方面的第二种可能的实现方式中，所述业务信息包括以下信息中至少一个：M2M业务提供设备的标识、基础节点的标识、应用类型、业务类型和位置中至少一个信息。In a second possible implementation manner of the second aspect, 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.
在第二方面的第三种可能的实现方式中，所述发送单元，具体用于：存储所述M2M-Ext-ID，以及向所述目标节点发送所述M2M-Ext-ID；或者，在所述接收单元接收到所述目标节点发送的收回指令后，向所述目标节点发送应答消息，所述应答消息携带所述M2M-Ext-ID。In a third possible implementation manner of the second aspect, 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.
在第二方面的第四种可能的实现方式中，所述基础节点还包括：In a fourth possible implementation manner of the second aspect, the base node further includes:
处理单元，用于获得用于存储所述M2M-Ext-ID的资源，所述M2M-Ext-ID的资源为所述目标节点在向所述基础节点发起注册后在所述基础节点创建的。And 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.
第三方面，本发明实施例还提供了一种标识配置方法，包括：In a third aspect, an embodiment of the present invention further provides an identifier configuration method, including:
终端管理服务器DMS接收目标节点发送的所述目标节点所在终端的标识；Receiving, by the terminal management server, the identifier of the terminal where the target node is sent by the target node;
所述DMS向底层网络实体发送的目标节点所在终端的标识，以使得所述底层网络实体依据所述目标节点所在终端的标识，获得所述目标节点的机器通信外部标识M2M-Ext-ID；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-ID of the target node according to the identifier of the terminal where the target node is located;
所述DMS接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID；Receiving, by the DMS, an M2M-Ext-ID of the target node sent by the underlying network entity;
所述DMS向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系，所述对应关系用于所述目标节点向基础节点发起注册时发送给所述基础节点。Sending, by the DMS, the M2M-Ext-ID to the target node, so that the target node obtains the M2M-Ext- according to the M2M-Ext-ID and a preset public service entity identifier CSE-ID. Correspondence relationship between the 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.
第四方面，本发明实施例还提供了一种标识配置方法，包括：In a fourth aspect, the embodiment of the present invention further provides an identifier configuration method, including:
基础节点向底层网络实体发送终端标识和业务信息，以使得所述底层网络实体依据所述终端标识和所述业务信息，获得目标节点的机器通信外部标识M2M-Ext-ID；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;
所述基础节点从所述底层网络实体获得所述目标节点的M2M-Ext-ID；Obtaining, by the base node, an M2M-Ext-ID of the target node from the underlying network entity;
所述基础节点向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系；Sending, by the base node, the M2M-Ext-ID to the target node, so that the target node obtains the M2M-Ext according to the M2M-Ext-ID and a preset public service entity identifier CSE-ID a correspondence between the ID and the CSE-ID;
所述基础节点接收所述目标节点向所述基础节点发起注册时发送的所述对应关系。The base node receives the correspondence that is sent when the target node initiates registration with the base node.
在第四方面的第一种可能的实现方式中，所述基础节点从所述底层网络实体获得所述目标节点的M2M-Ext-ID，包括：In a first possible implementation manner of the fourth aspect, the base node obtains the M2M-Ext-ID of the target node from the underlying network entity, including:
所述基础节点接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID；或者，Receiving, by the base node, an M2M-Ext-ID of the target node sent by the underlying network entity; or
所述基础节点从机器通信M2M业务提供设备接收所述目标节点的M2M-Ext-ID；所述M2M-Ext-ID为所述M2M业务提供设备从所述底层网络实体获得的。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.
在第四方面的第二种可能的实现方式中，所述业务信息包括以下信息中至少一个：M2M业务提供设备的标识、基础节点的标识、应用类型、业务类型和位置中至少一个信息。In a second possible implementation manner of the fourth aspect, 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.
在第四方面的第三种可能的实现方式中，所述基础节点向所述目标节点发送所述M2M-Ext-ID，包括：In a third possible implementation manner of the fourth aspect, the sending, by the base node, the M2M-Ext-ID to the target node includes:
所述基础节点存储所述M2M-Ext-ID，以及向所述目标节点发送所述M2M-Ext-ID；或者，The base node stores the M2M-Ext-ID, and sends the M2M-Ext-ID to the target node; or
所述基础节点在接收到所述目标节点发送的收回指令后，向所述目标节点发送应答消息，所述应答消息携带所述M2M-Ext-ID。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.
在第四方面的第四种可能的实现方式中，所述基础节点获得用于存储所述M2M-Ext-ID的资源，所述M2M-Ext-ID的资源为所述目标节点在向所述基础节点发起注册后在所述基础节点创建的。In a fourth possible implementation manner of the fourth aspect, 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.
通过上述技术方案，终端管理服务器（Device Management Server，DMS）或者基础节点可以获得底层网络实体为目标节点配置的M2M-Ext-ID，并将获得的M2M-Ext-ID提供给目标节点，这样，目标节点就能够在注册时将M2M-Ext-ID与CSE-ID的对应关系提供给基础节点，使得基础节点可以在向底层网络实体发送的装置触发请求中携带M2M-Ext-ID，底层网络实体能够依据M2M-Ext-ID将触发消息路由给相应的目标节点，因此，本发明实施例提供的技术方案能够实现OneM2M技术中的装置触发机制。Through the above technical solution, 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.
【附图说明】 [Description of the Drawings]
为了更清楚地说明本发明实施例的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动性的前提下，还可以根据这些附图获得其它的附图。In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings used in the embodiments will be briefly described below. It is obvious that the drawings in the following description are only some embodiments of the present invention. One of ordinary skill in the art can also obtain other drawings based on these drawings without paying for inventive labor.
图1是本发明实施例所提供的终端管理服务器的功能方块图；1 is a functional block diagram of a terminal management server according to an embodiment of the present invention;
图2是本发明实施例所提供的技术方案使用的***的架构示意图；2 is a schematic structural diagram of a system used by a technical solution provided by an embodiment of the present invention;
图3是本发明实施例所提供的终端管理服务器的结构示意图；3 is a schematic structural diagram of a terminal management server according to an embodiment of the present invention;
图4是本发明实施例所提供的基础节点的功能方块图；4 is a functional block diagram of a base node according to an embodiment of the present invention;
图5是本发明实施例所提供的基础节点的结构示意图；FIG. 5 is a schematic structural diagram of a base node according to an embodiment of the present invention; FIG.
图6是本发明实施例所提供的标识配置方法一的流程示意图；FIG. 6 is a schematic flowchart of a method 1 for configuring identity according to an embodiment of the present invention;
图7是本发明实施例所提供的标识配置方法二的流程示意图；FIG. 7 is a schematic flowchart of a second method for configuring identity according to an embodiment of the present invention;
图8是本发明实施例所提供的标识配置方法的实施例一的流程示意图；FIG. 8 is a schematic flowchart diagram of Embodiment 1 of an identifier configuration method according to an embodiment of the present disclosure;
图9是本发明实施例所提供的标识配置方法的实施例二的流程示意图；FIG. 9 is a schematic flowchart of Embodiment 2 of an identifier configuration method according to an embodiment of the present disclosure;
图10是本发明实施例所提供的标识配置方法的实施例三的流程示意图；10 is a schematic flowchart of Embodiment 3 of a method for configuring an identifier provided by an embodiment of the present invention;
图11是本发明实施例所提供的标识配置方法的实施例四的流程示意图。FIG. 11 is a schematic flowchart diagram of Embodiment 4 of an identifier configuration method according to an embodiment of the present invention.
【具体实施方式】 【detailed description】
为了更好的理解本发明的技术方案，下面结合附图对本发明实施例进行详细描述。For a better understanding of the technical solutions of the present invention, the embodiments of the present invention are described in detail below with reference to the accompanying drawings.
应当明确，所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其它实施例，都属于本发明保护的范围。It should be understood that the described embodiments are only a part of the embodiments of the invention, and not all of the embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts are within the scope of the present invention.
在本发明实施例中使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本发明。在本发明实施例和所附权利要求书中所使用的单数形式的“一种”、“所述”和“该”也旨在包括多数形式，除非上下文清楚地表示其他含义。还应当理解，本文中使用的术语“和/或”是指并包含一个或多个相关联的列出项目的任何或所有可能组合。The terms used in the embodiments of the present invention are for the purpose of describing particular embodiments only and are not intended to limit the invention. The singular forms "a", "the" and "the" It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
取决于语境，如在此所使用的词语“如果”可以被解释成为“在……时”或“当……时”或“响应于确定”或“响应于检测”。Depending on the context, the word "if" as used herein may be interpreted as "when" or "when" or "in response to determining" or "in response to detecting."
请参考图1，其为本发明实施例所提供的终端管理服务器的功能方块图。如图所示，该DMS包括：Please refer to FIG. 1 , which is a functional block diagram of a terminal management server according to an embodiment of the present invention. As shown, the DMS includes:
接收单元10，用于接收目标节点发送的所述目标节点所在终端的标识；The receiving unit 10 is configured to receive an identifier of a terminal where the target node is sent by the target node;
发送单元11，用于向底层网络实体发送的目标节点所在终端的标识，以使得所述底层网络实体依据所述目标节点所在终端的标识，获得所述目标节点的机器通信外部标识M2M-Ext-ID；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;
所述接收单元10，还用于接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID；The receiving unit 10 is further configured to receive an M2M-Ext-ID of the target node sent by the underlying network entity;
所述发送单元11，还用于向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系，所述对应关系用于所述目标节点向基础节点发起注册时发送给所述基础节点。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.
优选的，所述底层网络实体可以为第三代合作伙伴计划（3rd Generation Partnership Project，3GPP）网络实体。Preferably, the underlying network entity may be a 3rd Generation Partnership (3rd Generation Partnership) Project, 3GPP) Network entity.
本发明实施例中，所述M2M-Ext-ID可以包括：域标识（Domain ID）和区域标识（Local ID）；其中，依据提供业务的不同，所述域标识不同；依据区域标识可以获得所述目标节点所在终端的国际移动用户识别码（International Mobile Subscriber Identification Number，IMSI），而且，所述区域标识在域标识所对应的业务域中是唯一的。In the embodiment of the present invention, 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.
本发明实施例中，所述目标节点可以为应用业务节点（Application Service Node）中的公共业务实体（Common Service Entity，ASN-CSE），也可以为中间节点（Middle Node，MN）中的公共业务实体（Common Service Entity，MN-CSE）。In the embodiment of the present invention, 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).
本发明实施例中，所述基础节点可以为基础节点中的公共业务实体（Common Service Entity，IN-CSE）。In this embodiment of the present invention, the basic node may be a public service entity in the basic node (Common Service) Entity, IN-CSE).
请参考图2，其为本发明实施例所提供的技术方案使用的***的架构示意图，如图所示，ASD可以通过MN与基础节点连接，ASN还可以通过参考点Mcc与基础节点连接。Please refer to FIG. 2 , which is a schematic structural diagram of a system used by the technical solution provided by the embodiment of the present invention. As shown in the figure, 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.
如图2所示，本发明实施例所提供的技术方案使用的***中可以包括： IN-CSE、基础节点中的应用实体（Application Entity，IN-AE）、MN-CSE、中间节点中的应用实体（Application Entity，MN-AE）、应用专用节点（Application Dedicated Node，ADN）中的应用实体（Application Entity，ADN -AE）、ASN-CSE、应用业务节点中的的应用实体（Application Entity，ASN-AE）。图中的还包括Mcc接口、Mca接口和Mcn接口。As shown in FIG. 2, 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.
需要说明的是，每个目标节点可以获得至少一个M2M-Ext-ID。It should be noted that each target node can obtain at least one M2M-Ext-ID.
优选的，所述目标节点所在终端的标识可以为终端标识（Device ID），所述终端标识可以包括：国际移动设备身份识别码（International Mobile Equipment Identity，IMEI）、通用唯一识别码（Universally Unique Identifier，UUID）、电子序列号（Electronic Serial Number，ESN）或者移动设备识别码（(Mobile Equipment Identifier，MEID)。Preferably, 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).
请参考图3，其为本发明实施例所提供的终端管理服务器的结构示意图。如图所示，该终端管理服务器包括：Please refer to FIG. 3 , which is a schematic structural diagram of a terminal management server according to an embodiment of the present invention. As shown, the terminal management server includes:
接收器30，用于接收目标节点发送的所述目标节点所在终端的标识；a receiver 30, configured to receive an identifier of a terminal where the target node is sent by the target node;
发射器31，用于向底层网络实体发送的目标节点所在终端的标识，以使得所述底层网络实体依据所述目标节点所在终端的标识，获得所述目标节点的机器通信外部标识M2M-Ext-ID；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;
所述接收器30，还用于接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID；The receiver 30 is further configured to receive an M2M-Ext-ID of the target node sent by the underlying network entity;
所述发射器31，还用于向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系，所述对应关系用于所述目标节点向基础节点发起注册时发送给所述基础节点。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.
还可以包括：It can also include:
存储器32，用于存储包括程序例程的信息；a memory 32 for storing information including a program routine;
处理器33，与存储器32、发射器31、接收器30分别耦合，用于控制所述程序例程的执行。The processor 33 is coupled to the memory 32, the transmitter 31, and the receiver 30, respectively, for controlling execution of the program routine.
请参考图4，其为本发明实施例所提供的基础节点的功能方块图。如图所示，该基础节点包括：Please refer to FIG. 4 , which is a functional block diagram of a base node according to an embodiment of the present invention. As shown, the base node includes:
发送单元40，用于向底层网络实体发送终端标识和业务信息，以使得所述底层网络实体依据所述终端标识和所述业务信息，获得目标节点的机器通信外部标识M2M-Ext-ID；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;
接收单元41，用于从所述底层网络实体获得所述目标节点的M2M-Ext-ID；The receiving unit 41 is configured to obtain an M2M-Ext-ID of the target node from the underlying network entity;
所述发送单元40，还用于向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系；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;
所述接收单元41，还用于接收所述目标节点向所述基础节点发起注册时发送的所述对应关系。The receiving unit 41 is further configured to receive the correspondence that is sent when the target node initiates registration with the base node.
优选的，所述接收单元41，具体用于：Preferably, the receiving unit 41 is specifically configured to:
接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID；或者，Receiving an M2M-Ext-ID of the target node sent by the underlying network entity; or
从机器通信M2M业务提供设备接收所述目标节点的M2M-Ext-ID；所述M2M-Ext-ID为所述M2M业务提供设备从所述底层网络实体获得的。Receiving, by the machine communication M2M service providing device, an M2M-Ext-ID of the target node; the M2M-Ext-ID being obtained by the M2M service providing device from the underlying network entity.
例如，底层网络实体可以依据业务类型，将业务类型对应的所有M2M-Ext-ID都发送给M2M业务提供设备，由M2M业务提供设备在为目标节点分配CSE-ID时，将CSE-ID与M2M-Ext-ID的对应关系存储在基础节点中。For example, 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.
优选的，所述业务信息包括以下信息中至少一个：M2M业务提供设备的标识、基础节点的标识、应用类型、业务类型和位置中至少一个信息。Preferably, 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.
例如，其中，所述终端标识可以包括目标节点的IP地址或者目标节点所在终端的IMSI。For example, the terminal identifier may include an IP address of the target node or an IMSI of the terminal where the target node is located.
例如，所述底层网络实体可以依据所述终端标识和所述业务信息，为目标节点分配至少一个M2M-Ext-ID。For example, 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.
例如，所述基础节点的标识可以是机器类型通信交互功能（Machine-Type Communication Interworking Function，MTC-IWF）实体能够识别的业务能力服务器（Service Capability Server，SCS）的标识。For example, 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.
优选的，所述发送单元40具体用于：存储所述M2M-Ext-ID，以及向所述目标节点发送所述M2M-Ext-ID；或者，在所述接收单元接收到所述目标节点发送的收回指令后，向所述目标节点发送应答消息，所述应答消息携带所述M2M-Ext-ID。Preferably, 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.
例如，所述基础节点存储所述M2M-Ext-ID具体包括：基础节点可以将获得的M2M-Ext-ID存储在目标节点对应的<remoteCSE>资源中，其中，可以存储在该<remoteCSE>资源的已有属性中，也可以在<remoteCSE>资源中创建新的属性，然后利用该<remoteCSE>资源中新的属性存储M2M-Ext-ID。For example, 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. In 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.
可选的，所述基础节点还包括：Optionally, the base node further includes:
处理单元42，用于获得用于存储所述M2M-Ext-ID的资源，所述M2M-Ext-ID的资源为所述目标节点在向所述基础节点发起注册后在所述基础节点创建的。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. .
例如，所述目标节点可以在基础节点中创建<remoteCSE>资源，该<remoteCSE>资源用于存储所述目标节点获得的M2M-Ext-ID。For example, 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.
请参考图5，其为本发明实施例所提供的基础节点的结构示意图。如图所示，该基础节点包括：Please refer to FIG. 5 , which is a schematic structural diagram of a base node according to an embodiment of the present invention. As shown, the base node includes:
发射器50，用于向底层网络实体发送终端标识和业务信息，以使得所述底层网络实体依据所述终端标识和所述业务信息，获得目标节点的机器通信外部标识M2M-Ext-ID；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;
接收器51，用于从所述底层网络实体获得所述目标节点的M2M-Ext-ID；a receiver 51, configured to obtain an M2M-Ext-ID of the target node from the underlying network entity;
所述发射器50，还用于向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系；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;
所述接收器51，还用于接收所述目标节点向所述基础节点发起注册时发送的所述对应关系。The receiver 51 is further configured to receive the correspondence that is sent when the target node initiates registration with the base node.
存储器52，用于存储包括程序例程的信息；a memory 52 for storing information including a program routine;
处理器51，与存储器52、发射器50、接收器51分别耦合，用于控制所述程序例程的执行。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.
本发明实施例给出一种标识配置方法，请参考图6，其为本发明实施例所提供的标识配置方法一的流程示意图，是终端管理服务器侧实现标识配置的方法；如图6所示，该方法包括以下步骤：An embodiment of the present invention provides a method for configuring an identifier. Referring to 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:
步骤601，终端管理服务器DMS接收目标节点发送的所述目标节点所在终端的标识。Step 601: The terminal management server DMS receives the identifier of the terminal where the target node is sent by the target node.
步骤602，所述DMS向底层网络实体发送的目标节点所在终端的标识，以使得所述底层网络实体依据所述目标节点所在终端的标识，获得所述目标节点的机器通信外部标识M2M-Ext-ID。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.
步骤603，所述DMS接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID。Step 603: The DMS receives an M2M-Ext-ID of the target node sent by the underlying network entity.
步骤604，所述DMS向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系，所述对应关系用于所述目标节点向基础节点发起注册时发送给所述基础节点。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.
本发明实施例给出一种标识配置方法，请参考图7，其为本发明实施例所提供的标识配置方法二的流程示意图，是基础节点侧实现标识配置的方法；如图7所示，该方法包括以下步骤：An embodiment of the present invention provides a method for configuring an identifier. Referring to 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:
步骤701，基础节点向底层网络实体发送终端标识和业务信息，以使得所述底层网络实体依据所述终端标识和所述业务信息，获得目标节点的机器通信外部标识M2M-Ext-ID。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.
优选的，所述业务信息包括以下信息中至少一个：M2M业务提供设备的标识、基础节点的标识、应用类型、业务类型和位置中至少一个信息。Preferably, 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.
步骤702，所述基础节点从所述底层网络实体获得所述目标节点的M2M-Ext-ID。Step 702: The base node obtains an M2M-Ext-ID of the target node from the underlying network entity.
具体的，所述基础节点从所述底层网络实体获得所述目标节点的M2M-Ext-ID的方法可以包括以下两种：Specifically, 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:
第一种：所述基础节点接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID。First: the base node receives an M2M-Ext-ID of the target node sent by the underlying network entity.
第二种：所述基础节点从机器通信M2M业务提供设备接收所述目标节点的M2M-Ext-ID；所述M2M-Ext-ID为所述M2M业务提供设备从所述底层网络实体获得的。Second: 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.
步骤703，所述基础节点向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系。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.
具体的，所述基础节点向所述目标节点发送所述M2M-Ext-ID的方法可以包括以下两种：Specifically, the method for the base node to send the M2M-Ext-ID to the target node may include the following two types:
第一种：所述基础节点存储所述M2M-Ext-ID，以及向所述目标节点发送所述M2M-Ext-ID。First: the base node stores the M2M-Ext-ID and sends the M2M-Ext-ID to the target node.
第二种：所述基础节点在接收到所述目标节点发送的收回指令后，向所述目标节点发送应答消息，所述应答消息携带所述M2M-Ext-ID。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.
步骤704，所述基础节点接收所述目标节点向所述基础节点发起注册时发送的所述对应关系。Step 704: The base node receives the correspondence that is sent when the target node initiates registration with the base node.
可选的，上述方法还可以包括：Optionally, the foregoing method may further include:
所述基础节点获得用于存储所述M2M-Ext-ID的资源，所述M2M-Ext-ID的资源为所述目标节点在向所述基础节点发起注册后在所述基础节点创建的。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.
实施例一Embodiment 1
请参考图8，其为本发明实施例所提供的标识配置方法的实施例一的流程示意图，本实施例中，底层网络实体通过开放移动联盟（Open Mobile Alliance，OMA）终端管理（Device Management）方式为目标节点配置M2M-Ext-ID；如图8所示，该方法包括以下步骤：Please refer to FIG. 8 , which is a schematic flowchart of Embodiment 1 of an identifier configuration method according to an embodiment of the present invention. In this embodiment, 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:
步骤801，目标节点利用终端标识（Device ID）进行启动载入（Boot Trapped）操作，其中，终端标识可以包括IMEI、UUID、ESN或者MEID。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.
步骤802，目标节点所在终端中DM客户端进行初始化，以获得终端标识，目标节点向DMS发送该获得的终端标识。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.
步骤803，DMS依据收到的终端标识，获得目标节点所在终端的IMEI，然后向底层网络实体发送该目标节点所在终端的IMEI。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.
步骤804，底层网络实体依据DMS发送的IMSI，为该IMSI对应的终端中的目标节点分配M2M-Ext-ID，然后向DMS返回分配的M2M-Ext-ID。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.
步骤805，DMS向目标节点发送从底层网络实体接收到的M2M-Ext-ID。In step 805, the DMS sends the M2M-Ext-ID received from the underlying network entity to the target node.
步骤806，目标节点存储从DMS收到的M2M-Ext-ID。当目标节点向基础节点发起注册时，目标节点将该M2M-Ext-ID与预设的CSE-ID的对应关系提供给基础节点，基础节点可以存储该对应关系。例如，基础节点可以在<remoteCSE>资源的访问点（Point of Access，PoA）属性中存储该对应关系，也可以在<remoteCSE>资源中创建新的属性来存储该对应关系。In step 806, the target node stores the M2M-Ext-ID received from the DMS. When the target node initiates registration with the base node, 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. For example, 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.
需要说明的是，实施例一中，目标节点与DMS可以通过OMA DM协议中定义的DM-1接口或者DM-2接口连接；而DMS与底层网络实体之间没有定义私有接口，不需要进行标准化处理。DMS与底层网络实体都属于移动网络运营商（Mobile Network Operator，MNO）。It should be noted that in the first embodiment, 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).
实施例二Embodiment 2
请参考图9，其为本发明实施例所提供的标识配置方法的实施例二的流程示意图，本实施例中，底层网络实体通过基础节点为目标节点配置M2M-Ext-ID；如图9所示，该方法包括以下步骤：FIG. 9 is a schematic flowchart of Embodiment 2 of an identifier configuration method according to an embodiment of the present invention. In this embodiment, an underlying network entity configures an M2M-Ext-ID for a target node by using a base node; The method includes the following steps:
步骤901，目标节点注册到基础节点，并在基础节点中创建<remoteCSE>资源，该<remoteCSE>资源用于存储目标节点的相关信息，如该目标节点的M2M-Ext-ID与CSE-ID的对应关系。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.
步骤902，基础节点向底层网络实体发送标识请求（M2M-Ext-ID Request）消息，该标识请求消息中携带终端标识（Device ID）；其中，该终端标识可以是目标节点的IP地址或者目标节点所在终端的IMEI。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.
可选的，所述标识请求消息中还可以携带业务信息，该业务信息可以包括以下信息中至少一个：M2M业务提供设备的标识、基础节点的标识、应用类型（Application Type）、业务类型（Service Type）和位置（Location）。其中，如果MTC-IWF与SCS之间的接口是Tsp接口，基础节点的标识可以为MTC-IWF实体能够识别的业务能力服务器的标识（SCS ID）。Optionally, 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). If the interface between the MTC-IWF and the SCS is a Tsp interface, the identifier of the basic node may be an identifier of the service capability server (SCS) that the MTC-IWF entity can identify. ID).
步骤903，底层网络实体依据收到的终端标识，或者，依据收到的终端标识和业务信息，为目标节点分配对应的M2M-Ext-ID；这里，底层网络实体可以为目标节点分配至少一个M2M-Ext-ID；底层网络实体向基础节点发送标识应答（M2M-Ext-ID Response）消息，该标识应答消息中携带分配的M2M-Ext-ID。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.
步骤904，基础节点依据收到的M2M-Ext-ID，得到M2M-Ext-ID与CSE-ID的对应关系，并将该对应关系存储在M2M-Ext-ID对应的目标节点的<remoteCSE>资源中，其中，可以存储在<remoteCSE>资源的已有属性中，也可以存储在<remoteCSE>资源中创建的新的属性中。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.
其中，基础节点可以为收到的M2M-Ext-ID对应的目标节点分配CSE-ID，分配好CSE-ID后，基础节点就可以获得M2M-Ext-ID与CSE-ID的对应关系。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.
步骤905，目标节点向基础节点发送创建订阅请求（Create Subscription Request）消息或者收回（Retrieve）指令。Step 905, the target node sends a create subscription request to the base node (Create Subscription) Request) message or Retrieve instruction.
步骤906，基础节点向目标节点发送应答（Response）消息，该应答消息中包含该目标节点的M2M-Ext-ID。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.
步骤907，目标节点在自身的<CSEBase>资源中存储从基础节点收到的M2M-Ext-ID，在下次向基础节点发起注册时，目标节点将M2M-Ext-ID与CSE-ID的对应关系提供给基础节点。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.
实施例三Embodiment 3
请参考图10，其为本发明实施例所提供的标识配置方法的实施例三的流程示意图，本实施例中，该多个目标节点注册到同一个基础节点，底层网络实体通过该基础节点同时为多个目标节点配置M2M-Ext-ID；如图10所示，该方法包括以下步骤：Please refer to FIG. 10, which is a schematic flowchart of Embodiment 3 of an identifier configuration method according to an embodiment of the present invention. In this embodiment, 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:
步骤1001，至少两个目标节点注册到同一基础节点，并在该基础节点中创建<remoteCSE>资源，该<remoteCSE>资源用于存储目标节点的相关信息，如该目标节点的M2M-Ext-ID与CSE-ID的对应关系。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.
步骤1002，基础节点向底层网络实体发送标识请求（M2M-Ext-ID Request）消息，该标识请求消息中携带终端标识（Device ID）列表，该终端标识列表中可以包括至少两个终端标识，其中，终端标识可以是注册到该基础节点的目标节点的IP地址或者目标节点所在终端的IMEI。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.
可选的，所述标识请求消息中还可以携带业务信息，该业务信息可以包括以下信息中至少一个：M2M业务提供设备的标识、基础节点的标识、应用类型（Application Type）、业务类型（Service Type）和位置（Location）。其中，如果是Tsp接口，基础节点的标识可以MTC-IWF实体能够识别的业务能力服务器的标识（SCS ID）。Optionally, 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). Wherein, if it is a Tsp interface, the identifier of the base node may be an identifier (SCS ID) of the service capability server that the MTC-IWF entity can identify.
步骤1003，底层网络实体依据收到的终端标识列表，或者，依据收到的终端标识列表和业务信息，为终端标识列表中每个终端标识所对应的目标节点都分配M2M-Ext-ID；这里，底层网络实体可以为每个目标节点都分配至少一个M2M-Ext-ID；底层网络实体向基础节点发送标识应答（M2M-Ext-ID Response）消息，该标识应答消息中携带标识列表，该标识列表中包括底层网络实体为终端标识列表中每个终端标识所对应的目标节点分配的M2M-Ext-ID。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.
其中，所述标识列表可以包括每个终端标识以及对应的M2M-Ext-ID，如（Device ID，M2M-Ext-ID），也可以只包括M2M-Ext-ID，且M2M-Ext-ID的顺序与终端标识列表中终端标识的顺序一致，以保证可以一一对应。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.
步骤1004，基础节点依据收到的标识列表，依据其中的每个M2M-Ext-ID，得到M2M-Ext-ID与CSE-ID的对应关系，并将该对应关系存储在M2M-Ext-ID对应的目标节点的<remoteCSE>资源中，其中，可以存储在<remoteCSE>资源的已有属性中，也可以存储在<remoteCSE>资源中创建的新的属性中。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.
步骤1005，若注册到基础节点的多个目标节点中，某目标节点需要获得自身的M2M-Ext-ID，则该目标节点向基础节点发送创建订阅请求（Create Subscription Request）消息或者收回（Retrieve）指令。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.
步骤1006，基础节点向该目标节点发送应答（Response）消息，该应答消息中包含该目标节点的M2M-Ext-ID。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.
步骤1007，该目标节点在自身的<CSEBase>资源中存储从基础节点收到的M2M-Ext-ID，在下次向基础节点发起注册时，目标节点将M2M-Ext-ID与CSE-ID的对应关系提供给基础节点。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.
实施例四Embodiment 4
请参考图11，其为本发明实施例所提供的标识配置方法的实施例四的流程示意图，本实施例中，该多个目标节点注册到同一个基础节点，底层网络实体通过该基础节点同时为多个目标节点配置M2M-Ext-ID；如图11所示，该方法包括以下步骤：Please refer to FIG. 11 , which is a schematic flowchart of Embodiment 4 of an identifier configuration method according to an embodiment of the present invention. In this embodiment, 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:
步骤1101，基础节点向底层网络实体发送标识请求（M2M-Ext-ID Request）消息，该标识请求消息中携带终端标识（Device ID）列表，该终端标识列表中可以包括至少两个终端标识，其中，终端标识可以是基础节点的目标节点的IP地址或者目标节点所在终端的IMEI。其中，可以预先在基础节点上配置好所述至少两个终端标识。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.
可选的，所述标识请求消息中还可以携带业务信息，该业务信息可以包括以下信息中至少一个：M2M业务提供设备的标识、基础节点的标识、应用类型（Application Type）、业务类型（Service Type）和位置（Location）。其中，如果是Tsp接口，基础节点的标识可以MTC-IWF实体能够识别的业务能力服务器的标识（SCS ID）。Optionally, 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). Wherein, if it is a Tsp interface, the identifier of the base node may be an identifier (SCS ID) of the service capability server that the MTC-IWF entity can identify.
步骤1102，底层网络实体依据收到的终端标识列表，或者，依据收到的终端标识列表和业务信息，为终端标识列表中每个终端标识所对应的目标节点都分配M2M-Ext-ID；这里，底层网络实体可以为每个目标节点都分配至少一个M2M-Ext-ID；底层网络实体向基础节点发送标识应答（M2M-Ext-ID Response）消息，该标识应答消息中携带标识列表，该标识列表中包括底层网络实体为终端标识列表中每个终端标识所对应的目标节点分配的M2M-Ext-ID。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.
其中，所述标识列表可以包括每个终端标识以及对应的M2M-Ext-ID，如（Device ID，M2M-Ext-ID），也可以只包括M2M-Ext-ID，且M2M-Ext-ID的顺序与终端标识列表中终端标识的顺序一致，以保证可以一一对应。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.
步骤1103，至少两个目标节点注册到上述基础节点，并在该基础节点中创建<remoteCSE>资源，该<remoteCSE>资源用于存储目标节点的相关信息，如该目标节点的M2M-Ext-ID与CSE-ID的对应关系。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.
步骤1104，基础节点依据目标节点的业务信息，从标识列表中选择一个M2M-Ext-ID作为该目标节点的M2M-Ext-ID，然后得到M2M-Ext-ID与CSE-ID的对应关系，并将该对应关系存储在M2M-Ext-ID对应的目标节点的<remoteCSE>资源中，其中，可以存储在<remoteCSE>资源的已有属性中，也可以存储在<remoteCSE>资源中创建的新的属性中。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.
步骤1105，若注册到基础节点的多个目标节点中，某目标节点需要获得自身的M2M-Ext-ID，则该目标节点向基础节点发送创建订阅请求（Create Subscription Request）消息或者收回（Retrieve）指令。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.
步骤1106，基础节点向该目标节点发送应答（Response）消息，该应答消息中包含该目标节点的M2M-Ext-ID。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.
步骤1107，该目标节点在自身的<CSEBase>资源中存储从基础节点收到的M2M-Ext-ID，在下次向基础节点发起注册时，目标节点将M2M-Ext-ID与CSE-ID的对应关系提供给基础节点。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.
本发明实施例提供的技术方案中，终端管理服务器（Device Management Server，DMS）或者基础节点可以获得底层网络实体为目标节点配置的M2M-Ext-ID，并将获得的M2M-Ext-ID提供给目标节点，这样，目标节点就能够在注册时将M2M-Ext-ID与CSE-ID的对应关系提供给基础节点，使得基础节点可以在向底层网络实体发送的装置触发请求中携带M2M-Ext-ID，底层网络实体能够依据M2M-Ext-ID将触发消息路由给相应的目标节点，因此，本发明实施例提供的技术方案能够实现OneM2M技术中的装置触发机制。In the technical solution provided by the embodiment of the present invention, 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.
以上所述仅为本发明的较佳实施例而已，并不用以限制本发明，凡在本发明的精神和原则之内，所做的任何修改、等同替换、改进等，均应包含在本发明保护的范围之内。The above are only the preferred embodiments of the present invention, and are not intended to limit the present invention. Any modifications, equivalents, improvements, etc., which are made within the spirit and principles of the present invention, should be included in the present invention. Within the scope of protection.

Claims (12)

  1. 一种终端管理服务器DMS，其特征在于，所述DMS包括：A terminal management server DMS, characterized in that the DMS comprises:
    接收单元，用于接收目标节点发送的所述目标节点所在终端的标识；a receiving unit, configured to receive an identifier of a terminal where the target node is sent by the target node;
    发送单元，用于向底层网络实体发送的目标节点所在终端的标识，以使得所述底层网络实体依据所述目标节点所在终端的标识，获得所述目标节点的机器通信外部标识M2M-Ext-ID；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 ;
    所述接收单元，还用于接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID；The receiving unit is further configured to receive an M2M-Ext-ID of the target node sent by the underlying network entity;
    所述发送单元，还用于向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系，所述对应关系用于所述目标节点向基础节点发起注册时发送给所述基础节点。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.
  2. 一种基础节点，其特征在于，所述基础节点包括：A basic node, wherein the basic node comprises:
    发送单元，用于向底层网络实体发送终端标识和业务信息，以使得所述底层网络实体依据所述终端标识和所述业务信息，获得目标节点的机器通信外部标识M2M-Ext-ID；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;
    接收单元，用于从所述底层网络实体获得所述目标节点的M2M-Ext-ID；a receiving unit, configured to obtain an M2M-Ext-ID of the target node from the underlying network entity;
    所述发送单元，还用于向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系；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.
  3. 根据权利要求2所述的基础节点，其特征在于，所述接收单元，具体用于：The base node according to claim 2, wherein the receiving unit is specifically configured to:
    接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID；或者，Receiving an M2M-Ext-ID of the target node sent by the underlying network entity; or
    从机器通信M2M业务提供设备接收所述目标节点的M2M-Ext-ID；所述M2M-Ext-ID为所述M2M业务提供设备从所述底层网络实体获得的。Receiving, by the machine communication M2M service providing device, an M2M-Ext-ID of the target node; the M2M-Ext-ID being obtained by the M2M service providing device from the underlying network entity.
  4. 根据权利要求2所述的基础节点，其特征在于，The base node of claim 2, wherein
    所述业务信息包括以下信息中至少一个：M2M业务提供设备的标识、基础节点的标识、应用类型、业务类型和位置中至少一个信息。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.
  5. 根据权利要求2所述的基础节点，其特征在于，The base node of claim 2, wherein
    所述发送单元，具体用于：存储所述M2M-Ext-ID，以及向所述目标节点发送所述M2M-Ext-ID；或者，在所述接收单元接收到所述目标节点发送的收回指令后，向所述目标节点发送应答消息，所述应答消息携带所述M2M-Ext-ID。The sending unit is specifically configured to: store the M2M-Ext-ID, and send the M2M-Ext-ID to the target node; or receive, at the receiving unit, a retracting instruction sent by the target node Afterwards, a response message is sent to the target node, and the response message carries the M2M-Ext-ID.
  6. 根据权利要求2所述的基础节点，其特征在于，所述基础节点还包括：The base node according to claim 2, wherein the base node further comprises:
    处理单元，用于获得用于存储所述M2M-Ext-ID的资源，所述M2M-Ext-ID的资源为所述目标节点在向所述基础节点发起注册后在所述基础节点创建的。And 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.
  7. 一种标识配置方法，其特征在于，所述方法包括：An identification configuration method, the method comprising:
    终端管理服务器DMS接收目标节点发送的所述目标节点所在终端的标识；Receiving, by the terminal management server, the identifier of the terminal where the target node is sent by the target node;
    所述DMS向底层网络实体发送的目标节点所在终端的标识，以使得所述底层网络实体依据所述目标节点所在终端的标识，获得所述目标节点的机器通信外部标识M2M-Ext-ID；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-ID of the target node according to the identifier of the terminal where the target node is located;
    所述DMS接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID；Receiving, by the DMS, an M2M-Ext-ID of the target node sent by the underlying network entity;
    所述DMS向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系，所述对应关系用于所述目标节点向基础节点发起注册时发送给所述基础节点。Sending, by the DMS, the M2M-Ext-ID to the target node, so that the target node obtains the M2M-Ext- according to the M2M-Ext-ID and a preset public service entity identifier CSE-ID. Correspondence relationship between the 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.
  8. 一种标识配置方法，其特征在于，所述方法包括：An identification configuration method, the method comprising:
    基础节点向底层网络实体发送终端标识和业务信息，以使得所述底层网络实体依据所述终端标识和所述业务信息，获得目标节点的机器通信外部标识M2M-Ext-ID；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;
    所述基础节点从所述底层网络实体获得所述目标节点的M2M-Ext-ID；Obtaining, by the base node, an M2M-Ext-ID of the target node from the underlying network entity;
    所述基础节点向所述目标节点发送所述M2M-Ext-ID，以使得所述目标节点依据所述M2M-Ext-ID和预设的公共服务实体标识CSE-ID，获得所述M2M-Ext-ID与所述CSE-ID的对应关系；Sending, by the base node, the M2M-Ext-ID to the target node, so that the target node obtains the M2M-Ext according to the M2M-Ext-ID and a preset public service entity identifier CSE-ID a correspondence between the ID and the CSE-ID;
    所述基础节点接收所述目标节点向所述基础节点发起注册时发送的所述对应关系。The base node receives the correspondence that is sent when the target node initiates registration with the base node.
  9. 根据权利要求8所述的方法，其特征在于，所述基础节点从所述底层网络实体获得所述目标节点的M2M-Ext-ID，包括：The method according to claim 8, wherein the base node obtains the M2M-Ext-ID of the target node from the underlying network entity, including:
    所述基础节点接收所述底层网络实体发送的所述目标节点的M2M-Ext-ID；或者，Receiving, by the base node, an M2M-Ext-ID of the target node sent by the underlying network entity; or
    所述基础节点从机器通信M2M业务提供设备接收所述目标节点的M2M-Ext-ID；所述M2M-Ext-ID为所述M2M业务提供设备从所述底层网络实体获得的。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.
  10. 根据权利要求8所述的方法，其特征在于，The method of claim 8 wherein:
    所述业务信息包括以下信息中至少一个：M2M业务提供设备的标识、基础节点的标识、应用类型、业务类型和位置中至少一个信息。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.
  11. 根据权利要求8所述的方法，其特征在于，所述基础节点向所述目标节点发送所述M2M-Ext-ID，包括：The method according to claim 8, wherein the base node sends the M2M-Ext-ID to the target node, including:
    所述基础节点存储所述M2M-Ext-ID，以及向所述目标节点发送所述M2M-Ext-ID；或者，The base node stores the M2M-Ext-ID, and sends the M2M-Ext-ID to the target node; or
    所述基础节点在接收到所述目标节点发送的收回指令后，向所述目标节点发送应答消息，所述应答消息携带所述M2M-Ext-ID。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.
  12. 根据权利要求8所述的方法，其特征在于，所述方法还包括：The method of claim 8 further comprising:
    所述基础节点获得用于存储所述M2M-Ext-ID的资源，所述M2M-Ext-ID的资源为所述目标节点在向所述基础节点发起注册后在所述基础节点创建的。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.
PCT/CN2014/085035 2014-08-22 2014-08-22 Identity configuration method, device management server and infrastructure node WO2016026145A1 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201480080213.8A CN106471788B (en) 2014-08-22 2014-08-22 Identity configuration method, terminal management server and base node
PCT/CN2014/085035 WO2016026145A1 (en) 2014-08-22 2014-08-22 Identity configuration method, device management server and infrastructure node

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/085035 WO2016026145A1 (en) 2014-08-22 2014-08-22 Identity configuration method, device management server and infrastructure node

Publications (1)

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

Family

ID=55350130

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/085035 WO2016026145A1 (en) 2014-08-22 2014-08-22 Identity configuration method, device management server and infrastructure node

Country Status (2)

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

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101902681A (en) * 2010-07-21 2010-12-01 中兴通讯股份有限公司 Method for processing M2M (Machine to Machine) platform service and M2M platform
CN101932068A (en) * 2009-06-19 2010-12-29 华为技术有限公司 Method, system and device for realizing machine-to-machine service
US20130227036A1 (en) * 2012-02-23 2013-08-29 Kt Corporation Providing machine-to-machine service
CN103618800A (en) * 2013-12-05 2014-03-05 华为技术有限公司 Method and device for achieving subscription informing

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011025876A1 (en) * 2009-08-27 2011-03-03 Interdigital Patent Holdings, Inc. Method and apparatus for solving limited addressing space in machine-to-machine (m2m) environments
CN102014144A (en) * 2009-09-04 2011-04-13 华为技术有限公司 Method and device for submitting terminal data
CN102148863A (en) * 2011-01-27 2011-08-10 华为技术有限公司 Method and device for delivering M2M (machine to machine) service messages
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 (en) * 2009-06-19 2010-12-29 华为技术有限公司 Method, system and device for realizing machine-to-machine service
CN101902681A (en) * 2010-07-21 2010-12-01 中兴通讯股份有限公司 Method for processing M2M (Machine to Machine) platform service and M2M platform
US20130227036A1 (en) * 2012-02-23 2013-08-29 Kt Corporation Providing machine-to-machine service
CN103618800A (en) * 2013-12-05 2014-03-05 华为技术有限公司 Method and device for achieving subscription informing

Also Published As

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

Similar Documents

Publication Publication Date Title
WO2016024695A1 (en) Method and apparatus for profile download of group devices
WO2016111600A1 (en) Mutual authentication between user equipment and an evolved packet core
WO2012141556A2 (en) Machine-to-machine node erase procedure
WO2014148859A1 (en) Method and user equipment for implementing device to device communications between ues
WO2015157942A1 (en) Device and method for accessing wireless network
WO2013025085A2 (en) Apparatus and method for supporting family cloud in cloud computing system
WO2015016627A1 (en) Method and device for connecting single ap device among multiple ap devices on same network to terminal
WO2018147711A1 (en) APPARATUS AND METHOD FOR ACCESS CONTROL ON eSIM
WO2015137787A1 (en) Method for supporting ue access control
WO2017030399A1 (en) Ue access method and apparatus
WO2016195199A1 (en) Method for processing request through polling channel in wireless communication system and apparatus therefor
WO2015037909A1 (en) Method and apparatus for providing push service in communication system
WO2011155733A2 (en) Communication method between a device and another device
WO2018038412A1 (en) Method and user equipment for connecting by means of plurality of accesses in next generation network
WO2018184302A1 (en) Data transmission method, system, virtual load balancer and readable storage medium
WO2015020488A1 (en) Method and apparatus for obtaining authentication information
WO2015002436A1 (en) Method and apparatus for optimizing data route in mobile communication system
WO2014205778A1 (en) Data transmission method and gateway
WO2015096040A1 (en) Access node, mobile management network element and paging message processing method
WO2015100537A1 (en) Transmission device, user plane node and control plane node, and data transmission method
WO2015053602A1 (en) Method and system for supporting security and information for proximity based service in mobile communication system environment
WO2017003255A1 (en) Network selection method and base station
WO2019194412A1 (en) Network apparatus and control method thereof
WO2022102949A1 (en) Edge setup server, edge enable server, and operation method therefor
WO2015035640A1 (en) Network access method, device and system

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