WO2014183369A1 - Procédé et dispositif de traitement de surveillance, et passerelle m2m - Google Patents

Procédé et dispositif de traitement de surveillance, et passerelle m2m Download PDF

Info

Publication number
WO2014183369A1
WO2014183369A1 PCT/CN2013/084886 CN2013084886W WO2014183369A1 WO 2014183369 A1 WO2014183369 A1 WO 2014183369A1 CN 2013084886 W CN2013084886 W CN 2013084886W WO 2014183369 A1 WO2014183369 A1 WO 2014183369A1
Authority
WO
WIPO (PCT)
Prior art keywords
monitoring
gateway
event
identifier
configuration information
Prior art date
Application number
PCT/CN2013/084886
Other languages
English (en)
Chinese (zh)
Inventor
吴昊
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2014183369A1 publication Critical patent/WO2014183369A1/fr

Links

Classifications

    • 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]

Definitions

  • the present invention relates to the field of communications, and in particular to a monitoring processing method, apparatus, and M2M gateway.
  • M2M Machine to machine
  • BACKGROUND OF THE INVENTION Machine to machine (M2M) communication network extends the communication field and communication field of existing information communication networks, and acquires information from the physical world by embedding intelligence and communication capabilities in various possible objects. And based on the analysis and processing of this information to enhance and enhance the intelligence, interactivity and automation of existing information communication network services.
  • the M2M communication network has multiple network forms, and may be an independent physical network constructed separately, or a logical network built on an existing public communication network and various government-enterprise private networks.
  • the M2M communication network can be divided into three layers in terms of logical functions, namely: perceptual extension layer, network/service layer and application layer.
  • Perceptual extension layer It mainly realizes the collection, automatic identification and intelligent control of physical world information.
  • the various things in the physical world are not capable of communication.
  • Intelligent nodes such as sensors, actuators, smart devices, and radio frequency identification (RFID) readers collect information in the physical world and exchange information through the communication module and the network layer.
  • RFID radio frequency identification
  • Network/business layer Network/business layer support The transmission, routing and control of the sensing layer information provides support for the Internet of Things and people, things and things. Combined with the Internet of Things classification, the network forms specifically included in the network layer are: communication network, Internet, and industry network. The main components it contains are the M2M platform.
  • Application layer The application layer contains various specific IoT applications, ranging from public services to industry services.
  • the industry services can be public-oriented public services or industry-specific services that meet specific application needs within the industry. Among them, public services are basic services provided to the general public, such as smart homes and mobile payments.
  • Industry-specific services are usually tailored to the industry's own unique needs, such as smart grids, intelligent transportation, intelligent environments, etc.; some of the industry services can also be provided to the public, such as intelligent transportation, known as industry public services.
  • the main components it contains are M2M application servers.
  • the M2M gateway device relays the connection between the M2M terminal device to the M2M communication network service layer and the application layer. For example, some M2M terminal devices may only have short-range communication functions. In order to connect to a wide-area network, access to the WAN through the M2M gateway device is required. In addition, the M2M gateway device can be used to implement network connection aggregation and information. Convergence, simplifying network connectivity and corresponding management.
  • the M2M platform provides some common capabilities and support to M2M applications and provides an open interface for applications to access and use network resources and capabilities. By shielding the underlying specific network implementation to specific M2M applications, the complexity of IoT application development and the cost of deploying IoT application development can be simplified.
  • the M2M platform or the M2M server cannot grasp the operating state of the M2M gateway and the terminal peripheral, and thus cannot deal with possible faults.
  • the present invention provides a monitoring processing method, apparatus, and M2M gateway, so as to at least solve the M2M platform or the M2M server in the related art, and cannot grasp the operating state of the M2M gateway and the terminal peripheral, and thus cannot exist for possible existence. The problem of handling the failure.
  • a monitoring processing method including: a machine-to-machine M2M gateway receiving monitoring configuration information delivered by an M2M platform and/or an M2M server, where the monitoring configuration information includes a monitoring event;
  • the M2M gateway monitors the monitoring event in the monitoring configuration information.
  • the monitoring, by the M2M gateway, the monitoring event in the monitoring configuration information includes: determining whether the monitoring event occurs; and if the determination result is yes, reporting to the M2M platform and/or the The M2M server sends a monitoring report.
  • the monitoring configuration information includes reporting the configuration information
  • the monitoring report is sent to the M2M platform and/or the M2M server according to the reporting configuration information.
  • the monitoring event comprises at least one of: whether the terminal peripheral is disconnected, whether the number of connected terminal peripherals exceeds a predetermined number, whether the software download fails, whether the firmware download fails, whether the software installation fails, whether the firmware download is successful, Failure, IP address changed.
  • the monitoring, by the M2M gateway, the monitoring event in the monitoring configuration information includes: sending detection information to the terminal peripheral device; Determining whether the M2M gateway is disconnected from the terminal peripheral according to whether the feedback information of the terminal peripheral is received; if the determination result is yes, sending to the M2M platform and/or the M2M server
  • the monitoring report includes: at least one of the following: a monitoring identifier for identifying a monitoring task, an event identifier for identifying the monitoring event, an identifier of the terminal peripheral, and an identifier of the M2M gateway.
  • the monitoring, by the M2M gateway, the monitoring event in the monitoring configuration information comprises: connecting to the M2M gateway The number of the terminal peripherals is counted; whether the number of statistics is greater than a predetermined number; If the result is YES, the monitoring report is sent to the M2M platform and/or the M2M server, where the monitoring report includes at least one of the following: a monitoring identifier used to identify the monitoring task, used to identify the An event identifier of the monitoring event, a counted number of the terminal peripherals connected to the M2M gateway, and an identifier of the M2M gateway.
  • the monitoring, by the M2M gateway, the monitoring event in the monitoring configuration information, if the monitoring event is an IP address includes: determining whether a WAN IP address of the M2M gateway changes; If the result of the determination is yes, the monitoring report is sent to the M2M service platform and/or the M2M application server, where the monitoring report includes at least one of the following: a monitoring identifier used to identify the monitoring task, used for An event identifier identifying the monitoring event, an identifier of the M2M gateway, and a new IP address of the M2M gateway.
  • a monitoring processing method including: transmitting monitoring configuration information to a machine-to-machine M2M gateway, where the monitoring configuration information includes a monitoring event; receiving the M2M gateway to the monitoring A monitoring report obtained after the event is monitored.
  • the monitoring event comprises at least one of: whether the terminal peripheral is disconnected, whether the number of connected terminal peripherals exceeds a predetermined number, whether the software download fails, whether the firmware download fails, whether the software installation fails, whether the firmware download is successful, Failure, IP address changed.
  • a monitoring processing apparatus including: a first receiving module, configured to receive, by a machine-to-machine M2M gateway, monitoring configuration information delivered by an M2M platform and/or an M2M server, where the monitoring The configuration information includes a monitoring event, and the monitoring module is configured to monitor, by the M2M gateway, the monitoring event in the monitoring configuration information.
  • the monitoring module includes: a first determining unit, configured to determine whether the monitoring event occurs; the first sending unit is configured to, when the determining result of the determining unit is yes, to the M2M platform and/or Or the M2M server sends a monitoring report.
  • the monitoring module includes: a second sending unit, configured to send detection information to the terminal peripheral device when the monitoring event is that the terminal peripheral is disconnected; the second determining unit is configured to Determining, according to whether the feedback information of the terminal peripheral device is received, whether the M2M gateway is disconnected from the terminal peripheral device; and the third sending unit is configured to, when the determination result of the second determining unit is YES, to the The monitoring report is sent by the M2M platform and/or the M2M server, where the monitoring report includes at least one of the following: a monitoring identifier for identifying a monitoring task, an event identifier for identifying the monitoring event, and the terminal peripheral The identifier of the M2M gateway.
  • the monitoring module comprises: a statistical unit, configured to: if the monitoring event is a connected terminal peripheral number exceeds a predetermined number, the number of the terminal peripherals connected to the M2M gateway is performed
  • the third determining unit is configured to determine whether the number of statistics is greater than a predetermined number
  • the fourth sending unit is configured to, when the determining result of the third determining unit is yes, to the M2M platform and/or the M2M
  • the server sends a monitoring report, where the monitoring report includes at least one of the following: a monitoring identifier for identifying a monitoring task, an event identifier for identifying the monitoring event, and a statistical connection to the terminal of the M2M gateway.
  • the monitoring module includes: a fourth determining unit, configured to determine whether the WAN IP address of the M2M gateway changes if the monitoring event is an IP address change; the fifth sending unit is set to If the determination result of the fourth determining unit is yes, the monitoring report is sent to the M2M service platform and/or the M2M application server, where the monitoring report includes at least one of the following: And a monitoring identifier, an event identifier used to identify the monitoring event, an identifier of the M2M gateway, and a new IP address of the M2M gateway.
  • a machine to machine M2M gateway is provided, comprising the apparatus of any of the above.
  • a monitoring processing apparatus including: a first sending module, configured to send monitoring configuration information to a machine-to-machine M2M gateway, where the monitoring configuration information includes a monitoring event;
  • the receiving module is configured to receive a monitoring report obtained by the M2M gateway after monitoring the monitoring event.
  • the monitoring configuration information sent by the M2M platform and/or the M2M server is received by the machine to the machine M2M gateway, where the monitoring configuration information includes a monitoring event; and the M2M gateway monitors the monitoring configuration information.
  • the event is monitored to solve the problem that the M2M platform or the M2M server in the related technology cannot grasp the running state of the M2M gateway and the terminal peripheral, and therefore cannot deal with the possible faults, thereby achieving the problem according to the M2M platform and / /
  • the monitoring indication information issued by the M2M server is correspondingly supervised, which not only can effectively control the running state of the M2M gateway and the terminal peripherals, but also can timely process according to the acquired monitoring information, thereby effectively optimizing the system effect.
  • FIG. 1 is a flowchart of a monitoring processing method according to an embodiment of the present invention.
  • FIG. 2 is a flowchart of a monitoring processing method according to an embodiment of the present invention.
  • FIG. 3 is a structural block diagram of a monitoring processing apparatus 1 according to an embodiment of the present invention;
  • FIG. 5 is a block diagram of a preferred structure of the monitoring module 34 in the monitoring processing device 1 according to an embodiment of the present invention
  • FIG. 6 is a block diagram of a preferred configuration of the monitoring module 34 in the monitoring processing device 1 according to an embodiment of the present invention
  • FIG. 7 is a block diagram of a preferred structure of the monitoring module 34 in the monitoring processing device 1 according to an embodiment of the present invention
  • FIG. 8 is a schematic diagram of a machine to the monitoring module 34 according to an embodiment of the present invention
  • FIG. 9 is a structural block diagram of a monitoring processing apparatus 2 according to an embodiment of the present invention
  • FIG. 10 is a flowchart of a monitoring processing method according to a preferred embodiment of the present invention.
  • FIG. 1 is a flowchart 1 of a monitoring processing method according to an embodiment of the present invention. As shown in FIG. 1, the flow includes the following steps: Step S102, a machine-to-machine M2M gateway The monitoring configuration information sent by the M2M platform and/or the M2M server is received, where the monitoring configuration information includes a monitoring event. Step S104: The M2M gateway monitors the monitoring event in the monitoring configuration information.
  • the M2M gateway monitors the monitoring event according to the received monitoring configuration information, and expands the function of the M2M gateway in the related technology, that is, the M2M gateway not only has the function of connecting and managing the extended layer terminal device, but also can be the terminal.
  • the monitoring of the peripherals and their own operating status can not only solve the problem in the related art that the operating state of the M2M gateway and the terminal peripherals cannot be mastered, and therefore cannot deal with possible faults, and can also be used for the M2M gateway.
  • the operating state of the terminal peripherals is effectively controlled, and the acquired monitoring information can be processed in time to effectively optimize the system.
  • the M2M gateway can determine whether the monitoring event occurs; if the determination result is yes, send a monitoring report to the M2M platform and/or the M2M server, where the monitoring report is used for Report the occurrence of this monitoring event.
  • the monitoring configuration information includes the reporting configuration information
  • the monitoring report is sent to the M2M platform and/or the M2M server according to the reporting configuration information, where the reporting configuration information may include related content for describing the monitoring event, for example, It may be an identifier for identifying the monitoring event, a time when the monitoring event occurs, the M2M gateway identifier.
  • monitoring events may be multiple, for example, may include at least one of the following: whether the terminal peripheral is disconnected, whether the number of connected terminal peripherals exceeds a predetermined number, whether the software download fails, and whether the firmware download fails. Whether the software installation failed, the firmware download failed, and the IP address changed.
  • the software referred to above may be an application, and the firmware referred to above may be a driver. The following describes the differences in monitoring events separately.
  • the monitoring event can be monitored in the following simple manner: sending detection information to the terminal peripheral, wherein the detection information can be sent in various ways, for example, Send a Ping command to the terminal peripheral, or send a tracert command to the terminal peripheral; determine whether the terminal peripheral is connected to the M2M gateway according to whether the feedback information of the terminal peripheral is received, for example, receiving the terminal peripheral
  • the feedback information is that the terminal peripheral is connected to the M2M gateway, and when the feedback of the terminal peripheral is not received, it is considered that the terminal peripheral is not connected to the M2M gateway.
  • determining whether the monitoring event occurs may also be performed in various manners.
  • the monitoring report may be sent to the M2M platform and/or the M2M server, where the monitoring report includes at least one of the following: a monitoring identifier for identifying the monitoring task (for example, It can be set to 00001), an event identifier (for example, D1) for identifying a monitoring event, an identifier of the terminal peripheral, an identifier of the M2M gateway, and the like, and information related to the monitoring event.
  • a monitoring identifier for identifying the monitoring task for example, It can be set to 00001
  • an event identifier for example, D1
  • the M2M gateway monitors the monitoring event in the monitoring configuration information by using the following processing manner: counting the number of terminal peripherals connected to the M2M gateway, For example, the method of determining whether the terminal peripheral is connected to the M2M gateway, that is, the manner of sending the detection information to the terminal peripheral device, may be used to determine whether the number of statistics is greater than a predetermined number, wherein It should be noted that the number of statistics may be the number of M2M gateways that have been connected to the M2M gateway in the current state, or may be the number after the terminal peripherals that are connected; if the judgment result is yes (that is, the number of statistics exceeds
  • the monitoring report is sent to the M2M platform and/or the M2M server, where the monitoring report may also include at least one of the following: The identity (eg, may be 00002), the event identifier used to identify the monitoring event (eg, may be D2), the number of statistically
  • the M2M gateway monitors the monitoring event in the monitoring configuration information by using the following processing: determining whether the WAN IP address of the M2M gateway is changed; if the judgment result is yes,
  • the M2M service platform and/or the M2M application server sends a monitoring report, where the monitoring report may include at least one of the following: a monitoring identifier for identifying the monitoring task (for example, may be 0005), and an event identifier for identifying the monitoring event ( For example, it can be D5), the identity of the M2M gateway, and the new IP address of the M2M gateway.
  • a monitoring identifier for identifying the monitoring task for example, may be 0005
  • an event identifier for identifying the monitoring event For example, it can be D5
  • the identity of the M2M gateway for example, it can be D5
  • the new IP address of the M2M gateway the various identifiers listed above are only a relatively simple embodiment, and the implementation of the present invention is not limited.
  • FIG. 2 is a second flowchart of a monitoring processing method according to an embodiment of the present invention.
  • the flow includes the following steps: Step S202, to a machine to a machine
  • the monitoring configuration information is sent by the M2M gateway, where the monitoring configuration information includes a monitoring event.
  • the monitoring event may be at least one of the following: whether the terminal peripheral is disconnected, and the number of connected terminal peripherals exceeds a predetermined number. Whether the software download fails, whether the firmware download fails, whether the software installation fails, whether the firmware download fails, or whether the IP address is changed; Step S204, receiving a monitoring report obtained by the M2M gateway monitoring the monitoring event.
  • FIG. 3 is a structural block diagram of a monitoring processing apparatus 1 according to an embodiment of the present invention. As shown in FIG. 3, the apparatus includes a first receiving module 32 and a monitoring module 34. The apparatus will be described below.
  • the first receiving module 32 is configured to receive the monitoring configuration information sent by the M2M platform and/or the M2M server, where the monitoring configuration information includes a monitoring event, and the monitoring module 34 is connected to the first receiving module. 32.
  • the monitoring module 34 is connected to the first receiving module. 32.
  • 4 is a block diagram of a preferred structure of the monitoring module 34 in the monitoring processing device 1 according to an embodiment of the present invention. As shown in FIG. 4, the monitoring module 34 includes a first determining unit 42 and a first transmitting unit 44. The device is described.
  • the first determining unit 42 is configured to determine whether the monitoring event occurs; the first sending unit 44 is connected to the first determining unit 42 and is configured to, when the determination result of the first determining unit 42 is YES, to the M2M platform and / or M2M server sends monitoring reports.
  • 5 is a block diagram of a preferred structure of the monitoring module 34 in the monitoring processing device 1 according to an embodiment of the present invention. As shown in FIG. 5, the monitoring module 34 includes a second transmitting unit 52, a second determining unit 54, and a third transmitting unit. 56. The monitoring module 34 will be described below.
  • the second sending unit 52 is configured to send the detection information to the terminal peripheral device when the monitoring event is that the terminal peripheral is disconnected; the second determining unit 54 is connected to the second sending unit 52, and is set according to whether Receiving feedback information of the terminal peripheral device to determine whether the M2M gateway is disconnected from the terminal peripheral device; the third sending unit 56 is connected to the second determining unit 54 and configured to determine that the result of the second determining unit 54 is If yes, the monitoring report is sent to the M2M platform and/or the M2M server, where the monitoring report includes at least one of the following: a monitoring identifier for identifying the monitoring task, an event identifier for identifying the monitoring event, and a terminal peripheral. Identification, the identity of the M2M gateway.
  • FIG. 6 is a block diagram 3 of a preferred structure of the monitoring module 34 in the monitoring processing device 1 according to an embodiment of the present invention.
  • the monitoring module 34 includes a statistical unit 62, a third determining unit 64, and a fourth transmitting unit 66.
  • the monitoring module 34 will be described below.
  • the statistic unit 62 is configured to count the number of terminal peripherals connected to the M2M gateway if the monitoring event is the number of connected terminal peripherals exceeds a predetermined number; the third determining unit 64 is connected to the statistic unit 62 Is set to determine whether the number of statistics is greater than a predetermined number; the fourth transmitting unit 66 is connected to the third determining unit 64, and is set to the M2M platform and/or if the determination result of the third determining unit 64 is YES. Or the M2M server sends a monitoring report, where the monitoring report may include at least one of the following: a monitoring identifier for identifying the monitoring task, an event identifier for identifying the monitoring event, and a counted number of terminal peripherals connected to the M2M gateway.
  • FIG. 7 is a block diagram of a preferred structure of the monitoring module 34 in the monitoring processing device 1 according to an embodiment of the present invention. As shown in FIG. 7, the monitoring module 34 includes a fourth determining unit 72 and a fifth transmitting unit 74. The monitoring module 34 is described. The fourth determining unit 72 is configured to determine whether the WAN IP address of the M2M gateway changes if the monitoring event is an IP address is changed.
  • the fifth sending unit 74 is connected to the fourth determining unit 72, and is configured to be If the determination result of the fourth determining unit 72 is yes, the monitoring report is sent to the M2M service platform and/or the M2M application server, where the monitoring report includes at least one of the following: The monitoring identifier, the event identifier used to identify the monitoring event, the identifier of the M2M gateway, and the new IP address of the M2M gateway.
  • a machine-to-machine M2M gateway is also provided in this embodiment.
  • FIG. 8 is a structural block diagram of a machine-to-machine M2M gateway according to an embodiment of the present invention. As shown in FIG. 8, the M2M gateway 80 includes any of the above.
  • the monitoring processing device 82 is described.
  • FIG. 9 is a structural block diagram of a monitoring processing device 2 according to an embodiment of the present invention.
  • the device includes a first sending module 92 and a second receiving module. 94.
  • the device will be described below.
  • the first sending module 92 is configured to send monitoring configuration information to the machine-to-machine M2M gateway, where the monitoring configuration information includes a monitoring event;
  • the second receiving module 94 is connected to the second sending module 92, and is configured to receive the M2M gateway.
  • a monitoring report obtained after monitoring the monitoring event.
  • the gateway functions as a functional entity for connecting and managing the extended extension layer terminal device, and needs to be able to provide the M2M platform or the M2M application server M2M application execution state, the gateway software and the hardware running state, and the running state of the terminal device.
  • Statistic data and fault alarms are fed back according to the requirements of the M2M platform or the M2M application server.
  • a method for managing a machine type communication (MTC) terminal is proposed, that is, a method for monitoring an application and a device at a gateway, and the M2M gateway can be used in an M2M service platform or an M2M application.
  • MTC machine type communication
  • FIG. 10 is a flowchart of a monitoring processing method according to a preferred embodiment of the present invention. As shown in FIG.
  • the process includes the following steps: S1002: The M2M gateway receives the monitoring configuration message sent by the M2M service platform or the M2M application server, where the monitoring configuration message includes an event to be monitored, and the monitoring event may include one or more of the following definitions: Event D1: Whether the terminal peripheral is disconnected Event D2: The number of terminal peripherals connected to the gateway exceeds a predetermined value; Event G1: Gateway software or firmware download failed; Event G2: Gateway software or firmware installation failed; Event G3: Gateway IP address changed; Step S1004, M2M gateway according to Monitor event execution monitoring in configuration messages; Step S1006: When the event occurs, the M2M gateway sends a monitoring report to the M2M service platform or the M2M application server.
  • the invention will now be described in connection with preferred embodiments.
  • the first embodiment the SI, the M2M service platform or the M2M application server sends a monitoring configuration message to the gateway.
  • the monitoring configuration message may include the monitoring identifier, the monitoring object, and the report configuration: the monitoring identifier: used to uniquely identify a monitoring task. It is allocated by the M2M service platform or the M2M application server. For example, it can be set to 00001 in the preferred embodiment. It should be noted that here, 00001 is a simple implementation manner, but it is not limited to the unique monitoring identification mode; monitoring object: used to indicate objects that need to be monitored, including terminal peripherals or gateways.
  • the gateway can be set as a terminal peripheral; report configuration: includes events that need to be monitored and parameters that need to be included in the monitoring report after the event occurs. For example, in the preferred embodiment, it can be set as: Event - ⁇ ID: D1; Timeout interval: N milliseconds; Report parameters: (event identifier, disconnected terminal peripheral identifier, event occurrence time, gateway identifier) ⁇ S2
  • the gateway parses the event identifier D1 in the monitoring configuration information according to the local event definition list to determine whether the monitoring terminal peripheral is disconnected. Then, the gateway uses the ping or tracert command, and the timeout interval parameter in the command is set to the timeout interval parameter N in the monitoring configuration information.
  • the gateway detects that the terminal peripheral is disconnected, sends a monitoring report to the M2M service platform or the M2M application server, where the monitoring report includes: monitoring identifier: 00001, event identifier: Dl, disconnected terminal peripheral identifier, Event occurrence time, gateway ID.
  • monitoring report includes: monitoring identifier: 00001, event identifier: Dl, disconnected terminal peripheral identifier, Event occurrence time, gateway ID.
  • the S2, the M2M service platform or the M2M application server sends a monitoring configuration message to the gateway.
  • the monitoring configuration message may include the monitoring identifier, the monitoring object, and the report configuration: Monitoring identifier: 00002. Monitored by: Terminal Peripheral Report Configuration: Event - ⁇ Identification: D2; Maximum: M; Report Parameters: (Event ID, number of terminal peripherals connected to the gateway, event occurrence time, gateway ID) ⁇
  • the gateway after receiving the monitoring configuration information, the gateway reads the address of the locally stored terminal peripheral, uses the ping command to detect whether each terminal peripheral is connected to the gateway, and counts the number of terminal peripherals that are normally connected.
  • the SI2, the M2M service platform or the M2M application server sends a monitoring configuration message to the gateway.
  • the monitoring configuration message may include the monitoring identifier, the monitoring object, and the report configuration: The monitoring identifier: 00003.
  • Monitoring object Gateway Report configuration: Event - ⁇ ID: G1; Report parameters: (event ID, event occurrence time, gateway ID)
  • the S2, the M2M service platform, or the M2M application server sends a monitoring configuration message to the gateway.
  • the monitoring configuration message may include the monitoring identifier, the monitoring object, and the report configuration: Monitoring identifier: 00004.
  • Monitoring Object Gateway Report Configuration: Event -
  • the S2, the M2M service platform or the M2M application server sends a monitoring configuration message to the gateway.
  • the monitoring configuration message may include the monitoring identifier, the monitoring object, and the report configuration: The monitoring identifier: 00005.
  • Monitoring object Gateway Report configuration: Event - ⁇ ID: G3; Report parameters: (event ID, event occurrence time, gateway ID)
  • the gateway After receiving the monitoring configuration message, the gateway monitors the IP address of the gateway WAN. If the IP address changes, the monitoring report is sent to the M2M service platform or the M2M application server.
  • the monitoring report includes: 00005, Event ID: G3, event occurrence time, gateway ID.

Landscapes

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

Abstract

L'invention concerne un procédé et un dispositif de traitement de surveillance, et une passerelle M2M. Le procédé comprend les étapes suivantes : une passerelle de machine à machine (M2M) reçoit des informations de configuration de surveillance, qui sont délivrées par une plate-forme M2M et/ou un serveur M2M, les informations de configuration de surveillance comprenant un événement de surveillance; et la passerelle M2M surveille l'événement de surveillance dans les informations de configuration de surveillance. Grâce à la présente invention, le problème de l'art antérieur, à savoir qu'il est impossible pour la plate-forme M2M ou le serveur M2M de traiter les défaillances possibles en raison de leur incapacité à maîtriser l'état de fonctionnement des passerelles et des périphériques terminaux M2M est résolu, permettant ainsi une supervision en conséquence en fonction des informations d'indication de surveillance qui sont délivrées par la plate-forme M2M et/ou le serveur M2M, et non seulement l'état de fonctionnement de la passerelle et des périphériques terminaux M2M peut être maîtrisé efficacement, mais un traitement rapide peut également être effectué en fonction des informations de surveillance obtenues, optimisant ainsi efficacement le système.
PCT/CN2013/084886 2013-05-17 2013-10-09 Procédé et dispositif de traitement de surveillance, et passerelle m2m WO2014183369A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310185760.XA CN104168597A (zh) 2013-05-17 2013-05-17 监控处理方法、装置及m2m网关
CN201310185760.X 2013-05-17

Publications (1)

Publication Number Publication Date
WO2014183369A1 true WO2014183369A1 (fr) 2014-11-20

Family

ID=51897625

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/084886 WO2014183369A1 (fr) 2013-05-17 2013-10-09 Procédé et dispositif de traitement de surveillance, et passerelle m2m

Country Status (2)

Country Link
CN (1) CN104168597A (fr)
WO (1) WO2014183369A1 (fr)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106162715A (zh) * 2015-04-28 2016-11-23 中兴通讯股份有限公司 监控管理方法及装置
CN107295554A (zh) * 2016-03-30 2017-10-24 中兴通讯股份有限公司 一种管理应用状态的方法和装置

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056128A (zh) * 2009-10-30 2011-05-11 中兴通讯股份有限公司 机器类通讯终端信息的获取方法和系统
CN102056140A (zh) * 2009-11-06 2011-05-11 中兴通讯股份有限公司 机器类通讯终端信息的获取方法和系统
CN102158835A (zh) * 2010-02-12 2011-08-17 华为技术有限公司 机器类型通信信息传输方法和设备及系统
US20130039277A1 (en) * 2010-04-26 2013-02-14 Zte Corporation Machine type communication event reporting method, device and system

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5894193B2 (ja) * 2011-02-11 2016-03-23 インターデイジタル パテント ホールディングス インコーポレイテッド マシンツーマシン（ｍ２ｍ）エンティティを管理するシステム、方法、および装置
WO2013049912A1 (fr) * 2011-10-07 2013-04-11 Benbria Corporation Système de notification

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102056128A (zh) * 2009-10-30 2011-05-11 中兴通讯股份有限公司 机器类通讯终端信息的获取方法和系统
CN102056140A (zh) * 2009-11-06 2011-05-11 中兴通讯股份有限公司 机器类通讯终端信息的获取方法和系统
CN102158835A (zh) * 2010-02-12 2011-08-17 华为技术有限公司 机器类型通信信息传输方法和设备及系统
US20130039277A1 (en) * 2010-04-26 2013-02-14 Zte Corporation Machine type communication event reporting method, device and system

Also Published As

Publication number Publication date
CN104168597A (zh) 2014-11-26

Similar Documents

Publication Publication Date Title
US11770317B2 (en) Internet of Things event management systems and methods
CN108432282B (zh) 用于通过无线通信管理电子装置的方法和设备
WO2014056344A1 (fr) Procédé et dispositif de surveillance
CN105580327A (zh) 用于在m2m系统中传送通知消息的方法及其装置
CN103944746A (zh) 一种双机热备的方法及装置
WO2014056345A1 (fr) Appareil et procédé de gestion permettant de surveiller une tâche
CN106993043B (zh) 基于代理的数据通信系统和方法
WO2011150707A1 (fr) Procédé et système de gestion d'états de terminal ou d'événements de terminal dans un service de communication machine-machine ou machine-homme ou homme-machine (m2m)
CN102340410A (zh) 集群管理系统及方法
JP2016511451A (ja) ネットワーク機能を開くためのシステムおよび方法、ならびに関連するネットワーク要素
CN111866063A (zh) 一种工业物联网ai算法的在线更新系统、方法及装置
CN110809262B (zh) 一种基于coap协议的物联网设备运维管理方法
WO2014166218A1 (fr) Procédé et appareil de gestion de défaut
WO2014183369A1 (fr) Procédé et dispositif de traitement de surveillance, et passerelle m2m
EP2883414B1 (fr) Rapports d'évènements de réseaux auto-organisateurs
CN117579651A (zh) 物联网系统
CN109144919B (zh) 一种接口转接方法及装置
CN103001832B (zh) 分布式文件系统中节点的检测方法和装置
EP2506605B1 (fr) Système et procédé de gestion de service basés sur la communication machine to machine
US20120072545A1 (en) Remote maintenance and monitoring service framework for heterogeneous device and system
CN117290428B (zh) 物联设备的数据管理方法、设备和可读存储介质
CN116846947A (zh) 一种设备接入方法及装置
CN115865651A (zh) 一种数据采集方法、装置、电子设备及存储介质
WO2024125802A1 (fr) Procédé de fonctionnement d'une entité ou d'une fonctionnalité de services communs pour un système de l'internet des objets, le système de l'internet des objets comprenant une pluralité de dispositifs de communication de l'internet des objets dans un réseau de télécommunication, système de l'internet des objets ou réseau de télécommunication, programme et support lisible par ordinateur
KR102012028B1 (ko) M2m 시스템에서 데이터의 송수신을 동적으로 제어하는 방법 및 장치

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

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

Country of ref document: EP

Kind code of ref document: A1