[go: up one dir, main page]

WO2012136005A1 - Procédé pour adresser un terminal m2m et un dispositif de plate-forme m2m - Google Patents

Procédé pour adresser un terminal m2m et un dispositif de plate-forme m2m Download PDF

Info

Publication number
WO2012136005A1
WO2012136005A1 PCT/CN2011/072552 CN2011072552W WO2012136005A1 WO 2012136005 A1 WO2012136005 A1 WO 2012136005A1 CN 2011072552 W CN2011072552 W CN 2011072552W WO 2012136005 A1 WO2012136005 A1 WO 2012136005A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
platform
route
message
gateway
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/CN2011/072552
Other languages
English (en)
Inventor
Frédéric Fok ah chuen
Yu Li
Wanpeng FAN
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 PCT/CN2011/072552 priority Critical patent/WO2012136005A1/fr
Publication of WO2012136005A1 publication Critical patent/WO2012136005A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L45/00—Routing or path finding of packets in data switching networks
    • H04L45/42—Centralised routing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46—Interconnection of networks
    • H04L12/4604—LAN interconnection over a backbone network, e.g. Internet, Frame Relay
    • H04L12/462—LAN interconnection over a bridge based backbone
    • H04L12/4625—Single bridge functionality, e.g. connection of two networks over a single bridge
    • 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
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/04—Communication route or path selection, e.g. power-based or shortest path routing based on wireless node resources
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0805—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability
    • H04L43/0817—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters by checking availability by checking functioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing

Definitions

  • the present invention relates to the wireless communication field, and particularly, to a method for addressing a M2M terminal and a M2M platform device.
  • the Machine-to-Machine (M2M) communication refers to communication between entities without necessarily human intervention.
  • the M2M platform provides the service Application Programming Interface (API), and the service API makes abstracting simpler.
  • the M2M platform opens interfaces to applications, and provides operational management which includes (but not limited to): terminal management (such as software versions, and terminal status, etc.), customer application management (such as lifecycle deployment, and right permissions, etc.), message routing, and operational supports (such as billing, network statistics, error resiliency, and service availability, etc.).
  • M2M terminals communicate with the M2M platform over wired or wireless networks.
  • a M2M terminal can be:
  • a M2M device which is an end-node of a network communicating with sensors and/or actors. Wherein sensors gather information about the physical world while actors take decisions and perform adequate actions upon the environment.
  • the M2M device implements the intelligence to receive events from sensors and to send orders to actors; or a M2M Gateway, which serves as a go-between for the M2M platform and external sensors and/or actors networks (comprising M2M devices and/or M2M gateways).
  • the M2M gateway can have different levels of intelligence and different packet inspections capabilities.
  • the M2M Gateway is usually seen as a bridge between a Wide Area Network and one or multiple sensors and/or actors networks.
  • the sensors and/or actors networks can communicate using different wired or wireless technologies, such as: ZigBee, XI 0,
  • M2M platform (PF), as expressed in ETSI TS 102 690, to manage "Network Communication Service Selection" when a M2M device or a M2M gateway has several network addresses, taking into account the Request Service Class to be matched with available communication network paths and provide alternative communication paths according to selectable available communication networks.
  • PF M2M platform
  • a reason for that is the cost of intermediary M2M gateways and M2M devices should remain low, so the addressing capabilities should be available on the M2M platform, meaning that M2M gateways and M2M devices should be reachable and managed by the M2M platform.
  • the M2M devices Dl .2.1 can be reached through the M2M Gateway 1(GW1) and the M2M Gateway 1.2 (GW1.2), namely, GW1 -> GW1.2 -> Dl .2.1.
  • both the M2M gateway and the M2M devices should be reachable and managed by the M2M platform.
  • FIG. 2 is a sketch map of a M2M area network in which the M2M gateway has a high level intelligence.
  • the M2M gateway can communicate with the M2M platform on behalf of the M2M devices, and therefore the M2M gateway has application level capabilities, for example authentication, registration, and message routing with protocol mediation (such as using different M2M protocol in the M2M sub area network, which includes the M2M gateway GW1, and M2M devices Dl . l, D1.2 and D1.3 in FIG.2).
  • the M2M gateway can interpret and inspect the protocol communication and trigger networks or application functions for authentication, or protocol mediation, etc..
  • the visibility of the M2M platform (the PF in FIG.2) is only for the M2M gateway, which means that all M2M devices are reachable through the address of the M2M Gateway.
  • An address binding can be provided in the M2M platform, which associates a M2M device name (or the M2M device identifier) with the address of the M2M Gateway. The binding is either pre-provisioned or discovered when a M2M device connects to the M2M platform.
  • the M2M gateway GW1 By adding the M2M device name (or the M2M device identifier) into the signaling messages, the M2M gateway GW1 is able to control, manage or receive events from the M2M devices within its sub area network, or sends events to the M2M devices in its sub area network, and acts as a "state M2M proxy" (which is for maintaining communication status and message delivery, potentially reformatting through protocol mediation, and so on). In this situation, it is up to the M2M gateway to maintain the knowledge of the M2M devices attached to its sub area network.
  • state M2M proxy which is for maintaining communication status and message delivery, potentially reformatting through protocol mediation, and so on
  • the M2M Gateway acts as a router and cannot process the M2M protocol communication on behalf of the M2M devices within its sub area network (hereby "sub area network” refers as the M2M Local area network in FIG.3).
  • sub area network refers as the M2M Local area network in FIG.3
  • the M2M gateway does not make any transformation of the protocol communication technology used in the sub area network, and it just relays the messages to the M2M platform which has to understand and adapt to the protocol technology used.
  • the M2M gateway GW1 has a low level intelligence.
  • M2M devices in the M2M sub area network of the GW1 include a Dl .
  • the M2M gateway GW1 is able to route the message. Name resolution enables the M2M Gateway to transfer the request to the M2M devices, and this is dependent upon the technology used (such as IP, Zigbee, X10, PLC, and 6LowPan, etc.) in the sub area network (i.e. M2M Local Area Network in FIG.3).
  • the M2M Gateway GW1 After receiving the M2M device identifier (or the M2M device name) contained in signaling messages, the M2M Gateway GW1 has to perform some additional works to know where to route the request. Indeed the M2M device identifier (or the M2M device name) is just a representation of the M2M device while its address is dependent upon the device technology used (such as IP, XI 0, 6LowPan, etc.).
  • the M2M Gateway GW1 does not perform the routing decisions in the prior art in this situation, it just relays the message based on address resolution.
  • the M2M platform has to calculate the best route to reach the M2M device, and provide information to all intermediary M2M gateways (e.g. GW1, GW1.2 in FIG.3) so that those M2M gateways are able to relay messages to one or more M2M terminals.
  • intermediary M2M gateways e.g. GW1, GW1.2 in FIG.3
  • M2M terminals can have a Universal Resource Identifier (URI).
  • the M2M terminals can be seen as a resource identified by a URI on a server (which is advantageously located in the M2M platform).
  • the M2M platform can find the authority address and join the first M2M gateway (for example GW1) to which the request is sent. Since the URI representation may contain other M2M gateways along the path (e.g.
  • GW1 -> GW1.2 -> Dl .2.1 "GW1 -> GW1.2 -> Dl .2.1"
  • the GW1 analyzes the URI in the request to forward the request to the M2M gateway GW1.2 which in turn forwards the request to the M2M device DL L
  • This URI representation needs to be provisioned in the M2M platform so that the M2M platform can join the M2M device DL L
  • a list of all possible route paths shall be maintained as well as an accurate route selection, and more particularly if a M2M gateway becomes faulty or if the quality (such as bandwidth, bit rate, etc.) is degrading, and there is no such a technical scheme how to get all possible route paths as well as an accurate route selection for the M2M platform.
  • the technical problem to be solve in the present invention is to provide a method for addressing a M2M terminal and a M2M platform device, which enables the M2M platform get all possible route paths as well as an accurate route selection, especially for non-intelligence or low-intelligence M2M gateways.
  • the present invention provides a method for addressing a Machine-to Machine (M2M) terminal, and the method comprising: a M2M platform obtaining possible route paths for each connected M2M terminal by received identifiers or names of all of the M2M terminals on the route path from an initiate M2M terminal to said M2M platform;
  • M2M Machine-to Machine
  • a M2M terminal is a M2M device or a M2M gateway.
  • step of a M2M platform obtaining possible route paths for each connected M2M terminal comprises:
  • the M2M platform receiving a message initiated by a M2M terminal, said message carrying the identifier or name list of father nodes of said M2M terminal together with the identifier or name of said M2M terminal, and said M2M platform obtaining and recording a father and child relationship for said M2M terminal; wherein all the father and child relationships of one M2M terminal are the possible route paths for said M2M terminal.
  • a stack of terminal identifiers in said message carries the identifier or name list of the father nodes of said M2M terminal along with the identifier or name of said M2M terminal.
  • step of the M2M platform receiving a message initiated by a M2M terminal comprises:
  • the M2M device when a M2M device initiates a message to said M2M platform, the M2M device sending a message which includes its own identifier in the stack of terminal identifiers in the message to a father node, wherein said father node is an intermediary M2M gateway or the M2M platform; if the father node is an intermediary M2M gateway, the intermediary M2M gateway receiving the message from the M2M device or other intermediary M2M gateway, the intermediary M2M gateway adding its own identifier in the stack of terminal identifiers, which also includes the identifier of the M2M device, and then sending the message to a father node of the intermediary M2M gateway, wherein the father node of the intermediary M2M gateway is the M2M platform or another intermediary M2M gateway; and
  • the M2M platform receiving the message sent by an intermediary M2M gateway or a M2M device.
  • the M2M platform selects one or more route paths for the M2M terminal based on the Quality of Service (QoS) and/or availability information of the route paths, or the M2M platform selects one or more route paths indicated by the M2M terminal.
  • QoS Quality of Service
  • the way of the M2M platform selecting the route paths for each M2M terminal based on the QoS and/or availability information of the route comprises:
  • the M2M platform retrieving the route paths the M2M terminals indicated by terminal identifiers or terminal names; checking status of the M2M terminals in the route path, and if a M2M terminal is fault, the M2M platform looking up the other online father nodes of the M2M terminal to reach and calculating selection priorities according to a weighted sum of route path information, and selecting the maximal selection priority route path.
  • the method further comprises: the M2M platform updating the father and child relationships for said M2M terminal recorded in the M2M platform.
  • the weighted sum of the route path information is equal to a weighted sum of the bandwidth, 1/load and 1/ (nodes number).
  • the method further comprising: the M2M platform monitoring status of all the M2M terminals according to one or more of following information: heartbeat, status reporting and fault reporting messages.
  • the present invention also provides a M2M platform device, which comprises:
  • a route path obtaining module which is configured to obtain possible route paths for each connected M2M terminal by received identifiers or names of all of the M2M terminals on the route path from an initiate M2M terminal to said M2M platform device;
  • a selection module which is configured to when the M2M platform device transmits a message to a M2M terminal, select one or more route paths from the possible route paths; and a routing module, which is configured to route messages according to selected route paths; wherein a M2M terminal is a M2M device or a M2M gateway.
  • route path obtaining module is configured to obtain possible route paths for each connected M2M terminal as following way:
  • the route path obtaining module receiving a message sent by a M2M terminal, said message carrying the identifier or name list of the father nodes of said M2M terminal along with the identifier or name of said M2M terminal, and said route path obtaining module obtaining and recording a father and child relationship for said M2M terminal; wherein all the father and child relationships of one M2M terminal are the possible route paths for said M2M terminal.
  • a stack of terminal identifiers in said message carries the identifier or name list of the father nodes of said M2M terminal along with the identifier or name of said M2M terminal.
  • selection module is configured to select a route path from the possible route paths the M2M terminal as following way: the selection module selecting one or more route paths for the M2M terminal based on the Quality of Service (QoS) and/or availability information of the route paths, or the selection module selecting one or more route paths indicated by the M2M terminal.
  • QoS Quality of Service
  • the selection module is configured to select the route paths for each M2M terminal based on the QoS and/or availability information of the route as following way:
  • the selection module retrieving the route paths for the M2M terminals indicated by terminal identifiers or terminal names; checking status of the M2M terminals in the route path, and if a M2M terminal is fault, the selection module looking up the other online father nodes of the M2M terminal to reach and calculating selection priorities according to a weighted sum of route path information, and selecting the maximal selection priority route path.
  • the selection module is also configured to monitor status of all the M2M terminals according to one or more of following information: heartbeat, status reporting and fault reporting message.
  • the method and the M2M platform in present invention associates to LeveW protocol routing, and the present invention is for optimizing and calculating the M2M network route paths by the M2M platform, and for addressing the M2M devices behind multiple M2M gateways over multi-access networks.
  • the present invention further allows the M2M platform knowing the routes that are currently active, i.e. the route paths through which are sent messages between the M2M platform and M2M terminals, especially for non-intelligence or low-intelligence M2M gateways.
  • FIG. 1 is a sketch map of a Tree-based M2M area network
  • FIG.2 is a sketch map of the M2M area network in which a M2M gateway has a high level intelligence
  • FIG.3 is a sketch map of the M2M area network in which a M2M gateway has a low level intelligence
  • FIG.4 is a sketch map of the M2M overlay wide area network on top of a multi-access network
  • FIG.5 is a sketch map of the message transmission from a M2M device according to an example of the present invention.
  • FIG.6 is a sketch map of the Routing via GW hierarchy according to an example of the present invention.
  • FIG.7 is a sketch map of messages transmission according to an example of the present invention.
  • FIG. 8 is a flow chart of the method for addressing a M2M terminal according to the present invention.
  • FIG. 9 is a sketch map of the structure of the M2M platform device according to the example of the present invention.
  • Proposed invention is particularly adapted for signaling communication protocols over well known transport protocols like the User Datagram Protocol (UDP) or the Transmission Control Protocol (TCP). It can be adapted in protocols like the Wireless Machine-to-Machine Protocols for Terminal side (WMMP-T) or the Machine-to-Machine Data Management Protocol (MDMP) which are M2M protocols defined in China.
  • the proposed invention also has a wider scope in the field of M2M addressing and routing capabilities, namely, addressing and routing capabilities in a multi-access network environment.
  • the multi-access network environment refers to the agnostic communication capability of exchanging messages over both Fixed (such as Broadband network) and Mobile networks (such as the General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), and so on).
  • Fixed such as Broadband network
  • Mobile networks such as the General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), Worldwide Interoperability for Microwave Access (WiMAX), and so on).
  • GPRS General Packet Radio Service
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • WiMAX Worldwide Interoperability for Microwave Access
  • FIG.4 is a sketch map of the M2M overlay wide area network on top of a multi-access network.
  • the multi-access network is composed of different network nodes enabling the network communication over fixed or mobile network infrastructures, which are independent of the application communication protocols used. Some of those network nodes in the multi-access network may also be M2M gateway nodes in the plane of the M2M Overlay Wide Area Network.
  • the M2M platform has a view of the M2M overlay wide area network, which is independent of the network communication protocols.
  • FIG. 8 The method for addressing a M2M terminal according to the present invention is shown in FIG. 8, and the method comprises:
  • Step 801 the M2M platform obtains possible route paths for each connected M2M device by receiving the messages sent from the M2M devices, and the message includes identifiers or names of all of the M2M terminals on the route path, wherein the possible route paths are currently active route paths for each connected M2M terminal;
  • Step 802 when the M2M platform transmits a message to a M2M terminal, the M2M platform selects one or more route paths for the M2M terminal from obtained possible route paths;
  • Step 803 the M2M platform routes messages according to the selected route paths.
  • the M2M platform selects one or more route paths for the M2M based on the Quality of Service (QoS) and/or Availability information of the route paths.
  • QoS Quality of Service
  • Availability Availability information
  • the way of the M2M platform obtaining possible route paths for each connected M2M terminal comprises:
  • a M2M terminal sending a register message carrying the identifiers (IDs) list of the father nodes of the M2M devices and the identifier or name of the M2M device itself, and the M2M platform recording the father-child relationship for all nodes (including M2M gateways and M2M devices).
  • IDs list above is a list including the father nodes' identifiers or the father nodes' names.
  • the father node refers to the intermediary M2M gateways that transmit the message sent by a M2M device or a M2M gateway to the M2M platform.
  • the way of the M2M platform obtaining the currently active route paths of a M2M terminal comprises:
  • a stack of terminal identifiers being added into the protocol message, and the stack carrying the names or identifiers of the intermediary gateways' and the M2M terminal who initiates the protocol message.
  • the principle of adding the stack of terminal identifiers in the protocol message is as following (taking the identifier as an example to describe):
  • the M2M device sends a message which includes its own identifier in the stack of terminal identifiers in the message to an intermediary M2M gateway or the M2M platform;
  • the intermediary M2M gateway adds its own identifier in the stack of terminal identifiers in the message initiated by the M2M device, which also includes the identifier of the M2M device, and then sends the message to the M2M platform or another intermediary M2M gateway;
  • the M2M platform receives the protocol message including the stack of terminal identifiers transmitted by a M2M device or an intermediary M2M gateway
  • the M2M platform can obtain the currently active route paths of the M2M according to the identifiers in the stack of terminal identifiers in the message. And in this way, the M2M platform has a dynamic view of current active route paths for each connected M2M device because the M2M platform knows which route path being used by a M2M device.
  • the M2M platform sends a message including the route path which is denoted by the identifiers or the names of the M2M terminals on the route path, and the M2M device can be reached by the route path.
  • the route path is either the one indicated by the M2M devices or one that is selected as described below.
  • the way the M2M platform selecting the route paths for each M2M terminal based on the QoS and/or Availability information of the route comprises:
  • the M2M platform retrieving the route path indicated by the M2M terminals and checking the nodes' status in the route path, and if a node is fault, the M2M platform looking up the other online father nodes of the M2M terminal to reach and calculate the selection priority according to weighted sum of the bandwidth, load, and nodes number, wherein the node with maximal selection priority is selected as spare route;
  • the M2M platform updating the IDs list of the father nodes stored in the M2M platform.
  • a M2M device D 1.2.1 sends a message to the M2M gateway GW1.2, carrying the identifier 1.2.1 of the M2M device in the stack of terminal identifiers in the message; and the M2M gateway GW1.2 adds the identifier 1.2 of the M2M gateway GW1.2 into the stack of terminal identifiers in the message, and then sends the message to the gateway GW1; the gateway GW1 adds its term, namely identifier 1 of the gateway GW1, into the stack of terminal identifiers in the message, and then sends to the M2M platform. Therefore, the M2M platform has the route path of the M2M device Dl .2.1. Preferably, the M2M platform can also retrieve the QoS parameters of the intermediary M2M gateways, as shown in FIG. 6.
  • FIG.6 illustrates the mechanism of the dynamic route paths made by the M2M platform.
  • the M2M device D 1.1.1 has three father nodes including the GW1.1 , GW2 and GW3.1 (Notes: the father nodes information has been set in the M2M device manually during installation, and thus the M2M device has the father nodes information).
  • the M2M device registers to the M2M platform, the register message sent by the M2M device carries the IDs list of the father nodes, and the M2M platform records the father-child relationship for all nodes (including M2M gateways and M2M devices).
  • the M2M platform can also monitor status of all the nodes according to one or more of following information: heartbeat, status reporting and fault reporting messages and so on.
  • the M2M device D 1.1.1 first registers to the M2M platform through the GW1.1 and the GW1, the M2M platform records the current route path to the D 1.1.1 as (@1, @1.1, @1.1.1).
  • the M2M platform checks the nodes' status in the route path. If a node (for example, GW1.1) is fault, the M2M platform looks up the other online father nodes of the D 1.1.1, and calculates the selection priority according to weighted sum of the bandwidth by 1/load and 1 /(nodes number). The nodes with maximal selection priority will be selected as a spare route path.
  • the M2M platform maintains a tree hierarchy structure of said M2M device identifiers. As a M2M device may be reachable through potentially different route paths, the route path is selected based on QoS and/or Availability information (such as the number of hops, link QoS, available bandwidth, etc.) provided by the intermediary M2M gateways. Therefore it is possible for the M2M platform to route messages depending on the level of priority. For instance, alarm or urgent requests may be sent via a specific route path, while other messages are transmitted over different route paths. Besides, the M2M platform can also use other technique to select the best route path based on priority level of the M2M devices, such as well known flooding technique can be employed with a configurable maximum number of hops to avoid infinite loops etc.
  • the PF or M2M terminals either can be recipients or can be the initiator depending on who initiates the message.
  • the process of the M2M terminal message transfer including:
  • the M2M terminal Based on an identifier extracted from a M2M message, the M2M terminal performs name resolution (i.e. association between IP address ⁇ -> Identifier) to obtain the address of the next M2M gateway (or the next M2M platform); and
  • the message is forwarded to the next M2M Terminal or the M2M platform corresponding to the identifier.
  • the M2M gateway When a M2M gateway receives a message from the M2M platform, the M2M gateway inspects the stack of terminal identifiers in the message, and performs as following:
  • the message is for this M2M gateway itself.
  • the message is consumed (namely the message is treated and not forwarded to any other nodes). If the first identifier in The Stack is not its own identifier, the M2M Gateway extracts this identifier, and carries out Step A;
  • the M2M Gateway unpacks its own identifier, extracts the next identifier from the M2M message and carries out the Step A.
  • a M2M device When a M2M device receives a message from a M2M gateway, the M2M device performs as following:
  • the M2M device inspects the stack of terminal identifiers in said message
  • the message is consumed
  • the M2M device rejects this message. In this case, The M2M device does not forward the message to avoid network flooding. However, the M2M device may reply a non-acknowledgment message to the M2M gateway that sends the message to indicate the error. This can help the M2M gateway to avoid repetitive device flooding and refine/recover the identifier list.
  • the M2M gateway When a M2M device sends a message to a M2M gateway, the M2M gateway adds its own identifier in the stack of terminal identifiers in the message.
  • the M2M device is configured with network address of the M2M platform used as the recipient;
  • the M2M device is configured with at least one IDs list of the Father nodes. This list may be configured during device initial provisioning, or updated through the Over-The-Air methods (SMS Push, HTTP, etc.) and so on.
  • the M2M platform When the M2M platform sends a message to a M2M terminal, the M2M platform retrieves the route path, comprising:
  • the M2M terminal supports sending a registration message: the M2M terminal sending a register message carrying the IDs list of the father nodes of the device, and the M2M platform recording the father-child relationship for all nodes (including M2M gateways and M2M devices). Otherwise, the M2M platform is provisioned with default or alternative father-child relationship for all nodes.
  • the M2M platform After the M2M platform obtains all possible route paths for all M2M terminals, the M2M platform performs a route selection process, comprising:
  • the M2M platform can choose a network route path to reach a M2M terminal depending on the message priority, desired QoS, or node Availability and so on along the route path.
  • the M2M platform After the M2M platform performs a route selection process, the M2M platform sends a message to the M2M terminal (device or gateway) including the path route.
  • a default route path is used to reach the M2M device, or using alternative transmission means, such as sending a short message (SMS) to a M2M device if the M2M device supports the SMS bearer.
  • SMS short message
  • the example of the present invention also provides a M2M platform device, which includes:
  • a route path obtaining module 901 which is configured to obtain one or more possible route paths for each connected M2M terminal by received identifiers or names of all of the M2M terminals on the route path from an initiate M2M terminal to said M2M platform;
  • a selection module 902 which is configured to when the M2M platform transmits a message to a M2M terminal, select one or more route paths from the possible route paths; and a routing module 903, which is configured to route messages according to selected route paths;
  • a M2M terminal is a M2M device or a M2M gateway.
  • the route path obtaining module 901 is configured to obtain possible route paths for each connected M2M terminal as following way:
  • the route path obtaining module 901 receiving a message sent by a M2M terminal, said message carrying the identifier or name list of the father nodes of said M2M terminal along with the identifier or name of said M2M terminal, and said route path obtaining module 901 obtaining and recording father and child relationships for said M2M terminal; wherein all the father and child relationships of one M2M terminal are the possible route paths for said M2M terminal.
  • a stack of terminal identifiers in said message carries the identifier or name list of the father nodes of said M2M terminal along with the identifier or name of said M2M terminal.
  • the selection module 902 is configured to select a route path from the possible route paths the M2M terminal as following way: the selection module 902 selecting one or more route paths for the M2M terminal based on the Quality of Service (QoS) and/or availability information of the route paths, or the selection module 902 selecting one or more route paths indicated by the M2M terminal.
  • QoS Quality of Service
  • the selection module 902 is configured to select the route paths for each M2M terminal based on the QoS and/or availability information of the route as following way:
  • the selection module 902 retrieving the route paths for the M2M terminals indicated by terminal identifiers or terminal names; checking status of the M2M terminals in the route path, and if a M2M terminal is fault, the selection module 902 looking up the other online father nodes of the M2M terminal to reach and calculating selection priorities according to a weighted sum of route path information, and selecting the maximal selection priority route path.
  • the selection module 902 is also configured to monitor status of all the M2M terminals according to one or more of following information: heartbeat, status reporting and fault reporting messages.
  • the proposed approach relates to the M2M communication over multi access networks, but it is not limited to the multi access networks.
  • Proposed invention differentiates from other research in that it focuses on large scale network of M2M terminals, providing means for message routing on capillary networks to achieve optimized route path selection thereby offering means for operators or carriers to choose different paths while having knowledge of currently active routes to reach M2M terminals.
  • the route selection can be based on required end-to-end quality of service, availability of nodes along the path to reach one or more M2M terminals, switching from one route to another.
  • the method and the M2M platform device in present invention associates to LeveW protocol routing, and the present invention is for optimizing and calculating the M2M network route path by the M2M platform, and for addressing the M2M devices behind multiple M2M gateways over multi-access networks.
  • the method further allow the M2M platform knowing the routes that are currently active, i.e. the route through which are sent messages between the M2M platform and M2M terminals, especially for non-intelligence or low-intelligence M2M gateways.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

La présente invention se rapporte à un procédé adapté pour adresser un terminal de machine à machine (M2M, Machine to Machine). Le procédé selon l'invention comprend les étapes suivantes : une plate-forme M2M obtient des voies de routage possibles pour chaque terminal M2M connecté, sur la base d'identifiants ou de noms reçus de tous les terminaux M2M sur la voie de routage, d'un terminal M2M initiateur à ladite plate-forme M2M ; quand la plate-forme M2M transmet un message à un terminal M2M, elle sélectionne une ou plusieurs voies de routage parmi les voies de routage possibles ; et la plate-forme M2M achemine les messages sur la base des voies de routage sélectionnées. L'invention est caractérisée en ce qu'un terminal M2M est un dispositif M2M ou une passerelle M2M. La présente invention se rapporte d'autre part à un dispositif de plate-forme M2M. La présente invention permet à la plate-forme M2M d'obtenir toutes les voies de routage possibles et de réaliser une sélection précise de la ou des voies de routage.
PCT/CN2011/072552 2011-04-08 2011-04-08 Procédé pour adresser un terminal m2m et un dispositif de plate-forme m2m Ceased WO2012136005A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/072552 WO2012136005A1 (fr) 2011-04-08 2011-04-08 Procédé pour adresser un terminal m2m et un dispositif de plate-forme m2m

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2011/072552 WO2012136005A1 (fr) 2011-04-08 2011-04-08 Procédé pour adresser un terminal m2m et un dispositif de plate-forme m2m

Publications (1)

Publication Number Publication Date
WO2012136005A1 true WO2012136005A1 (fr) 2012-10-11

Family

ID=46968537

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2011/072552 Ceased WO2012136005A1 (fr) 2011-04-08 2011-04-08 Procédé pour adresser un terminal m2m et un dispositif de plate-forme m2m

Country Status (1)

Country Link
WO (1) WO2012136005A1 (fr)

Cited By (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013115946A1 (fr) * 2012-02-03 2013-08-08 Interdigital Patent Holdings Inc. Identificateurs et déclencheurs pour dispositifs capillaires
WO2015126296A1 (fr) * 2014-02-21 2015-08-27 Telefonaktiebolaget L M Ericsson (Publ) Procédé et noeuds permettant de sélectionner une passerelle de réseau capillaire
US9554392B2 (en) 2014-10-15 2017-01-24 At&T Intellectual Property I, L.P. Machine to machine traffic management methods and systems
JP2017511630A (ja) * 2014-02-21 2017-04-20 テレフオンアクチーボラゲット エルエム エリクソン（パブル） メッセージボックスを選択するための方法およびノード
US10104521B2 (en) 2014-02-21 2018-10-16 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for CGW selection
US10104607B2 (en) 2014-02-21 2018-10-16 Telefonaktiebolaget Lm Ericsson (Publ) Method and node for selecting a capillary network gateway
RU2707939C2 (ru) * 2014-12-12 2019-12-02 Виза Интернэшнл Сервис Ассосиэйшн Платформа обеспечения для межмашинных устройств

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1091570A (zh) * 1992-11-27 1994-08-31 国际商业机器公司 区域间多路传送路由
CN101543013A (zh) * 2006-11-27 2009-09-23 斯凯普有限公司 通信系统
CN101577964A (zh) * 2008-11-11 2009-11-11 中兴通讯股份有限公司 一种互通网关的寻址方法
CN101656631A (zh) * 2009-09-07 2010-02-24 中兴通讯股份有限公司 一种统一管理平台中实现支持多网关的方法和装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1091570A (zh) * 1992-11-27 1994-08-31 国际商业机器公司 区域间多路传送路由
CN101543013A (zh) * 2006-11-27 2009-09-23 斯凯普有限公司 通信系统
CN101577964A (zh) * 2008-11-11 2009-11-11 中兴通讯股份有限公司 一种互通网关的寻址方法
CN101656631A (zh) * 2009-09-07 2010-02-24 中兴通讯股份有限公司 一种统一管理平台中实现支持多网关的方法和装置

Cited By (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9730176B2 (en) 2012-02-03 2017-08-08 Interdigital Patent Holdings, Inc. Identifiers and triggers for capillary devices
US9049685B2 (en) 2012-02-03 2015-06-02 Interdigital Patent Holdings, Inc. Identifiers and triggers for capillary devices
US10244502B2 (en) 2012-02-03 2019-03-26 Iot Holdings, Inc. Identifiers and triggers for capillary devices
WO2013115946A1 (fr) * 2012-02-03 2013-08-08 Interdigital Patent Holdings Inc. Identificateurs et déclencheurs pour dispositifs capillaires
US10104520B2 (en) 2014-02-21 2018-10-16 Telefonaktiebolaget Lm Ericsson (Publ) Method and nodes for selecting a capillary network gateway
JP2017511630A (ja) * 2014-02-21 2017-04-20 テレフオンアクチーボラゲット エルエム エリクソン（パブル） メッセージボックスを選択するための方法およびノード
US10104521B2 (en) 2014-02-21 2018-10-16 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for CGW selection
US10104607B2 (en) 2014-02-21 2018-10-16 Telefonaktiebolaget Lm Ericsson (Publ) Method and node for selecting a capillary network gateway
WO2015126296A1 (fr) * 2014-02-21 2015-08-27 Telefonaktiebolaget L M Ericsson (Publ) Procédé et noeuds permettant de sélectionner une passerelle de réseau capillaire
US10511660B2 (en) 2014-02-21 2019-12-17 Telefonaktiebolaget Lm Ericsson (Publ) Method and node for selecting a message box
US9554392B2 (en) 2014-10-15 2017-01-24 At&T Intellectual Property I, L.P. Machine to machine traffic management methods and systems
RU2707939C2 (ru) * 2014-12-12 2019-12-02 Виза Интернэшнл Сервис Ассосиэйшн Платформа обеспечения для межмашинных устройств
US11580519B2 (en) 2014-12-12 2023-02-14 Visa International Service Association Provisioning platform for machine-to-machine devices

Similar Documents

Publication Publication Date Title
US9634928B2 (en) Mesh network of simple nodes with centralized control
US8732338B2 (en) Mesh network bridge routing
KR102182167B1 (ko) M2m 서비스 설정 변경 방법 및 이를 위한 장치
JP6001797B2 (ja) モノのインターネットにおけるＺｉｇＢｅｅネットワークを管理する方法
US10499313B2 (en) Efficient hybrid resource and schedule management in time slotted channel hopping networks
CN100579034C (zh) 上报设备信息的方法、获取设备信息的系统和设备
CN104468205B (zh) 执行路径导向的系统管理
US20160073278A1 (en) Control system, apparatus, methods, and computer readable storage medium storing instructions for a network node and/or a network controller
WO2012136005A1 (fr) Procédé pour adresser un terminal m2m et un dispositif de plate-forme m2m
CN102804738A (zh) 机器对机器的网关架构和功能
CN111771359A (zh) 用于连接通信网络的方法和系统
EP3941006B1 (fr) Système et procédé pour le transport et l'optimisation de trafic internet dans un réseau d'acheminement de trajet sélectionné par source
US20250088937A1 (en) System and method for active standby policy based routing in a network
KR102023137B1 (ko) 연합형 진화 패킷 코어 서비스 버스를 위한 시스템 및 방법
US20250088936A1 (en) System and method for hybrid routing in 5g networks
US20240365205A1 (en) System and method for performing ingress/egress active -active routing in 5g networks
EP4402881A1 (fr) Système et procédé de routage secondaire primaire dans des réseaux 5g
Mahmod et al. Review and evaluation of the proposed wireless Mesh routing protocols
JP6296736B2 (ja) 経路制御装置
CN112737811A (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: 11862958

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

Country of ref document: EP

Kind code of ref document: A1