WO2011076001A1 - M2m网络管理系统及实现终端业务聚合和虚拟专用网的方法 - Google Patents

M2m网络管理系统及实现终端业务聚合和虚拟专用网的方法 Download PDF

Info

Publication number
WO2011076001A1
WO2011076001A1 PCT/CN2010/075053 CN2010075053W WO2011076001A1 WO 2011076001 A1 WO2011076001 A1 WO 2011076001A1 CN 2010075053 W CN2010075053 W CN 2010075053W WO 2011076001 A1 WO2011076001 A1 WO 2011076001A1
Authority
WO
WIPO (PCT)
Prior art keywords
platform
terminal
packet
level
serial number
Prior art date
Application number
PCT/CN2010/075053
Other languages
English (en)
French (fr)
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 中兴通讯股份有限公司
Publication of WO2011076001A1 publication Critical patent/WO2011076001A1/zh

Links

Classifications

    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00Programme-control systems
    • G05B19/02Programme-control systems electric
    • G05B19/418Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • G05B19/4185Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by the network communication
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00Data switching networks
    • H04L12/28Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/46Interconnection of networks
    • H04L12/4641Virtual LANs, VLANs, e.g. virtual private networks [VPN]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • GPHYSICS
    • G05CONTROLLING; REGULATING
    • G05BCONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00Program-control systems
    • G05B2219/30Nc systems
    • G05B2219/31From computer integrated manufacturing till monitoring
    • G05B2219/31198VPN virtual private networks
    • YGENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02PCLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • the present invention relates to the field of machine-to-machine and Internet of Things technologies, and more particularly to a machine-to-machine network management system.
  • Machine to Machine is a networked application and service centered on intelligent interaction of machine terminals.
  • M2M provides customers with a comprehensive information solution to meet customers' information needs for monitoring, command and dispatch, data collection and measurement.
  • the M2M platform provides unified M2M terminal management and device authentication to clients using M2M application services, and authenticates access methods that have not been implemented by existing SMS gateways.
  • the M2M platform supports multiple network access modes, provides standardized interfaces, makes data transmission simple and direct, and provides management functions such as data routing, monitoring, user authentication, and accounting. It is an indispensable part of M2M applications.
  • the mainstream method for implementing the M2M platform in the industry is to use a single platform.
  • the M2M terminal performs access authentication authentication on the M2M platform. After the authentication is passed, the M2M terminal sends its service data to the M2M platform, and the M2M platform meets its application requirements. .
  • the service of the single M2M platform is relatively simple.
  • the service is implemented through another application platform. For example, after logging in to the M2M platform, you can log in to the application platform to forward the service flow, but still stay at the assumption stage. There are no implementation plans for specific businesses.
  • M2M platform With the increasing number of M2M terminals, management tasks will become more and more arduous. For example, if company A has 100 terminals in area A, it is necessary to separately perform login verification on these 100 terminals, and issue task processing.
  • the technical problem to be solved by the present invention is to provide a machine-to-machine network management system and a method for realizing terminal service aggregation and virtual private network, solving the problem of heavy management tasks and serial number shortage of a single M2M platform, and realizing hierarchical management of terminals. And serial number reuse.
  • the present invention provides a machine-to-machine network management system, which includes: a multi-level M2M platform, each level of the M2M platform interacts with its upper and/or lower level M2M platform, the superior The M2M platform is set to: assign a serial number to the terminal and its next level M2M platform, and the final M2M platform is set to: assign a serial number to the terminal.
  • Each of the multi-level M2M platforms includes multiple M2M platforms of the same level.
  • the M2M platform of the same level is set to: ⁇ Use the same serial number field to assign serial numbers to the terminal and the next level M2M platform.
  • Each of the multi-level M2M platforms includes multiple M2M platforms of the same level, which are different.
  • the M2M platform with no M2M platform and no subordinate relationship is set to: ⁇ Use the same serial number field to assign the serial number to the M2M platform of the terminal and the next level.
  • the M2M platform of each level is set as: assigning a serial number to a terminal set, the end The terminal in the end set uses the same serial number; or assigns a serial number to each terminal in the terminal set;
  • the different final M2M platforms are configured to: Use the same sequence number field to assign a sequence number to a terminal set or a set of terminals belonging to the M2M platform.
  • the M2M platforms at the top level M2M platform are also set to: Implement the conversion of different M2M protocols between the upper and lower levels.
  • the present invention also provides a method for implementing terminal service aggregation, which is applied to a network management system of an M2M, and includes:
  • the device After the terminal logs in to the last-level M2M platform, the device sends a service application information message to the last-level M2M platform, where the service application information message includes: an M2M packet header and service information, where the M2M packet header carries the last-level M2M The serial number assigned by the platform to the terminal;
  • the M2M platform that receives the service application information packet replaces the sequence number carried in the M2M packet header of the service application information packet with the M2M platform that the upper-level M2M platform allocates for the service application information packet.
  • the serial number is sent to the upper-level M2M platform until the top-level M2M platform receives the service application information message.
  • the above methods also include:
  • the top-level M2M platform After receiving the service application information packet, the top-level M2M platform returns a service application response message to the M2M platform of the next-level M2M platform that sends the service application information, and the service application response message includes: an M2M packet a header and a service response information, where the M2M packet header carries a sequence number assigned by the top-level M2M platform to the M2M platform of the next level;
  • the M2M platform that receives the service application response message replaces the sequence number carried in the M2M packet header with the sequence number of the M2M platform that is sent to the next level to send the service application information packet, and the service is The application response message is sent to the next level M2M platform, and so on, until the last level M2M platform receives the service application response message;
  • the final M2M platform replaces the sequence number carried in the M2M4 header of the received service application response message with the sequence number of the terminal allocated to the service application information message, and responds to the service application. A message is sent to the terminal.
  • the steps of the terminal logging in to the last-level M2M platform include: The terminal sends a login message to the last-level M2M platform, where the login message includes: an M2M packet header and login information, where the M2M packet header carries the serial number assigned by the last-level M2M platform to the terminal;
  • the terminal M2M platform authenticates the terminal according to the serial number and the login information of the terminal. After the authentication is passed, the login response is returned to the terminal, where the login response includes: an M2M packet header and response information, the M2M The sequence number of the terminal is carried in the packet header.
  • the above methods also include:
  • the M2M platform that receives the service application information packet records a serial number or a port number of the service application information packet, and establishes a sequence of the serial number or the port number and the M2M platform that sends the service application information message. Correspondence information of the number;
  • the service application response message further includes a serial number or a port number of the corresponding service application information
  • the M2M platform that receives the service application response message is based on the serial number or the sending port included in the application response message. No.
  • the information of the corresponding relationship between the serial number and the sending port number and the serial number is obtained, and the serial number of the M2M platform that sends the service application information message of the next level is obtained.
  • the above methods also include:
  • the last stage M2M platform records the serial number or the sending port number of the service application information sent by the terminal, and establishes the correspondence relationship between the serial number or the sending port number and the serial number assigned by the last M2M platform to the terminal;
  • the service application response message further includes a serial number or a port number of the corresponding service application information text, and the last M2M platform queries the serial number or the sending port number according to the serial number or the sending port number included in the application response message. Sending the correspondence between the port number and the serial number, and knowing the serial number of the terminal that sends the service application information message.
  • the present invention also provides a method for implementing a virtual private network, which is applied to a machine-to-machine (M2M) network management system, and includes:
  • the M2M platform is logged in to the M2M platform from the top M2M platform until the second terminal belongs to the M2M platform;
  • the step of the first terminal logging in to the M2M platform at each level includes: The first terminal sends a service application information message to the top M2M platform, where the message includes: an M2M packet header and a packet body, where the M2M packet header carries the serial number assigned by the top M2M platform to the first terminal.
  • the "3 ⁇ 4 style" is at least one layer, and each layer of the text corresponds to the first-level M2M platform, and the upper layer of the message body carries the message of the next layer, and the last layer of the message body carries the login information;
  • the M2M platform that receives the service application information message sends the message to the next-level M2M platform according to the destination address in the packet body of the corresponding layer; the M2M platform that the first terminal needs to log in receives the report. After the text, the login operation is performed according to the login information.
  • the destination address, the virtual private network (VPN)_tag (TAG), and the VPN-value (VALUE) are carried in each layer of the packet, and the destination address is the next level of the M2M platform corresponding to the layer where the destination address is located.
  • the step of performing the login operation according to the login information includes: after the M2M platform that the first terminal is logged in receives the packet, after parsing the packet After the VPN-TAG of the layer packet, the login operation is performed according to the login information carried in the VPN_VALUE of the packet body.
  • the above methods also include:
  • the M2M platform After the M2M platform to be logged in by the first terminal completes the terminal login, the M2M platform returns a service application information message, and the message includes: an M2M packet header and a packet body, where the M2M packet header carries the The serial number of the M2M platform to which the terminal is to be logged in.
  • the packet body is at least one layer. Each layer of the packet body corresponds to the first-level M2M platform.
  • the upper layer packet carries the next layer of packets, and the last layer of the packet carries the login.
  • the M2M platform that receives the service application information packet sends the packet to the upper-level M2M platform according to the destination address in the packet body of the corresponding layer, until the top M2M platform receives the packet, and the M2M platform receives the packet.
  • the message is sent to the first terminal.
  • the destination address, the VPN_TAG, and the VPN_VALUE are carried in each of the packets, and the destination address is the serial number of the upper M2M platform of the M2M platform corresponding to the layer where the destination address is located, and the destination address of the last layer.
  • the packet, the VPN-VALUE of the last packet body carries the sequence number assigned by the top M2M platform to the first terminal and the login response information.
  • the above methods also include:
  • the device When the first terminal interacts with the second terminal in the M2M platform, the device sends a service application information message to the top M2M platform, where the message includes: an M2M packet header and a packet body, where the M2M packet header carries the top layer.
  • the M2M platform allocates a sequence number to the first terminal.
  • the packet body is at least one layer. Each layer of the packet body corresponds to the first-level M2M platform, and the upper layer packet body carries the next layer of the message, and the last layer of the message body. Carrying business information;
  • the M2M platform that receives the packet sends the message to the next-level M2M platform according to the destination address in the packet body of the corresponding layer; the M2M platform to which the first terminal belongs receives the message And performing interaction between the first terminal and the second terminal according to the service information.
  • the above methods also include:
  • the M2M platform to which the second terminal belongs returns a service application information message to the M2M platform, and the message includes: an M2M packet header and a packet body, where the M2M packet header carries the M2M platform to which the second terminal belongs.
  • the serial number, the >3 ⁇ 4 style is at least one layer, each layer of the text corresponds to the first-level M2M platform, and the upper layer of the packet carries the message of the next layer, and carries the interactive content information in the last layer of the message body;
  • the M2M platform that receives the service application information packet sends the packet to the upper-level M2M platform according to the destination address of the packet body in the corresponding layer, until the top M2M platform receives the packet, and the M2M platform receives the packet.
  • the message is sent to the first terminal.
  • the present invention provides a multi-level M2M platform, centrally manages terminals, and implements service aggregation and VPN functions of the terminal, thereby providing diversified, richer, and more integrated applications for the M2M platform in the Internet of Things.
  • the business development method improves the application competitiveness of M2M in the Internet of Things, and also plays the role of multiplexing serial numbers and saving serial number resources.
  • FIG. 2 is a flowchart of a method for implementing terminal service aggregation according to an embodiment of the present invention
  • FIG. 3 is a flowchart of a method for implementing a virtual private network according to an embodiment of the present invention.
  • the embodiment of the present invention implements service aggregation by deploying a multi-level M2M platform (hereinafter referred to as a platform), so as to conveniently manage terminals and implement VPN at the same time.
  • a multi-level platform can be deployed according to the actual situation, the top-level platform interacts with the platform of the next level, the intermediate-level platform interacts with the platform of the superior and lower-level platforms, and the final-level platform interacts with the platform of the upper-level platform, and the previous one
  • the level platform assigns a serial number to its next level platform, and the terminals can be managed under each level platform, and each level platform assigns a serial number to its lower terminal.
  • the system of the two-stage platform is taken as an example for description.
  • the relationship between the upper and lower platforms is the same as that of the second-level platform and the first-level platform described below.
  • the deployment top-level platform (hereinafter referred to as the primary platform) is the core platform, interconnected with the secondary platform (or the following multi-level platform), and assigns the serial number to the secondary platform under it and is responsible for the terminal.
  • each level contains multiple platforms of the same level.
  • the serial number field assigns a serial number to the next level platform, and the platform belonging to different platforms and having no subordinate relationship may also use the same serial number field to assign a serial number to the platform of the next level, in which case There is no conflict between the platform serial numbers.
  • the platforms at all levels plan the terminals registered under them, and assign serial numbers, which can be divided according to enterprises and regions, or can be divided according to priorities.
  • the planned serial number is the internal serial number, which can be freely allocated, only on the platform. (At two levels or more, it refers to all levels of platforms with assigned serial numbers below one level) Internal use.
  • each platform may assign a serial number to the terminals in the set or a serial number to each terminal in the set, and a serial number to the upper platform. That is, the serial number of the platform to which the collection belongs, and the processing initiated by each level of the platform is the serial number for the next level platform.
  • Different final platforms can also use the same sequence number field to assign serial numbers to terminal sets or terminals.
  • the terminal can log in to the final platform by using the serial number assigned by the final platform.
  • the serial number assigned by the final platform is not visible to the upper platform, and the final platform needs to use the upper platform allocation.
  • the serial number sends the terminal information to its upper level platform.
  • the terminal can also directly log in to the primary platform by using the serial number assigned by the primary platform, and then use the service mode to log in to access any level of the platform.
  • the secondary platform is used as an example. After the terminal logs in to the primary platform, the terminal The level platform sends a service application information message carrying the information of the login secondary platform, and the secondary platform performs the login operation of the terminal. After the terminal logs in to the secondary platform, the terminal can be mutually accessed with the terminal under the secondary platform. If the platform is a secondary or higher platform, the terminal sends the service application information packet to the primary platform again.
  • the packet is a two-layer packet.
  • the destination address of the first-layer packet is the second-layer platform.
  • the serial number, the destination address of the second layer packet is the serial number of the third layer platform
  • the second layer packet carries the login information of the login level three platform, and the primary platform and the secondary platform are respectively according to the first and second
  • the destination address of the layer packet is forwarded, and the packet arrives at the third-level platform.
  • the third-level platform parses the login information of the second-level packet, and then performs login processing. After the login is complete, the terminal can work with the third-level platform.
  • the terminal interacts, and so on, can realize the interaction between a certain terminal and the terminal under each platform.
  • the platforms at different levels need to convert different M2M protocols (such as China Telecom and China Mobile's M2M protocol) to achieve compatibility with different M2M protocols to avoid direct access to the primary platform. It is compatible with all the difficulties caused by the M2M protocol interface.
  • M2M protocols such as China Telecom and China Mobile's M2M protocol
  • the serial number assigned by the primary platform to the secondary platform is TF1 ⁇ TFN ( N > 1 ).
  • the secondary platform is a set of terminals (which can be a single enterprise or a terminal with common characteristics such as the same area) with the serial number TS1 ⁇ TSN (N > 1). If the serial number of the secondary platform is TF1, the terminal under the secondary platform corresponds to the same serial number TF1 for the primary platform.
  • the secondary platform can log in to the primary platform by using the serial number TFX of the secondary platform to which the terminal belongs when logging in to the terminal with the serial number TSX.
  • Figure 2 shows the process of the terminal logging in to the primary platform from the secondary platform to implement service aggregation for centralized management.
  • the process includes:
  • the terminal sends the login message to the secondary platform, where the login message includes the M2M packet header and the login information, and the M2M packet header carries the serial number TSX assigned by the secondary platform to the terminal;
  • the login information includes information such as passwords and digests for authentication.
  • the secondary platform authenticates the terminal according to the TSX and the login information. After the authentication is passed, the login response is returned to the terminal, where the login response includes the M2M packet header and the response information, and the M2M packet header carries the secondary platform as the terminal. Assigned serial number TSX;
  • the process of authentication includes: Checking whether the terminal is online and determining whether the password is expired. After the authentication is passed, the terminal logs in to the secondary platform.
  • the terminal After receiving the login response, the terminal sends a service application information packet to the secondary platform, where the service application information packet includes an M2M packet header and service information, and the M2M packet header carries the serial number assigned by the secondary platform to the terminal.
  • TSX TSX
  • the M2M ⁇ header carries the serial number assigned by the last M2M platform to the terminal.
  • the secondary platform After receiving the service application information packet, the secondary platform reports the service application information to the primary platform according to the serial number TF1 assigned by the primary platform to the secondary platform, and the secondary platform applies the M2M packet of the service application information packet.
  • the secondary platform carried in the header replaces the serial number TSX assigned by the terminal with the serial number TFX of the secondary platform;
  • the platform that receives the service application information message includes the last-level platform and the intermediate-level platform, and replaces the serial number carried in the M2M packet header with the serial number assigned by the upper-level platform. And sending the service application information message to the upper-level platform until the first-level platform receives the service application information message.
  • the secondary platform After receiving the service application information, the secondary platform also records the correspondence relationship between the serial number of the TSX and the service application information or the sending port number.
  • the platform that receives the service application information message establishes the correspondence relationship between the serial number or the serial number of the sending port number and the M2M platform of the sent message.
  • the serial number assigned by the secondary platform to the terminal is not visible to the primary platform, and the primary platform only sees TF1. Therefore, the purpose of service aggregation for TS1, TS2, ... TSN is achieved.
  • the primary platform returns a service application response message to the secondary platform, where the service application response message includes an M2M header and a service response information, and the M2M header carries the serial number TF1 of the secondary platform; in the case of the multi-level platform, the receiving Platform to business application response messages, including level 1 or below The platform of each level replaces the serial number carried in the M2M packet header with the serial number of the platform that is sent to the next level to send the service application information message, and sends the service application response message to the next level platform until the end The platform receives the business application response message.
  • the primary platform also carries the serial number of the corresponding service application information in the service response information (the transmission port number can also be used when using UDP) as the identifier.
  • the secondary platform After receiving the service response information, the secondary platform searches for the serial number assigned by the secondary platform of the terminal according to the serial number (or port number); in the multi-level case, the platform that receives the service application response message is based on the application response message.
  • the serial number or the sending port number included in the query query the correspondence information of the serial number or the sending port number and the serial number, and obtain the serial number of the platform of the next-level service application information message.
  • the last stage platform needs to record the serial number or the sending port number of the service application information packet sent by the terminal, and establish the correspondence relationship between the serial number or the sending port number and the serial number of the terminal. After receiving the application response message, the serial number is based on the serial number. Or send the port number, query the corresponding relationship information, and learn the serial number of the terminal that sends the service application information message.
  • the secondary platform replaces the TF1 carried in the service response information with the serial number TSX assigned by the secondary platform for the terminal, and sends the service response information to the terminal.
  • the final platform replaces the serial number carried in the M2M packet header of the received service application response message with the sequence number assigned to the terminal, and sends the service application response message to the terminal.
  • Figure 3 shows the process of the terminal logging in from the primary platform to the third-level platform to implement the VPN function. It is assumed that the serial number assigned by the primary platform to the terminal is TFX, the serial number assigned by the secondary platform to the terminal is TSX, and the tertiary platform is allocated for the terminal.
  • the serial number is TIX, and the process includes:
  • the terminal logs in to the primary platform, and sends a login message to the primary platform.
  • the login message includes an M2M packet header and login information, and the M2M packet header carries the primary platform serial number TFX of the terminal.
  • the primary platform performs authentication on the terminal according to the TFX and the login information. After the authentication is passed, the login response is returned to the terminal, where the login response includes the M2M packet header and the response information, and the M2M packet header carries the primary platform as the terminal. Assigned serial number TFX; 303: After receiving the login response, the terminal sends a service application information packet to the primary platform, where the service application information packet includes an M2M packet header and a packet body, and the M2M packet header carries a serial number assigned by the primary platform to the terminal.
  • the packet body contains the destination address of the packet body, VPN_TAG and VPN VALUE (value), the destination address is the serial number of the secondary platform to which the terminal belongs, and the VPN-VALUE carries the serial number TSX assigned by the secondary platform to the terminal. login information;
  • the platform is transparently transmitted to the secondary platform according to the destination address of the received service application information message.
  • the transparent transmission specifications of each operator are different.
  • the transparent transmission specification of the China Mobile M2M specification is TRANSDATA.
  • the secondary platform parses the received service application information sent by the primary platform, and parses the
  • the terminal After VPN-TAG, the terminal is authenticated according to the TSX and login information in the VPN-VALUE;
  • the secondary platform After the authentication is passed, the secondary platform returns the service application information to the primary platform, the M2M header carries the serial number of the secondary platform, and the destination address of the packet body carried in the M2M packet is TFX, VPN_TAG And the VPN-VALUE, the VPN VALUE contains the TSX and the login response information; the packet sent by the secondary platform to the primary platform is still the service flow message.
  • the primary platform After receiving the service application information message returned by the secondary platform, the primary platform forwards the application information to the terminal in a service flow manner according to the forwarding destination address TFX;
  • the terminal After parsing the received application information packet, the terminal parses the VPN-TAG, and confirms whether the login to the secondary platform is successful according to the login response information carried in the VPN-VALUE. If the login is successful, the terminal can initiate the login with the secondary platform. Terminal interaction;
  • the service application information packet is sent to the primary platform, and the difference between the packet and the packet sent by the terminal to the primary platform when the secondary platform is logged in (step 303) is , VPN—VALUE carries business information, not login information.
  • the secondary platform After receiving the exchanged message, the secondary platform completes the interaction between the terminal and the lower terminal according to the service information, and returns a service application information message to the primary platform, and the message is returned to the primary platform when the secondary platform is logged in.
  • the difference between the message is that the interactive content information is carried in the VPN_VALUE instead of the login response information.
  • the terminal logs in to the third-level platform, and sends a service application information packet to the primary platform.
  • the service application information packet includes an M2M packet header and a packet body, and the M2M packet header carries the TFX, and the packet body is Layer 2, the first layer corresponds to the primary platform, and the second layer corresponds to the secondary platform.
  • Each layer of the packet carries the destination address, VPN-TAN and VPN-VALUE, and the destination address of the first-layer packet is corresponding.
  • the serial number of the secondary platform, the destination address of the second layer is the serial number of the corresponding three-level platform, the VPN-VALUE of the first layer packet carries the TSX and the second layer packet, and the VPN of the second layer packet — VALUE carries login information for TIX and login to the third-level platform;
  • the primary platform After receiving the service application information packet, the primary platform sends the packet to the secondary platform according to the destination address of the first layer packet body. After receiving the packet, the secondary platform receives the packet according to the destination address of the second layer packet body. Send the message to the third-level platform;
  • the third-level platform After receiving the application information packet, the third-level platform parses the packet, parses the VPN_TAG of the second layer packet, and authenticates the terminal according to the TIX and the login information in the VPN-VALUE.
  • the third-level platform After the authentication is passed, the third-level platform returns a service application information message to the secondary platform, where the message includes: an M2M packet header and a packet body, and the M2M packet header carries the serial number of the third-level M2M platform, and the style The second layer, the first layer corresponds to the secondary platform, and the second layer corresponds to the primary platform.
  • Each layer of the packet carries the destination address, VPN-TAN and VPN-VALUE, and the destination address of the first layer packet is corresponding.
  • the serial number of the first-level platform, the destination address of the second layer " ⁇ " is the serial number assigned by the corresponding first-level platform to the terminal, and the VPN-VALUE of the first-layer packet body carries the TSX and the second-layer message body, The VPN-VALUE of the Layer 2 packet carries the TFX and login response information.
  • the secondary platform After receiving the service application information packet, the secondary platform sends the packet to the primary platform according to the destination address of the first layer packet body. After receiving the packet, the primary platform receives the packet according to the destination address of the second layer packet body. Send the packet to the terminal;
  • the terminal After parsing the received application information packet, the terminal parses the VPN_TAG of the second layer packet body, and then confirms whether the login to the third-level platform is successful according to the login response information carried in the VPN-VALUE. Initiate interaction with terminals under the three-level platform.
  • the service application information packet is sent to the primary platform, and the difference between the packet and the packet sent by the terminal to the primary platform when the third-level platform is logged in (step 309) is
  • the VPN-VALUE of the second layer of the packet carries the service information instead of the login information.
  • the third-level platform completes the interaction between the terminal and the next terminal according to the service information, and returns the service application information message to the primary platform.
  • the message is returned to the primary platform when the third-level platform is logged in.
  • the difference between the message is that the interactive content information is carried in the VPN_VALUE of the second layer message body instead of the login response information.
  • the secondary platform is adopted (if it is a multi-level platform of two or more levels, it is one) Platforms below the level) Implement the conversion of the M2M protocol.
  • the M2M network A is an M2M network deployed earlier, and the A specification is used.
  • the secondary platform needs to convert the M2M protocol and convert the M2M protocol A into the M2M protocol B.
  • the corresponding data is filled into the M2M information of the B specification corresponding to the primary platform, and sent to the primary platform, that is, the secondary platform implements the conversion process between different M2M protocols, Reduce interface pressure on the primary platform.
  • the three-level platform deployment is a protocol conversion by a three-level platform and/or a secondary platform.
  • the present invention provides a diversified, richer and more integrated service development method for the application of the M2M platform in the Internet of Things by deploying a multi-level M2M platform, centrally managing terminals, and implementing service aggregation and VPN functions of the terminal.
  • the application of M2M in the Internet of Things has the ability to compete, and it can also reuse the serial number and save the serial number resources.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Manufacturing & Machinery (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

M2M网络管理系统及实现终端业务聚合和虚拟专用网的方法
技术领域
本发明涉及机器对机器及物联网技术领域, 尤其涉及一种机器对机器的 网络管理系统。
背景技术
机器对机器(Machine to Machine, M2M )是一种以机器终端智能交互为 核心的网络化的应用与服务。 M2M通过在机器内部嵌入无线通信模块, 以无 线通信为接入手段, 为客户提供综合的信息化解决方案, 以满足客户对监控、 指挥调度、 数据釆集和测量等方面的信息化需求。
目前, 随着 M2M的不断普及, 其规模也在不断扩大, 各大运营商相继 推出了自己的 M2M协议, 物联网的发展趋势主要集中在终端的标准化和智 能化, 通信的多元化、 协同化和宽带化, 服务的综合化和泛在化, 目前物联 网的应用业务也是多种多样。 M2M作为物联网的承载应用, 必将得到更大规 模地发展。
M2M平台作为 M2M终端接入认证的平台, 向使用 M2M应用服务的客 户提供统一的 M2M终端管理和设备鉴权, 并对现有短信网关尚未实现的接 入方式进行鉴权。 M2M平台支持多种网络接入方式, 提供标准化的接口, 使 数据传输简单直接, 提供数据路由、 监控、 用户鉴权和计费等管理功能, 是 M2M应用不可或缺的部分。
目前, 业界实现 M2M平台的主流方法为釆用单一平台, M2M终端在 M2M平台进行接入认证鉴权, 认证通过后, M2M终端将其业务数据上才艮给 M2M平台, M2M平台满足其应用要求。
釆用单一 M2M平台的方式业务会比较单一, 目前已有通过另外的应用 平台来实现业务, 比如登录 M2M平台后可以登录到应用平台, 进行业务流 的转发处理, 但还停留在设想阶段, 并没有针对具体业务的实施方案。
并且, 上述方式仍然存在以下不足: ( 1 ) M2M平台随着 M2M终端数量的不断增加, 管理任务会变得愈加 繁重。 比如, 公司 A在区域 A有 100个终端, 则需要分别对这 100个终端分 别进行登录校验, 并下发任务处理。
( 2 )对于物联网国际化兼容不利, 因为不同 M2M基础协议可能并不相 同, 如果要在一个 M2M平台上兼容所有的接口难度势必会很大, 同时, 由 于业务的多样化和早期出现的一些小运营商平台, 也造成了 M2M的登录方 式不一致, 相互融合比较困难。
( 3 )一旦物联网规模化普及, 可能会出现 M2M终端的序列号短缺的问 题, 由于 M2M终端的序列号的分配方式不同, 对于序列号的升级也会存在 潜在的困难。
( 4 )没有对虚拟专用网 ( Virtual Private Network, VPN ) 的业务开展进 行具体应用的方案部署。
发明内容
本发明要解决的技术问题是提供一种机器对机器的网络管理系统及实现 终端业务聚合和虚拟专用网的方法, 解决单 M2M平台管理任务繁重以及序 列号短缺的问题, 实现对终端的分级管理以及序列号复用。
为解决上述技术问题, 本发明提供一种机器对机器的网络管理系统, 其 包括: 多级 M2M平台, 每一级的 M2M平台与其上一级和 /或下一级的 M2M 平台交互, 上级的 M2M平台设置为: 为终端和其下一级的 M2M平台分配序 列号, 末级 M2M平台设置为: 为终端分配序列号。
所述多级 M2M平台中的每一级均包含多个同级的 M2M平台, 同级的 M2M平台是设置为: 釆用相同的序列号域为终端和下一级的 M2M平台分配 序列号。
所述多级 M2M平台中的每一级均包含多个同级的 M2M平台,分属不同
M2M平台且无上下级关系的 M2M平台是设置为: 釆用相同的序列号域为终 端和下一级的 M2M平台分配序列号。
所述每一级的 M2M平台是设置为: 为一个终端集合分配序列号, 该终 端集合中的终端釆用相同的序列号; 或为该终端集合中的每个终端均分配序 列号;
不同的末级 M2M平台是设置为: 釆用相同的序列号域为归属于该 M2M 平台的终端集合或终端集合中的终端分配序列号。
多级 M2M平台中, 在顶层 M2M平台下的各级 M2M平台还设置为: 实 现上下级之间不同 M2M协议的转换。
本发明还提供一种实现终端业务聚合的方法, 应用于 M2M的网络管理 系统中, 包括:
终端登录到末级 M2M平台后,向该末级 M2M平台发送业务应用信息报 文, 该业务应用信息报文包括: M2M报文头和业务信息, 该 M2M报文头中 携带所述末级 M2M平台为该终端分配的序列号; 以及
接收到所述业务应用信息报文的 M2M平台将该业务应用信息报文的 M2M报文头中携带的序列号替换为上一级 M2M平台为该接收到业务应用信 息报文的 M2M平台分配的序列号, 并将该业务应用信息报文发送给上一级 M2M平台, 直到顶层 M2M平台接收到所述业务应用信息报文。
上述方法还包括:
所述顶层 M2M平台接收到业务应用信息报文后, 向发送该业务应用信 息才艮文的该顶层 M2M平台下一级的 M2M平台返回业务应用响应消息,该业 务应用响应消息包括: M2M报文头和业务响应信息, 该 M2M报文头中携带 所述顶层 M2M平台为所述下一级的 M2M平台分配的序列号;
接收到所述业务应用响应消息的 M2M平台将所述 M2M报文头中携带的 序列号替换为分配给下一级的发送所述业务应用信息报文的 M2M平台的序 列号, 并将该业务应用响应消息发送给该下一级的 M2M平台, 以此类推, 直到所述末级 M2M平台接收到该业务应用响应消息; 以及
所述末级 M2M平台将接收到的所述业务应用响应消息的 M2M4艮文头中 携带的序列号替换为分配给发送所述业务应用信息报文的终端的序列号, 并 将该业务应用响应消息发送给该终端。
所述终端登录末级 M2M平台的步骤包括: 所述终端向末级 M2M平台发送登录报文, 该登录报文包括: M2M报文 头和登录信息,该 M2M报文头中携带所述末级 M2M平台为该终端分配的序 列号; 以及
所述末级 M2M平台根据所述终端的序列号和登录信息对该终端进行鉴 权, 鉴权通过后, 向该终端返回登录响应, 该登录响应包括: M2M报文头和 响应信息, 该 M2M报文头中携带所述终端的序列号。
上述方法还包括:
所述接收到所述业务应用信息报文的 M2M平台记录该业务应用信息报 文的流水号或发送端口号, 建立该流水号或发送端口号与发送该业务应用信 息报文的 M2M平台的序列号的对应关系信息;
所述业务应用响应消息还包括相对应的业务应用信息 文的流水号或发 送端口号, 所述接收到所述业务应用响应消息的 M2M平台根据所述应用响 应消息中包含的流水号或发送端口号, 查询流水号或发送端口号与序列号的 对应关系信息, 获知下一级的发送所述业务应用信息报文的 M2M平台的序 列号。
上述方法还包括:
所述末级 M2M平台记录终端发送的业务应用信息 文的流水号或发送 端口号, 建立该流水号或发送端口号与该末级 M2M平台为该终端分配的序 列号的对应关系信息;
所述业务应用响应消息中还包括相对应的业务应用信息 文的流水号或 发送端口号, 所述末级 M2M平台根据所述应用响应消息中包含的流水号或 发送端口号, 查询流水号或发送端口号与序列号的对应关系信息, 获知发送 所述业务应用信息报文的终端的序列号。
本发明还提供一种实现虚拟专用网的方法, 应用于机器对机器(M2M ) 的网络管理系统中, 包括:
第一终端若与 M2M平台下的第二终端交互,则从顶层 M2M平台开始逐 级登录各级 M2M平台, 直到登录到第二终端所属的 M2M平台;
所述第一终端登录各级 M2M平台的步骤包括: 所述第一终端向顶层 M2M平台发送业务应用信息报文, 该报文包括: M2M报文头和报文体, 该 M2M报文头中携带该顶层 M2M平台为该第一终 端分配的序列号, 该"¾文体为至少一层, 每一层 文体对应一级 M2M平台, 上一层报文体中携带下一层的报文, 末层报文体携带登录信息;
接收到所述业务应用信息报文的 M2M平台根据自身对应层的报文体中 的目的地址, 将该报文发送给下一级 M2M平台; 所述第一终端所要登录的 M2M平台接收到该报文后, 根据所述登录信息执行登录操作。
所述每一层报文体中均携带目的地址、虚拟专用网 ( VPN ) _标签 ( TAG ) 和 VPN—值 ( VALUE ) , 所述目的地址为该目的地址所在层对应的 M2M平 台的下一级 M2M平台的序列号, 所述 VPN VALUE包含该对应的 M2M平 台为第一终端分配的序列号和下一层的 文;
所述第一终端所要登录的 M2M平台接收到该报文后, 根据所述登录信 息执行登录操作的步骤包括: 所述第一终端所要登录的 M2M平台接收到该 报文后,在解析到末层报文体的 VPN— TAG后,根据该报文体的 VPN— VALUE 中携带的所述登录信息执行登录操作。
上述方法还包括:
所述第一终端所要登录的 M2M平台完成终端登录后,向上一级 M2M平 台返回业务应用信息报文, 该报文包括: M2M报文头和报文体, 该 M2M报 文头中携带所述第一终端所要登录的 M2M平台的序列号, 该报文体为至少 一层, 每一层报文体对应一级 M2M平台, 上一层报文体中携带下一层的报 文, 末层报文体携带登录响应信息;
接收到所述业务应用信息报文的 M2M平台根据自身对应层的报文体中 的目的地址,将该报文发送给上一级 M2M平台, 直到所述顶层 M2M平台接 收到该报文, 将该报文发送给所述第一终端。
所述每一层报文体中均携带目的地址、 VPN— TAG和 VPN— VALUE, 所 述目的地址为该目的地址所在层对应的 M2M平台的上一级 M2M平台的序列 号, 末层的目的地址为所述顶层 M2M平台为第一终端分配的序列号, 所述 VPN VALUE携带该对应的 M2M平台为第一终端分配的序列号和下一层的 报文, 末层报文体的 VPN— VALUE中携带所述顶层 M2M平台为第一终端分 配的序列号和所述登录响应信息。
上述方法还包括:
所述第一终端与 M2M平台下的第二终端进行交互时,向顶层 M2M平台 发送业务应用信息报文, 该报文包括: M2M报文头和报文体, 该 M2M报文 头中携带该顶层 M2M平台为该第一终端分配的序列号, 该报文体为至少一 层, 每一层报文体对应一级 M2M平台, 上一层报文体中携带下一层的报文, 在末层报文体中携带业务信息;
接收到所述报文的 M2M平台根据自身对应层的报文体中的目的地址, 将该 4艮文发送给下一级 M2M平台; 所述第一终端所属的 M2M平台接收到 该>¾文后, 根据所述业务信息进行所述第一终端与该第二终端的交互。
上述方法还包括:
所述第二终端所属的 M2M平台向上一级 M2M平台返回业务应用信息报 文, 该报文包括: M2M报文头和报文体, 该 M2M报文头中携带所述第二终 端所属的 M2M平台的序列号, 该>¾文体为至少一层, 每一层 文体对应一 级 M2M平台, 上一层报文体中携带下一层的报文, 在末层报文体中携带交 互内容信息;
接收到所述业务应用信息报文的 M2M平台根据自身对应层中的报文体 的目的地址,将该报文发送给上一级 M2M平台, 直到所述顶层 M2M平台接 收到该报文, 将该报文发送给所述第一终端。
综上所述, 本发明通过部署多级 M2M平台, 集中管理终端, 并实现终 端的业务聚合和 VPN功能, 为 M2M平台在物联网中的应用提供了多元化、 更加丰富且融合性更强的业务开展方法, 提高了 M2M在物联网中的应用竟 争能力, 同时也能起到复用序列号, 节约序列号资源的作用。 附图概述
Figure imgf000008_0001
图 2为本发明实施方式实现终端业务聚合的方法的流程图; 图 3为本发明实施方式实现虚拟专用网的方法的流程图。
本发明的较佳实施方式
本发明的实施方式通过部署多级 M2M平台 (以下简称平台) 实现业务 聚合, 以便于集中管理终端, 同时实现 VPN。 实际使用中, 可以根据实际情 况部署多级平台, 顶层平台与其下一级的平台交互, 中间级的平台与其上级 和下级的平台交互, 末级平台与其上一级的平台交互, 并且, 上一级平台为 其下一级平台分配序列号, 各级平台下均可管理终端, 各级平台各自为其下 终端分配序列号。 本实施例中以两级平台的系统为例对本发明进行说明, 釆 用两级以上的多级平台时, 上下两级平台的关系与以下描述的二级平台与一 级平台相同。
如图 1所示, 部署顶层平台 (以下称一级平台)为核心平台, 与其下的 二级平台 (或以下多级平台)互联, 为其下的二级平台分配序列号并负责终 端的相关处理, 每一级均包含多个同级平台, 为节约序列号资源, 实现序列 号的复用, 由于同级平台下的各平台相互之间均无影响, 因此, 同级平台可 釆用相同的序列号域为下一级平台分配序列号, 并且, 分属不同平台且无上 下级关系的平台也可以釆用相同的序列号域为下一级的平台分配序列号, 在 这种情况下, 平台序列号之间不会产生冲突。
各级平台对在其下登记的终端进行规划, 分配序列号, 可以按照企业和 区域等划分, 也可以按照优先级进行划分, 规划后的序列号为内部序列号, 可自由分配, 只在平台 (两级以上时指一级以下分配序列号的各级平台) 内 部使用。
对于划分为一个企业或者一个区域内的终端集合, 各平台可为该集合中 的终端分配一个序列号或为集合中的每个终端均分配一个序列号, 对上一级 平台则为一个序列号, 即该集合所属平台的序列号, 每一级平台发起的处理 都是针对下一级平台的序列号。 不同的末级平台同样可以釆用相同的序列号 域为终端集合或终端分配序列号。
终端可以使用末级平台为其分配的序列号登录到末级平台, 但是, 末级 平台分配的序列号对上一级平台不可见, 末级平台需要使用上一级平台分配 的序列号将终端信息发送给其上一级平台。
终端也可以使用一级平台为其分配的序列号直接登录到一级平台, 然后 使用业务方式逐级登录访问任意一级平台, 以二级平台为例, 终端登录到一 级平台后, 向一级平台发送携带登录二级平台信息的业务应用信息报文, 二 级平台执行终端的登录操作, 终端登录到二级平台后, 即可与二级平台下的 终端实现互访。 如果是二级以上平台, 登录到二级平台后, 终端再次向一级 平台发送业务应用信息报文, 该报文为两层报文体, 第一层报文体的目的地 址为第二层平台的序列号,第二层报文体的目的地址为第三层平台的序列号, 第二层报文体中携带登录三级平台的登录信息, 一级平台和二级平台分别根 据第一次和第二层报文体的目的地址进行转发, 报文到达三级平台, 三级平 台解析出第二层的报文体中的本级登录信息, 则进行登录处理, 完成登录后, 终端可以与三级平台下的终端进行交互, 并以此类推, 可以实现某一终端与 各级平台下的终端的交互。
并且, 在业务运行中除一级平台外, 各级平台需要对不同的 M2M协议 (例如中国电信和中国移动的 M2M协议)进行转换, 实现对不同 M2M协议 的兼容, 以避免直接在一级平台上兼容所有 M2M协议接口产生的困难。
下面结合附图对本发明的的具体实施方式进行说明。
殳设一级平台为二级平台分配的序列号为 TF1~TFN ( N > 1 )。 二级平台 为一个终端集合(可以为一个企业也可以为相同区域等具有共同特性的终端) 分配序列号 TS1~TSN ( N > 1 )。 若二级平台的序列号为 TF1 , 则对于一级平 台该二级平台下的终端对应一个相同的序列号 TF1。 二级平台可以在序列号 为 TSX的终端登录时, 使用该终端所属二级平台的序列号 TFX登录到一级 平台。
图 2为终端从二级平台登录到一级平台的过程, 从而实现业务聚合以便 于集中管理, 该过程包括:
201 : 终端向二级平台发送登录报文, 登录报文包括 M2M报文头和登录 信息, M2M报文头中携带二级平台为终端分配的序列号 TSX; 登录信息包括密码和摘要等信息, 用于鉴权。
202: 二级平台根据 TSX和登录信息对终端进行鉴权, 鉴权通过后, 向 终端返回登录响应, 该登录响应包括 M2M报文头和响应信息, M2M报文头 中携带二级平台为终端分配的序列号 TSX;
鉴权的过程包括: 检查终端是否在线以及判断密码是否到期等。 鉴权通 过后终端即登录到二级平台。
203: 终端接收到登录响应后, 向二级平台发送业务应用信息报文, 该业 务应用信息报文包括 M2M报文头和业务信息, M2M报文头中携带二级平台 为终端分配的序列号 TSX;
在多级平台的情况下, M2M ^艮文头中携带末级 M2M平台为终端分配的 序列号。
204: 二级平台接收到业务应用信息报文后, 根据一级平台为该二级平台 分配的序列号 TF1向一级平台上报业务应用信息, 二级平台将业务应用信息 报文的 M2M报文头中携带的二级平台为终端分配的序列号 TSX替换为二级 平台的序列号 TFX;
在多级平台的情况下, 接收到业务应用信息报文的平台, 包括末级平台 和中间各级平台, 将 M2M报文头中携带的序列号替换为上一级平台为其分 配的序列号, 并将业务应用信息报文发送给上一级平台, 直到一级平台接收 到业务应用信息报文。
二级平台接收到业务应用信息后,还记录 TSX与业务应用信息的流水号 或发送端口号的对应关系信息。
多级情况下, 接收到业务应用信息报文的平台建立流水号或发送端口号 与发送 文的 M2M平台的序列号的对应关系信息。
交互中, 二级平台为终端分配的序列号 TSX对一级平台不可见, 一级平 台只可见 TF1 , 因此, 达到了对 TS1、 TS2...TSN的业务聚合的目的。
205: 一级平台向二级平台返回业务应用响应消息, 该业务应用响应消息 包括 M2M 文头和业务响应信息, M2M 文头携带二级平台的序列号 TF1; 在多级平台的情况下, 接收到业务应用响应消息的平台, 包括一级以下 各级平台, 将 M2M报文头中携带的序列号替换为分配给下一级的发送上述 业务应用信息报文的平台的序列号, 并将业务应用响应消息发送给下一级平 台, 直到末级平台接收到业务应用响应消息。
一级平台还在业务响应信息中携带对应的业务应用信息的流水号 (釆用 UDP时还可釆用发送端口号)作为标识。
206: 二级平台接收到业务响应信息后, 根据流水号(或端口号)查找终 端的二级平台为终端分配的序列号; 多级情况下, 接收到业务应用响应消息的平台根据应用响应消息中包含 的流水号或发送端口号,查询流水号或发送端口号与序列号的对应关系信息, 获知下一级的发送业务应用信息报文的平台的序列号。
末级平台需要记录终端发送的业务应用信息报文的流水号或发送端口 号, 建立该流水号或发送端口号与终端的序列号的对应关系信息, 在接收到 应用响应消息后, 根据流水号或发送端口号, 查询对应关系信息, 获知发送 业务应用信息报文的终端的序列号。
207: 二级平台将业务响应信息中 Μ2Μ · ^艮文头中携带的 TF1替换为二级 平台为终端分配的序列号 TSX, 并将业务响应信息发送给终端。
在多级平台的情况下, 末级平台将接收到的业务应用响应消息的 M2M 报文头中携带的序列号替换为分配给终端的序列号, 并将业务应用响应消息 发送给该终端。
图 3为终端从一级平台登录到三级平台实现 VPN功能的过程,假设一级 平台为终端分配的序列号为 TFX, 二级平台为终端分配的序列号为 TSX, 三 级平台为终端分配的序列号为 TIX, 该过程包括:
301 :终端登录一级平台,向一级平台发送登录报文,登录报文包括 M2M 报文头和登录信息, M2M报文头中携带终端的一级平台序列号 TFX;
302: 一级平台根据 TFX和登录信息对终端进行鉴权, 鉴权通过后, 向 终端返回登录响应, 该登录响应包括 M2M报文头和响应信息, M2M报文头 中携带一级平台为终端分配的序列号 TFX; 303: 终端接收到登录响应后, 向一级平台发送业务应用信息报文, 该业 务应用信息报文包括 M2M报文头和报文体, M2M报文头中携带一级平台为 终端分配的序列号 TFX, 报文体中包含报文体的目的地址、 VPN— TAG和 VPN VALUE (值), 目的地址为终端所属二级平台的序列号, VPN— VALUE 中携带二级平台为终端分配的序列号 TSX和登录信息;
304:—级平台根据接收到的业务应用信息报文的目的地址透传给二级平 台 - 各个运营商的透传规范不尽相同, 如, 中国移动 M2M规范的透传规范 为 TRANSDATA。
305 : 二级平台解析接收到的一级平台发送的业务应用信息, 解析到
VPN— TAG后, 根据 VPN— VALUE中的 TSX和登录信息对终端进行鉴权;
306: 鉴权通过后, 二级平台向一级平台返回业务应用信息 ^艮文, M2M 头中携带二级平台的序列号, 在 M2M报文体中携带报文体的目的地址为 TFX、 VPN— TAG和 VPN— VALUE, VPN VALUE包含 TSX和登录响应信息; 二级平台发送给一级平台的报文仍然为业务流报文。
307: 一级平台接收到二级平台返回的业务应用信息报文后, 根据转发目 的地址 TFX , 以业务流方式将应用信息^艮文转发给终端;
308: 终端解析接收到的应用信息报文, 解析到 VPN— TAG后, 根据 VPN— VALUE中携带的登录响应信息, 确认是否成功登录二级平台, 若成功 登录, 则可以发起与二级平台下的终端的交互;
若终端发起与二级平台下终端的交互, 则向一级平台发送业务应用信息 报文, 该报文与登录二级平台时终端发送给一级平台的报文(步骤 303中) 的区别为, VPN— VALUE中携带业务信息, 而非登录信息。 二级平台接收 到进行交互的报文后, 根据业务信息完成终端与其下终端的交互, 并向一级 平台返回业务应用信息报文, 该报文与登录二级平台时返回给一级平台的报 文(步骤 306中)的区别为, 在 VPN— VALUE中携带交互内容信息, 而非登 录响应信息。
309: 终端登录三级平台, 向一级平台发送业务应用信息报文, 该业务应 用信息报文包括 M2M报文头和报文体, M2M报文头中携带 TFX, 报文体为 二层, 第一层对应一级平台, 第二层对应二级平台, 每一层的报文体中均携 带目的地址、 VPN— TAN和 VPN— VALUE, 第一层报文体的目的地址为对应 的二级平台的序列号,第二层 文体的目的地址为对应的三级平台的序列号, 第一层报文体的 VPN— VALUE中携带 TSX和第二层报文体,第二层报文体的 VPN— VALUE中携带 TIX和登录三级平台的登录信息;
310: 一级平台接收到业务应用信息报文后, 根据第一层报文体的目的地 址将报文发送给二级平台, 二级平台接收到报文后, 根据第二层报文体的目 的地址将报文发送给三级平台;
311 : 三级平台接收到应用信息报文后, 解析该报文, 解析到第二层报文 体的 VPN— TAG后,根据 VPN— VALUE中的 TIX和登录信息对终端进行鉴权;
312: 鉴权通过后, 三级平台向二级平台返回业务应用信息报文, 该报文 包括: M2M报文头和报文体, M2M报文头中携带第三级 M2M平台的序列 号, 文体为二层, 第一层对应二级平台, 第二层对应一级平台, 每一层的 报文体中均携带目的地址、 VPN— TAN和 VPN— VALUE, 第一层报文体的目 的地址为对应的一级平台的序列号, 第二层 "^文体的目的地址为对应的一级 平台为终端分配的序列号,第一层报文体的 VPN— VALUE中携带 TSX和第二 层报文体, 第二层报文体的 VPN— VALUE中携带 TFX和登录响应信息;
313: 二级平台接收到业务应用信息报文后, 根据第一层报文体的目的地 址将报文发送给一级平台, 一级平台接收到报文后, 根据第二层报文体的目 的地址将报文发送给终端;
314:终端解析接收到的应用信息报文,解析到第二层报文体的 VPN— TAG 后,根据 VPN— VALUE中携带的登录响应信息,确认是否成功登录三级平台, 若成功登录, 则可以发起与三级平台下的终端的交互。
若终端发起与三级平台下终端的交互, 则向一级平台发送业务应用信息 报文, 该报文与登录三级平台时终端发送给一级平台的报文(步骤 309中) 的区别为, 第二层报文体的 VPN— VALUE中携带业务信息, 而非登录信息。 三级平台接收到进行交互的报文后, 根据业务信息完成终端与其下终端的交 互, 并向一级平台返回业务应用信息报文, 该报文与登录三级平台时返回给 一级平台的报文(步骤 312中) 的区别为, 在第二层报文体的 VPN— VALUE 中携带交互内容信息, 而非登录响应信息。 由于不同 M2M基础协议存在差异, 如果要在一级平台上兼容所有的接 口难度将会^ ^大, 因此, 本发明实施方式中通过二级平台 (若为两级以上的 多级平台则为一级以下的各级平台) 实现 M2M协议的转换。
假设 M2M网络 A为早期部署的 M2M网络, 釆用 A规范, 而一级平台 釆用 B规范部署,则二级平台需要起到转化 M2M协议的作用,将 M2M协议 A转化为 M2M协议 B, 在收到网络 A的终端登录和上报数据后, 将对应数 据填写到一级平台对应的 B规范的 M2M信息中, 发送到一级平台, 即由二 级平台实现不同 M2M协议之间转换处理, 以减少一级平台的接口压力。
对于两级以上的多级平台的实现, 例如, 三级平台部署则由三级平台和 / 或二级平台进行协议的转换。
以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。 本领域普通技术人员可以理解上述方法中的全部或部分步骤可通 过程序来指令相关硬件完成, 所述程序可以存储于计算机可读存储介质中, 如只读存储器、 磁盘或光盘等。 可选地, 上述实施例的全部或部分步骤也可 以使用一个或多个集成电路来实现。 相应地, 上述实施例中的各模块 /单元可 以釆用硬件的形式实现, 也可以釆用软件功能模块的形式实现。 本发明不限 制于任何特定形式的硬件和软件的结合。
工业实用性
本发明通过部署多级 M2M平台, 集中管理终端, 并实现终端的业务聚 合和 VPN功能, 为 M2M平台在物联网中的应用提供了多元化、 更加丰富且 融合性更强的业务开展方法, 提高了 M2M在物联网中的应用竟争能力, 同 时也能起到复用序列号, 节约序列号资源的作用。

Claims

权 利 要 求 书
1、 一种机器对机器的网络管理系统, 其包括: 多级机器对机器(M2M ) 平台, 每一级的 M2M平台与其上一级和 /或下一级的 M2M平台交互, 上级 的 M2M平台设置为:为终端和其下一级的 M2M平台分配序列号,末级 M2M 平台设置为: 为终端分配序列号。
2、 如权利要求 1所述的系统, 其中,
所述多级 M2M平台中的每一级均包含多个同级的 M2M平台, 同级的 M2M平台是设置为: 釆用相同的序列号域为终端和下一级的 M2M平台分配 序列号。
3、 如权利要求 1所述的系统, 其中,
所述多级 M2M平台中的每一级均包含多个同级的 M2M平台,分属不同 M2M平台且无上下级关系的 M2M平台是设置为: 釆用相同的序列号域为终 端和下一级的 M2M平台分配序列号。
4、 如权利要求 1所述的系统, 其中,
所述每一级的 M2M平台是设置为: 为一个终端集合分配序列号, 该终 端集合中的终端釆用相同的序列号; 或为该终端集合中的每个终端均分配序 列号;
不同的末级 M2M平台是设置为: 釆用相同的序列号域为归属于该 M2M 平台的终端集合或终端集合中的终端分配序列号。
5、 如权利要求 1所述的系统, 其中,
多级 M2M平台中, 在顶层 M2M平台下的各级 M2M平台还设置为: 实 现上下级之间不同 M2M协议的转换。
6、 一种实现终端业务聚合的方法, 应用于机器对机器(M2M ) 的网络 管理系统中, 包括:
终端登录到末级 M2M平台后,向该末级 M2M平台发送业务应用信息报 文, 该业务应用信息报文包括: M2M报文头和业务信息, 该 M2M报文头中 携带所述末级 M2M平台为该终端分配的序列号; 以及
接收到所述业务应用信息报文的 M2M平台将该业务应用信息报文的 M2M报文头中携带的序列号替换为上一级 M2M平台为该接收到业务应用信 息报文的 M2M平台分配的序列号, 并将该业务应用信息报文发送给上一级 M2M平台, 直到顶层 M2M平台接收到所述业务应用信息报文。
7、 如权利要求 6所述的方法, 该方法还包括:
所述顶层 M2M平台接收到业务应用信息报文后, 向发送该业务应用信 息才艮文的该顶层 M2M平台下一级的 M2M平台返回业务应用响应消息,该业 务应用响应消息包括: Μ2Μ · ^艮文头和业务响应信息, 该 M2M 4艮文头中携带 所述顶层 M2M平台为所述下一级的 M2M平台分配的序列号;
接收到所述业务应用响应消息的 M2M平台将所述 M2M报文头中携带的 序列号替换为分配给下一级的发送所述业务应用信息报文的 M2M平台的序 列号, 并将该业务应用响应消息发送给该下一级的 M2M平台, 以此类推, 直到所述末级 M2M平台接收到该业务应用响应消息; 以及
所述末级 M2M平台将接收到的所述业务应用响应消息的 M2M4艮文头中 携带的序列号替换为分配给发送所述业务应用信息报文的终端的序列号, 并 将该业务应用响应消息发送给该终端。
8、 如权利要求 6所述的方法, 其中, 所述终端登录末级 M2M平台的步 骤包括:
所述终端向末级 M2M平台发送登录报文, 该登录报文包括: M2M报文 头和登录信息,该 M2M报文头中携带所述末级 M2M平台为该终端分配的序 列号; 以及
所述末级 M2M平台根据所述终端的序列号和登录信息对该终端进行鉴 权, 鉴权通过后, 向该终端返回登录响应, 该登录响应包括: M2M报文头和 响应信息, 该 M2M报文头中携带所述终端的序列号。
9、 如权利要求 7所述的方法, 该方法还包括: 所述接收到所述业务应用信息报文的 M2M平台记录该业务应用信息报 文的流水号或发送端口号, 建立该流水号或发送端口号与发送该业务应用信 息报文的 M2M平台的序列号的对应关系信息;
所述业务应用响应消息还包括相对应的业务应用信息 文的流水号或发 送端口号, 所述接收到所述业务应用响应消息的 M2M平台根据所述应用响 应消息中包含的流水号或发送端口号, 查询流水号或发送端口号与序列号的 对应关系信息, 获知下一级的发送所述业务应用信息报文的 M2M平台的序 列号。
10、 如权利要求 7所述的方法, 该方法还包括:
所述末级 M2M平台记录终端发送的业务应用信息 文的流水号或发送 端口号, 建立该流水号或发送端口号与该末级 M2M平台为该终端分配的序 列号的对应关系信息;
所述业务应用响应消息中还包括相对应的业务应用信息 文的流水号或 发送端口号, 所述末级 M2M平台根据所述应用响应消息中包含的流水号或 发送端口号, 查询流水号或发送端口号与序列号的对应关系信息, 获知发送 所述业务应用信息报文的终端的序列号。
11、 一种实现虚拟专用网的方法, 应用于机器对机器(M2M )的网络管 理系统中, 包括:
第一终端若与 M2M平台下的第二终端交互,则从顶层 M2M平台开始逐 级登录各级 M2M平台, 直到登录到第二终端所属的 M2M平台;
所述第一终端登录各级 M2M平台的步骤包括:
所述第一终端向顶层 M2M平台发送业务应用信息报文, 该报文包括: M2M报文头和报文体, 该 M2M报文头中携带该顶层 M2M平台为该第一终 端分配的序列号, 该"¾文体为至少一层, 每一层 文体对应一级 M2M平台, 上一层报文体中携带下一层的报文, 末层报文体携带登录信息;
接收到所述业务应用信息报文的 M2M平台根据自身对应层的报文体中 的目的地址, 将该报文发送给下一级 M2M平台; 所述第一终端所要登录的 M2M平台接收到该报文后, 根据所述登录信息执行登录操作。
12、 如权利要求 11所述的方法, 其中,
所述每一层报文体中均携带目的地址、虚拟专用网 ( VPN ) _标签 ( TAG ) 和 VPN—值 ( VALUE ) , 所述目的地址为该目的地址所在层对应的 M2M平 台的下一级 M2M平台的序列号, 所述 VPN— VALUE包含该对应的 M2M平 台为第一终端分配的序列号和下一层的 文;
所述第一终端所要登录的 M2M平台接收到该报文后, 根据所述登录信 息执行登录操作的步骤包括: 所述第一终端所要登录的 M2M平台接收到该 报文后,在解析到末层报文体的 VPN— TAG后,根据该报文体的 VPN— VALUE 中携带的所述登录信息执行登录操作。
13、 如权利要求 12所述的方法, 该方法还包括:
所述第一终端所要登录的 M2M平台完成终端登录后,向上一级 M2M平 台返回业务应用信息报文, 该报文包括: M2M报文头和报文体, 该 M2M报 文头中携带所述第一终端所要登录的 M2M平台的序列号, 该报文体为至少 一层, 每一层报文体对应一级 M2M平台, 上一层报文体中携带下一层的报 文, 末层报文体携带登录响应信息;
接收到所述业务应用信息报文的 M2M平台根据自身对应层的报文体中 的目的地址,将该报文发送给上一级 M2M平台, 直到所述顶层 M2M平台接 收到该报文, 将该报文发送给所述第一终端。
14、 如权利要求 13所述的方法, 其中,
所述每一层报文体中均携带目的地址、 VPN— TAG和 VPN— VALUE, 所 述目的地址为该目的地址所在层对应的 M2M平台的上一级 M2M平台的序列 号, 末层的目的地址为所述顶层 M2M平台为第一终端分配的序列号, 所述 VPN VALUE携带该对应的 M2M平台为第一终端分配的序列号和下一层的 报文, 末层报文体的 VPN— VALUE中携带所述顶层 M2M平台为第一终端分 配的序列号和所述登录响应信息。
15、 如权利要求 14所述的方法, 该方法还包括: 所述第一终端与 M2M平台下的第二终端进行交互时,向顶层 M2M平台 发送业务应用信息报文, 该报文包括: M2M报文头和报文体, 该 M2M报文 头中携带该顶层 M2M平台为该第一终端分配的序列号, 该报文体为至少一 层, 每一层报文体对应一级 M2M平台, 上一层报文体中携带下一层的报文, 在末层报文体中携带业务信息;
接收到所述报文的 M2M平台根据自身对应层的报文体中的目的地址, 将该报文发送给下一级 M2M平台; 所述第一终端所属的 M2M平台接收到 该>¾文后, 根据所述业务信息进行所述第一终端与该第二终端的交互。
16、 如权利要求 15所述的方法, 该方法还包括:
所述第二终端所属的 M2M平台向上一级 M2M平台返回业务应用信息报 文, 该报文包括: M2M报文头和报文体, 该 M2M报文头中携带所述第二终 端所属的 M2M平台的序列号, 该>¾文体为至少一层, 每一层 文体对应一 级 M2M平台, 上一层报文体中携带下一层的报文, 在末层报文体中携带交 互内容信息;
接收到所述业务应用信息报文的 M2M平台根据自身对应层中的报文体 的目的地址,将该报文发送给上一级 M2M平台, 直到所述顶层 M2M平台接 收到该报文, 将该报文发送给所述第一终端。
PCT/CN2010/075053 2009-12-24 2010-07-08 M2m网络管理系统及实现终端业务聚合和虚拟专用网的方法 WO2011076001A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN2009102612675A CN102111288A (zh) 2009-12-24 2009-12-24 一种机器对机器的网络管理架构
CN200910261267.5 2009-12-24

Publications (1)

Publication Number Publication Date
WO2011076001A1 true WO2011076001A1 (zh) 2011-06-30

Family

ID=44175322

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2010/075053 WO2011076001A1 (zh) 2009-12-24 2010-07-08 M2m网络管理系统及实现终端业务聚合和虚拟专用网的方法

Country Status (2)

Country Link
CN (1) CN102111288A (zh)
WO (1) WO2011076001A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3905741A1 (en) * 2013-12-05 2021-11-03 Huawei Device Co., Ltd. Method and device for downloading profile of operator

Families Citing this family (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102970192B (zh) * 2011-09-01 2017-08-25 中兴通讯股份有限公司 一种m2m有线终端接入控制方法及系统
CN103023935B (zh) * 2011-09-23 2018-06-26 中兴通讯股份有限公司 M2m平台云系统及其处理m2m服务的方法
EP2798868B1 (en) * 2011-12-29 2016-03-09 Telefonaktiebolaget LM Ericsson (publ) Remote provisioning of 3gpp downloadable subscriber identity module for virtual machine applications
US10136244B2 (en) * 2014-02-10 2018-11-20 Zte Corporation Extending connectivity in a machine to machine communication system
JP6302096B2 (ja) 2014-02-24 2018-03-28 華為技術有限公司Huawei Technologies Co.,Ltd. M2mにおける情報処理方法および装置
CN108419218B (zh) * 2017-02-08 2021-01-08 知鑫知识产权服务(上海)有限公司 一种用于机器对机器通信的资源复用方法
CN107294766B (zh) * 2017-05-03 2020-09-22 上海上讯信息技术股份有限公司 一种集中管控的方法及系统
CN108449425A (zh) * 2018-04-10 2018-08-24 时枫娇 一种基于物联网的机床监控系统及其方法

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101180852A (zh) * 2005-05-23 2008-05-14 西门子股份有限公司 经由ip多媒体子系统ims的ip链路远程管理机器的方法和系统

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101180852A (zh) * 2005-05-23 2008-05-14 西门子股份有限公司 经由ip多媒体子系统ims的ip链路远程管理机器的方法和系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
J. D. WEGNER ET AL.: "IP Addressing and Subnetting, Including IPV6.", CHINA MACHINE PRESS., 1 February 2001 (2001-02-01) *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3905741A1 (en) * 2013-12-05 2021-11-03 Huawei Device Co., Ltd. Method and device for downloading profile of operator

Also Published As

Publication number Publication date
CN102111288A (zh) 2011-06-29

Similar Documents

Publication Publication Date Title
WO2011076001A1 (zh) M2m网络管理系统及实现终端业务聚合和虚拟专用网的方法
WO2019157955A1 (zh) 设备接入方法、相关平台及计算机存储介质
CN105763426B (zh) 一种基于多协议即时通信系统的物联网业务处理系统
CN108092884A (zh) 一种无线接入网关系统及应用方法
TWI360781B (en) Method for configuring a computer device using loa
WO2015143610A1 (zh) 一种nfv系统的业务实现方法及通信单元
KR100933365B1 (ko) 액세스 네트워크의 자원 관리 시스템 및 방법
CN110535627A (zh) 一种数据查询方法及区块链平台
CN103607430A (zh) 一种网络处理的方法和系统及网络控制中心
CN102724175A (zh) 泛在绿色社区控制网络的远程通信安全管理架构与方法
CN108322467A (zh) 基于ovs的虚拟防火墙配置方法、电子设备及存储介质
CN109787992A (zh) 一种通过视联网访问专网的方法和装置
CN111865633B (zh) 一种通信方法、装置及系统
CN106332010B (zh) 一种分级组网的宽带集群通信系统及其点到点呼叫方法
WO2012088882A1 (zh) 一种数据传输方法、系统及接入网关
CN104092684A (zh) 一种OpenFlow协议支持VPN的方法及设备
CN114205815A (zh) 一种5g专网认证控制的方法和系统
CN101459532A (zh) 一种多网口设备自动组网的方法及设备
CN101227361B (zh) 将客户端接入下一代网络的方法及系统
CN105141526B (zh) 虚拟网络通信的方法及装置
CN102137102B (zh) 一种支持多类信息发布方式的业务支撑平台实现方法
JPH0779367B2 (ja) 連結モードネットワークと非連結モードネットワークとの間のosiトランスポートリレーシステム
WO2013185696A2 (zh) 一种数据处理的方法与设备
CN101621528B (zh) 基于以太交换机集群管理的会话系统及会话通道实现方法
WO2012037744A1 (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: 10838564

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

Country of ref document: EP

Kind code of ref document: A1