WO2014166218A1 - 故障管理方法和装置 - Google Patents

故障管理方法和装置 Download PDF

Info

Publication number
WO2014166218A1
WO2014166218A1 PCT/CN2013/085086 CN2013085086W WO2014166218A1 WO 2014166218 A1 WO2014166218 A1 WO 2014166218A1 CN 2013085086 W CN2013085086 W CN 2013085086W WO 2014166218 A1 WO2014166218 A1 WO 2014166218A1
Authority
WO
WIPO (PCT)
Prior art keywords
fault
identifier
fault management
gateway
definition
Prior art date
Application number
PCT/CN2013/085086
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 中兴通讯股份有限公司
Priority to US14/904,434 priority Critical patent/US9949061B2/en
Priority to EP13881512.1A priority patent/EP3010182A4/en
Publication of WO2014166218A1 publication Critical patent/WO2014166218A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/38—Services specially adapted for particular environments, situations or purposes for collecting sensor information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0663—Performing the actions predefined by failover planning, e.g. switching to standby network elements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0654—Management of faults, events, alarms or notifications using network fault recovery
    • H04L41/0659—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities
    • H04L41/0661—Management of faults, events, alarms or notifications using network fault recovery by isolating or reconfiguring faulty entities by reconfiguring faulty entities
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0686—Additional information in the notification, e.g. enhancement of specific meta-data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/70—Services for machine-to-machine communication [M2M] or machine type communication [MTC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0813—Configuration setting characterised by the conditions triggering a change of settings
    • H04L41/082—Configuration setting characterised by the conditions triggering a change of settings the condition being updates or upgrades of network functionality

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a fault management method and apparatus.
  • the Machine to Machine (M2M) communication network extends the communication and communication fields 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 these Information analysis and processing to enhance and enhance the intelligence, interactivity and automation of existing ICT services.
  • M2M Machine to Machine
  • the M2M communication network has multiple network forms, and may be an independent physical network constructed separately, or may be 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, the perceptual extension layer, the network/service layer, and the application layer.
  • Perceptual extension layer 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 from the physical world and exchange information through the communication module and the network layer.
  • RFID radio frequency identification
  • the main components it contains are M2M terminal equipment and M2M gateway equipment.
  • Network/business layer The network/business layer supports the transmission, routing and control of the information of the sensing layer, and provides support for the communication of people, things and things in the Internet of Things.
  • the network forms included in the network layer are: communication network, Internet, and industry network.
  • the main components it contains are the M2M flat application layer:
  • the application layer contains various IoT applications, both public and industrial services.
  • the industry services can be public-oriented public services for the public, or they can meet the specific application needs of the industry. Industry-specific services. Among them, public services are basic services provided to the general public, such as smart homes and mobile payments.
  • Industry-specific services are usually oriented to the unique needs of the industry, for the services provided within the industry, such as smart grid, intelligent transportation, intelligent environment, etc. Service by industry can also be provided to the public, such as intelligent transportation, known as industry public service.
  • the main components it contains are M2M application servers.
  • the M2M gateway device relays the connection between the M2M terminal device and the service layer and the application layer of the M2M communication network.
  • Some M2M terminal devices may only have short-range communication functions.
  • access to the wide-area network is required through the M2M gateway device.
  • Another typical requirement is to use M2M gateway devices to achieve convergence of network connections. Convergence of information, simplifying network connections 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 network from M2M applications, it can simplify the complexity of IoT application development and reduce the cost of deploying IoT application development.
  • the embodiment of the invention provides a fault management method and device, which solves the problem of fault monitoring of the M2M platform.
  • the embodiment of the invention provides a fault management method, including:
  • the machine-to-machine M2M gateway receives the fault management task sent by the M2M service platform; and the M2M gateway performs the fault management task.
  • the fault management object is the M2M gateway or / and a terminal peripheral registered to the M2M gateway.
  • the fault management task includes a fault management task identifier, a fault management object, a fault identifier, and a fault handling manner definition.
  • the method further includes: before the M2M gateway receives the fault management task sent by the M2M service platform,
  • the M2M gateway receives and stores the fault management parameter sent by the M2M service platform, where the fault management parameter includes a fault identifier and a fault definition corresponding to the fault identifier.
  • the fault management task includes a fault management task identifier, a fault management object, a fault identifier, and a fault handling manner identifier.
  • the method further includes: before the M2M gateway receives the fault management task sent by the M2M service platform,
  • the M2M gateway receives and stores the fault management parameter sent by the M2M service platform, where the fault management parameter includes a fault identifier, a fault definition corresponding to the fault identifier, a fault processing mode identifier, and a fault processing manner definition.
  • the performing, by the M2M gateway, the fault management task includes:
  • the M2M gateway queries the fault definition corresponding to the fault identifier
  • the M2M gateway performs fault monitoring on the fault management object according to the fault definition obtained by the query.
  • the method further includes: after the M2M gateway performs the fault management task, the M2M gateway searches for a fault processing mode identifier corresponding to the fault when detecting a fault occurrence;
  • the embodiment of the present invention further provides a fault management apparatus, which is applied to a machine-to-machine M2M gateway, and the apparatus includes:
  • a task receiving module configured to: receive a fault management task sent by the M2M service platform;
  • An execution module configured to: perform the fault management task.
  • the fault management object is the M2M gateway or/and a terminal peripheral registered to the M2M gateway;
  • the fault management task includes a fault management task identifier, a fault management object, a fault identifier, and a fault handling manner definition;
  • the device also includes:
  • a first configuration module configured to: receive and store a fault management parameter sent by the M2M service platform, where the fault management parameter includes a fault identifier and a fault identifier corresponding to the fault identifier Righteousness.
  • the fault management task includes a fault management task identifier, a fault management object, a fault identifier, and a fault handling manner identifier;
  • the device also includes:
  • a second configuration module configured to: receive and store a fault management parameter sent by the service platform, where the fault management parameter includes a fault identifier, a fault definition corresponding to the fault identifier, a fault processing manner identifier, and a fault processing manner definition .
  • the execution module includes:
  • a fault definition query unit configured to: query a fault definition corresponding to the fault identifier;
  • the monitoring unit is configured to: perform fault monitoring on the fault management object according to the fault definition obtained by the query.
  • the device further includes: a fault processing module, where
  • the fault processing module includes:
  • An identifier searching unit is configured to: when detecting a fault, find a fault processing mode identifier corresponding to the fault;
  • Defining a query unit configured to: identify a query fault processing mode definition according to the fault handling manner;
  • the fault processing unit is configured to: perform a fault handling operation according to the fault processing mode definition.
  • the fault management method and device provided by the embodiment of the present invention realize fault management of the ⁇ 2 ⁇ platform, and solve the problem of fault monitoring of the ⁇ 2 ⁇ platform.
  • FIG. 1 is a flowchart of a fault management method according to Embodiment 1 of the present invention
  • 2 is a flowchart of a fault management method according to Embodiment 2 of the present invention
  • FIG. 3 is a flowchart of a fault management method according to Embodiment 3 of the present invention.
  • FIG. 4 is a schematic structural diagram of a fault management apparatus according to Embodiment 4 of the present invention.
  • FIG. 5 is a schematic structural diagram of an execution module 402 of FIG. 4;
  • FIG. 6 is a schematic structural diagram of the fault processing module 405 of FIG. 4. Preferred embodiment of the invention
  • 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 network from M2M applications, it can simplify the complexity of IoT application development and reduce the cost of deploying IoT application development.
  • embodiments of the present invention provide a fault management method and apparatus. Embodiments of the present invention will be described in detail below with reference to the accompanying drawings. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.
  • the gateway acts as a functional entity for connecting and managing the perceptual extension layer terminal equipment, and can handle the faults of the terminal peripherals and the gateway.
  • the embodiment of the present invention provides a fault management method, and uses the method to complete the M2M platform monitoring process. As shown in FIG. 1, the method includes the following steps:
  • Step 101 The M2M service platform sends a fault management parameter to the M2M gateway.
  • the configuration scheme of the fault management parameters includes:
  • Solution 1 The fault identifier, the fault definition corresponding to the fault identifier, the fault handling mode identifier, and the fault handling mode definition;
  • Solution 2 A fault definition corresponding to the fault identifier and the fault identifier.
  • Step 102 The M2M gateway receives and stores a fault management parameter sent by the M2M service platform. In this step, the gateway saves the received fault management parameters in the local database.
  • Step 103 The gateway receives the fault management task sent by the service platform.
  • the ⁇ 2 ⁇ gateway receives the fault management task sent by the ⁇ 2 ⁇ service platform.
  • the fault management task includes a fault management task identifier, a fault management object, a fault identifier, and a fault handling mode identifier.
  • the fault management task includes a fault management task identifier, a fault management object, Fault identification and fault handling method definition.
  • the fault management object involved in the embodiment of the present invention includes a gateway and/or a terminal peripheral registered to the gateway.
  • Step 104 The gateway performs the fault management task.
  • the gateway queries the fault definition corresponding to the fault identifier locally according to the fault identifier.
  • the ⁇ 2 ⁇ gateway queries the fault definition corresponding to the fault identifier, and then the ⁇ 2 ⁇ gateway performs fault monitoring on the fault management object according to the fault definition obtained by the query.
  • the gateway detects a failure, it performs a fault handling operation according to the fault handling method in the fault management task, as shown in steps 105 to 107.
  • Step 105 When detecting the fault, the gateway searches for the fault handling mode identifier corresponding to the fault.
  • Step 106 The gateway identifies the fault processing mode definition according to the fault processing manner.
  • Step 107 The gateway is defined according to the fault processing manner, and performs a fault processing operation.
  • the embodiment of the present invention provides a fault management method.
  • the process for monitoring the fault of the ⁇ 2 ⁇ platform by using the method is as shown in FIG. 2, and includes the following steps:
  • Step 201 The service platform sends fault management parameters to the gateway, and the fault management parameters are as shown in Table 1.
  • Step 202 The M2M gateway saves the fault management parameters sent by the M2M service platform locally.
  • Step 203 The M2M service platform sends the fault management task information to the M2M gateway, and the information carried in the fault management task is as shown in Table 2.
  • “11111111” is the identifier of the terminal peripheral A
  • "22222222” is the identifier of the terminal peripheral B
  • the fault identification in the fault information corresponds to the fault identification in the fault management parameter in the first step.
  • Step 204 The M2M gateway performs a fault management task.
  • the M2M gateway queries the device to be monitored according to the identifier of the fault management object, which is a terminal peripheral.
  • the M2M gateway sets a timer Timerl with a timing length of T1 seconds.
  • the timer is started at the beginning of each detection period, and the detection information is sent to the terminal peripheral A. After receiving the detection information, the terminal peripheral sends the detection information to the M2M gateway. Online feedback message. If the online feedback message of terminal peripheral A has not been received when the timer Timer1 expires, it is determined to be offline.
  • the M2M gateway After detecting that the terminal peripheral A is offline, the M2M gateway defines the fault management mode according to the fault management task information, that is, reports, sends a fault management report to the M2M service platform, and reports the report.
  • the information includes the fault management task identifier 10001.
  • the M2M gateway queries the device that needs to be monitored as the terminal peripheral B, and according to the identifier of the fault, it is queried whether the terminal peripheral B is offline.
  • the M2M gateway sets a timer Timer2, and the timing length is T2 seconds.
  • the timer Timer2 is started at the beginning of each detection period, and the detection information is sent to the terminal peripheral B. After receiving the detection information, the terminal peripheral sends the detection information to the M2M gateway. Online feedback message. If the online feedback message of the terminal peripheral B has not been received when the timer Timer2 expires, it is determined to be offline.
  • the M2M gateway After detecting that the terminal peripheral B is offline, the M2M gateway defines the fault management method according to the fault management task information, that is, reports the fault management report to the M2M service platform, and the report information includes the fault management task identifier 10002.
  • the M2M gateway queries the device that needs to be monitored as the terminal peripheral B, and according to the identifier of the fault, it is queried whether the terminal peripheral B firmware upgrade fails.
  • the M2M gateway pushes the firmware upgrade program of the terminal peripheral B to the terminal peripheral B. If the terminal peripheral B fails to upgrade normally, the terminal peripheral B feeds back the firmware upgrade failure to the M2M gateway, and the M2M gateway fails according to the failure management task information.
  • the processing mode is defined, that is, restarted, and an instruction is sent to the terminal peripheral B to instruct it to restart.
  • the embodiment of the present invention provides a fault management method.
  • the process for monitoring the fault of the M2M platform by using the method is as shown in FIG. 3, and includes the following steps:
  • Step 301 The M2M service platform sends fault management parameters to the M2M gateway, and the fault management parameters are as shown in Table 3.
  • Step 302 The M2M gateway saves the fault management parameters sent by the M2M service platform locally.
  • Step 303 The M2M service platform sends the fault management task information to the M2M gateway, and the fault management task information is as shown in Table 4.
  • Step 304 The M2M gateway performs a fault management task.
  • the M2M gateway queries the device to be monitored according to the identifier of the fault management object, which is a terminal peripheral.
  • the M2M gateway sets a timer Timerl with a timing length of T1 seconds.
  • the timer is started at the beginning of each detection period, and the detection information is sent to the terminal peripheral A.
  • the terminal peripheral After receiving the detection information, the terminal peripheral sends the detection information to the M2M gateway. Online feedback message. If the online feedback message of the terminal peripheral A has not been received when the timer Timerl expires, it is determined that it is offline.
  • the M2M gateway After detecting that the terminal peripheral A is offline, the M2M gateway sends a fault management report to the M2M service platform, and the report information is sent to the M2M service platform if the M2M gateway queries the local fault processing mode according to the fault detection mode identifier "01001" in the fault management task information. Includes fault management task ID 10001.
  • the M2M gateway queries the device that needs to be monitored as the terminal peripheral B, and according to the identifier of the fault, it is queried whether the terminal peripheral B is offline.
  • the M2M gateway sets a timer Timer2, and the timing length is T2 seconds.
  • the timer Timer2 is started at the beginning of each detection period, and the detection information is sent to the terminal peripheral B. After receiving the detection information, the terminal peripheral sends the detection information to the M2M gateway. Online feedback message. If the online feedback message of the terminal peripheral B has not been received when the timer Timer2 expires, it is determined to be offline.
  • the M2M gateway After detecting that the terminal peripheral B is offline, if the M2M gateway defines the fault processing mode according to the fault processing mode identifier "01001" in the fault management task information, the M2M gateway sends a fault management report to the M2M service platform.
  • the information includes a fault management task identifier 10002.
  • the M2M gateway queries the device that needs to be monitored as the terminal peripheral B, and according to the identifier of the fault, it is queried whether the terminal peripheral B firmware upgrade fails.
  • the M2M gateway pushes the firmware upgrade program of the terminal peripheral B to the terminal peripheral B. If the terminal peripheral B fails to upgrade normally, the terminal peripheral B feeds back the firmware upgrade failure to the M2M gateway, and the M2M gateway fails according to the failure management task information.
  • the identification of the processing mode is defined in the local query fault handling mode is to restart, send an instruction to the terminal peripheral B to instruct it to restart.
  • the embodiment of the invention provides a fault management device.
  • the structure of the device is as shown in FIG. 4, which includes:
  • a task receiving module 401 configured to receive a fault management task sent by the M2M service platform
  • An execution module 402 is configured to perform the fault management task.
  • the fault management task includes a fault management task identifier, a fault management object, a fault identifier, and a fault handling manner definition; the device further includes:
  • the first configuration module 403 is configured to receive and store a fault management parameter sent by the M2M service platform, where the fault management parameter includes a fault identifier and a fault definition corresponding to the fault identifier.
  • the fault management task includes a fault management task identifier, a fault management object, a fault identifier, and a fault handling mode identifier.
  • the device further includes:
  • a second configuration module 404 configured to receive and store a fault management parameter sent by the M2M service platform, where the fault management parameter includes a fault identifier, a fault definition corresponding to the fault identifier, a fault processing manner identifier, and a fault processing manner definition .
  • the structure of the execution module 402 is as shown in FIG. 5, and includes:
  • a fault definition query unit 4021 configured to query a fault definition corresponding to the fault identifier
  • the monitoring unit 4022 is configured to perform fault monitoring on the fault management object according to the fault definition obtained by the query.
  • the device further includes a fault processing module 405.
  • the structure of the fault processing module 405 is as shown in FIG. 6, and includes:
  • An identifier searching unit 4051 configured to search for a fault processing mode identifier corresponding to the fault when a fault is detected;
  • the fault processing unit 4053 is configured to perform a fault processing operation according to the fault processing manner.
  • the above fault management device can be integrated into the M2M gateway, and the corresponding function is implemented by the M2M gateway.
  • the fault management method and device provided by the embodiment of the present invention the M2M gateway receives the fault management task sent by the M2M service platform, and then the M2M gateway performs the fault management task, thereby implementing fault management on the M2M platform. Solved the problem of M2M platform fault monitoring.
  • steps of the foregoing embodiments may also be implemented by using an integrated circuit. These steps may be separately fabricated into individual integrated circuit modules, or multiple modules or steps may be fabricated into a single integrated circuit module. achieve.
  • embodiments of the invention are not limited to any specific combination of hardware and software.
  • the various devices/function modules/functional units in the above embodiments may be implemented using a general-purpose computing device, which may be centralized on a single computing device or distributed over a network of multiple computing devices.
  • Each device/function module/functional unit in the above embodiments can be stored in a computer readable storage medium when implemented in the form of a software function module and sold or used as a standalone product.
  • the above mentioned computer readable storage medium may be a read only memory, a magnetic disk or an optical disk or the like.

Landscapes

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

Abstract

一种故障管理方法和装置。该方法包括：M2M网关接收M2M业务平台发送的故障管理任务；以及所述M2M网关执行所述故障管理任务。

Description

故障管理方法和装置
技术领域
本发明涉及移动通信领域， 尤其涉及一种故障管理方法和装置。
背景技术
机器对机器（Machine to Machine, M2M )通信网络延伸现有信息通信 网络的通信范畴、通信领域，通过在各种可能的物体中嵌入智能和通信能力， 获取来自物理世界的信息， 并基于对这些信息的分析和处理来增强和提升现 有信息通信网络业务的智能性、 交互性和自动化程度。
M2M通信网络具有多种网络形态， 可以是单独构建的独立物理网络， 也可以是构建在现有公众通信网和各种政企专网之上的逻辑网络。
M2M通信网络在逻辑功能上可以划分为三层， 即， 感知延伸层、 网络 / 业务层和应用层。
感知延伸层： 感知延伸层主要实现物理世界信息的釆集、 自动识别和智 能控制。 物理世界中的各种物本身不具备通信能力。 传感器、 执行器、 智能 装置、 以及无线射频识别 （ Radio Frequency Identification, RFID )读写器等 智能节点釆集物理世界的信息， 并通过通信模块和网络层进行信息交互。 其 包含的主要部件有 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业务平台发送的故障 管理参数， 其中， 所述故障管理参数包含故障标识和故障标识对应的故障定 义。
可选地 ,
所述故障管理任务包含故障管理任务标识、 故障管理对象、 故障标识和 故障处理方式标识；
该装置还包括：
第二配置模块， 其设置成： 接收并存储所述 Μ2Μ业务平台发送的故障 管理参数， 其中， 所述故障管理参数包含故障标识、 故障标识对应的故障定 义、 故障处理方式标识和故障处理方式定义。
可选地， 所述执行模块包括：
故障定义查询单元， 其设置成： 查询所述故障标识对应的故障定义； 以 及
监控单元， 其设置成： 根据查询得到的故障定义， 对所述故障管理对象 进行故障监控。
可选地， 该装置还包括： 故障处理模块， 其中，
所述故障处理模块包括：
标识查找单元， 其设置成： 在检测到故障发生时， 查找所述故障对应的 故障处理方式标识；
定义查询单元， 其设置成： 根据所述故障处理方式标识查询故障处理方 式定义； 以及
故障处理单元， 其设置成： 按照所述故障处理方式定义， 执行故障处理 操作。
釆用本发明实施例提供的一种故障管理方法和装置， 实现了对 Μ2Μ平 台的故障管理， 解决了 Μ2Μ平台故障监控的问题。
附图概述
图 1是本发明的实施例一提供的一种故障管理方法的流程图； 图 2是本发明的实施例二提供的一种故障管理方法的流程图；
图 3是本发明的实施例三提供的一种故障管理方法的流程图；
图 4是本发明的实施例四提供的一种故障管理装置的结构示意图;
图 5是图 4中执行模块 402的结构示意图；
图 6是图 4中故障处理模块 405的结构示意图。 本发明的较佳实施方式
M2M平台向 M2M应用提供一些共性的能力和支撑，并提供开放的接口， 使应用可以接入和使用网络资源和能力。 通过向 M2M应用屏蔽底层网络实 现， 可以简化物联网应用开发复杂度和降低物联网应用开发部署成本。
为了解决 M2M平台的故障管理， 本发明的实施例提供了一种故障管理 方法和装置。 下文中将结合附图对本发明的实施例进行详细说明。 需要说明 的是， 在不冲突的情况下， 本申请中的实施例及实施例中的特征可以相互任 意组合。
实施例一
首先结合附图， 对本发明的实施例一进行说明。
在 M2M通信网络架构中， 网关作为连接和管理感知延伸层终端设备的 功能实体， 可以对终端外设和网关的故障进行处理。 基于此， 本发明实施例 提供了一种故障管理方法， 使用该方法完成 M2M平台监控的流程， 如图 1 所示， 包括如下步骤：
步骤 101、 M2M业务平台发送故障管理参数给 M2M网关。
故障管理参数的配置方案包括：
方案一、 包含故障标识、 故障标识对应的故障定义、 故障处理方式标识 和故障处理方式定义；
方案二、 包含故障标识和故障标识对应的故障定义。
步骤 102、所述 M2M网关接收并存储所述 M2M业务平台发送的故障管 理参数。 本步骤中， Μ2Μ网关将接收到的故障管理参数保存在本地数据库。 步骤 103、 Μ2Μ网关接收 Μ2Μ业务平台发送的故障管理任务。
本步骤中， Μ2Μ网关接收 Μ2Μ业务平台发送的故障管理任务。 与步骤 101 中方案一对应， 故障管理任务包含故障管理任务标识、 故障管理对象、 故障标识和故障处理方式标识； 与步骤 101中方案二对应， 故障管理任务包 含故障管理任务标识、 故障管理对象、 故障标识和故障处理方式定义。
本发明实施例中所涉及的故障管理对象包括 Μ2Μ 网关和 /或注册到 Μ2Μ网关的终端外设。
步骤 104、 所述 Μ2Μ网关执行所述故障管理任务。
本步骤中， Μ2Μ 网关根据故障标识在本地查询故障标识对应的故障定 义。 所述 Μ2Μ网关查询所述故障标识对应的故障定义， 然后所述 Μ2Μ网 关根据查询得到的故障定义， 对所述故障管理对象进行故障监控。
Μ2Μ 网关一旦检测到故障发生， 则根据故障管理任务中的故障处理方 式执行故障处理操作， 如步骤 105至步骤 107所示。
步骤 105、 所述 Μ2Μ网关在检测到故障发生时， 查找所述故障对应的 故障处理方式标识。
步骤 106、 所述 Μ2Μ网关根据所述故障处理方式标识查询故障处理方 式定义。
步骤 107、 所述 Μ2Μ网关按照所述故障处理方式定义， 执行故障处理 操作。
实施例二
下面结合附图， 对本发明的实施例二进行说明。
本发明实施例提供了一种故障管理方法， 使用该方法对 Μ2Μ平台进行 故障监控的流程如图 2所示， 包括如下步骤：
步骤 201、 Μ2Μ业务平台发送故障管理参数给 Μ2Μ网关， 故障管理参 数如表 1所示。
表 1 故障标识 故障定义
00001 离线
00002 固件升级失败
步骤 202、M2M网关将 M2M业务平台发送的故障管理参数保存在本地。 步骤 203、 M2M业务平台发送故障管理任务信息给 M2M网关， 故障管 理任务中携带的信息如表 2所示。
表 2
Figure imgf000008_0001
其中， "11111111" 是终端外设 A的标识， "22222222" 是终端外设 B 的标识 ,故障信息中的故障标识与第一步中故障管理参数中的故障标识对应。
步骤 204、 M2M网关执行故障管理任务。
本发明实施例中， 以上"¾和重启两种故障处理方式为例进行说明。
1、 对于故障管理任务标识为 "10001" 的故障管理任务的执行
M2M 网关根据故障管理对象的标识查询到需要监控的设备是终端外设
A, 并根据故障的标识查询到需要监控的是终端外设 A是否离线。
M2M网关设置一个定时器 Timerl , 定时长度为 T1秒， 在每一个检测周 期开始时启动定时器 Timerl , 发送检测信息给终端外设 A, 终端外设在接收 到该检测信息后， 向 M2M网关发送在线反馈消息。 如果在定时器 Timerl到 时时， 仍未收到终端外设 A的在线反馈消息， 则判定其离线。
在检测到终端外设 A离线后， M2M网关根据故障管理任务信息中的故 障处理方式定义， 即， 上报， 向 M2M业务平台发送故障管理报告， 报告信 息包括故障管理任务标识 10001。
2、 对故障管理任务标识为 "10002" 的故障管理任务的执行
M2M 网关根据故障管理对象的标识查询到需要监控的设备是终端外设 B, 并根据故障的标识查询到需要监控的是终端外设 B是否离线。
M2M网关设置一个定时器 Timer2, 定时长度为 T2秒， 在每一个检测周 期开始时启动定时器 Timer2, 发送检测信息给终端外设 B, 终端外设在接收 到该检测信息后， 向 M2M网关发送在线反馈消息。 如果在定时器 Timer2到 时时， 仍未收到终端外设 B的在线反馈消息， 则判定其离线。
在检测到终端外设 B 离线后， M2M网关根据故障管理任务信息中的故 障处理方式定义， 即， 上报， 向 M2M业务平台发送故障管理报告， 报告信 息包括故障管理任务标识 10002。
3、 对于故障管理任务标识为 "10003" 的故障管理任务的执行
M2M 网关根据故障管理对象的标识查询到需要监控的设备是终端外设 B, 并根据故障的标识查询到需要监控的是终端外设 B固件升级是否失败。
M2M网关推送终端外设 B的固件升级程序到终端外设 B, 如果终端外 设 B未能正常升级， 则终端外设 B向 M2M网关反馈固件升级失败， M2M 网关根据故障管理任务信息中的故障处理方式定义， 即， 重启， 向终端外设 B发送指令， 指示其重启。
实施例三
下面结合附图， 对本发明的实施例三进行说明。
本发明实施例提供了一种故障管理方法， 使用该方法对 M2M平台进行 故障监控的流程如图 3所示， 包括如下步骤：
步骤 301、 M2M业务平台发送故障管理参数给 M2M网关， 故障管理参 数如表 3所示。
表 3
Figure imgf000009_0001
00002 固件升级失败
故障处理方式标识 故障处理方式定义
01001 上报
01002 重启
步骤 302、M2M网关将 M2M业务平台发送的故障管理参数保存在本地。 步骤 303、 M2M业务平台发送故障管理任务信息给 M2M网关， 故障管 理任务信息如表 4所示。
表 4
Figure imgf000010_0001
其中， "11111111" 是终端外设 A的标识， "22222222" 是终端外设 B 的标识， 故障信息中的标识与第一步中故障管理参数中的故障标识对应。
步骤 304、 M2M网关执行故障管理任务。
本发明实施例中， 以上"¾和重启两种故障处理方式为例进行说明。
1、 对于故障管理任务标识为 "10001" 的故障管理任务的执行
M2M 网关根据故障管理对象的标识查询到需要监控的设备是终端外设
A, 并根据故障的标识查询到需要监控的是终端外设 A是否离线。
M2M网关设置一个定时器 Timerl , 定时长度为 T1秒， 在每一个检测周 期开始时启动定时器 Timerl , 发送检测信息给终端外设 A, 终端外设在接收 到该检测信息后， 向 M2M网关发送在线反馈消息。 如果在定时器 Timerl到 时时， 仍未收到终端外设 A的在线反馈消息， 则判定其离线。 在检测到终端外设 A离线后， 若 M2M网关根据故障管理任务信息中的 故障处理方式的标识 "01001"在本地查询故障处理方式是上 则 M2M网 关向 M2M 业务平台发送故障管理报告， 报告信息包括故障管理任务标识 10001。
2、 对故障管理任务标识为 "10002" 的故障管理任务的执行
M2M 网关根据故障管理对象的标识查询到需要监控的设备是终端外设 B, 并根据故障的标识查询到需要监控的是终端外设 B是否离线。
M2M网关设置一个定时器 Timer2, 定时长度为 T2秒， 在每一个检测周 期开始时启动定时器 Timer2, 发送检测信息给终端外设 B, 终端外设在接收 到该检测信息后， 向 M2M网关发送在线反馈消息。 如果在定时器 Timer2到 时时， 仍未收到终端外设 B的在线反馈消息， 则判定其离线。
在检测到终端外设 B离线后， 若 M2M网关根据故障管理任务信息中的 故障处理方式的标识 "01001"在本地查询故障处理方式定义是上 则 M2M 网关向 M2M业务平台发送故障管理报告， 报告信息包括故障管理任务标识 10002。
3、 对故障管理任务标识为 "10003" 的故障管理任务的执行
M2M 网关根据故障管理对象的标识查询到需要监控的设备是终端外设 B, 并根据故障的标识查询到需要监控的是终端外设 B固件升级是否失败。
M2M网关推送终端外设 B的固件升级程序到终端外设 B, 如果终端外 设 B未能正常升级， 则终端外设 B向 M2M网关反馈固件升级失败， M2M 网关根据故障管理任务信息中的故障处理方式的标识在本地查询故障处理方 式定义是重启， 向终端外设 B发送指令， 指示其重启。
实施例 4
下面结合附图， 对本发明的实施例四进行说明。
本发明实施例提供了一种故障管理装置， 该装置的结构如图 4所示， 包 括：
任务接收模块 401 , 其用于接收 M2M业务平台发送的故障管理任务； 以及 执行模块 402 , 其用于执行所述故障管理任务。
可选地， 所述故障管理任务包含故障管理任务标识、 故障管理对象、 故 障标识和故障处理方式定义； 该装置还包括：
第一配置模块 403 , 其用于接收并存储所述 M2M业务平台发送的故障 管理参数， 其中， 所述故障管理参数包含故障标识和故障标识对应的故障定 义。
可选地， 所述故障管理任务包含故障管理任务标识、 故障管理对象、 故 障标识和故障处理方式标识； 该装置还包括：
第二配置模块 404 , 其用于接收并存储所述 M2M业务平台发送的故障 管理参数， 其中， 所述故障管理参数包含故障标识、 故障标识对应的故障定 义、 故障处理方式标识和故障处理方式定义。
可选地， 所述执行模块 402的结构如图 5所示， 包括：
故障定义查询单元 4021 , 其用于查询所述故障标识对应的故障定义； 以 及
监控单元 4022, 其用于根据查询得到的故障定义， 对所述故障管理对象 进行故障监控。
可选地， 该装置还包括故障处理模块 405 , 所述故障处理模块 405的结 构如图 6所示， 包括：
标识查找单元 4051 , 其用于在检测到故障发生时， 查找所述故障对应的 故障处理方式标识；
定义查询单元 4052,其用于根据所述故障处理方式标识查询故障处理方 式定义； 以及
故障处理单元 4053 , 其用于按照所述故障处理方式定义， 执行故障处理 操作。
上述故障管理装置可集成于 M2M网关中，由 M2M网关实现相应功能。 釆用本发明的实施例提供的一种故障管理方法和装置， M2M 网关接收 M2M业务平台发送的故障管理任务，然后所述 M2M网关执行所述故障管理 任务， 实现了对 M2M平台的故障管理，解决了 M2M平台故障监控的问题。
本领域普通技术人员可以理解上述实施例的全部或部分步骤可以使用计 算机程序流程来实现，所述计算机程序可以存储于一计算机可读存储介质中， 所述计算机程序在相应的硬件平台上 （如， 系统、 设备、 装置、 器件等）执 行， 在执行时， 包括方法实施例的步骤之一或其组合。
可选地， 上述实施例的全部或部分步骤也可以使用集成电路来实现， 这 些步骤可以被分别制作成一个个集成电路模块， 或者将它们中的多个模块或 步骤制作成单个集成电路模块来实现。 这样， 本发明实施例不限制于任何特 定的硬件和软件结合。
上述实施例中的各装置 /功能模块 /功能单元可以釆用通用的计算装置来 实现， 它们可以集中在单个的计算装置上， 也可以分布在多个计算装置所组 成的网络上。
上述实施例中的各装置 /功能模块 /功能单元以软件功能模块的形式实现 并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。 上述提到的计算机可读取存储介质可以是只读存储器， 磁盘或光盘等。
任何熟悉本技术领域的技术人员在本发明揭露的技术范围内， 可轻易想 到变化或替换， 都应涵盖在本发明所附权利要求的保护范围之内。 因此， 本 发明的保护范围应以权利要求所述的保护范围为准。
工业实用性
釆用本发明实施例的方法和装置， 实现了对 M2M平台的故障管理， 解 决了 M2M平台故障监控的问题。

Claims

权利要求书
1、 一种故障管理方法， 包括：
机器对机器 M2M网关接收 M2M业务平台发送的故障管理任务； 以及 所述 M2M网关执行所述故障管理任务。
2、 根据权利要求 1所述的方法， 其中， 故障管理对象是所述 M2M网关 或 /和注册到所述 M2M网关的终端外设。
3、根据权利要求 1所述的方法， 其中， 所述故障管理任务包含故障管理 任务标识、 故障管理对象、 故障标识和故障处理方式定义。
4、 根据权利要求 3所述的方法， 还包括： 所述 M2M网关接收 M2M业 务平台发送的故障管理任务之前，
所述 M2M网关接收并存储所述 M2M业务平台发送的故障管理参数， 其中， 所述故障管理参数包含故障标识和故障标识对应的故障定义。
5、根据权利要求 1所述的方法， 其中， 所述故障管理任务包含故障管理 任务标识、 故障管理对象、 故障标识和故障处理方式标识。
6、 根据权利要求 5所述的方法， 还包括： 所述 M2M网关接收 M2M业 务平台发送的故障管理任务之前， 所述 M2M网关接收并存储所述 M2M业 务平台发送的故障管理参数， 其中， 所述故障管理参数包含故障标识、 故障 标识对应的故障定义、 故障处理方式标识和故障处理方式定义。
7、 根据权利要求 3或 5所述的方法， 其中， 所述 M2M网关执行所述故 障管理任务包括：
所述 M2M网关查询所述故障标识对应的故障定义； 以及
所述 M2M网关根据查询得到的故障定义， 对所述故障管理对象进行故 障监控。
8、 根据权利要求 6所述的方法， 还包括： 所述 M2M网关执行所述故障 管理任务之后，
所述 M2M网关在检测到故障发生时， 查找所述故障对应的故障处理方 式标识； 根据所述故障处理方式标识查询故障处理方式定义； 以及
按照所述故障处理方式定义， 执行故障处理操作。
9、 一种故障管理装置， 应用于机器对机器 M2M网关， 所述装置包括： 任务接收模块， 其设置成： 接收 M2M业务平台发送的故障管理任务； 以及
执行模块， 其设置成： 执行所述故障管理任务。
10、 根据权利要求 9所述的装置， 其中，
故障管理对象是所述 M2M网关或 /和注册到所述 M2M网关的终端外设； 所述故障管理任务包含故障管理任务标识、 故障管理对象、 故障标识和 故障处理方式定义；
所述装置还包括：
第一配置模块， 其设置成： 接收并存储所述 M2M业务平台发送的故障 管理参数， 其中， 所述故障管理参数包含故障标识和故障标识对应的故障定 义。
11、 根据权利要求 9所述的装置， 其中，
所述故障管理任务包含故障管理任务标识、 故障管理对象、 故障标识和 故障处理方式标识；
所述装置还包括：
第二配置模块， 其设置成： 接收并存储所述 M2M业务平台发送的故障 管理参数， 其中， 所述故障管理参数包含故障标识、 故障标识对应的故障定 义、 故障处理方式标识和故障处理方式定义。
12、 根据权利要求 10或 11所述的装置， 其中， 所述执行模块包括： 故障定义查询单元， 其设置成： 查询所述故障标识对应的故障定义； 以 及
监控单元， 其设置成： 根据查询得到的故障定义， 对所述故障管理对象 进行故障监控。
13、根据权利要求 10或 11所述的装置，还包括：故障处理模块，其中， 所述故障处理模块包括：
标识查找单元， 其设置成： 在检测到故障发生时， 查找所述故障对应的 故障处理方式标识；
定义查询单元， 其设置成： 根据所述故障处理方式标识查询故障处理方 式定义； 以及
故障处理单元， 其设置成： 按照所述故障处理方式定义， 执行故障处理 操作。
PCT/CN2013/085086 2013-07-19 2013-10-12 故障管理方法和装置 WO2014166218A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US14/904,434 US9949061B2 (en) 2013-07-19 2013-10-12 Fault management method and apparatus
EP13881512.1A EP3010182A4 (en) 2013-07-19 2013-10-12 DEFAULT MANAGEMENT METHOD AND APPARATUS

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310306830.2 2013-07-19
CN201310306830.2A CN104301131A (zh) 2013-07-19 2013-07-19 故障管理方法和装置

Publications (1)

Publication Number Publication Date
WO2014166218A1 true WO2014166218A1 (zh) 2014-10-16

Family

ID=51688908

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/085086 WO2014166218A1 (zh) 2013-07-19 2013-10-12 故障管理方法和装置

Country Status (4)

Country Link
US (1) US9949061B2 (zh)
EP (1) EP3010182A4 (zh)
CN (1) CN104301131A (zh)
WO (1) WO2014166218A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017068597A1 (en) * 2015-10-23 2017-04-27 Telefonaktiebolaget Lm Ericsson (Publ) Establishment of operational status of a machine-to-machine device
US10298996B2 (en) 2016-08-18 2019-05-21 At&T Intellectual Property I, L.P. Satellite TV user community smart device monitoring and management
CN107257375B (zh) * 2017-06-19 2019-11-19 深圳市盛路物联通讯技术有限公司 一种基于过滤网关的终端设备工作状态检测方法及系统
US10477426B1 (en) * 2019-02-06 2019-11-12 Accenture Global Solutions Limited Identifying a cell site as a target for utilizing 5th generation (5G) network technologies and upgrading the cell site to implement the 5G network technologies
JP7243479B2 (ja) * 2019-06-24 2023-03-22 ブラザー工業株式会社 サーバ、サーバのためのコンピュータプログラム、及び、端末装置のためのコンピュータプログラム

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102264087A (zh) * 2010-05-31 2011-11-30 中兴通讯股份有限公司 一种m2m业务中终端状态或事件管理的方法及系统
CN102487488A (zh) * 2010-12-02 2012-06-06 中国移动通信集团上海有限公司 信息发送系统、方法、信息采集与设备控制系统及设备
WO2013030742A1 (en) * 2011-09-01 2013-03-07 Telefonaktiebolaget L M Ericsson (Publ) System and method for high availability machine-to-machine management

Family Cites Families (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8127277B2 (en) * 2007-05-21 2012-02-28 International Business Machines Corporation Framework for conditionally executing code in an application using conditions in the framework and in the application
KR100947286B1 (ko) * 2007-10-31 2010-03-16 한국전자통신연구원 무선 센서 네트워크 관리 장치 및 방법
US8843155B2 (en) * 2010-01-20 2014-09-23 Airpatrol Corporation Multi-band radio frequency detection and location system
CN102907068A (zh) * 2010-03-09 2013-01-30 交互数字专利控股公司 支持机器对机器通信的方法和设备
US8407520B2 (en) * 2010-04-23 2013-03-26 Ebay Inc. System and method for definition, creation, management, transmission, and monitoring of errors in SOA environment
EP2633727B1 (en) * 2010-10-29 2017-01-25 NEC Corporation Method and system for connecting a user equipment to a network device via a mobile communication network
US8560887B2 (en) * 2010-12-09 2013-10-15 International Business Machines Corporation Adding scalability and fault tolerance to generic finite state machine frameworks for use in automated incident management of cloud computing infrastructures
US8601323B2 (en) * 2010-12-13 2013-12-03 Sap Ag Advanced management of runtime errors
WO2012082151A2 (en) * 2010-12-13 2012-06-21 Telecommunication Systems, Inc. Location services gateway server
KR101169285B1 (ko) * 2011-12-08 2012-08-02 엘지전자 주식회사 지속적 스케줄링 정보를 전송 및 수신하는 방법 및 이를 위한 장치

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102264087A (zh) * 2010-05-31 2011-11-30 中兴通讯股份有限公司 一种m2m业务中终端状态或事件管理的方法及系统
CN102487488A (zh) * 2010-12-02 2012-06-06 中国移动通信集团上海有限公司 信息发送系统、方法、信息采集与设备控制系统及设备
WO2013030742A1 (en) * 2011-09-01 2013-03-07 Telefonaktiebolaget L M Ericsson (Publ) System and method for high availability machine-to-machine management

Non-Patent Citations (1)

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

Also Published As

Publication number Publication date
CN104301131A (zh) 2015-01-21
EP3010182A4 (en) 2016-06-22
EP3010182A1 (en) 2016-04-20
US9949061B2 (en) 2018-04-17
US20160212570A1 (en) 2016-07-21

Similar Documents

Publication Publication Date Title
US10721122B1 (en) Discovery of device capabilities
EP3060018B1 (en) Registration method and system for common service entity
US8001080B2 (en) Managing real-time execution of transactions in a network
WO2014166218A1 (zh) 故障管理方法和装置
JP2006237668A (ja) センサネット管理システム
CN103237060B (zh) 一种数据对象获取方法、装置及系统
WO2014056344A1 (zh) 监控方法及装置
CN111800443A (zh) 数据处理系统和方法、装置以及电子设备
WO2014056345A1 (zh) 监控任务的管理方法及装置
US20210058376A1 (en) Anonymization and randomization of device identities
US20160241635A1 (en) M2m data querying and invoking methods, querying and invoking devices, and system
EP3007385B1 (en) Terminal peripheral control method, m2m gateway, and communications system
WO2011157003A1 (zh) 管理无线传感网终端的方法和管理网元及网络节点
KR101894389B1 (ko) 기기간 연결 방법 및 그 장치
JP2016527846A (ja) データフィードの管理
US11140533B2 (en) Enable reliable and distributed M2M/IoT services
US20160294465A1 (en) Information collection system, relay terminal, control method for relay terminal to connect to center system, sensor terminal, and control method for sensor terminal to connect to center system
WO2014036902A1 (zh) 网关管理终端的方法及装置
CN104954462A (zh) 一种高并发可扩展的智能家居通信方法和系统
KR101997602B1 (ko) 디바이스 양방향 ｍ２ｍ 리소스 관리 방법
CN104462235A (zh) 一种基于Restful Web Service的物联网通用事件服务机制
US9516097B1 (en) Location aware service instance discovery
CN105607594A (zh) 基于智能家居的服务器内存查找设备的方法
Prabakar et al. Management of RFID-centric business networks using Web Services
WO2014183369A1 (zh) 监控处理方法、装置及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: 13881512

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 14904434

Country of ref document: US

WWE Wipo information: entry into national phase

Ref document number: 2013881512

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE