WO2016070565A1 - M2m节点的删除、注册方法、m2m节点及存储介质 - Google Patents

M2m节点的删除、注册方法、m2m节点及存储介质 Download PDF

Info

Publication number
WO2016070565A1
WO2016070565A1 PCT/CN2015/075907 CN2015075907W WO2016070565A1 WO 2016070565 A1 WO2016070565 A1 WO 2016070565A1 CN 2015075907 W CN2015075907 W CN 2015075907W WO 2016070565 A1 WO2016070565 A1 WO 2016070565A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
entity
resource
identifier
data
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2015/075907
Other languages
English (en)
French (fr)
Inventor
吴昊
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to US15/523,070 priority Critical patent/US10440763B2/en
Priority to EP15856893.1A priority patent/EP3217735B1/en
Publication of WO2016070565A1 publication Critical patent/WO2016070565A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/06—De-registration or detaching
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data

Definitions

  • the present invention relates to a communication technology of a Machine Type Communication (MTC) terminal in the communication field, and in particular, to a method for deleting, registering, M2M node and storage medium of an M2M node.
  • MTC Machine Type Communication
  • FIG. 1 shows an M2M (Machine To Machine) communication system, which comprises a bearer network and an M2M node communicating through a bearer network.
  • the M2M node includes an application node, an intermediate node, and a base node.
  • the M2M nodes communicate with each other through a bearer network, and each of the M2M nodes includes at least one Application Entity (AE) or a Common Service Entity (CSE).
  • AE Application Entity
  • CSE Common Service Entity
  • the application entity AE is a logical unit that performs an actual M2M application
  • the public service entity CSE is a logical unit that manages and services the application.
  • the communication between the M2M applications is performed through the public service entity CSE.
  • the M2M application registers with the CSE, and the CSEs also need to register with each other, and then the M2M application interaction can be realized through the communication between the CSEs.
  • the application node is an end execution node, such as a smart meter, a temperature measurement and control sensor, a fire alarm, a smart home appliance, etc.
  • the intermediate node is a middleware that connects the end execution node to the network side server, such as a gateway, and the base node is a network side server.
  • the application registered to the base node may be the management platform of the M2M service provider.
  • the application entity AE on the application node is registered on the CSE on the intermediate node, then the CSE on the intermediate node is called the local CSE of the AE on the application node or the registration CSE.
  • the CSE on the intermediate node is registered on the CSE on the base node, and the CSE on the base node is called the local CSE of the CSE on the intermediate node or the registered CSE.
  • the embodiments of the present invention are expected to provide a method for deleting, registering, M2M nodes, and storage media of an M2M node, so as to avoid data loss of data stored on the local CSE after the M2M node is deleted.
  • a first aspect of the embodiments of the present invention provides a method for deleting an M2M node.
  • the method includes:
  • Receiving step receiving a node deletion request of the first M2M node
  • the physical resource includes at least one of an application entity AE resource and a public service entity CSE resource.
  • the method further comprises a timing step:
  • the timing step includes:
  • the timer expires when a new node resource address is added to the attribute of the entity resource, otherwise the timer continues until the timer expires.
  • a second aspect of the embodiments of the present invention provides a method for deleting an M2M node.
  • the method includes:
  • the physical resource includes at least one of an application entity AE resource and a public service entity CSE resource.
  • the storing, on the physical resource corresponding to the first M2M node, the data includes:
  • the entity resource is retained to retain data stored on the entity resource.
  • the method further includes:
  • the duration of the association of the entity resource with the node resource is timed to form a storage duration
  • the physical resource is deleted when the storage duration reaches a specified length of time.
  • the storing, on the physical resource corresponding to the first M2M node, the data includes:
  • a third aspect of the embodiments of the present invention provides a method for registering an M2M node, where the method includes:
  • the registration request includes a node identifier; the registration request further includes an entity identifier; the entity identifier includes at least one of an application entity AE identifier and a public service entity CSE identifier;
  • the address of the node resource is stored as an attribute of the entity resource.
  • the query stores an entity resource associated with the entity identifier, including at least one of the following:
  • a fourth aspect of the embodiments of the present invention provides a method for registering an M2M node, where the method includes:
  • the registration request includes a node identifier; the registration request further includes an entity identifier; the entity identifier includes at least one of an application entity AE identifier and a public service entity CSE identifier;
  • the data is stored in a first entity resource corresponding to the entity identifier.
  • the storing the data in the The first entity resource corresponding to the entity identifier includes:
  • the node resource is associated with the second entity resource
  • the second entity resource is the first entity resource that has been registered according to the entity identifier.
  • the storing the data in the first entity resource corresponding to the entity identifier includes:
  • the data is stored into the first entity resource.
  • a fifth aspect of the embodiments of the present invention provides an M2M node, where the M2M node includes:
  • a receiving unit configured to receive a node deletion request of the first M2M node
  • a response unit configured to delete the first M2M node in response to the node deletion request a node resource, which retains an entity resource corresponding to the first M2M node;
  • the physical resource includes at least one of an application entity AE resource and a public service entity CSE resource.
  • the M2M node further includes a timing unit
  • the timing unit is configured to start a timer after the node resource is deleted, and start counting the retention duration; when a new node resource address is added to the attribute of the physical resource, the timer is suspended. Otherwise, the timing is continued; wherein, when the node resource address is added to the new node resource, the timing unit is configured to cause the timer to be aborted, otherwise the timing is continued until the timer expires;
  • the response unit is further configured to delete the physical resource after the timer expires.
  • a sixth aspect of the embodiments of the present invention provides an M2M node, where the M2M node includes:
  • a receiving unit configured to receive a node deletion request of the first M2M node
  • the response unit is configured to: in response to the node deletion request, delete the node resource of the first M2M node, and store data on the entity resource corresponding to the first M2M node;
  • the physical resource includes at least one of an application entity AE resource and a public service entity CSE resource.
  • the response unit is configured to reserve the physical resource to retain data stored on the physical resource.
  • the M2M node further includes:
  • timing unit configured to time the length of time when the entity resource is not associated with the node resource, to form a storage duration
  • the deleting unit is configured to delete the physical resource when the storage duration reaches a specified duration.
  • the response node is configured to extract data on the physical resource and store the data
  • the M2M node further includes a deleting unit that deletes the physical resource.
  • a seventh aspect of the embodiments of the present invention provides an M2M node, where the M2M node includes:
  • a receiving unit configured to receive a registration request of the second M2M node; the registration request includes a node identifier; the registration request further includes an entity identifier; the entity identifier includes at least an application entity AE identifier and a public service entity CSE identifier one of them;
  • An allocating unit configured to allocate a node resource according to the node identifier of the second M2M node
  • the query unit is configured to query, according to the entity identifier, whether there is an entity resource associated with the entity identifier;
  • control unit configured to store the address of the node resource as an attribute of the entity resource when there is an entity resource associated with the entity label.
  • the querying unit is configured to query whether the entity identifier of the AE resource is the same as the AE identifier according to the AE identifier in the registration request, and/or whether the query is based on the CSE identifier in the registration request.
  • the entity identifier of the CSE resource is the same as the CSE identifier.
  • An eighth aspect of the embodiments of the present invention provides an M2M node, where the M2M node includes:
  • a receiving unit configured to receive a registration request of the second M2M node; the registration request includes a node identifier; the registration request further includes an entity identifier; the entity identifier includes at least an application entity AE identifier and a public service entity CSE identifier one of them;
  • An allocating unit configured to allocate a node resource according to the node identifier of the second M2M node
  • a querying unit configured to query, according to the entity identifier, whether data associated with the entity identifier is stored
  • control unit configured to store the data in the first entity resource corresponding to the entity identifier when the data associated with the entity label is stored.
  • control unit is configured to: when the data is stored in the second entity resource, and the entity identifier of the second entity resource is the same as the entity identifier carried in the registration request And associating the node resource with the second entity resource;
  • the second entity resource is the same as the first entity resource.
  • control unit is further configured to control the allocation unit to create a first entity resource according to the entity identifier, and store the data in the first entity resource.
  • the embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores computer executable instructions, and the computer executable instructions are used to perform at least one of the foregoing methods.
  • the M2M node deletion and registration method, the M2M node, and the storage medium delete the node resource of the first M2M node and retain the physical resource or storage of the first M2M node when the first M2M node is deleted.
  • the data of the AE and/or CES of an M2M node so that after the first M2M node is repaired or after the M2M node is replaced, the first M2M node can be found again after maintaining the original AE and CSE unchanged.
  • the previously generated data solves the problem that the M2M node deletion in the prior art will result in data loss on the local CSE corresponding to the entity stored on the M2M node.
  • FIG. 1 is a schematic structural diagram of an M2M communication system
  • FIG. 2 is a schematic flowchart of a method for deleting an M2M according to an embodiment of the present invention
  • FIG. 3 is a second schematic flowchart of a method for deleting an M2M according to an embodiment of the present invention.
  • FIG. 4 is a third schematic flowchart of a method for deleting an M2M according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for registering an M2M according to an embodiment of the present invention
  • FIG. 6 is a second schematic flowchart of a method for registering an M2M according to an embodiment of the present invention.
  • FIG. 7 is a third schematic flowchart of a method for registering an M2M according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of an M2M node according to an embodiment of the present invention.
  • FIG. 9 is a second schematic structural diagram of an M2M node according to an embodiment of the present invention.
  • FIG. 10 is a second schematic structural diagram of an M2M node according to an embodiment of the present invention.
  • the method for deleting an M2M node in the embodiment of the present application can avoid deleting the M2M node by deleting the physical resource of the M2M node that needs to be deleted or storing the data on the M2M node that needs to be deleted when deleting the M2M node.
  • the deletion of the stored data so that when the M2M node is subsequently performed, the replaced M2M node can utilize the data of the previously deleted M2M node, thereby reducing various problems caused by data loss.
  • this embodiment provides a method for deleting an M2M node, where the method includes:
  • Receiving step S110 receiving a node deletion request of the first M2M node
  • the node resource of the first M2M node is deleted, and the entity resource corresponding to the first M2M node is reserved;
  • the physical resource includes at least one of an application entity AE resource and a public service entity CSE resource.
  • the method further includes a timing step:
  • the timing step includes:
  • the timer expires when a new node resource address is added to the attribute of the entity resource, otherwise the timer continues until the timer expires.
  • the timer is a timer that measures the retention time.
  • the timer is used to time the physical resource that is not associated with the node resource, and the specified time duration (for example, the timer expires) is considered to be deleted, so that a large number of physical resources are left unused and used.
  • the expiration time of the timer is the specified duration, and may be preset according to parameters such as different physical resources and importance of data of the AE or CSE.
  • this embodiment provides a method for deleting an M2M node, where the method includes:
  • Step S101 Receive a node deletion request of the first M2M node.
  • Step S102 Responding to the node deletion request, deleting the node resource of the first M2M node, and storing data on the entity resource corresponding to the first M2M node;
  • the physical resource includes at least one of an application entity AE resource and a public service entity CSE resource.
  • the node resource and the entity resource of the M2M node are synchronously deleted, resulting in data loss in the entity resource and loss of data in the entity resource; and when the M2M node registers with the registered CSE again.
  • the registration CSE does not change any data of the entity on the M2M, resulting in the loss of previous data.
  • the monitoring application is run on the camera installed in the A; the camera is the first M2M node, and the monitoring application is the AE; the camera is connected through the bearer network and registered to the B site.
  • a storage server is a registration CSE of the camera.
  • the storage server allocates node resources to the camera, and stores information of the entire node; the storage server further allocates application resources to the monitoring application on the camera; the application resource is used to store monitoring data.
  • the camera has a problem such as a failure, a node replacement phenomenon occurs, and the camera is removed from the installation site for repair, thereby avoiding waste of resources of the storage server.
  • the deletion process of the first M2M node is performed, and the prior art is discovered through observation.
  • the first M2M node is deleted, the node resource and the application resource are deleted, and the monitoring data stored on the application resource is deleted according to the deletion of the application resource, if the camera is repaired. After connecting to its registered node again, the camera will not be able to obtain the previous monitoring data, resulting in the loss of monitoring data.
  • the problem can be avoided.
  • the data stored on the physical resource is convenient to be acquired when the first M2M node is connected to the registered CSE again. The data generated by the AE or CSE operation on the first M2M node or the data submitted to the registered CSE.
  • the entity resource is retained to retain data stored on the entity resource.
  • This method retains the physical resources and does not delete the physical resources. Obviously, the data stored on the physical resources is also saved, and the same can avoid data loss.
  • step S102 includes:
  • the data on the physical resource is copied, compressed, and stored, and the resource utilization of the registered CSE node is increased in response to the deletion request, and the physical resource is also deleted.
  • the data may be directly stored without data compression, and data compression is performed to briefly describe the amount of data, so as to reduce the amount of data stored on the registered CSE.
  • the CSE is usually registered with the AE resource assigned to the AE or assigned to CSE's CSE resources are usually not fully loaded, so even if you do not compress and store data, you can save the resources of registering CSE.
  • the first method is used to save the data formed by the AE or the CSE on the first M2M node, when the first M2M node registers with the registered CSE again, the registered CSE does not need to allocate the physical resource again;
  • the method saves the data formed by the AE or the CSE on the first M2M node, and the registered CSE needs to allocate the entity resource again.
  • the embodiment further improves.
  • the method further includes:
  • Step S103 Timing the duration in which the entity resource is not associated with the node resource, and forming a storage duration
  • Step S104 Delete the physical resource when the storage duration reaches a specified duration.
  • the resource utilization of the registered CSE is not high. Therefore, in this embodiment, an already registered entity resource is not associated with the node resources. The associated duration is counted, and the AE resource or CSE resource is deleted when the specified duration is reached, so as to improve the resource utilization of the registered CSE.
  • the resource of the monitoring application A in the camera remains in the registered CSE for a specified period of time, and the node resource of the new camera is still associated with it, indicating that the entity resource is in an idle state, and there is no duration for the M2M node to use.
  • the specified duration is reached.
  • the physical resource can be deleted.
  • the deleting the physical resource in the embodiment does not remove the part of the resource from the registration CSE, but the physical resource cannot be used again with respect to the first M2M node, and is equivalent to deleting the first M2M.
  • the physical resource. Registering the CSE to delete the entity resource is to use the entity resource for other purposes.
  • the method for deleting an M2M node in this embodiment deletes a node resource.
  • the data on the physical resource is saved or the physical resource is directly saved, so that when the same application entity or public service entity is re-registered to the corresponding registered CSE, the previously formed data can be utilized, thereby avoiding data loss. .
  • a method for registering an M2M node may further include:
  • Step S210 Receive a registration request of the second M2M node; the registration request includes a node identifier; the registration request further includes an entity identifier; and the entity identifier includes at least one of an application entity AE identifier and a public service entity CSE identifier.
  • the registration request includes a node identifier; the registration request further includes an entity identifier; and the entity identifier includes at least one of an application entity AE identifier and a public service entity CSE identifier.
  • Step S220 Create a node resource according to the node identifier of the second M2M node.
  • Step S230 Query whether the entity resource associated with the entity identifier is stored according to the entity identifier; if yes, proceed to step S240:
  • Step S240 Store the address of the node resource as an attribute of the entity resource.
  • the method described in this embodiment is correspondingly set according to the method for deleting the M2M node in the first embodiment of the method. Since the physical resource of the deleted previous M2M node is retained when the M2M node is replaced, the new one is retained.
  • the M2M node uses the same entity as the previous M2M node, so that when the new M2M node registers, only the node resource is created, and the retained entity resource is associated with the node resource; in this embodiment, the entity resource and the physical resource are When a node resource is associated, the address of the node resource is directly stored as an attribute of the entity resource, that is, the attribute of the entity resource is updated; In the embodiment, when the entity resource and the node resource are associated, the mapping relationship between the entity resource and the node resource may be established, or the address of the entity resource may be added to the attribute of the node resource.
  • the step S230 may include at least one of the following:
  • step S220 and the step S230 are not in a certain order, and only the step S220 and the step S230 are required to be before step S240.
  • the method further reserves the entity resource for the second M2M node according to the entity resource.
  • the physical resource is associated with the node resource
  • the mapping table including the entity resource and the node resource may be established by storing the address of the node resource as an attribute of the entity resource.
  • this embodiment provides a method for deleting an M2M node, where the method includes:
  • Step S310 Receive a node deletion request of the first M2M node.
  • Step S320 deleting the node resource of the first M2M node according to the deletion request, extracting specified data stored on the physical resource of the first M2M node, storing the specified data to a specified storage location, and using the specified data Deleting the physical resource after storing to a specified storage location;
  • the physical resource includes at least one of an application entity AE resource and a public service entity CSE resource.
  • the method in this embodiment extracts the specified data on the physical resource, such as monitoring the monitoring video of the M2M node, and stores the information to the specified location; for example, the database of the physical resource data deleted and deleted, etc. Location, this obviously can also avoid the problem of data loss stored on the physical resources after the M2M node is deleted.
  • the storing the specified data to the specified location includes: compressing the specified data; and storing the compressed specified data to the specified location . Storage after compression can save storage resources.
  • this embodiment provides a method for registering an M2M node, where the method includes:
  • Step S201 Receive a registration request of the second M2M node; the registration request includes a node identifier; the registration request further includes an entity identifier; and the entity identifier includes at least one of an application entity AE identifier and a public service entity CSE identifier.
  • the registration request includes a node identifier; the registration request further includes an entity identifier; and the entity identifier includes at least one of an application entity AE identifier and a public service entity CSE identifier.
  • Step S202 Allocating node resources according to the node identifier of the second M2M node
  • Step S203 Query whether the data associated with the entity identifier is stored according to the entity identifier; if yes, proceed to step S203;
  • Step S204 The data is stored in a first entity resource corresponding to the entity identifier.
  • the step of creating an entity resource according to the entity identifier may be directly entered.
  • the AE resource is created according to the AE identifier
  • the CSE resource is created according to the CSE identifier.
  • the registration method of the M2M node in this embodiment adds a query step to the previous M2M node. If an AE or CSE is registered to its corresponding registered CSE again, the historical data of the response may be queried; AE and CSE operate using their historical data. Specifically, if the historical data includes control data for running the AE or the CSE, the user does not need to configure the data again, which improves user satisfaction.
  • the step S204 includes: when the data is stored in the second entity resource, and the entity identifier of the second entity resource is the same as the entity identifier carried in the registration request, the node resource and the first The two entity resources are associated; the second entity resource is the same as the first entity resource.
  • the data corresponding to the entity on the M2M is maintained by deleting the corresponding entity resource, and the registered second entity resource can be directly used as the first entity currently assigned to the AE and/or the CSE.
  • the resource is allocated to the second M2M, and the node resource of the second M2M node and the second entity resource need to be associated with each other, and the data on the AE or CSE that has been registered on the second M2M node can be maintained. And can speed up the second The registration response speed of the M2M node.
  • the second M2M node in this embodiment may be the same M2M node as the first M2M node described in the first embodiment of the method, or may be an M2M node different from the first M2M node.
  • the method for deleting the M2M node and the method for performing the registration method of the M2M node in the embodiment may be a registered CSE, where the registered CSE is a registered public service entity carried on the third M2M node. .
  • the step S204 may further include: creating a first entity resource according to the entity identifier; storing the data into the first entity resource.
  • the method described in this embodiment is applicable to a registration method of an M2M node that deletes an entity resource but saves data in a previous entity resource when performing deletion of an M2M node.
  • the M2M node that receives the M2M registration and deletion may specifically open up a database for storing the data on the corresponding entity resource on the M2M node, so as to facilitate the query and use of the data when re-registering.
  • the embodiment provides an M2M node, where the M2M node includes:
  • the receiving unit 110 is configured to receive a node deletion request of the first M2M node
  • the response unit 120 is configured to: in response to the node deletion request, delete a node resource of the first M2M node, and retain an entity resource corresponding to the first M2M node;
  • the physical resource includes at least one of an application entity AE resource and a public service entity CSE resource.
  • the receiving unit 110 may include a communication interface, which may be a wired communication interface and a wireless communication interface, and the wireless communication interface includes a transmitting antenna; the wired communication connection may be various types of cable interfaces, such as a fiber interface.
  • the specific structure of the response unit 120 may include various types of processors, such as an application processor AP, a digital signal processor DSP, a programmable logic array PLC, a central processing unit CPU. Or a structure such as a microprocessor MCU.
  • the processor is connected to a communication interface in the receiving unit via a bus or the like.
  • the M2M node in this embodiment may be a third M2M node.
  • the physical resource corresponding to the first M2M node is reserved, and the data loss caused by the deletion of the physical resource of the first M2M node may be avoided.
  • the M2M node further includes a timing unit
  • the timing unit is configured to start a timer after the node resource is deleted, and start counting the retention duration; when a new node resource address is added to the attribute of the physical resource, the timer is suspended. Otherwise, the timing is continued; wherein, when the node resource address is added to the new node resource, the timing unit is configured to cause the timer to be aborted, otherwise the timing is continued until the timer expires;
  • the response unit 120 is further configured to delete an entity resource after the timer expires.
  • the timing unit includes at least a timer.
  • the timer may be used for a countdown retention duration, that is, when the timer is started, the retention duration is 15 days, and the specified duration upper limit value; when the reserved entity resource is not associated with the new node resource for one day, the reservation The duration is deducted for one day until the abort time or timer associated with sending the physical resource associated with the new node resource fails.
  • the idle rate of the physical resources on the third M2M node can be reduced by the setting of the timing unit.
  • the embodiment provides an M2M node, where the M2M node can be a third M2M node, and the third M2M node includes:
  • the receiving unit 110 is configured to receive a node deletion request of the first M2M node
  • the response unit 120 is configured to: in response to the node deletion request, delete the node resource of the first M2M node, and store data on the entity resource corresponding to the first M2M node;
  • the physical resource includes at least an application entity AE resource and a public service entity CSE resource one of them.
  • the M2M node in this embodiment is a node including a CSE entity, and the CSE node receives registration and deletion of other M2M nodes, and manages these nodes.
  • the receiving unit may include a communication interface, which may be a wired communication interface and a wireless communication interface, and the wireless communication interface includes a transmitting antenna; the wired communication connection may be various types of cable interfaces, such as a fiber interface.
  • the response unit 120 is configured to reserve the physical resource to retain data stored on the physical resource.
  • the response unit 120 by storing physical resources to store data, there is an advantage of simple implementation, and the response efficiency of re-registration can be improved.
  • the M2M node further includes:
  • the timing unit 130 is configured to time the length of time when the physical resource is not associated with the node resource, to form a storage duration
  • the deleting unit 140 is configured to delete the physical resource when the storage duration reaches a specified duration.
  • the specific structure of the timing unit 130 may include a timer for measuring the storage duration.
  • the specific structures of the deleting unit 140 and the response unit 120 may each be various types of processors.
  • the processor implements the functions of the deletion unit 140 and the response unit 120 by executing predetermined instructions.
  • the deleting unit 140 and the response unit 120 may correspond to the same processor or different processors, and when the deleting unit 140 and the response unit 120 correspond to the same processor, the processor adopts time division multiplexing. Or concurrent threads handle the functionality of different units.
  • the processor may be an electronic component having processing functions such as an application processor AP, a central processing unit CPU, a digital signal processor DSP, a microprocessor MCU, or a programmable logic circuit PLC.
  • the response unit 120 is configured to extract data on the physical resource; and compress and store the data; the M2M node further includes a deleting unit that deletes the physical resource.
  • the M2M node further defines that the M2M node deletes the physical resource when deleting the M2M node. , but you need to store the data on the physical resource before deleting the physical resource.
  • this embodiment further provides an M2M node, where the M2M node includes:
  • the receiving unit 210 is configured to receive a registration request of the second M2M node, where the registration request includes a node identifier, and the registration request further includes an entity identifier, where the entity identifier includes an application entity AE identifier and a public service entity CSE identifier. At least one of them;
  • the allocating unit 220 is configured to allocate a node resource according to the node identifier of the second M2M node;
  • the querying unit 230 is configured to query, according to the entity identifier, whether there is an entity resource associated with the entity identifier;
  • the control unit 240 is configured to store the address of the node resource as an attribute of the entity resource when there is an entity resource associated with the entity label.
  • the M2M node in this embodiment may be a third M2M node.
  • the third M2M node retains the corresponding entity resource on the first M2M node when deleting the first M2M node, and the entity resource may be the second M2M node.
  • the historical resource of the running entity and therefore includes a query unit for querying and a control unit, and storing the node resource address as an attribute of the entity resource.
  • the allocation unit creates an entity resource according to the entity identifier if the entity resource associated with the entity identifier is not queried.
  • the specific structure of the receiving unit 210 refer to the receiving unit 110 in the previous device embodiment, which is not repeated here.
  • the specific structure of the allocation unit 220, the query unit 230, and the control unit 240 may include various types of processors.
  • the processor may be an electronic component having processing functions such as an AP, an MCU, a CPU, a DSP, or a PLC.
  • the querying unit 230 is configured to query whether the entity identifier of the AE resource is the same as the AE identifier according to the AE identifier in the registration request, and/or query whether there is a CSE resource according to the CSE identifier in the registration request.
  • the entity identifier is the same as the CSE identifier.
  • this embodiment provides an M2M node, where the M2M node may be a third M2M node, and the third M2M node includes:
  • the receiving unit 210 is configured to receive a registration request of the second M2M node, where the registration request includes a node identifier, and the registration request further includes an entity identifier, where the entity identifier includes an application entity AE identifier and a public service entity CSE identifier. At least one of them;
  • the allocating unit 220 is configured to allocate a node resource according to the node identifier of the second M2M node;
  • the querying unit 230 is configured to query, according to the entity identifier, whether data associated with the entity identifier is stored;
  • the control unit 240 is configured to store the data in the first entity resource corresponding to the entity identifier when the data associated with the entity label is stored.
  • the same M2M node in this embodiment is also a node that includes a registered CSE entity.
  • the M2M node in this embodiment includes a query unit when performing other M2M node registration, and the current registration number can be obtained through the query unit. Whether the application entity on the second M2M node has previously registered and formed data to facilitate the use of historical data.
  • the receiving unit 210 For the specific structure of the receiving unit 210, refer to the receiving unit 110 in the previous device embodiment, which is not repeated here.
  • the specific structure of the allocation unit 220, the query unit 230, and the control unit 240 may include various types of processors.
  • the processor may be an electronic component having processing functions such as an AP, an MCU, a CPU, a DSP, or a PLC.
  • control unit 240 is configured to store the data in the second physical resource.
  • entity identifier of the second entity resource is the same as the entity identifier carried in the registration request
  • the second entity resource is the same as the first entity resource.
  • control unit 240 is further configured to control the allocation unit to create a first entity resource according to the entity identifier, and store the data in the first entity resource.
  • the control unit 240 may determine, according to the location of the current data storage, whether the entity resource needs to be recreated for the AE or CSE requesting registration, and the data is stored on the entity resource.
  • the present embodiment provides an M2M node for implementing the method described in Embodiment 2 of the method, so that when the AE or CSE is deleted and the registration is rewritten, the historical data before the deletion can be obtained, and the subsequent operation is performed. Use to avoid data loss.
  • the embodiment of the present invention further provides a computer storage medium, where the computer storage medium stores computer executable instructions, and the computer executable instructions are used to perform at least one of the foregoing methods, specifically, as shown in FIG. 2 to FIG. 7 At least one of them.
  • the computer storage medium in this embodiment may be a dynamic storage device, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like.
  • the medium of the computer storage medium in the embodiment may be a non-transitory storage medium; conveniently storing the program code stably.
  • Step 1 The AE or CSE sends a resource creation request to its own registered CSE.
  • the request message can include the following:
  • Node ID Set to the ID of this node.
  • Step 2 After receiving the resource creation request, the registration CSE creates a node resource of the node type, and labels the node resource with the node identifier. If the AE identifier of the AE is included in the request message, and the AE is found to be the initial registration by the query, the AE resource is directly allocated to the AE, and the AE resource is used to mark the AE resource; if the request message includes the CSE If the CSE is the initial registration, the CSE resource is directly allocated to the CSE, and the CSE resource is marked with the CSE identifier.
  • Step 3 When the M2M node needs to be replaced, the AE or CSE on the M2M node sends a replacement request to the registration CSE, and the replacement request (the replacement request is one of the foregoing deletion requests) may include:
  • Replacement indication used to indicate that the current node is to be replaced, indicating that a node needs to be deleted and then re-registered;
  • Entity identifier includes at least one of an AE identifier and a CSE identifier
  • Step 4 After the registration CSE receives the deletion request, if the request message includes a replacement indication, the node resource is deleted according to the address of the node resource, but the attribute AE resource and/or the CSE resource are not deleted.
  • Step 5 Register the CSE to save the attributes of the saved node resources to form a replacement request identifier.
  • the entity identifier is included in an attribute of the node resource, and the entity identifier and the replacement request identifier are associated
  • Step 6 The registration CSE receives a registration request sent by the new M2M node, and the registration request includes:
  • the replacement request identifier may be obtained by the new M2M node from the old M2M;
  • Node ID Set to the ID of this node.
  • Step 7 After receiving the resource creation request, the CSE creates a node resource of the "node" type, sets a node identifier of the attribute of the node resource, and sets a node according to the replacement request identifier and the associated information stored in the registration CSE.
  • the AE identifier or CSE identifier in the attribute of the resource implements the purpose of associating the undeleted entity resource with the node resource.
  • the entity resource is associated with the node resource, and may be implemented by adding a corresponding attribute tag to any one of the resources, or by constructing an association table. There are various implementation methods, which are not described in detail herein.

Landscapes

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

Abstract

本发明公开了一种M2M节点的删除、注册方法及M2M节点；所述删除方法包括：接收步骤：接收第一M2M节点的节点删除请求；响应步骤：响应所述节点删除请求，删除所述第一M2M节点的节点资源，保留所述第一M2M节点对应的实体资源；所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。本发明实施例还提供了一种计算机存储介质。

Description

M2M节点的删除、注册方法、M2M节点及存储介质 技术领域
本发明涉及通信领域的机器类型通信(MTC：Machine Type Communication)终端的通信技术，尤其涉及一种M2M节点的删除、注册方法、M2M节点及存储介质。
背景技术
图1所示为M2M(Machine To Machine)通信系统，所述系统包括承载网络和通过承载网通信的M2M节点组成。所述M2M节点包括应用节点、中间节点以及基础节点。所述M2M节点通过承载网络实现互相通信，每一个所述M2M节点至少包含一个应用实体(Application Entity，AE)或者一个公共业务实体(Common Service Entity，CSE)。
应用实体AE是执行实际M2M应用的逻辑单元，公共业务实体CSE是对应用进行管理和服务的逻辑单元。M2M应用之间的通信是通过公共业务实体CSE进行信息交互的，M2M应用通过注册到CSE，CSE之间也需要相互注册，然后才能通过CSE之间的通信实现M2M应用的交互。
应用节点是末端的执行节点，例如智能电表，温度测控传感器，火警报警器，智能家电等等，中间节点是连接末端执行节点到网络侧服务器的中间件，例如网关，基础节点是网络侧的服务器，注册到基础节点上的应用可以是M2M服务商的管理平台。
在图1中，应用节点上的应用实体AE在中间节点上的CSE上注册，那么中间节点上的CSE叫做应用节点上的AE的本地CSE或者注册CSE。同样的，中间节点上的CSE在基础节点上的CSE上注册，基础节点上的CSE叫做中间节点上的CSE的本地CSE或者注册CSE。
在现有技术中发现，当M2M节点上因为故障等原因被删除后，再次注册到其注册CSE上时，该M2M节点上的AE和CSE保存在其注册CSE上的数据都丢失了，导致M2M节点故障维修好后数据的丢失。
发明内容
有鉴于此，本发明实施例期望提供一种M2M节点的删除、注册方法、M2M节点及存储介质，以避免M2M节点删除后存储在其本地CSE上的数据丢失的问题。
本发明实施例的技术方案是这样实现的：
本发明实施例第一方面提供了一种M2M节点的删除方法，
所述方法包括：
接收步骤：接收第一M2M节点的节点删除请求；
响应步骤：响应所述节点删除请求，删除所述第一M2M节点的节点资源，保留所述第一M2M节点对应的实体资源；
所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。
可选地，在所述响应步骤之后，所述方法还包括计时步骤：
所述计时步骤包括：
启动计时器，开始对保留时长进行计时；
当所述实体资源的属性中有添加了新的节点资源地址时，所述计时器计时中止，否则持续计时；
当所述计时器失效后，删除实体资源；
其中，当所述实体资源的属性中有添加了新的节点资源地址时，所述计时器计时中止，否则持续计时直至所述计时器失效。
本发明实施例第二方面提供一种M2M节点的删除方法，
所述方法包括：
接收第一M2M节点的节点删除请求；
响应所述节点删除请求，删除所述第一M2M节点的节点资源，存储所述第一M2M节点对应的实体资源上的数据；
所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。
可选地，所述存储所述第一M2M节点对应的实体资源上的数据，包括：
保留所述实体资源，以保留存储在所述实体资源上的数据。
可选地，所述方法还包括：
对所述实体资源未与节点资源关联的时长进行计时，形成存储时长；
当所述存储时长达到指定时长删除实体资源。
可选地，所述存储所述第一M2M节点对应的实体资源上的数据，包括：
提取所述实体资源上的数据；
存储所述数据；
删除所述实体资源。
本发明实施例第三方面提供一种M2M节点的注册方法，所述方法包括：
接收第二M2M节点的注册请求；所述注册请求中包括节点标识；所述注册请求中还包括实体标识；所述实体标识包括应用实体AE标识和公共业务实体CSE标识的至少其中之一；
依据所述节点标识所述第二M2M节点创建节点资源；
依据所述实体标识查询是否存储有与所述实体标识关联的实体资源；
若是，则将所述节点资源的地址作为实体资源的属性存储。
可选地，所述依据所述实体标识查询是否存储有与所述实体标识关联的实体资源，包括以下至少其中之一：
依据所述注册请求中的AE标识查询是否有AE资源的实体标识与所述 AE标识相同；
依据所述注册请求中的CSE标识查询是否有CSE资源的实体标识与所述CSE标识相同。
本发明实施例第四方面提供一种M2M节点的注册方法，所述方法包括：
接收第二M2M节点的注册请求；所述注册请求中包括节点标识；所述注册请求中还包括实体标识；所述实体标识包括应用实体AE标识和公共业务实体CSE标识的至少其中之一；
依据所述节点标识为所述第二M2M节点分配节点资源；
依据所述实体标识查询是否存储有与所述实体标识关联的数据；
若是，将所述数据存储在与所述实体标识对应的第一实体资源中。
可选地，当所述数据存储在第二实体资源中，且所述第二实体资源的实体标识与所述注册请求中携带的实体标识相同时，所述将所述数据存储在与所述实体标识对应的第一实体资源中，包括：
当所述第二实体资源为依据所述实体标识已注册过的实体资源时，将所述节点资源与所述第二实体资源进行关联；
所述第二实体资源为依据所述实体标识已注册过的所述第一实体资源。
可选地，所述使所述数据存储在与所述实体标识对应的第一实体资源中，包括：
依据所述实体标识创建第一实体资源；
将所述数据存储到所述第一实体资源中。
本发明实施例第五方面提供一种M2M节点，所述M2M节点包括：
接收单元，配置为接收第一M2M节点的节点删除请求；
响应单元，配置为响应所述节点删除请求，删除所述第一M2M节点的 节点资源，保留所述第一M2M节点对应的实体资源；
所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。
可选地，所述M2M节点还包括计时单元；
所述计时单元，配置为在删除所述节点资源后，启动计时器，开始对保留时长进行计时；当所述实体资源的属性中有添加了新的节点资源地址时，所述计时器计时中止，否则持续计时；其中，当所述节点资源地址被添加到了新的节点资源中时，所述计时单元用于使所述计时器计时中止，否则持续计时直至所述计时器失效；
所述响应单元，还配置为且当所述计时器失效后，删除实体资源。
本发明实施例第六方面提供一种M2M节点，所述M2M节点包括：
接收单元，配置为接收第一M2M节点的节点删除请求；
响应单元，配置为响应所述节点删除请求，删除所述第一M2M节点的节点资源，存储所述第一M2M节点对应的实体资源上的数据；
所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。
可选地，所述响应单元，配置为保留所述实体资源，以保留存储在所述实体资源上的数据。
可选地，所述M2M节点还包括：
计时单元，配置为对所述实体资源未与节点资源关联的时长进行计时，形成存储时长；
删除单元，配置为当所述存储时长达到指定时长删除实体资源。
可选地，所述响应节点，配置为提取所述实体资源上的数据及存储所述数据；
所述M2M节点还包括删除所述实体资源的删除单元。
本发明实施例第七方面提供一种M2M节点，所述M2M节点包括：
接收单元，配置为接收第二M2M节点的注册请求；所述注册请求中包括节点标识；所述注册请求中还包括实体标识；所述实体标识包括应用实体AE标识和公共业务实体CSE标识的至少其中之一；
分配单元，配置为依据所述节点标识所述第二M2M节点分配节点资源；
查询单元，配置为依据所述实体标识查询是否有与所述实体标识关联的实体资源；
控制单元，配置为当有与所述实体标注关联的实体资源时，将所述节点资源的地址作为实体资源的属性存储。
可选地，所述查询单元，配置为依据所述注册请求中的AE标识查询是否有AE资源的实体标识与所述AE标识相同；和/或依据所述注册请求中的CSE标识查询是否有CSE资源的实体标识与所述CSE标识相同。
本发明实施例第八方面提供一种M2M节点，所述M2M节点包括：
接收单元，配置为接收第二M2M节点的注册请求；所述注册请求中包括节点标识；所述注册请求中还包括实体标识；所述实体标识包括应用实体AE标识和公共业务实体CSE标识的至少其中之一；
分配单元，配置为依据所述节点标识所述第二M2M节点分配节点资源；
查询单元，配置为依据所述实体标识查询是否存储有与所述实体标识关联的数据；
控制单元，配置为当存储有与所述实体标注关联的数据时，使所述数据存储在与所述实体标识对应的第一实体资源中。
可选地，所述控制单元，配置为当所述数据存储在第二实体资源中，且所述第二实体资源的实体标识与所述注册请求中携带的实体标识相同 时，将所述节点资源与所述第二实体资源进行关联；
所述第二实体资源与所述第一实体资源相同。
可选地，所述控制单元，还配置为控制所述分配单元依据所述实体标识创建第一实体资源；并将所述数据存储到所述第一实体资源中。
本发明实施例还提供一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行上述方法的至少其中之一。
本发明实施例所述的M2M节点的删除、注册方法、M2M节点及存储介质，在进行第一M2M节点删除时，删除第一M2M节点的节点资源，保留第一M2M节点的实体资源或存储第一M2M节点的AE和/或CES的数据，这样方便第一M2M节点维修好后或更换M2M节点后，在保持原有的AE和CSE不变的情况下，可以再次查找到第一M2M节点更换前生成的数据，解决现有技术中M2M节点删除将导致对应M2M节点上实体存储在本地CSE上数据丢失的问题。
附图说明
图1为一种M2M通信系统的结构示意图；
图2为本发明实施例所述的M2M的删除方法的流程示意图之一；
图3为本发明实施例所述的M2M的删除方法的流程示意图之二；
图4为本发明实施例所述的M2M的删除方法的流程示意图之三；
图5为本发明实施例所述的M2M的注册方法的流程示意图之一；
图6为本发明实施例所述的M2M的注册方法的流程示意图之二；
图7为本发明实施例所述的M2M的注册方法的流程示意图之三；
图8为本发明实施例所述的M2M节点的结构示意图之一；
图9为本发明实施例所述的M2M节点的结构示意图之二；
图10为本发明实施例所述的M2M节点的结构示意图之二。
具体实施方式
以下结合说明书附图及具体实施例对本发明的技术方案做进一步的详细阐述；应当理解，以下所说明的优选实施例仅用于说明和解释本发明，并不用于限定本发明。
本申请实施例中所述的M2M节点的删除方法，在删除M2M节点时通过保留需要删除的M2M节点的实体资源或存储需要删除的所述M2M节点上的数据，从而能够避免在删除M2M节点上存储数据的删除，从而后续在进行M2M节点时，被更换后的M2M节点能够利用之前被删除的M2M节点的数据，从而减少了数据丢失导致的各种问题。
方法实施例一：
如图2所示，本实施例提供一种M2M节点的删除方法，所述方法包括：
接收步骤S110：接收第一M2M节点的节点删除请求；
响应步骤S120：响应所述节点删除请求，删除所述第一M2M节点的节点资源，保留所述第一M2M节点对应的实体资源；
所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。
在本实施例中在节点删除时，因为保留了所述实体资源，显然实体资源中的数据能够得以保存，显然不会出现实体资源内存储的数据丢失的问题。
在所述响应步骤之后，所述方法还包括计时步骤：
所述计时步骤包括：
启动计时器，开始对保留时长进行计时；
当所述实体资源的属性中有添加了新的节点资源地址时，所述计时器计时中止，否则持续计时；
当所述计时器失效后，删除实体资源；
其中，当所述实体资源的属性中有添加了新的节点资源地址时，所述计时器计时中止，否则持续计时直至所述计时器失效。
所述计时器为计量保留时长的计时器。
所述计时器用于对未与节点资源关联的实体资源进行计时，达到指定时长(具体如计时器失效)则认为可以删除了该实体资源，避免大量的实体资源处于闲置未使用的状态，以提高实体资源的使用效率。所述计时器的失效时长即为所述指定时长，可以根据不同的实体资源以及AE或CSE的数据的重要性等参数，预先设置。
方法实施例二：
如图3所示，本实施例提供一种M2M节点的删除方法，所述方法包括：
步骤S101：接收第一M2M节点的节点删除请求；
步骤S102：响应所述节点删除请求，删除所述第一M2M节点的节点资源，存储所述第一M2M节点对应的实体资源上的数据；
所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。
在现有技术中M2M节点删除时，将同步删除M2M节点的节点资源和实体资源，导致实体资源中的数据丢失，且对实体资源中的数据丢失；而M2M节点再次注册到其注册CSE上时，该注册CSE中没有改M2M上实体的任何数据，导致之前的数据丢失。
具体如安装在A地的摄像头上运行有监控应用；所述摄像头即为所述第一M2M节点，所述监控应用即为所述AE；所述摄像头通过承载网连接并注册到位于B地的存储服务器；所述存储服务器即为所述摄像头的注册CSE。所述存储服务器上为所述摄像头分配了节点资源，存储了整个节点的信息；所述存储服务器上还为所述摄像头上的监控应用分配了应用资源；所述应用资源用于存储监控数据。
若所述摄像头出现故障等问题时，将发生节点更替现象，摄像头从安装地取下送修，避免存储服务器的资源浪费，通常会进行第一M2M节点的删除过程，通过观测发现在现有技术中，删除所述第一M2M节点时，将通过删除所述节点资源和应用资源，显然存储在所述应用资源上的监控数据就随着应用资源的删除而被删除了，若当摄像头修复好后，再次连接到其注册节点时，该摄像头将无法获得之前的监控数据，从而导致了监控数据的丢失。而采用本实施例中所述的方法，则能避免这种问题，本发明中将存储在所述实体资源上的数据，便于下次第一M2M节点再次连接到其注册CSE上时，能够获取第一M2M节点上AE或CSE运行产生的数据或提交到所述注册CSE的数据。
保存所述数据的方法有多种方式，以下提供两种：
第一种：所述步骤S102包括：
保留所述实体资源，以保留存储在所述实体资源上的数据。
这种方法即保留实体资源，没有删除实体资源，显然存储在所述实体资源上的数据也达到了保存，同样的能够避免数据的丢失。
第二种：所述步骤S102包括：
提取所述实体资源上的数据；
压缩并存储所述数据；
删除所述实体资源。
将实体资源上的数据拷贝、压缩并存储，同时为了响应删除请求提高其注册CSE节点的资源利用率，还将删除所述实体资源。
在具体的实现过程中，也可以直接存储所述数据即可，而不用进行数据压缩，进行数据压缩是为了简述数据量，以便减少注册CSE上存储的数据量。
在具体的实现过程中，通常注册CSE分配给AE的AE资源或分配给 CSE的CSE资源通常都不会处于满负荷状态，故即便不进行压缩进行数据存储，也能达到节省注册CSE部分资源的目的。
若采用第一种方法保存第一M2M节点上AE或CSE形成的数据，则当第一M2M节点再次注册到所述注册CSE时，所述注册CSE无需再次为分配实体资源；而采用第二种方法保存第一M2M节点上AE或CSE形成的数据，则所述注册CSE需再次为分配实体资源。
如图4所示，在所述第二种方法的基础上，本实施例还做了进一步改进，
所述方法还包括：
步骤S103：对所述实体资源未与节点资源关联的时长进行计时，形成存储时长；
步骤S104：当所述存储时长达到指定时长删除实体资源。
为了避免有些第一M2M节点永久删除，若长期为其保存实体资源，会导致注册CSE的资源利用率不高的问题，故在本实施例中还会对一个已经注册的实体资源未与节点资源关联的时长进行计时，达到指定时长就删除该AE资源或CSE资源，以提高注册CSE的资源利用率。
具体如，摄像头中的监控应用A的资源保留在注册CSE中达到指定时长1个月，依旧没有新的摄像头的节点资源与其关联，表示该实体资源依据处于闲置状态，没有M2M节点进行使用的时长已经达到了指定时长，为了提高注册CSE的资源使用效率，可以删除该实体资源。
值得注意的是，本实施例中所述的删除实体资源不是从注册CSE去除掉这部分资源，而是相对于第一M2M节点不能再使用该实体资源，对于第一M2M而言相当于删除了该实体资源。注册CSE删除所述实体资源是将该实体资源用于他用。
综合上述，本实施例所述的M2M节点的删除方法，会在删除节点资源 的同时保存实体资源上的数据或直接保存实体资源，这样能避免后续同样的应用实体或公共业务实体再次注册到对应的注册CSE上时，能够利用到之前已经形成的数据，从而避免数据的丢失。
具体地，如图5所示，本实施例一种M2M节点的注册方法，所述方法还可包括：
步骤S210：接收第二M2M节点的注册请求；所述注册请求中包括节点标识；所述注册请求中还包括实体标识；所述实体标识包括应用实体AE标识和公共业务实体CSE标识的至少其中之一；
步骤S220：依据所述节点标识所述第二M2M节点创建节点资源；
步骤S230：依据所述实体标识查询是否存储有与所述实体标识关联的实体资源；若是则进入步骤S240：
步骤S240：将所述节点资源的地址作为实体资源的属性存储。
本实施例所述的方法是基于方法实施例一中的M2M节点删除的方法而对应设置的，由于在进行M2M节点更替时，被删除的前一个M2M节点的实体资源保留下来了，而新的M2M节点使用了与前一个M2M节点相同的实体，故可以在新的M2M节点注册时，仅创建节点资源，把保留下来的实体资源与节点资源进行关联；在本实施例中在进行实体资源和节点资源关联时，直接将节点资源的地址作为实体资源的属性进行存储，即更新实体资源的属性；这样后续能方便后续使用。在本实施例中在进行实体资源和节点资源关联时，还可以是建立实体资源与节点资源的映射关系表，或将实体资源的地址添加到节点资源的属性中。
所述步骤S230可包括以下至少其中之一：
依据所述注册请求中的AE标识查询是否有AE资源的实体标识与所述AE标识相同；依据所述注册请求中的CSE标识查询是否有CSE资源的实体标识与所述CSE标识相同。
在具体实现时，所述步骤S220和步骤S230没有一定的先后顺序，仅需满足步骤S220和步骤S230均在步骤S240之前即可。
其中，若所述步骤S230中没有查询到与所述实体标识关联的实体资源时，所述方法还保留根据所述实体资源为所述第二M2M节点创建实体资源。
在具体实现时，将所述实体资源与节点资源进行关联，除将所述节点资源的地址作为所述实体资源的属性存储之外，还可以通过建立包括实体资源和节点资源的映射表。
方法实施例三：
如图6所示，本实施例提供一种M2M节点的删除方法，所述方法包括：
步骤S310：接收第一M2M节点的节点删除请求；
步骤S320：依据所述删除请求删除所述第一M2M节点的节点资源、提取第一M2M节点的实体资源上存储的指定数据、将所述指定数据存储到指定存储位置并在将所述指定数据存储到指定存储位置之后删除所述实体资源；
所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。
本实施例所述的方法，在删除实体资源之前，先提取实体资源上的指定数据，具体如监控M2M节点的监控视频等信息，存储到指定位置；具体如备份删除的实体资源数据的数据库等位置，这样显然也可以避免M2M节点删除后实体资源上存储的数据丢失的问题。
进一步地，为了防止待另存为的指定数据的数据量大，所述将所述指定数据存储到指定位置包括：压缩所述指定数据；及将压缩后的所述指定数据存储到所述指定位置。先压缩后存储能够有效节省存储资源。
方法实施例四：
如图7所示，本实施例提供一种M2M节点的注册方法，所述方法包括：
步骤S201：接收第二M2M节点的注册请求；所述注册请求中包括节点标识；所述注册请求中还包括实体标识；所述实体标识包括应用实体AE标识和公共业务实体CSE标识的至少其中之一；
步骤S202：依据所述节点标识所述第二M2M节点分配节点资源；
步骤S203：依据所述实体标识查询是否存储有与所述实体标识关联的数据；若是则进入步骤S203；
步骤S204：使所述数据存储在与所述实体标识对应的第一实体资源中。
在具体的实现过程中，若判断结果为否，则可以直接进入依据所述实体标识创建实体资源的步骤；具体如依据所述AE标识创建AE资源，依据所述CSE标识创建CSE资源等。
本实施例所述的M2M节点的注册方法，相对于之前的M2M节点增加了查询的步骤，若一个AE或CSE再次注册到其对应的注册CSE上，则可能会查询到响应的历史数据；方便AE和CSE使用其历史数据进行操作。具体如所述历史数据包括对AE或CSE运行的控制数据，则用户无需再次对这些数据进行配置了，提高了用户使用满意度。
所述步骤S204包括：当所述数据存储在第二实体资源中，且所述第二实体资源的实体标识与所述注册请求中携带的实体标识相同时，将所述节点资源与所述第二实体资源进行关联；所述第二实体资源与所述第一实体资源相同。
当删除M2M节点时，通过不删除其对应的实体资源的方式保持了M2M上实体对应的数据，则可以直接将已注册过的第二实体资源作为当前分配给AE和/或CSE的第一实体资源分配给第二M2M，无需重新创建，仅需之间关联第二M2M节点的节点资源与所述第二实体资源即可，不仅能够保持第二M2M节点上已注册过AE或CSE上的数据，而且能加快第二 M2M节点的注册响应速度。本实施例所述的第二M2M节点可以是与方法实施例一所述的第一M2M节点是相同的M2M节点，还可以是与所述第一M2M节点不同的M2M节点。
方法实施例一所述的M2M节点的删除方法及本实施例中所述M2M节点的注册方法的执行主体均可以是注册CSE，所述注册CSE是承载在第三M2M节点上的注册公共服务实体。
可选地，所述步骤S204还可以包括：依据所述实体标识创建第一实体资源；将所述数据存储到所述第一实体资源中。本实施例所述的方法适用于在进行M2M节点的删除时，删除了实体资源但是保存了之前实体资源中数据的M2M节点的注册方法。
在具体的实现构成中接收M2M注册和删除的M2M节点，可以专门开辟一个数据库，用于存储已经删除M2M节点上对应的实体资源上的数据，方便再次注册时数据的查询和使用。
设备实施例一：
如图8所示，本实施例提供一种M2M节点，所述M2M节点包括：
接收单元110，配置为接收第一M2M节点的节点删除请求；
响应单元120，配置为响应所述节点删除请求，删除所述第一M2M节点的节点资源，保留所述第一M2M节点对应的实体资源；
所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。
所述接收单元110可包括通信接口，可以是有线通信接口和无线通信接口，所述无线通信接口包括发送天线；所述有线通信接扩可以各种类型的线缆接口，如光纤接口。
所述响应单元120的具体结构可包括各种类型的处理器，具体如应用处理器AP、数字信号处理器DSP、可编程逻辑阵列PLC、中央处理器CPU 或微处理器MCU等结构。所述处理器通过总线等结构与所述接收单元中的通信接口相连。
本实施例所述的M2M节点可为第三M2M节点，在删除第一M2M节点时，保留第一M2M节点对应的实体资源，可以避免第一M2M节点的实体资源被删除导致的数据丢失现象。
所述M2M节点还包括计时单元；
所述计时单元，配置为在删除所述节点资源后，启动计时器，开始对保留时长进行计时；当所述实体资源的属性中有添加了新的节点资源地址时，所述计时器计时中止，否则持续计时；其中，当所述节点资源地址被添加到了新的节点资源中时，所述计时单元用于使所述计时器计时中止，否则持续计时直至所述计时器失效；
所述响应单元120，还配置为且当所述计时器失效后，删除实体资源。
所述计时单元至少包括计时器。所述计时器可用于倒计时保留时长，即当所述计时器启动时，保留时长为15天等指定时长上限值；当被保留的实体资源未与新的节点资源关联一天，则所述保留时长扣除一天，直至发送实体资源与新的节点资源关联的中止时间或计时器失效。
本实施例通过计时单元的设置，能够降低第三M2M节点上实体资源的闲置率。
设备实施例二：
如图8所示，本实施例提供一种M2M节点，所述M2M节点可为第三M2M节点；所述第三M2M节点包括：
接收单元110，配置为接收第一M2M节点的节点删除请求；
响应单元120，配置为响应所述节点删除请求，删除所述第一M2M节点的节点资源，存储所述第一M2M节点对应的实体资源上的数据；
所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少 其中之一。
本实施例所述的M2M节点是包括CSE实体的节点，该CSE节点接收其他M2M节点的注册和删除、对这些节点进行管理。
所述接收单元可包括通信接口，可以是有线通信接口和无线通信接口，所述无线通信接口包括发送天线；所述有线通信接扩可以各种类型的线缆接口，如光纤接口。
可选地，所述响应单元120，用于保留所述实体资源，以保留存储在所述实体资源上的数据。在本实施例中通过保留实体资源来存储数据，具有实现简单的优点，且能提高再注册的响应效率。
如图9所示，所述M2M节点还包括：
计时单元130，配置为对所述实体资源未与节点资源关联的时长进行计时，形成存储时长；
删除单元140，配置为当所述存储时长达到指定时长删除实体资源。
所述计时单元130的具体结构可包括计时器，用于计量所述存储时长。
所述删除单元140和所述响应单元120的具体结构均可以为各种类型的处理器。所述处理器通过执行预定的指令实现所述删除单元140和所述响应单元120的功能。所述删除单元140和所述响应单元120可以对应相同的处理器或不同的处理器，当所述删除单元140和所述响应单元120对应于同一处理器时，所述处理器采用时分复用或并发线程处理不同单元的功能。
所述处理器可以是应用处理器AP、中央处理器CPU、数字信号处理器DSP、微处理器MCU或可编程逻辑电路PLC等具有处理功能的电子元器件。
所述响应单元120，配置为提取所述实体资源上的数据；及压缩并存储所述数据；所述M2M节点还包括删除所述实体资源的删除单元。
所述响应单元120和删除单元的具体结构可以参见本实施例中的上述部分，再次就不再重复了，本实施例中进一步限定了M2M节点在进行M2M节点的删除时，将会删除实体资源，但是删除实体资源之前需要存储好实体资源上的数据。
设备实施例三：
如图10所示，本实施例还提供一种M2M节点，所述M2M节点包括：
接收单元210，配置为接收第二M2M节点的注册请求；所述注册请求中包括节点标识；所述注册请求中还包括实体标识；所述实体标识包括应用实体AE标识和公共业务实体CSE标识的至少其中之一；
分配单元220，配置为依据所述节点标识所述第二M2M节点分配节点资源；
查询单元230，配置为依据所述实体标识查询是否有与所述实体标识关联的实体资源；
控制单元240，配置为当有与所述实体标注关联的实体资源时，将所述节点资源的地址作为实体资源的属性存储。
本实施例所述的M2M节点可以为第三M2M节点，由于第三M2M节点在删除所述第一M2M节点时保留了第一M2M节点上对应的实体资源，该实体资源可能是第二M2M节点上运行的实体的历史资源，故还包括查询单元进行查询以及控制单元，将节点资源地址作为所述实体资源的属性保存。在具体实现时，若没有查询到所述实体标识关联的实体资源时，则由所述分配单元依据所述实体标识创建实体资源。
所述接收单元210的具体结构可以参见上一设备实施例中的接收单元110，在此就不再重复了。所述分配单元220、查询单元230及控制单元240的具体结构可包括各种类型的处理器。所述处理器可以为AP、MCU、CPU、DSP或PLC等具有处理功能的电子元器件。
所述查询单元230，用于依据所述注册请求中的AE标识查询是否有AE资源的实体标识与所述AE标识相同；和/或依据所述注册请求中的CSE标识查询是否有CSE资源的实体标识与所述CSE标识相同。
设备实施例四：
如图10所示，本实施例提供一种M2M节点，所述M2M节点可以为第三M2M节点；所述第三M2M节点包括：
接收单元210，配置为接收第二M2M节点的注册请求；所述注册请求中包括节点标识；所述注册请求中还包括实体标识；所述实体标识包括应用实体AE标识和公共业务实体CSE标识的至少其中之一；
分配单元220，配置为依据所述节点标识所述第二M2M节点分配节点资源；
查询单元230，配置为依据所述实体标识查询是否存储有与所述实体标识关联的数据；
控制单元240，配置为当存储有与所述实体标注关联的数据时，使所述数据存储在与所述实体标识对应的第一实体资源中。
同样的本实施例所述的M2M节点也是包括注册CSE实体的节点，本实施例中的所述的M2M节点在进行其他M2M节点注册时，包括了查询单元，通过查询单元可以获知当前注册的第二M2M节点上的应用实体是否之前注册过及形成过的数据，方便对历史数据的使用。
所述接收单元210的具体结构可以参见上一设备实施例中的接收单元110，在此就不再重复了。
所述分配单元220、查询单元230及控制单元240的具体结构可包括各种类型的处理器。所述处理器可以为AP、MCU、CPU、DSP或PLC等具有处理功能的电子元器件。
一方面所述控制单元240，可配置为当所述数据存储在第二实体资源 中，且所述第二实体资源的实体标识与所述注册请求中携带的实体标识相同时
将所述节点资源与所述第二实体资源进行关联；所述第二实体资源与所述第一实体资源相同。
另一方面所述控制单元240，还配置为控制所述分配单元依据所述实体标识创建第一实体资源；并将所述数据存储到所述第一实体资源中。
所述控制单元240可以根据当前数据存储的位置，确定出是否需要为请求注册的AE或CSE重新创建实体资源，并将数据存储到所述实体资源上。
综合上述，本实施例提供了一种M2M节点用于实现方法实施例二所述的方法，以便于AE或CSE删除后重写注册时，能够获取到删除前的历史数据，并与后续运行的使用，避免数据丢失。
本发明实施例还提供了一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行上述方法的至少其中之一，具体如图2至图7中的至少其中之一。
本实施例所述的计算机存储介质可为动存储设备、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质，在本实施例中所述计算机存储介质可为非瞬间存储介质；方便稳定存储所述程序代码。
以下结合上述实施例提供几个具体示例：
第1步：AE或CSE向自己的注册CSE发送资源创建请求，请求消息中可包含以下内容：
AE或CSE的标识；
资源类型：值设置为“节点”；
节点标识：设置为该节点的标识。
第2步：注册CSE接收到资源创建请求后，创建节点类型的节点资源，并用所述节点标识标注所述节点资源。如果请求消息中包含AE的AE标识，且通过查询发现所述AE为初次注册，则直接为所述AE分配AE资源，并求用所述AE标注所述AE资源；如果请求消息中包含CSE的CSE标识，且所述CSE为初次注册，则直接为所述CSE分配CSE资源，并用所述CSE标识标注所述CSE资源。
第3步：当M2M节点需要更换时，该M2M节点上的AE或CSE向注册CSE发送更替请求，所述更替请求(所述更替请求为上述删除请求的一种)中可包含：
更换指示：用于指示当前节点要被更换，表示有节点需要删除后重新注册；
节点资源的地址；
实体标识；(实体标识至少包括AE标识与CSE标识中的至少一种)
第4步：注册CSE接收到删除请求后，如果请求消息中包含更换指示，则根据节点资源的地址删除节点资源，但不删除属性AE资源和/或CSE资源。
第5步：注册CSE保存保存节点资源的属性，形成更换请求标识。其中，在所述节点资源的属性中包括实体标识；并关联所述实体标识与所述更换请求标识
第6步：注册CSE接收新的M2M节点发送的注册请求，所述注册请求中包括：
所述更换请求标识；该标志可以是新的M2M节点从旧的M2M上获取的；
资源类型：值设置为“节点”；
节点标识：设置为该节点的标识。
第7步：注册CSE接收到资源创建请求后，创建“节点”类型的及节点资源，并设置节点资源的属性的节点标识，并根据所述更换请求标识和注册CSE中存储的关联信息设置节点资源的属性中的AE标识或CSE标识，实现未删除的实体资源与节点资源关联的目的。
实体资源与节点资源关联，可以是在任意一种资源中添加对应的属性标签来实现，也可以通过构建关联表来实现，实现方式有多种，在此就不再详细说明了。
以上所述，仅为本发明的具体实施方式，但本发明的保护范围并不局限于此，凡按照本发明原理所作的修改，都应当理解为落入本发明的保护范围。

Claims (23)

  1. 一种M2M节点的删除方法，所述方法包括：
    接收步骤：接收第一M2M节点的节点删除请求；
    响应步骤：响应所述节点删除请求，删除所述第一M2M节点的节点资源，保留所述第一M2M节点对应的实体资源；
    所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。
  2. 根据权利要求1所述的方法，其中，
    在所述响应步骤之后，所述方法还包括计时步骤：
    所述计时步骤包括：
    启动计时器，开始对保留时长进行计时；
    当所述实体资源的属性中有添加了新的节点资源地址时，所述计时器计时中止，否则持续计时；
    当所述计时器失效后，删除实体资源；
    其中，当所述实体资源的属性中有添加了新的节点资源地址时，所述计时器计时中止，否则持续计时直至所述计时器失效。
  3. 一种M2M节点的删除方法，所述方法包括：
    接收第一M2M节点的节点删除请求；
    响应所述节点删除请求，删除所述第一M2M节点的节点资源，存储所述第一M2M节点对应的实体资源上的数据；
    所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。
  4. 根据权利要求3所述的方法，其中，
    所述存储所述第一M2M节点对应的实体资源上的数据，包括：
    保留所述实体资源，以保留存储在所述实体资源上的数据。
  5. 根据权利要求4所述的方法，其中，
    所述方法还包括：
    对所述实体资源未与节点资源关联的时长进行计时，形成存储时长；
    当所述存储时长达到指定时长删除实体资源。
  6. 根据权利要求3所述的方法，其中，
    所述存储所述第一M2M节点对应的实体资源上的数据，包括：
    提取所述实体资源上的数据；
    存储所述数据；
    删除所述实体资源。
  7. 一种M2M节点的注册方法，所述方法包括：
    接收第二M2M节点的注册请求；所述注册请求中包括节点标识；所述注册请求中还包括实体标识；所述实体标识包括应用实体AE标识和公共业务实体CSE标识的至少其中之一；
    依据所述节点标识所述第二M2M节点创建节点资源；
    依据所述实体标识查询是否存储有与所述实体标识关联的实体资源；
    若是，则将所述节点资源的地址作为实体资源的属性存储。
  8. 根据权利要求7所述的方法，其中，
    所述依据所述实体标识查询是否存储有与所述实体标识关联的实体资源，包括以下至少其中之一：
    依据所述注册请求中的AE标识查询是否有AE资源的实体标识与所述AE标识相同；
    依据所述注册请求中的CSE标识查询是否有CSE资源的实体标识与所述CSE标识相同。
  9. 一种M2M节点的注册方法，所述方法包括：
    接收第二M2M节点的注册请求；所述注册请求中包括节点标识；所述注册请求中还包括实体标识；所述实体标识包括应用实体AE标识和公共业务实体CSE标识的至少其中之一；
    依据所述节点标识为所述第二M2M节点分配节点资源；
    依据所述实体标识查询是否存储有与所述实体标识关联的数据；
    若是，将所述数据存储在与所述实体标识对应的第一实体资源中。
  10. 根据权利要求9所述的方法，其中，
    当所述数据存储在第二实体资源中，且所述第二实体资源的实体标识与所述注册请求中携带的实体标识相同时，所述将所述数据存储在与所述实体标识对应的第一实体资源中，包括：
    当所述第二实体资源为依据所述实体标识已注册过的实体资源时，将所述节点资源与所述第二实体资源进行关联；
    所述第二实体资源为依据所述实体标识已注册过的所述第一实体资源。
  11. 根据权利要求9所述的方法，其中，
    所述使所述数据存储在与所述实体标识对应的第一实体资源中，包括：
    依据所述实体标识创建第一实体资源；
    将所述数据存储到所述第一实体资源中。
  12. 一种M2M节点，所述M2M节点包括：
    接收单元，配置为接收第一M2M节点的节点删除请求；
    响应单元，配置为响应所述节点删除请求，删除所述第一M2M节点的节点资源，保留所述第一M2M节点对应的实体资源；
    所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。
  13. 根据权利要求12所述的节点，其中，
    所述M2M节点还包括计时单元；
    所述计时单元，配置为在删除所述节点资源后，启动计时器，开始对保留时长进行计时；当所述实体资源的属性中有添加了新的节点资源地址时，所述计时器计时中止，否则持续计时；其中，当所述节点资源地址被添加到了新的节点资源中时，所述计时单元用于使所述计时器计时中止，否则持续计时直至所述计时器失效；
    所述响应单元，还配置为且当所述计时器失效后，删除实体资源。
  14. 一种M2M节点，所述M2M节点包括：
    接收单元，配置为接收第一M2M节点的节点删除请求；
    响应单元，配置为响应所述节点删除请求，删除所述第一M2M节点的节点资源，存储所述第一M2M节点对应的实体资源上的数据；
    所述实体资源包括应用实体AE资源和公共业务实体CSE资源的至少其中之一。
  15. 根据权利要求14所述的M2M节点，其中，
    所述响应单元，配置为保留所述实体资源，以保留存储在所述实体资源上的数据。
  16. 根据权利要求15所述的M2M节点，其中，
    所述M2M节点还包括：
    计时单元，配置为对所述实体资源未与节点资源关联的时长进行计时，形成存储时长；
    删除单元，配置为当所述存储时长达到指定时长删除实体资源。
  17. 根据权利要求14所述的M2M，其中，
    所述响应节点，配置为提取所述实体资源上的数据及存储所述数据；
    所述M2M节点还包括删除所述实体资源的删除单元。
  18. 一种M2M节点，所述M2M节点包括：
    接收单元，配置为接收第二M2M节点的注册请求；所述注册请求中包括节点标识；所述注册请求中还包括实体标识；所述实体标识包括应用实体AE标识和公共业务实体CSE标识的至少其中之一；
    分配单元，配置为依据所述节点标识所述第二M2M节点分配节点资源；
    查询单元，配置为依据所述实体标识查询是否有与所述实体标识关联的实体资源；
    控制单元，配置为当有与所述实体标注关联的实体资源时，将所述节点资源的地址作为实体资源的属性存储。
  19. 根据权利要求18所述的M2M节点，其中，
    所述查询单元，配置为依据所述注册请求中的AE标识查询是否有AE资源的实体标识与所述AE标识相同；和/或依据所述注册请求中的CSE标识查询是否有CSE资源的实体标识与所述CSE标识相同。
  20. 一种M2M节点，所述M2M节点包括：
    接收单元，配置为接收第二M2M节点的注册请求；所述注册请求中包括节点标识；所述注册请求中还包括实体标识；所述实体标识包括应用实体AE标识和公共业务实体CSE标识的至少其中之一；
    分配单元，配置为依据所述节点标识所述第二M2M节点分配节点资源；
    查询单元，配置为依据所述实体标识查询是否存储有与所述实体标识关联的数据；
    控制单元，配置为当存储有与所述实体标注关联的数据时，使所述数据存储在与所述实体标识对应的第一实体资源中。
  21. 根据权利要求20所述的M2M节点，其中，
    所述控制单元，配置为当所述数据存储在第二实体资源中，且所述第 二实体资源的实体标识与所述注册请求中携带的实体标识相同时，将所述节点资源与所述第二实体资源进行关联；
    所述第二实体资源与所述第一实体资源相同。
  22. 根据权利要求20所述的M2M，其中，
    所述控制单元，还配置为控制所述分配单元依据所述实体标识创建第一实体资源；并将所述数据存储到所述第一实体资源中。
  23. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1至11所述方法的至少其中之一。
PCT/CN2015/075907 2014-11-04 2015-04-03 M2m节点的删除、注册方法、m2m节点及存储介质 Ceased WO2016070565A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/523,070 US10440763B2 (en) 2014-11-04 2015-04-03 M2M node deletion and registration method, M2M node and storage medium
EP15856893.1A EP3217735B1 (en) 2014-11-04 2015-04-03 M2m node deletion and registration method, m2m node and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410613868.9 2014-11-04
CN201410613868.9A CN105636241B (zh) 2014-11-04 2014-11-04 M2m节点的删除、注册方法及m2m节点

Publications (1)

Publication Number Publication Date
WO2016070565A1 true WO2016070565A1 (zh) 2016-05-12

Family

ID=55908477

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/075907 Ceased WO2016070565A1 (zh) 2014-11-04 2015-04-03 M2m节点的删除、注册方法、m2m节点及存储介质

Country Status (4)

Country Link
US (1) US10440763B2 (zh)
EP (1) EP3217735B1 (zh)
CN (1) CN105636241B (zh)
WO (1) WO2016070565A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3461177A4 (en) * 2016-06-08 2019-03-27 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR SWITCHING ON AN ACCESS POINT

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102069751B1 (ko) * 2015-01-07 2020-01-23 후아웨이 테크놀러지 컴퍼니 리미티드 응답 메시지 처리 방법, 장치 및 시스템
WO2018058625A1 (zh) * 2016-09-30 2018-04-05 华为技术有限公司 一种检测报文反压的方法及装置
CN106506693B (zh) * 2016-12-09 2019-06-18 北京奇虎科技有限公司 从提供云服务的服务器集群中删除服务器的方法和装置
CN109788011B (zh) * 2017-11-13 2021-11-26 京东方科技集团股份有限公司 对资源进行关联的方法、通信终端和通信节点设备
CN110110003A (zh) * 2018-01-26 2019-08-09 广州中国科学院计算机网络信息中心 M2m平台的数据存储控制方法及装置
KR102701581B1 (ko) * 2022-10-13 2024-09-02 한국전자기술연구원 데이터 플랫폼 미가동시에도 손실 없이 데이터를 저장하고 제공하는 방법

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103220670A (zh) * 2012-01-19 2013-07-24 华为技术有限公司 一种设备切换方法、m2m平台和网络系统
CN103796300A (zh) * 2012-10-29 2014-05-14 中兴通讯股份有限公司 机器类型通信系统中终端外设注销方法及装置、网关
WO2014169804A1 (zh) * 2013-11-26 2014-10-23 中兴通讯股份有限公司 公共业务实体注册方法和系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104012013B (zh) * 2011-10-24 2018-01-23 Lg电子株式会社 一种在无线通信系统中发送信号的d2d（设备对设备）设备以及发送信号方法
WO2013190503A1 (en) * 2012-06-22 2013-12-27 Telefonaktiebolaget L M Ericsson (Publ) Method and apparatus for machine-to-machine event data recording
WO2014129802A1 (ko) 2013-02-19 2014-08-28 엘지전자 주식회사 M2m 서비스 설정 변경 방법 및 이를 위한 장치
KR102039908B1 (ko) * 2013-04-01 2019-11-04 삼성전자주식회사 단말간 통신을 위한 상태 천이 방법 및 장치
US10182351B2 (en) * 2013-11-29 2019-01-15 Lg Electronics Inc. Method for service subscription resource-based authentication in wireless communication system
CN104104713B (zh) * 2014-02-24 2018-03-23 中兴通讯股份有限公司 设备触发消息处理方法、承载网网元、m2m节点及系统
KR20160046244A (ko) * 2014-10-20 2016-04-28 한국전자통신연구원 단말간 직접 통신을 위한 단말 정보 관리 방법 및 장치

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103220670A (zh) * 2012-01-19 2013-07-24 华为技术有限公司 一种设备切换方法、m2m平台和网络系统
CN103796300A (zh) * 2012-10-29 2014-05-14 中兴通讯股份有限公司 机器类型通信系统中终端外设注销方法及装置、网关
WO2014169804A1 (zh) * 2013-11-26 2014-10-23 中兴通讯股份有限公司 公共业务实体注册方法和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP3217735A4 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3461177A4 (en) * 2016-06-08 2019-03-27 Huawei Technologies Co., Ltd. METHOD AND DEVICE FOR SWITCHING ON AN ACCESS POINT
US10932171B2 (en) 2016-06-08 2021-02-23 Huawei Technologies Co., Ltd. Access point switching method and apparatus

Also Published As

Publication number Publication date
US20170332426A1 (en) 2017-11-16
CN105636241A (zh) 2016-06-01
EP3217735A1 (en) 2017-09-13
EP3217735A4 (en) 2017-10-04
US10440763B2 (en) 2019-10-08
CN105636241B (zh) 2020-11-17
EP3217735B1 (en) 2018-10-10

Similar Documents

Publication Publication Date Title
CN105636241B (zh) M2m节点的删除、注册方法及m2m节点
CN106850710B (zh) 一种数据云存储系统、客户终端、存储服务器及应用方法
FI3852331T3 (fi) Istunnonkäsittelymenetelmä ja liittyvä laite
CN107562386A (zh) 一种分布式存储集群的数据写入方法及装置
US10834559B2 (en) Information processing method for machine-to-machine/man (M2M) application, common services entity (CSE) and application entity (AE)
CN109788027A (zh) 数据同步方法、装置、服务器及计算机存储介质
US20180242177A1 (en) Monitoring management method and apparatus
CN105208654B (zh) 一种通知消息发送方法及装置
CN103237075A (zh) 一种数据同步方法、装置及系统
CN107770754A (zh) 一种通知发送方法、装置和系统
CN105282118A (zh) 控制资源变更通知消息发送方法及装置
CN106230938A (zh) 一种客户端与服务器之间的目录信息同步方法及系统
CN105611484A (zh) 一种m2m节点的管理方法和装置
CN105491507B (zh) 一种m2m中管理应用资源的方法和注册节点
EP3197207A1 (en) Method for managing application resources and registered node in m2m
WO2015184850A1 (zh) 过期数据采集方法、装置及系统
CN105656768B (zh) 一种提高Alljoyn网关的资源利用率的方法和Alljoyn网关
CN106569741A (zh) 磁盘空间扩容方法及装置
US10085175B2 (en) Load control method and apparatus for notification messages
CN103118115A (zh) 面向云计算用户的虚拟机管理方法及装置
EP3174322A1 (en) Method for deleting notification resource, and common service entity
CN107634963B (zh) 一种现场监控单元注册系统及方法
CN104869532B (zh) 一种群组成员管理方法和装置
CN104869531A (zh) 一种群组成员更新方法和装置
CN104219258A (zh) 号码归属地的实时查询方法、终端、服务器及系统

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

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15523070

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

REEP Request for entry into the european phase

Ref document number: 2015856893

Country of ref document: EP