WO2015123893A1 - Procédé et dispositif de commutation de dispositif - Google Patents

Procédé et dispositif de commutation de dispositif Download PDF

Info

Publication number
WO2015123893A1
WO2015123893A1 PCT/CN2014/072475 CN2014072475W WO2015123893A1 WO 2015123893 A1 WO2015123893 A1 WO 2015123893A1 CN 2014072475 W CN2014072475 W CN 2014072475W WO 2015123893 A1 WO2015123893 A1 WO 2015123893A1
Authority
WO
WIPO (PCT)
Prior art keywords
node
information
replacement
target
notification
Prior art date
Application number
PCT/CN2014/072475
Other languages
English (en)
Chinese (zh)
Inventor
陶源
于琦
Original Assignee
华为技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 华为技术有限公司 filed Critical 华为技术有限公司
Priority to PCT/CN2014/072475 priority Critical patent/WO2015123893A1/fr
Priority to CN201480041406.2A priority patent/CN105409304B/zh
Publication of WO2015123893A1 publication Critical patent/WO2015123893A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • 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
    • H04W84/00—Network topologies
    • H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
    • H04W84/04—Large scale networks; Deep hierarchical networks

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a method and device for device switching. Background technique
  • Machine-to-Machine (M2M) communication (Communication) is a networked application and service centered on intelligent interaction between machines and machines. It embeds wireless or wired communication inside the machine. Modules and application processing logic enable data communication without manual intervention to meet the information needs of users in monitoring, command scheduling, data collection and measurement.
  • the overall goal of M2M communication is to create open standards for the business layer of M2M communication to facilitate the establishment of a future network that integrates various devices and services, enabling M2M services to be interoperable, and enabling M2M applications to share basic services and be independent of Network implementation.
  • M2M systems can be used in a variety of industries, primarily in the healthcare, transportation, energy, security and surveillance, home automation and control industries.
  • equipment deployments for smart metering systems in the energy industry can be applied, and these smart metering devices (such as electricity meters, gas meters, water meters) can be connected to the data center through a gateway.
  • FIG. 1 is a basic architecture diagram of an M2M device.
  • the M2M device specifically includes: Application Entity (AE), Common Services Entity (CSE), and Underlying Network Service Entity (NSE). .
  • AE Application Entity
  • CSE Common Services Entity
  • NSE Underlying Network Service Entity
  • communication between the AE and the CSE through the Mca reference point communication between the CSE and the CSE through the Mcc reference point
  • the specific communication method may be based on a wired method or a wireless method, and the wireless method specifically includes a cellular network and a short distance, and the 3GPP cellular network is a widely used wireless method.
  • Figure 2 is a deployment scenario supported by the M2M system, which includes an Application Dedicated Node and an Application Service Node.
  • the four functional entities the Middle Node and the Infrastructure Node.
  • a node may be a functional entity containing one or more AEs, or a functional entity containing one CSE and any number of AEs (including 0).
  • the application node may only include a functional entity of the AE, which is called an application-specific node; in the example 3 and the example 4, the application node may also include a functional entity of the AE and the CSE, which is called an application. Service node.
  • the application dedicated node and the application month service node can communicate with the infrastructure node through the intermediate node; as in example 1 and instance 4: the application dedicated node and the application service node are also It is possible to communicate directly with the infrastructure node without going through an intermediate node.
  • the application-specific node and the application service node can be used as user devices, the intermediate node can be used as a gateway device, and the infrastructure node can be used as a server.
  • the signaling process for replacement of equipment in the M2M system provided by the European Telecommunication Standardization Institute (ETSI) in the case of repair or failure is shown in Figure 3, when the old equipment ( Issuerl ) is confirmed with the target SCL.
  • the administrator manually initiates a registration process for the new device to the target SCL, and then the new device ( Issuer2 ) sends a registration request to the target SCL according to the setting to complete the replacement of the old and new devices. That is to say, in the existing M2M system, the replacement mechanism of the device is a manual replacement mechanism, and the selection of the new device cannot be completed by itself, thereby failing to ensure the continuity of the communication of the M2M system.
  • the invention provides a method and a device for device switching, so as to realize a self-selection of a replaceable device in a machine-to-machine system, complete device replacement, and thereby ensure continuity of communication of the M2M system.
  • a target node in a machine-to-machine system including:
  • a storage module configured to store device information of each registered node
  • a selecting module configured to determine, when the first node that communicates with the target node needs to be replaced, determining, according to the stored device information of the registered nodes, the second node that replaces the first node;
  • a sending module configured to send, to the first node, replacement notification information that carries the identifier information of the second node, or send, to the second node, notification replacement information that carries the identifier information of the first node;
  • a receiving module configured to receive the replaced notification information sent by the second node or the first node
  • an update module configured to update the stored device information of the first node and the second node according to the replaced notification information.
  • the receiving module is further configured to receive a request replacement information that is sent by the first node according to a state of the first node; or, the target node further includes: a monitoring module And for monitoring a state of the first node;
  • the selecting module is specifically configured to determine, according to the request replacement information or the monitoring result of the monitoring module, that the first node that communicates with the target node needs to be replaced.
  • the selecting module is further configured to: after the target node sends the notification replacement information to the second node, if the receiving time is not received within the set time Deleting the replaced notification information sent by the second node, and then re-determining the second node replacing the first node;
  • the sending module is further configured to send the notification replacement information to the re-determined second node; or, the sending module is further configured to: after the target node sends the notification replacement information to the second node, if If the replaced notification information sent by the second node is not received within a predetermined time, the unreplaceable notification information is sent to the first node.
  • the storage module is specifically configured to store state information of whether each node is online, service information that each node can provide, location information of each node, and registration of each node. information.
  • the sending, by the sending module, the notification replacement information further includes: requesting the second node to target the target The service information provided by the node in the system.
  • the first node and the second node are An application service node or an application specific node, where the target node is an intermediate node or an infrastructure node; or
  • a first node in a machine-to-machine system comprising:
  • a receiving module configured to replace, by the target node in the machine M2M system, replacement notification information sent when the first node that communicates with the target node needs to be replaced, where the replacement notification information includes replacing the first node Identification information of the second node;
  • a sending module configured to send, to the second node, replacement information including the identifier information of the target node according to the replacement notification information
  • a network management module configured to disconnect communication with the target node after receiving the replacement information that is replied by the second node according to the replacement information.
  • the sending module is further configured to send request replacement information to the target node when confirming that the user needs to be replaced.
  • the sending module is further configured to: after sending the replacement information to the second node, if the second node is not received within the set time Accepting the replacement information, sending replacement failure information to the target node.
  • the replacement information that is sent by the sending module further includes: requesting the service information in the M2M system that is provided by the second node to the target node.
  • the sending module is further configured to: after receiving the replacement information that is replied by the second node, send the data information to the second node.
  • the first node and the second node are An application service node or an application specific node, where the target node is an intermediate node or an infrastructure node; or
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node.
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node;
  • the replacement information used by the sending module to be sent further includes: identifier information of the device registered at the first node.
  • a second node in a machine-to-machine system including:
  • a receiving module configured to be used by the receiver in the machine-to-machine M2M system to notify the replacement information that is sent when the first node that communicates with the target node needs to be replaced, where the notification replacement information includes the first node
  • the determining module is configured to: determine, according to the notification replacement information, whether the first node can be replaced, and the sending module, configured to determine, according to the notification replacement information, After replacing the first node, sending, to the first node, permission replacement information that carries the identifier information of the target node; after receiving the acknowledgement information replied by the first node, sending the replaced information to the target node Notification information.
  • the receiving module is further configured to receive data information sent by the first node.
  • the request replacement information received by the receiving module further includes: requesting, by the second node, the service information in the M2M system provided by the target node.
  • the first possible implementation manner of the third aspect, or the second possible implementation manner of the third aspect, in a third possible implementation manner, the first node and the second node are An application service node or an application specific node, where the target node is an intermediate node or an infrastructure node; or
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node.
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node;
  • the confirmation information received by the receiving module further includes: identifier information of the device registered at the first node;
  • the sending module is further configured to send update information to the device registered at the first node, where the update information includes an identifier of the second node and an identifier of the first node.
  • a first node in a machine-to-machine system including:
  • a storage module configured to store device information of each node registered in the target node
  • a selection module configured to determine, according to the stored device information of each node registered in the target node, when confirming that it needs to be replaced The second node of itself;
  • a sending module configured to send request replacement information to the second node, where the request replacement information includes identifier information of the target node;
  • a receiving module configured to receive the replacement information sent by the second node according to the request replacement information
  • a network management module configured to disconnect communication with the target node after receiving the replacement information sent by the second node according to the request replacement information.
  • the sending module is further configured to: after receiving the acceptance replacement information sent by the second node, send the data information to the second node.
  • the selecting module is further configured to: after the first node sends the request replacement information to the second node, if not received within the set time Receiving the replacement information sent by the second node, and then determining to replace the second node of the first node;
  • the sending module is further configured to send request replacement information to the re-determined second node.
  • the storage module is specifically configured to store state information of whether each node is online, service information that each node can provide, location information of each node, and registration of each node. information.
  • the request replacement information sent by the sending module further includes: requesting the second node to the target node Service information provided in the M2M system.
  • the first possible implementation manner of the fourth aspect, the second possible implementation manner of the fourth aspect, the third possible implementation manner of the fourth aspect, and the fourth possible are application service nodes or application dedicated nodes, and the target node is an intermediate node or an infrastructure node; or, the first node And the second node is an intermediate node, and the target node is an infrastructure node.
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node;
  • the request replacement information sent by the sending module further includes: identifier information of the device registered at the first node.
  • a second node in a machine-to-machine system including:
  • a receiving module configured to be used by the first node in the receiver-to-machine M2M system to confirm that the user needs to be replaced, and the request replacement information includes the identification information of the target node that communicates with the first node;
  • a determining module configured to determine, according to the request replacement information, whether the communication with the target node is possible
  • a sending module configured to send the acceptance replacement information to the first node, and send the replaced notification information to the target node, after determining that the information may be communicated with the target node according to the request replacement information.
  • the receiving module is further configured to: after receiving the replacement information to the first node, receive the data information sent by the first node.
  • the request replacement information received by the receiving module further includes: requesting, by the second node, the service information in the M2M system provided by the target node.
  • the first node and the second node are An application service node or an application specific node, where the target node is an intermediate node or an infrastructure node; or,
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node.
  • a third possible implementation manner of the fifth aspect in a fourth possible implementation manner, the first node and the second node are intermediate nodes, and the target node is an infrastructure node;
  • the request replacement information received by the receiving module further includes: identifier information of the device registered at the first node;
  • the sending module is further configured to send update information to the device registered at the first node, where the update information includes an identifier of the second node and an identifier of the first node.
  • a method for device switching comprising:
  • the target node in the machine-to-machine M2M system confirms that the first node communicating with the target node needs to be replaced, determining, according to the stored device information of each registered node, the second node replacing the first node;
  • the target node sends the replacement notification information that carries the identifier information of the second node to the first node, or sends the notification replacement information that carries the identifier information of the first node to the second node;
  • the target node receives the replaced notification information sent by the second node or the first node, and updates the stored device information of the first node and the second node according to the replaced notification information.
  • the target node in the machine-to-machine M2M system confirms that the first node that communicates with the target node needs to be replaced, and specifically includes:
  • the target node receives the request replacement information sent by the first node according to its own state, and confirms that the first node needs to be replaced according to the request replacement information;
  • the target node monitors a state of the first node, and determines, according to a state of the first node, that the first node needs to be replaced.
  • the method further includes:
  • the target node After the target node sends the notification replacement information to the second node, if the replaced notification information sent by the second node is not received within the set time, sending to the first node The notification information cannot be replaced, or the second node replacing the first node is re-determined according to the stored device information of each registered node, and the notification replacement information is sent to the re-determined second node.
  • the device information of each node includes: status information of whether each node is online, service information that each node can provide, location information of each node, and registration information of each node.
  • the notification replacement information further includes: requesting, by the second node, the service information in the M2M system provided by the target node.
  • the first node and the second node are application service nodes or application dedicated nodes
  • the target node is an intermediate node or an infrastructure node
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node.
  • a method for device switching is provided, the method comprising:
  • the first node in the machine-to-machine M2M system receives replacement notification information sent by the target node when it is confirmed that the first node communicating with the target node needs to be replaced, and the replacement notification information includes a replacement of the first node Identification information of the two nodes;
  • the first node sends replacement information to the second node according to the replacement notification information, where the replacement information includes identification information of the target node;
  • the first node disconnects communication with the target node after receiving the acceptance replacement information replied by the second node according to the replacement information.
  • the first node before the first node receives the replacement notification information that is sent when the first node that needs to communicate with the target node needs to be replaced, the first node further includes:
  • the first node sends a request replacement message to the target node when it confirms that it needs to be replaced.
  • the method further includes: After the first node sends the replacement information to the second node, if the replacement information sent by the second node is not received within the set time, the replacement failure information is sent to the target node.
  • the first node, in the replacement information sent to the second node further includes: requiring the second node to provide the target node
  • the method further includes: sending, by the first node, the second node Data information.
  • the first implementation manner of the seventh aspect, the second implementation manner of the seventh aspect, the third implementation manner of the seventh aspect, or the fourth implementation manner of the seventh aspect In an implementation manner, the first node and the second node are application service nodes or application dedicated nodes, and the target node is an intermediate node or an infrastructure node; or
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node.
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node;
  • the replacement information sent by the first node to the second node further includes: identifier information of the device registered at the first node.
  • a method for device switching comprising:
  • the second node in the machine-to-machine M2M system receives notification replacement information that is sent when the first node that needs to communicate with the target node needs to be replaced, and the notification replacement information includes the identification information of the first node. ;
  • the second node After the second node determines that the first node can be replaced according to the notification replacement information, the second node sends the permission replacement information that carries the identifier information of the target node to the first node;
  • the second node After receiving the confirmation information replied by the first node, the second node sends the replaced notification information to the target node.
  • the second node is in the foregoing After the node sends the permission replacement information, the method further includes: receiving data information sent by the first node.
  • the request replacement information received by the second node further includes: requesting, by the second node, the service information in the M2M system provided by the target node.
  • the first node and the second node are An application service node or an application specific node, where the target node is an intermediate node or an infrastructure node; or
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node.
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node;
  • the confirmation information received by the second node further includes: identifier information of the device registered at the first node;
  • the method further includes: sending, by the second node, update information to a device registered at the first node, where the update information includes the second node And an identifier of the first node.
  • a method for device switching comprising:
  • the first node in the machine-to-machine M2M system confirms that it needs to be replaced, it determines to replace the second node of the first node according to the stored device information of each node registered in the target node;
  • the first node sends request replacement information to the second node, where the request replacement information includes identification information of the target node;
  • the first node disconnects communication with the target node after receiving the acceptance replacement information sent by the second node according to the request replacement information.
  • the first node after receiving the receiving replacement information sent by the second node, the first node further includes: sending a data message to the second node Interest.
  • the method further includes:
  • the second replacement of the first node is re-determined. a node, and sends a request replacement information to the re-determined second node.
  • the device information of each node includes: status information of whether each node is online, service information that each node can provide, location information of each node, and registration of each node information.
  • the request replacement information sent by the first node to the second node further includes: an M2M system that is required to be provided by the second node to the target node Service information in .
  • the first possible implementation manner of the ninth aspect, the second possible implementation manner of the ninth aspect, the third possible implementation manner of the ninth aspect, or the fourth possible aspect of the ninth aspect In a fifth possible implementation, the first node and the second node are application service nodes or application dedicated nodes, and the target node is an intermediate node or an infrastructure node; or
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node.
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node;
  • the request replacement information sent by the first node to the second node further includes: identifier information of the device registered at the first node.
  • a method for device switching comprising:
  • the second node in the machine-to-machine M2M system receives the request replacement information sent by the first node when confirming that it needs to be replaced, and the request replacement information includes the identification information of the target node that communicates with the first node;
  • the second node after the sending, by the second node, the replacement information to the first node, the second node further includes: receiving data information sent by the first node.
  • the method further includes: the request replacement information received by the second node further includes: requesting, by the second node, the service in the M2M system provided by the target node information.
  • the first node and the second node are An application service node or an application specific node, where the target node is an intermediate node or an infrastructure node; or
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node.
  • the first node and the second node are intermediate nodes, and the target node is an infrastructure node;
  • the request replacement information received by the second node further includes: identifier information of the device registered at the first node;
  • the method further includes: sending, by the second node, update information to a device registered at the first node, where the update information includes the second node And an identifier of the first node.
  • FIG. 2 is a schematic structural diagram of an M2M system deployment in the background art
  • FIG. 4 is a schematic structural diagram of a target node according to Embodiment 1 of the present invention
  • FIG. 5 is a schematic structural diagram of a first node according to Embodiment 1 of the present invention
  • FIG. 6 is a schematic diagram of an embodiment of the present invention.
  • FIG. 7 is a schematic structural diagram of a first node according to Embodiment 2 of the present invention
  • FIG. 8 is a schematic structural diagram of a second node according to Embodiment 2 of the present invention
  • FIG. 9 is a schematic diagram of a device switching method on a target node side according to Embodiment 3 of the present invention;
  • FIG. 10 is a schematic diagram of a device switching method on a first node side according to Embodiment 3 of the present invention.
  • FIG. 11 is a schematic diagram of a device switching method on a second node side according to Embodiment 3 of the present invention.
  • FIG. 12 is a schematic diagram of a device switching method on a first node side according to Embodiment 4 of the present invention.
  • FIG. 13 is a schematic diagram of a device switching method on a second node side according to Embodiment 4 of the present invention.
  • FIG. 14a and FIG. 14b are respectively a signaling interaction diagram of each node in Embodiment 3 according to an embodiment of the present invention.
  • FIG. 15a and FIG. 15b are respectively another signaling interaction diagram of each node in Embodiment 3 according to an embodiment of the present invention. detailed description
  • the embodiment of the present invention provides a device switching.
  • the method and machine-to-machine system equipment can select the replaceable equipment in the machine-to-machine system and complete the equipment replacement to ensure the continuity of communication.
  • the device switching method and device provided by the embodiments of the present invention may be applied to an old node in a machine-to-machine system, which may not be able to provide continuous service due to reasons such as insufficient power, etc., and needs to select an appropriate one.
  • the device replacement mechanism provided by the embodiment of the present invention implements replacement of the pre-smart smart device, which effectively prevents communication interruption caused by unexpected situations of some devices, and ensures continuity of data communication, especially in some special scenarios such as field monitoring. It is especially suitable for nuclear power plant monitoring and other non-human-capable equipment replacement scenarios.
  • the manner of trigger replacement of the device switching mechanism provided by the embodiment of the present invention may be divided into the following two situations:
  • the old node triggers the replacement process when it is unable to continue to communicate with the target node due to reasons such as detecting that its own low battery is about to leave the network and cannot continue to provide the corresponding service.
  • the target node detects that the old node communicating with it has to leave the network and cannot continue to provide the corresponding service due to low power, it needs to be replaced, and the replacement process is triggered.
  • the execution body of the device switching mechanism provided by the embodiment of the present invention may be a target node, that is, when the target node satisfies the condition of trigger replacement, the target node selects a suitable new node to replace the old node to perform device switching.
  • the execution body of the device switching mechanism provided by the embodiment of the present invention may also be an old node, that is, when the old node satisfies the condition of triggering replacement, the old node selects a suitable new node that replaces the old node to perform a device switching mechanism.
  • the old node and the new node may be application service nodes or application specific nodes in the machine-to-machine system, and correspondingly, the target node may be an intermediate node or an infrastructure node; or, the old node and the new node may also be The intermediate node in the machine-to-machine system, correspondingly, the target node may be an infrastructure node.
  • Embodiment 1 In the following description of the embodiments of the present invention, for convenience of explanation, we refer to the old node as the first node, and the new node that can replace the old node as the second node.
  • Embodiment 1 For convenience of explanation, we refer to the old node as the first node, and the new node that can replace the old node as the second node.
  • the execution body of the device switching mechanism is a target node, and the target node in the machine-to-machine system, as shown in FIG. 4, specifically includes:
  • a storage module 401 configured to store device information of each registered node
  • a selection module 402 configured to determine, when the first node that communicates with the target node needs to be replaced, according to The stored device information of each node is determined, and the second node that replaces the first node is determined; the sending module 403 is configured to send the replacement notification information that carries the identifier information of the second node to the first node, or send the information to the second node.
  • the notification replacement information that carries the identifier information of the first node; wherein, if the first node and the second node are application-specific nodes, the identifier information may be an App-ID of the node, if the first node and the second node are application services a node or an intermediate node, the identification information may be an App-ID and/or a CSE-ID of the node;
  • the receiving module 404 is configured to receive the replaced notification information sent by the second node or the first node
  • the update module 405 is configured to update the stored device information of the first node and the second node according to the replaced notification information.
  • the receiving module 404 is further configured to receive the request replacement information sent by the first node according to the state, that is, the old node. And triggering the replacement process; or, the target node, as shown in FIG. 4, further includes: a monitoring module 406, configured to monitor a state of the first node, that is, the target node actively monitors the state of the old node, when the old node meets the replacement condition , the target node triggers the replacement process;
  • the selecting module 402 is specifically configured to determine, according to the request replacement information or the monitoring result of the monitoring module 406, that the first node that communicates with the target node needs to be replaced.
  • the sending module 403 in the target node provided in the first embodiment sends the notification replacement information to the second node
  • the receiving module 404 does not receive the replaced notification information sent by the second node within the set time. , indicating that it is possible that the second node may fail when performing device replacement with the first node, or the second node does not receive the notification replacement information at all.
  • the foregoing target node provided in Embodiment 1 may perform an operation of re-determining the second node replacing the first node, or directly notify the first node that the device replacement is impossible.
  • the selecting module 402 in the target node is further configured to: after the target node sends the notification replacement information to the second node, if the replaced notification information sent by the second node is not received within the set time, the replacement is re-determined. a second node of the first node;
  • the sending module 403 is further configured to send the notification replacement information to the re-determined second node; or, the sending module 403 is further configured to: after the target node sends the notification replacement information to the second node, If the replaced notification information sent by the second node is not received within the set time, the unreplaceable notification information is sent to the first node.
  • the storage module 401 in the foregoing target node provided in the first embodiment is specifically configured to store state information of whether each node is online, service information that each node can provide, location information of each node, and registration information of each node.
  • the selection module 402 selects a suitable second node that can replace the first node according to the above information of each node stored in the storage module 401 when determining that the first node needs to be replaced.
  • the selection module 402 may select a node that is online, registered, and the same as the service provided by the first node as the second node.
  • the second node may also be selected according to other conditions, and no comment is made here.
  • the notification replacement information used by the sending module 403 in the foregoing target node provided by the first embodiment may further include: requesting, by the second node, service information in the M2M system provided by the target node, for example, the service information.
  • the information may be a service that provides a forwarding or sharing function to the target node, so that the second node that receives the notification replacement information determines whether it can replace the first node according to the service information in the M2M system provided by the second node to the target node. Conduct the service.
  • the foregoing target node provided in Embodiment 1 may be an intermediate node or an infrastructure node in actual application, and correspondingly, the first node and the second node should be an application service node or an application dedicated node; or, an embodiment
  • the above-mentioned target node provided may also be an infrastructure node in actual application, and correspondingly, the first node and the second node should be intermediate nodes.
  • the sending module 403 in the target node provided in the first embodiment sends the replacement notification information carrying the identifier information of the second node to the first node
  • the first embodiment further provides a first one in the corresponding machine-to-machine system.
  • the node as shown in Figure 5, specifically includes:
  • the receiving module 501 is configured to be used by the receiver in the machine system to confirm that the first node that needs to communicate with the target node needs to be replaced, and the replacement notification information includes the identifier of the second node that replaces the first node.
  • Information wherein, if the second node is an application-specific node, the identifier information may be an App-ID of the node, and if the second node is an application service node or an intermediate node, the identifier information may be an App-ID of the node and/or Or CSE-ID;
  • the sending module 502 is configured to send, according to the replacement notification information, a label including the target node to the second node. Identifying the replacement information of the information, so that the second node determines whether to replace the first node to communicate with the target node;
  • the network management module 503 is configured to disconnect the communication with the target node after receiving the replacement information that is replied by the second node according to the replacement information, and complete the device replacement.
  • the sending module 502 in the first node provided in the first embodiment is also used to confirm that it needs to be replaced.
  • the target node sends the request replacement information.
  • the first node may send the request replacement information to the target node according to reasons such as detecting that the self-power is low and the network is unable to continue to provide the corresponding service.
  • the sending module 502 is further configured to: after sending the replacement information to the second node, if the first node does not receive the first time within the set time When the replacement information is sent by the two nodes, the replacement failure information is sent to the target node, so that the target node re-determines to replace the second node of the first node or directly sends the unreplaceable notification information to the first node when receiving the replacement failure information. .
  • the replacement information used by the sending module 502 in the foregoing first node provided by the first embodiment may further include: requesting, by the second node, the service information in the M2M system provided by the target node, so that the second node is used. According to the received service information in the M2M system provided by the second node to the target node, it is determined whether the second node can replace the first node for service, and if the second node can send the acceptance replacement information to the first node.
  • the sending module 502 in the first node which is provided in the first embodiment, is further configured to send data information to the second node after receiving the replacement information that is replied by the second node, where the data information may include Information stored in a node that provides historical data for the target node.
  • the first node provided in Embodiment 1 may be an application service node or an application dedicated node in actual application, and correspondingly, the second node should be an application service node or an application dedicated node, and the target node is an intermediate node.
  • the replacement information used by the module 502 to be sent further includes: identifier information of the device registered at the first node, to send a notification to the devices registered in the first node after the second node replaces the first node for communication. Update information for device replacement.
  • the sending module 403 in the target node provided in the first embodiment sends the replacement notification information carrying the identifier information of the first node to the second node
  • the first embodiment further provides a second in the corresponding machine-to-machine system.
  • the node as shown in Figure 6, specifically includes:
  • the receiving module 601 is configured to receive, by the receiver, the notification information that is sent by the target node in the machine system when the first node that is in communication with the target node needs to be replaced, where the notification replacement information includes the identification information of the first node; And receiving the confirmation information of the reply of the first node; wherein, if the first node is an application-specific node, the identifier information may be an App-ID of the node, and if the first node is an application service node or an intermediate node, the identifier information may be App-ID and/or CSE-ID of the node;
  • the determining module 602 is configured to determine, according to the notification replacement information, whether the first node can be replaced, and the sending module 603, configured to: after the first node is replaced according to the notification replacement information, send the permission to carry the identifier information of the target node to the first node. Replacement information; after receiving the confirmation message replied by the first node, sending the replaced notification information to the target node.
  • the receiving module 601 in the foregoing second node provided in the first embodiment is further configured to: after receiving the acknowledgement information sent by the first node, receive the data information sent by the first node, where the data information may include Information stored in a node that provides historical data for the target node.
  • the request replacement information received by the receiving module 601 in the foregoing second node provided in the first embodiment may further include: requesting, by the second node, the service information in the M2M system provided by the target node, so that the second node is configured according to The received service information in the M2M system requested by the second node to the target node determines whether it can replace the first node for service, and if the second node can send the acceptance replacement information to the first node.
  • the foregoing second node provided in Embodiment 1 may be an application service node or an application dedicated node in actual application, and correspondingly, the first node should be an application service node or an application specific.
  • the node, the target node is an intermediate node or an infrastructure node; or, the second node provided in the first embodiment may be an intermediate node in actual application, and correspondingly, the first node should be an intermediate node, and the target node should be an infrastructure. node.
  • the confirmation information received by the module 601 further includes: identifier information of the device registered at the first node;
  • the sending module 602 in the second node is further configured to send update information to the device registered in the first node, where the update information includes the identifier of the second node and An identifier of the first node, wherein the identifier may be a universal resource identifier (URI).
  • URI universal resource identifier
  • Embodiment 2 is a diagrammatic representation of Embodiment 1:
  • the execution entity of the device switching mechanism is the first node, that is, the old node, and the first node in the machine-to-machine system, as shown in FIG. 7, specifically includes:
  • a storage module 701 configured to store device information of each node that has been registered in the target node
  • a selection module 702 configured to: according to the stored device information of each node registered in the target node, when confirming that it needs to be replaced, Determining to replace the second node of itself;
  • the sending module 703 is configured to send the request replacement information to the second node, where the request replacement information includes the identifier information of the target node, where the identifier information of the target node generally refers to the CSE-ID;
  • the receiving module 704 is configured to receive, by the second node, the replacement information sent according to the request replacement information.
  • the network management module 705 is configured to disconnect the communication with the target node after receiving the acceptance replacement information sent by the second node according to the request replacement information.
  • the sending module 703 in the foregoing first node provided in the second embodiment is further configured to: after receiving the accepting replacement information sent by the second node, send the data information to the second node, where the data information may include Information stored in a node that provides historical data for the target node.
  • the sending module 703 in the first node provided in the second embodiment sends the request replacement information to the second node
  • the receiving module 704 does not receive the first time in the set time.
  • the replacement information sent by the two nodes indicates that it is possible that the second node rejects the replacement request, or the second node does not receive the request replacement information at all.
  • the foregoing first node provided in Embodiment 2 may perform an operation of re-determining the second node replacing the first node.
  • the selecting module 702 in the first node is further configured to: after the first node sends the request replacement information to the second node, if the receiving replacement information sent by the second node is not received within the set time, re-determining Replacing the second node of the first node;
  • the sending module 703 is further configured to send the request replacement information to the re-determined second node.
  • the storage module 701 in the foregoing second node provided in the second embodiment is specifically configured to store state information of whether each node is online, service information that each node can provide, location information of each node, and registration of each node. Information, so that the selection module 702 selects a suitable second node that can replace the first node according to the above information of each node stored in the storage module 701 when determining that the first node needs to be replaced.
  • the selection module 702 can select the same node that is registered in the online node and is the same as the service provided by the first node as the second node.
  • the second node can also be selected according to other conditions, which is not mentioned here.
  • the request replacement information used by the sending module 703 in the foregoing first node provided by the second embodiment further includes: requesting, by the second node, service information in the M2M system provided by the target node, to receive the request.
  • the second node replacing the information determines whether it can replace the first node for service according to the service information in the M2M system provided by the second node to the target node.
  • the foregoing first node provided in Embodiment 2 may be an application service node or an application dedicated node in actual application, and correspondingly, the second node should be an application service node or an application dedicated node, and the target node is an intermediate node.
  • the infrastructure node; or, the foregoing first node provided in the second embodiment may be an intermediate node in actual application, and correspondingly, the second node should be an intermediate node, and the target node should be an infrastructure node.
  • the request replacement information sent by the module 703 also needs to include: The identification information of the device of the book, so that after the second node replaces the first node for communication, the device that is registered in the first node is sent update information notifying the device replacement.
  • the execution entity of the device switching mechanism is the first node, that is, the old node.
  • the second embodiment further provides a second node in the corresponding machine-to-machine system. As shown in FIG. 8, the method specifically includes:
  • the receiving module 801 is configured to receive, by the receiver, a request replacement information sent by the first node in the machine system when confirming that the user needs to be replaced, where the request replacement information includes the identifier information of the target node that communicates with the first node;
  • the identification information generally refers to the CSE-ID of the target node;
  • a determining module 802 configured to determine, according to the request replacement information, whether the communication with the target node is possible
  • the sending module 803 is configured to, after determining that the information can be communicated with the target node according to the request replacement information, send the acceptance replacement information to the first node, and send the replaced notification information to the target node, so that the first node receives the replacement information. After leaving the network, the target node updates the locally stored device information after receiving the replaced notification information.
  • the receiving module 801 in the foregoing second node which is provided by the second embodiment, is further configured to: after sending the replacement information to the first node, receive the data information sent by the first node, where the data information may include the first Information such as historical data that the node saves for the target node.
  • the request replacement information received by the receiving module 801 in the foregoing second node provided by the second embodiment further includes: requesting, by the second node, service information in the M2M system provided by the target node, to receive the request replacement information.
  • the second node determines whether it can replace the first node for service according to the service information in the M2M system provided by the second node to the target node.
  • the foregoing second node provided in Embodiment 2 may be an application service node or an application dedicated node in actual application, and correspondingly, the first node should be an application service node or an application dedicated node, and the target node is an intermediate node.
  • the infrastructure node; or, the foregoing second node provided in the second embodiment may be an intermediate node in actual application, and correspondingly, the first node should be an intermediate node, and the target node should be an infrastructure node.
  • the target node is an infrastructure node
  • the device that communicates with the first node is also provided in the machine-to-machine system. Therefore, the request replacement information received by the receiving module 801 in the second node further includes: Identification information;
  • the sending module is further configured to send update information to the device registered at the first node, where the update information includes an identifier of the second node and an identifier of the first node, where the identifier may be a universal resource identifier Symbol (URI).
  • URI universal resource identifier Symbol
  • Embodiment 3 is a diagrammatic representation of Embodiment 3
  • the execution body of the device switching mechanism is a target node.
  • a device switching method based on the target node side in the machine-to-machine system is provided. As shown in FIG. 9, the method specifically includes:
  • the target node in the machine-to-machine system confirms that the first node that communicates with the target node needs to be replaced, determining, according to the stored device information of each registered node, determining to replace the second node of the first node;
  • the device information of each node may include: status information of whether each node is online, service information that each node can provide, location information of each node, and registration information of each node;
  • the target node confirms the trigger replacement mode that the first node needs to be replaced, and may be the first node triggering the replacement process, or the target node triggering the replacement process; specifically, the target node may receive the first node according to itself.
  • the request sent by the status replaces the information, and confirms that the first node needs to be replaced according to the request replacement information; or, the target node monitors the state of the first node, and determines that the first node needs to be replaced according to the state of the first node.
  • the state of the first node refers to a state in which the power is low, the network may not continue to provide the corresponding service, the quality of the service provided cannot meet the requirements, or the fault occurs, and the communication with the target node cannot be continued;
  • the target node sends the replacement notification information that carries the identifier information of the second node to the first node, or sends the notification replacement information that carries the identifier information of the first node to the second node, where the first node and the second node are
  • the identification information may be the App-ID of the node, and if the first node and the second node are application service nodes or intermediate nodes, the identification information may be an App-ID and/or a CSE-ID of the node;
  • the target node may choose to send information to the first node or the second node to indicate that the device replacement confirmation interaction between the first node and the second node is performed, and further, the sent notification replacement information may also be
  • the method includes: requesting, by the second node, the service information in the M2M system provided by the target node, so that the second node that receives the notification replacement information determines whether the second node can provide the service information in the M2M system provided by the
  • the target node sends the notification replacement information to the second node
  • the first node sends the irreplaceable notification information, or according to the stored Registering device information of each node, re-determining to replace the second node of the first node, and sending notification replacement information to the re-determined second node; the re-determined second node performs execution with the first node according to the notification replacement information Equipment replacement confirmation;
  • the target node receives the replaced notification information sent by the second node or the first node, and updates the stored device information of the first node and the second node according to the replaced notification information.
  • the target node when the target node sends the replacement notification information carrying the identification information of the second node to the first node, the first node side in the machine-to-machine system is also provided in this embodiment.
  • the device switching method is as shown in FIG. 10, and the method specifically includes:
  • the first node in the machine-to-machine system receives the replacement notification information sent by the target node when it is confirmed that the first node that communicates with the target node needs to be replaced, and the replacement notification information includes the identifier of the second node that replaces the first node.
  • the replacement notification information received by the first node may be sent when the target node actively monitors the state of the first node, and the first node needs to be replaced; the replacement notification information received by the first node may also be The first node sends the request replacement information to the target node when confirming that it needs to be replaced, and the target node sends the replacement information according to the request and then selects a suitable replacement for the second node of the first node; S1002. The first node sends, to the second node, replacement information according to the replacement notification information, where the replacement information includes the identifier information of the target node.
  • the first node may further include: in the replacement information sent to the second node, the service information in the M2M system that is required to be provided by the second node to the target node, so that the second node that receives the replacement information is second according to the requirement.
  • the service information in the M2M system provided by the node to the target node determines whether it can replace the first node for service;
  • the replacement failure information is sent to the target node
  • the first node After receiving the replacement information that is replied by the second node according to the replacement information, the first node disconnects the communication with the target node.
  • the first node may further send the data information to the second node, where the data information may include the service saved by the first node to serve the target node. Historical data and other information.
  • the first node and the second node in the device switching method may be an application service node or an application dedicated node in actual application, and correspondingly, the target node should be an intermediate node or an infrastructure node, and FIG. 14a is the first The signaling interaction diagram of the device handover when the node and the second node are the application service node or the application dedicated node, and the target node is the intermediate node or the infrastructure node; or, the first node and the second node in the device switching method are actually The application may also be an intermediate node.
  • the target node should be an infrastructure node.
  • FIG. 14b is a signaling interaction diagram of the device handover when the first node and the second node are intermediate nodes, and the target node is an infrastructure node.
  • the device when the first node and the second node are intermediate nodes, and the target node is an infrastructure node, the device also generally has a device for communicating with the first node in the machine-to-machine system, and therefore, the second node is in the second node.
  • the replacement information sent by the node may further include: identifier information of the device registered at the first node, so that the second node sends the update information to the device that has been registered in the first node after completing the device replacement.
  • the target node sends the label carrying the first node to the second node.
  • a device switching method based on the second node side in the machine-to-machine system is also provided. As shown in FIG. 11, the method specifically includes:
  • the second node in the machine-to-machine system receives the notification replacement information that is sent when the first node that needs to communicate with the target node needs to be replaced, and the notification replacement information includes the identification information of the first node, so that the second The node sends the permission replacement information to the first node according to the identifier information of the first node; wherein, if the first node is an application-specific node, the identifier information may be a CSE-ID of the node, if the first node is an application service node or The intermediate node, the identification information may be an AE-ID and/or a CSE-ID of the node;
  • the request replacement information received by the second node may further include: requesting the service information in the M2M system provided by the second node to the target node, so that the second node is in the M2M system provided by the second node to the target node according to the requirement Service information, to determine whether it can replace the first node for service;
  • the second node After the first node determines that the first node can be replaced according to the notification replacement information, the second node sends the permission replacement information carrying the identifier information of the target node to the first node.
  • the second node After receiving the confirmation information replied by the first node, the second node sends the replaced notification information to the target node.
  • the method may further include: receiving data information sent by the first node, where the data information may include historical data saved by the first node and serving the target node. And the first node may send the data information to the second node in the confirmation information, or may be separately sent to the second node, which is not limited herein.
  • the first node and the second node in the device switching method may be an application service node or an application dedicated node in actual application, and correspondingly, the target node should be an intermediate node or an infrastructure node, and FIG. 15a is the first The signaling interaction diagram of the device handover when the node and the second node are the application service node or the application dedicated node, and the target node is the intermediate node or the infrastructure node; or, the first node and the second node in the device switching method are actually The application may also be an intermediate node.
  • the target node should be an infrastructure node
  • FIG. 15b is a first node and a second node is an intermediate node. Point, the signaling interaction diagram of device switching when the target node is an infrastructure node.
  • the machine-to-machine system generally has a device that communicates with the first node, and therefore, the second node receives the confirmation information.
  • the method may further include: identifying information of the device registered at the first node, so that the second node sends update information to the device registered in the first node after completing the device replacement; that is, the second node sends the replaced notification to the target node.
  • the method may further include: sending, by the second node, update information to the device registered at the first node, where the update information includes an identifier of the second node and an identifier of the first node, where the identifier may be a universal resource identifier Symbol (URI).
  • URI universal resource identifier Symbol
  • Embodiment 4 is a diagrammatic representation of Embodiment 4:
  • the execution entity of the device switching mechanism is the first node, that is, the old node.
  • a device switching method based on the target node side in the machine-to-machine system is provided. As shown in FIG. 12, The method specifically includes:
  • the device information of each node may include: status information of whether each node is online, service information that each node can provide, location information of each node, and registration information of each node;
  • the first node sends the request replacement information to the second node, where the request replacement information includes the identifier information of the target node, where the identifier information of the target node generally refers to the CSE-ID;
  • the first node, in the request replacement information sent to the second node may further include: requesting, by the second node, the service information in the M2M system provided by the target node, to receive the second node requesting the replacement information according to the request
  • the service information in the M2M system provided by the second node to the target node determines whether it can replace the first node for service
  • the second node of the first node is re-determined, and Sending request replacement information to the re-determined second node to complete device replacement;
  • the first node receives the replacement letter sent by the second node according to the request replacement information. After the message, disconnect the communication with the target node;
  • the first node may further send data information to the second node, where the data information may include information such as historical data saved by the first node and serving the target node.
  • the first node and the second node in the device switching method may be an application service node or an application dedicated node, and correspondingly, the target node should be an intermediate node or an infrastructure node; or, in the foregoing device
  • the first node and the second node in the handover method may also be intermediate nodes in actual application, and correspondingly, the target node should be an infrastructure node.
  • the device when the first node and the second node are intermediate nodes, and the target node is an infrastructure node, the device also generally has a device for communicating with the first node in the machine-to-machine system, and therefore, the second node is in the second node.
  • the request replacement information sent by the node may further include: identifier information of the device registered at the first node, so that the second node sends the update information to the device registered in the first node after completing the device replacement.
  • a device switching method based on the second node side in the machine-to-machine system is further provided. As shown in FIG. 13, the method includes:
  • the second node in the machine-to-machine system receives the request replacement information sent by the first node when confirming that it needs to be replaced, and the request replacement information includes the identifier information of the target node that communicates with the first node; wherein, the target node
  • the identification information generally refers to the CSE-ID;
  • the request replacement information received by the second node may further include: requesting the service information in the M2M system provided by the second node to the target node, so that the second node is in the M2M system provided by the second node to the target node according to the requirement Service information, to determine whether it can replace the first node for service;
  • S1302 After determining, according to the request replacement information, that the second node can communicate with the target node, send the acceptance replacement information to the first node, and send the replaced notification information to the target node.
  • the method may further include: receiving data information sent by the first node, where the data information may include information, such as historical data, that is saved by the first node and serving the target node.
  • the first node and the second node in the device switching method may be an application service node or an application dedicated node, and correspondingly, the target node should be an intermediate node or an infrastructure node; or, in the foregoing device
  • the first node and the second node in the handover method may also be intermediate nodes in actual application, and correspondingly, the target node should be an infrastructure node.
  • the machine-to-machine system generally has a device that communicates with the first node, and therefore, the request received by the second node is replaced.
  • the information may further include: identifier information of the device registered at the first node; and after the second node sends the replaced notification information to the target node, the method further includes: the second node sending the update information to the device registered at the first node,
  • the update information includes an identifier of the second node and an identifier of the first node, wherein the identifier may be a universal resource identifier (URI).
  • URI universal resource identifier
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can be embodied in the form of one or more computer program products embodied on a computer-usable storage medium (including but not limited to disk storage, CD-ROM, optical storage, etc.) in which computer usable program code is embodied.
  • a computer-usable storage medium including but not limited to disk storage, CD-ROM, optical storage, etc.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

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

Abstract

L'invention concerne un procédé et un dispositif de commutation de dispositif. Le procédé consiste : pour un nœud cible ou un premier nœud dans un système de machine-à-machine, lorsqu'il est déterminé qu'un remplacement de dispositif doit être réalisé sur le premier nœud, et selon les informations de dispositif stockées et associées à divers autres nœuds qui ont été enregistrés, à déterminer un second nœud grâce auquel le premier nœud est remplacé pour réaliser le remplacement de dispositif. Au moyen du dispositif et du procédé décrits dans les modes de réalisation de la présente invention, un dispositif remplaçable peut être sélectionné automatiquement dans un système de machine-à-machine pour réaliser le remplacement de dispositif, en assurant ainsi la continuité de la communication du système M2M.
PCT/CN2014/072475 2014-02-24 2014-02-24 Procédé et dispositif de commutation de dispositif WO2015123893A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/CN2014/072475 WO2015123893A1 (fr) 2014-02-24 2014-02-24 Procédé et dispositif de commutation de dispositif
CN201480041406.2A CN105409304B (zh) 2014-02-24 2014-02-24 一种设备切换的方法和设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2014/072475 WO2015123893A1 (fr) 2014-02-24 2014-02-24 Procédé et dispositif de commutation de dispositif

Publications (1)

Publication Number Publication Date
WO2015123893A1 true WO2015123893A1 (fr) 2015-08-27

Family

ID=53877576

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2014/072475 WO2015123893A1 (fr) 2014-02-24 2014-02-24 Procédé et dispositif de commutation de dispositif

Country Status (2)

Country Link
CN (1) CN105409304B (fr)
WO (1) WO2015123893A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017071118A1 (fr) * 2015-10-28 2017-05-04 西安中兴新软件有限责任公司 Procédé et appareil de gestion de ressource de surveillance, cse, et support de stockage

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107484211B (zh) 2016-06-08 2020-06-26 华为技术有限公司 切换接入点的方法及装置
CN115315967A (zh) * 2020-05-11 2022-11-08 Oppo广东移动通信有限公司 切换方法与装置、云平台和设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20120227097A1 (en) * 2011-03-01 2012-09-06 General Instrument Corporation Providing Subscriber Consent in an Operator Exchange
CN102740452A (zh) * 2011-04-02 2012-10-17 中兴通讯股份有限公司 机器类通信终端触发方法及装置
CN102907068A (zh) * 2010-03-09 2013-01-30 交互数字专利控股公司 支持机器对机器通信的方法和设备
CN103220670A (zh) * 2012-01-19 2013-07-24 华为技术有限公司 一种设备切换方法、m2m平台和网络系统

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101626629B (zh) * 2009-07-28 2011-11-16 广州飞瑞敖电子科技有限公司 机器互联无线网络系统
US8867458B2 (en) * 2010-04-30 2014-10-21 Nokia Corporation Network controlled device to device / machine to machine cluster operation
JP5776161B2 (ja) * 2010-10-04 2015-09-09 ソニー株式会社 通信装置、通信制御方法及び通信システム
CN102025551A (zh) * 2010-12-23 2011-04-20 中兴通讯股份有限公司 基于接入网关的主备用设备切换方法和装置
CN102547657B (zh) * 2010-12-31 2015-03-25 中兴通讯股份有限公司 远程改变机器对机器设备的归属运营商的方法
US20120281694A1 (en) * 2011-05-05 2012-11-08 Telefonaktiebolaget L M Ericsson (Publ) M2m scalable addressing and routing
CN103079237B (zh) * 2012-03-05 2015-12-16 上海寰创通信科技股份有限公司 一种基于无线网络环境的代理无线接入设备选择方法

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102907068A (zh) * 2010-03-09 2013-01-30 交互数字专利控股公司 支持机器对机器通信的方法和设备
US20120227097A1 (en) * 2011-03-01 2012-09-06 General Instrument Corporation Providing Subscriber Consent in an Operator Exchange
CN102740452A (zh) * 2011-04-02 2012-10-17 中兴通讯股份有限公司 机器类通信终端触发方法及装置
CN103220670A (zh) * 2012-01-19 2013-07-24 华为技术有限公司 一种设备切换方法、m2m平台和网络系统

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017071118A1 (fr) * 2015-10-28 2017-05-04 西安中兴新软件有限责任公司 Procédé et appareil de gestion de ressource de surveillance, cse, et support de stockage

Also Published As

Publication number Publication date
CN105409304A (zh) 2016-03-16
CN105409304B (zh) 2019-10-25

Similar Documents

Publication Publication Date Title
EP2945326B1 (fr) Procédé de changement de passerelle dans un système machine à machine (m2m) et dispositif correspondant
EP3499965B1 (fr) Système de communication, dispositif de communication, et programme
EP2961122B1 (fr) Procédé pour modifier un paramètre de service m2m et appareil associé
JP6102942B2 (ja) 無線通信システム
JP2023075075A (ja) サービス加入方法および装置
WO2011150707A1 (fr) Procédé et système de gestion d'états de terminal ou d'événements de terminal dans un service de communication machine-machine ou machine-homme ou homme-machine (m2m)
EP2982052A1 (fr) Commutateur de découverte de dispositif entre un mode assisté par réseau et un mode direct
WO2014196371A2 (fr) Système de communications
US20150264601A1 (en) Apparatus and method for controlling handover in wireless communication system
JP6384486B2 (ja) 通信システム、中継装置、通信方法及びプログラム
WO2010151662A1 (fr) Procédé et système de mise à jour d'informations de présence dans un système de communication
TW201446055A (zh) 無線電鏈路建立
JP6447712B2 (ja) 同報配信システム、ゲートウェイ装置、同報配信方法及びプログラム
WO2013066628A1 (fr) Procédé et appareil destinés à garantir l'affectation de ressources critiques pour les appels de groupe passés dans l'environnement de communication de la messagerie instantanée (ptt)
JP2022058919A (ja) 第１の装置の方法、第１のコアネットワークノードの方法、及び第１の装置
EP3039894B1 (fr) Transfert de profil zeroconf pour permettre l'itinérance rapide
WO2015123893A1 (fr) Procédé et dispositif de commutation de dispositif
CN111955021A (zh) 5g系统中用于用户平面保护的安全策略的amf控制处理
EP2999169B1 (fr) Système de communication, appareil de commande de temporisation de communication, procédé de commande de temporisation de communication et support lisible par ordinateur
CN104604183B (zh) 使用移动通信设备发送消息的方法和系统
US10122540B2 (en) Device and method for managing multicast group in wireless network
EP3206420B1 (fr) Procédé et dispositif d'adressage
CN101568116A (zh) 一种证书状态信息的获取方法及证书状态管理系统
EP4250802A1 (fr) Optimisation d'attribution d'identifiant de cellule physique dans un réseau de communication sans fil
JP2018508161A (ja) Ｓｃｔｐ接続の再確立方法及び装置、記憶媒体

Legal Events

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

Ref document number: 201480041406.2

Country of ref document: CN

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

Ref document number: 14883427

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

Country of ref document: EP

Kind code of ref document: A1