WO2014056344A1 - 监控方法及装置 - Google Patents
监控方法及装置 Download PDFInfo
- Publication number
- WO2014056344A1 WO2014056344A1 PCT/CN2013/081329 CN2013081329W WO2014056344A1 WO 2014056344 A1 WO2014056344 A1 WO 2014056344A1 CN 2013081329 W CN2013081329 W CN 2013081329W WO 2014056344 A1 WO2014056344 A1 WO 2014056344A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- monitoring
- gateway
- reporting
- report
- application server
- Prior art date
Links
- 238000012544 monitoring process Methods 0.000 title claims abstract description 285
- 238000000034 method Methods 0.000 title claims abstract description 35
- 230000002093 peripheral effect Effects 0.000 claims description 23
- 230000000737 periodic effect Effects 0.000 claims description 22
- 230000001960 triggered effect Effects 0.000 claims description 9
- 238000012806 monitoring device Methods 0.000 claims description 2
- 230000000694 effects Effects 0.000 abstract description 6
- 238000004891 communication Methods 0.000 description 17
- 230000008859 change Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 238000011161 development Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
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]
-
- 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
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/04—Large scale networks; Deep hierarchical networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/16—Gateway arrangements
Definitions
- TECHNICAL FIELD The present invention relates to the field of communications, and in particular to a monitoring method and apparatus.
- BACKGROUND OF THE INVENTION Machine to Machine (M2M) communication network can extend the communication field and communication field of existing information communication networks, and acquire 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 ICT services.
- M2M Machine to Machine
- 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.
- Intelligent nodes such as sensors, actuators, smart devices, and Radio Frequency Identification Devices (RFID) readers collect information from the physical world and exchange information through the communication module and the network layer.
- RFID Radio Frequency Identification Devices
- the main components it contains are M2M terminal equipment and M2M gateway equipment.
- Network/service layer The network/service layer supports the transmission, routing and control of the information of the sensing layer, and provides support for the communication of people and things, things and things in the Internet of Things.
- the network forms specifically included in the network layer are: communication network, Internet, industry network, and so on.
- 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.
- Industry services can be public services for the public, or industry-specific services that meet specific application needs within the industry.
- public services are basic services provided to the general public, such as smart homes and mobile payments.
- Industry-specific services are usually tailor-made for the industry's own needs, for the industry's internal services, such as smart grid, intelligent transportation, intelligent environment, 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.
- Terminal peripherals refer to a single device such as an environment-aware sensor that can send the perceived information to the M2M service platform or M2M application through the M2M gateway, and can also receive the M2M application or the M2M service platform. Downward control over it.
- M2M terminal peripherals have the characteristics of processing capability, storage capacity and power limitation. They cannot communicate directly with the communication network and need to access the communication network through the M2M gateway.
- the M2M gateway can perform protocol conversion between the M2M-aware extension layer and the upper layer network.
- the M2M gateway can also receive control information of the M2M application or the M2M service platform to manage the terminal peripherals.
- 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 providing a standardized application programming interface (API) to specific M2M applications, IoT application development complexity and IoT application development deployment costs can be simplified.
- 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. To provide statistics and fault alarms to the M2M platform or M2M application server.
- the prior art does not provide a monitoring method that satisfies this requirement in the M2M communication network architecture.
- a monitoring method including: the gateway monitors a monitoring object in the monitoring configuration information, and obtains a monitoring result; the gateway configures the machine to the machine (M2M) according to the report configuration in the monitoring configuration information.
- the monitoring result is reported by the service platform or the M2M application server.
- the method further includes: the gateway acquiring the monitoring configuration information, where the monitoring configuration information is pre-configured on the gateway, or is the gateway from the M2M service. Received on the platform or M2M application server.
- the monitoring configuration information includes a monitoring task or multiple monitoring tasks, where the monitoring task includes: a monitoring identifier, which is used to uniquely identify a monitoring task, which is performed by an M2M service platform or an M2M application server or network. Off-targeted; monitoring object, used to indicate the objects that need to be monitored; report configuration, including: report mode and report parameters.
- the monitoring object comprises: a wide area network WAN port of the gateway, a local area network LAN port of the gateway, a terminal peripheral device, a gateway software module, or a gateway hardware module.
- the reporting manner includes: periodic reporting and event triggering reporting, wherein the periodic reporting setting includes a predetermined reporting period; the event triggering reporting setting has at least one event definition, wherein the event definition includes: an event identifier and a trigger condition.
- the same monitoring object can set a plurality of reporting methods.
- the gateway monitors the monitoring object in the monitoring configuration information, and obtains the monitoring result, including: the gateway saves the monitoring task in the local monitoring task list; the gateway monitors the monitoring object according to the monitoring task list, and obtains monitoring of the monitoring object. result.
- the reporting module is configured to report, to the M2M service platform or the M2M application server, a monitoring result that the monitoring object does not exist if the terminal peripheral is not registered at the gateway.
- the reporting module is configured to report the monitoring result to the M2M service platform or the M2M application server when the reporting period is the periodic reporting, and the reporting module, When the reporting mode is triggered by the event, when the triggering condition is met, the monitoring result is reported to the M2M service platform or the M2M application server.
- a monitoring apparatus is provided, which is located at a gateway, and includes: a monitoring module configured to monitor a monitoring object in the monitoring configuration information to obtain a monitoring result; and the reporting module is configured to be configured according to the monitoring The report configuration in the information reports the monitoring result to the machine-to-machine M2M service platform or the M2M application server.
- the device further includes: an obtaining module, configured to obtain monitoring configuration information, where the monitoring configuration information is pre-configured on the gateway, or is received by the gateway from the M2M service platform or the M2M application server.
- the monitoring configuration information includes a monitoring task or a plurality of monitoring tasks, where the monitoring task includes: a monitoring identifier, which is used to uniquely identify a monitoring task, which is allocated by the M2M service platform or the M2M application server or the gateway; Used to indicate which objects need to be monitored; report configuration, including: report mode and report parameters.
- the monitoring object comprises: a wide area network WAN port of the gateway, a local area network LAN port of the gateway, a terminal peripheral device, a gateway software module, or a gateway hardware module.
- the reporting manner includes: periodic reporting and event triggering reporting, wherein the periodic reporting setting includes a predetermined reporting period; the event triggering reporting setting has at least one event definition, wherein the event definition includes: an event identifier and a trigger condition.
- the same monitoring object can set a plurality of reporting methods.
- the monitoring module comprises: a saving unit, configured to save the monitoring task in the local monitoring task list; and the monitoring unit is configured to monitor the monitoring object according to the monitoring task list, and obtain the monitoring result of the monitoring object.
- the gateway reports the monitoring result that the monitoring object does not exist to the M2M service platform or the M2M application server.
- the reporting mode is periodic reporting
- the gateway reports the monitoring result to the M2M service platform or the M2M application server at the end of the monitoring period;
- the reporting mode is the event triggering report, when the triggering condition is met, the gateway reports the monitoring result.
- the gateway monitors the M2M device according to the monitoring configuration information, obtains the monitoring report, and reports the monitoring report, and solves the problem that the gateway cannot provide the M2M application execution status or the gateway for the M2M platform or the M2M application server.
- the software and hardware running status, the operating status of the terminal peripherals, etc. can also provide statistics and fault alarms to the M2M platform or the M2M application server, thereby enabling the M2M network to grasp various state parameters according to requirements.
- the fault alarm information can be obtained in time, and the corresponding operation effect can be timely performed.
- FIG. 1 is a flow chart of a monitoring method according to an embodiment of the present invention
- FIG. 2 is a monitoring flow chart according to a preferred embodiment of the present invention
- FIG. 3 is a monitoring flow chart according to a preferred embodiment 2 of the present invention
- 4 is a block diagram showing the structure of a monitoring apparatus according to an embodiment of the present invention.
- FIG. 5 is a structural block diagram of a monitoring apparatus according to a preferred embodiment of the present invention.
- BEST MODE FOR CARRYING OUT THE INVENTION the present invention will be described in detail 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.
- 1 is a flowchart of a monitoring method according to an embodiment of the present invention. As shown in FIG. 1, the method mainly includes the following steps (step S102-step S104): Step S102, the gateway monitors a monitoring object in monitoring configuration information. The operation is performed to obtain the monitoring result.
- Step S104 The gateway reports the monitoring result to the machine-to-machine M2M service platform or the M2M application server according to the report configuration in the monitoring configuration information.
- the method before the step S102, the method further includes: the gateway acquiring the monitoring configuration information, where the monitoring configuration information is pre-configured on the gateway, or is received by the gateway from the M2M service platform or the M2M application server.
- the monitoring configuration information includes a monitoring task or multiple monitoring tasks, where the monitoring task includes: a monitoring identifier, which is used to uniquely identify a monitoring task, which is allocated by the M2M service platform or the M2M application server or the gateway; Monitoring object, used to indicate the objects that need to be monitored; report configuration, including: report mode and report parameters.
- the monitoring object comprises: a wide area network WAN port of the gateway, a local area network LAN port of the gateway, a terminal peripheral device, a gateway software module, or a gateway hardware module.
- the reporting manner includes: periodic reporting and event triggering reporting, wherein the periodic reporting setting includes a predetermined reporting period; the event triggering reporting setting has at least one event definition, wherein the event definition includes: an event identifier and a trigger condition.
- the same monitoring object can set a plurality of reporting modes.
- step S102 can be implemented in the following manner: The gateway saves the monitoring task in the local monitoring task list; the gateway monitors the monitoring object according to the monitoring task list, and obtains the monitoring result of the monitoring object.
- FIG. 2 is a monitoring flowchart according to a preferred embodiment of the present invention. As shown in FIG. 2, the process includes the following steps (step S202-step S206): Step S202, the M2M service platform or the M2M application server sends monitoring. Configure the message to the gateway.
- the information contained in the monitoring configuration message is shown in Table 1:
- Monitoring ID used to uniquely identify a monitoring task, which is assigned by the M2M service platform or the M2M application server.
- Monitoring object Used to indicate the object to be monitored, for example, the WAN port of the gateway. (wide area network), or gateway LAN (local area network), or terminal peripherals, or gateway software module, or gateway hardware module; report configuration: including reporting mode and reporting parameters; wherein, reporting mode is: periodic reporting, or event triggering
- the report is generated by the M2M service platform or the M2M application server.
- the report triggers the set event time.
- the event triggers the report to set the event definition. It should be noted that multiple reporting methods can be set for the same monitoring object, and multiple reporting events can also be set for the event triggering reporting.
- the reporting method is “event-triggered reporting”
- the event identifier is “event A”
- the triggering condition is “IP address change”
- the reporting parameter is "gateway identification, time, event”
- the gateway will change when the IP address is changed.
- Monitoring configuration example 1 (event-triggered monitoring task), as shown in Table 2: Table 2
- Monitoring configuration example 2 (periodic triggering class monitoring task), as shown in Table 3
- Step S204 After receiving the monitoring configuration message, the gateway performs monitoring according to the monitoring configuration message.
- the gateway saves the monitoring task in the monitoring configuration in the local monitoring task list, and monitors the monitoring object set in the monitoring configuration to obtain the monitoring result of the monitoring object.
- the monitoring result is the report parameter set in the report configuration according to the monitoring configuration. Come to get.
- Step S206 The gateway sends a monitoring report to the M2M service platform or the M2M application server.
- the gateway should report to the M2M service platform or the M2M application that the monitoring object does not exist;
- the gateway sends the monitoring result to the M2M service platform or the M2M application server when the monitoring period timer expires; the monitoring result is the data obtained according to the report parameter.
- the monitoring configuration indication is triggered by an event, the monitoring result is sent to the M2M service platform or the M2M application server after the event occurs.
- the monitoring report sent by the gateway contains the information shown in Table 4: Table 4
- FIG. 3 is a monitoring flowchart according to a preferred embodiment 2 of the present invention. As shown in FIG. 3, the flow includes the following steps (Step S302-Step S306): Step S302, according to the needs of the user, the gateway may be pre- The monitoring task is configured locally, and the monitoring task is implemented by setting a monitoring configuration message.
- the monitoring configuration message contains information as shown in Table 6: Table 6
- Monitoring ID Used to uniquely identify a monitoring task, assigned by the gateway
- Monitoring object Used to indicate the object to be monitored, for example, the gateway's WAN port (wide area network), or gateway LAN (LAN), or terminal peripherals, or gateways, or gateway software modules, or gateway hardware modules.
- the report configuration includes: the report mode and the report parameter.
- the report mode is: periodic report, or event trigger report, where the periodic report set cycle time, event trigger report event setting, including setting event identifier and trigger condition; report parameter
- the monitoring result needs to be reported to the M2M service platform or the M2M application server. It should be noted that multiple reporting methods can be set for the same monitoring object, and multiple reporting events can be set for the event trigger reporting method.
- the reporting method is “event-triggered reporting", the event identifier is “event A”, the triggering condition is “IP address change”, and the reporting parameter is "gateway identification, time, event”, then the gateway will change when the IP address is changed.
- Step S304 the gateway performs monitoring according to the monitoring configuration message.
- the gateway saves the monitoring task in the monitoring configuration in the local monitoring task list, and monitors the monitoring object set in the monitoring configuration to obtain the monitoring result of the monitoring object.
- the monitoring result is the report parameter set in the report configuration according to the monitoring configuration. Come to get.
- Step S306 the gateway sends a monitoring report to the M2M service platform or the M2M application server.
- the monitoring configuration indicator is periodically reported, the monitoring result is sent to the M2M service platform or the M2M application server according to the report parameter specified in the report configuration when the monitoring period timer expires; wherein the monitoring result is based on the report parameter The data obtained.
- the monitoring configuration indication is triggered by an event, after the event occurs, the monitoring result is sent to the M2M service platform or the M2M application server according to the report parameter specified in the report configuration; wherein the monitoring report sent by the gateway includes information such as a table. Seven shows: Table seven
- FIG. 4 is a structural block diagram of a monitoring apparatus according to an embodiment of the present invention.
- the apparatus is located at a gateway to implement the monitoring method provided by the foregoing embodiment. As shown in FIG.
- the apparatus mainly includes: a monitoring module 10 and a reporting module 20.
- the monitoring module 10 is configured to perform monitoring operations on the monitoring objects in the monitoring configuration information to obtain monitoring results.
- the reporting module 20 is connected to the monitoring module 10, and configured to configure the machine-to-machine M2M service according to the report configuration in the monitoring configuration information.
- the monitoring result is reported by the platform or the M2M application server.
- 5 is a structural block diagram of a monitoring apparatus according to a preferred embodiment of the present invention. As shown in FIG. 5, the apparatus further includes: an obtaining module 30, connected to the monitoring module 10, configured to acquire monitoring configuration information, where the monitoring configuration information is Pre-configured on the gateway, or received by the gateway from the M2M service platform or the M2M application server.
- the monitoring configuration information includes a monitoring task or multiple monitoring tasks, where the monitoring task includes: a monitoring identifier, which is used to uniquely identify a monitoring task, which is allocated by the M2M service platform or the M2M application server or the gateway. ; monitoring object, used to indicate the objects that need to be monitored; report configuration, including: report mode and report parameters.
- the monitoring objects include: a wide area network WAN port of the gateway, a local area network LAN port of the gateway, a terminal peripheral, a gateway software module, or a gateway hardware module.
- the report mode includes: a periodic report and an event trigger report, wherein the periodic report setting includes a predetermined report period; the event trigger report setting has at least one event definition, wherein the event definition includes: an event identifier and a trigger condition.
- the same monitoring object can set a plurality of reporting methods.
- the monitoring module 10 includes: a saving unit 12 configured to save the monitoring task in the local monitoring task list; the monitoring unit 14 is connected to the saving unit 12, and is configured to monitor the monitoring object according to the monitoring task list. , Get the monitoring result of the monitored object.
- the reporting module is configured to report, to the M2M service platform or the M2M application server, a monitoring result that the monitoring object does not exist if the terminal peripheral is not registered at the gateway.
- the reporting module is configured to report the monitoring result to the M2M service platform or the M2M application server when the reporting period is the periodic reporting, when the monitoring period ends;
- the reporting module is configured to report the monitoring result to the M2M service platform or the M2M application server when the triggering condition is met when the reporting mode is triggered by the event.
- the gateway can perform the monitoring operation on the M2M device according to the monitoring configuration information, obtain the monitoring report, and report the monitoring report, which can solve the problem that the gateway cannot be related in the related technology.
- modules or steps of the present invention can be implemented by a general-purpose computing device, which can be concentrated on a single computing device or distributed over a network composed of multiple computing devices. Alternatively, they may be implemented by program code executable by the computing device, such that they may be stored in the storage device by the computing device and, in some cases, may be different from the order herein.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Telephonic Communication Services (AREA)
Abstract
本发明公开了一种监控方法及装置。其中,该方法包括:网关对监控配置信息中的监控对象进行监控操作,获得监控结果(S102);网关根据监控配置信息中的报告配置向机器对机器(M2M)业务平台或M\2M应用服务器上报监控结果(S104)。通过本发明,达到了能够使M2M网络能根据需求掌握各种状态参数进行统计,同时还能根据配置及时的获得故障报警信息,及时做出相应的操作的效果。
Description
监控方法及装:
技术领域 本发明涉及通信领域, 具体而言, 涉及一种监控方法及装置。 背景技术 机器对机器 (Machine To Machine, 简称为 M2M) 通信网络可以延伸现有信息通 信网络的通信范畴、 通信领域, 通过在各种可能的物体中嵌入智能和通信能力, 获取 来自物理世界的信息, 并基于对这些信息的分析和处理来增强和提升现有信息通信网 络业务的智能性、 交互性和自动化程度。
M2M通信网络具有多种网络形态,可以是单独构建的独立物理网络,也可以是构 建在现有公众通信网和各种政企专网之上的逻辑网络。
M2M通信网络在逻辑功能上可以划分为三层, 即: 感知延伸层、 网络 /业务层和 应用层。 下对这三层进行介绍: 感知延伸层: 主要实现物理世界信息的采集、 自动识别和智能控制。 物理世界中 的各种物本身不具备通信能力。 传感器、 执行器、 智能装置、 无线射频识别 (Radio Frequency Identification Devices, 简称为 RFID) 读写器等智能节点采集物理世界的信 息, 并通过通信模块和网络层进行信息交互。 其包含的主要部件有 M2M终端设备, M2M网关设备。 网络 /业务层:网络 /业务层支撑感知层信息的传递、路由和控制,为物联网人与物、 物与物通信提供支撑。 结合物联网分类, 网络层面具体包含的网络形态有: 通信网、 互联网、 行业网等。 其包含的主要部件有 M2M平台。 应用层: 应用层包含各种具体物联网应用, 既有公众服务, 也有行业服务, 行业 服务可以是面向公众的行业公众服务, 也可以是满足行业内部特定应用需求的行业专 用服务。 其中公众服务是面向公众普遍需求提供的基础服务, 如智能家居、 移动支付 等。 行业专用服务通常是面向行业自身特有的需要, 面向行业内部提供的服务, 如智 能电网、 智能交通、 智能环境等; 其中部分行业服务也可以面向公众提供, 如智能交 通, 称为行业公众服务。 其包含的主要部件有 M2M应用服务器。
终端外设: 终端外设指的是具有环境感知功能的传感器等单个设备, 它能将感知 到的信息通过 M2M网关发送给 M2M业务平台或 M2M应用, 同时还可以接收 M2M 应用或 M2M业务平台的对其的下行控制。
M2M网关: M2M终端外设其处理能力、 存储能力以及电源受限等特点, 不能直 接与通信网络进行通信,需要通过 M2M网关接入通信网络。 M2M网关可以进行 M2M 感知延伸层与上层网络之间的协议转换。 M2M网关除了能够汇聚和转发 M2M终端外 设采集到的数据信息外,还可以接收 M2M应用或 M2M业务平台的控制信息,对终端 外设进行管理。
M2M平台向 M2M应用提供一些共性的能力和支撑, 并提供开放的接口, 使应用 可以接入和使用网络资源和能力。 通过向具体 M2M应用提供标准化的应用程序接口 (API), 可以简化物联网应用开发复杂度和降低物联网应用开发部署成本。 在 M2M通信网络架构中, 网关作为连接和管理感知延伸层终端设备的功能实体, 需要能够提供给 M2M平台或 M2M应用服务器 M2M应用执行状态, 网关软件和硬件 运行状态,终端设备的运行状态等信息, 以提供给 M2M平台或 M2M应用服务器统计 数据和故障报警。 然而, 现有技术并没有提供一种监控方式能够满足 M2M通信网络 架构中的这一需求。 针对相关技术中网关无法为 M2M平台或 M2M应用服务器提供 M2M应用执行状 态、 网关软件和硬件运行状态、 终端设备的运行状态等信息, 也无法向 M2M平台或 M2M应用服务器提供统计数据和故障报警的问题, 目前尚未提出有效的解决方案。 发明内容 本发明实施例提供了一种监控方法及装置, 以至少解决上述问题。 根据本发明的一个实施例, 提供了一种监控方法, 包括: 网关对监控配置信息中 的监控对象进行监控操作, 获得监控结果; 网关根据监控配置信息中的报告配置向机 器对机器 (M2M) 业务平台或 M2M应用服务器上报监控结果。 优选地,在网关对监控配置信息中的监控对象进行监控操作之前, 该方法还包括: 网关获取监控配置信息, 其中, 监控配置信息是预先配置在网关上的, 或者, 是由网 关从 M2M业务平台或 M2M应用服务器上接收来的。 优选地, 监控配置信息包括一个监控任务或多个监控任务, 其中, 监控任务包括: 监控标识,用于唯一标识一个监控任务,是由 M2M业务平台或 M2M应用服务器或网
关分配的; 监控对象, 用于指示需要监控的对象; 报告配置, 包括: 报告方式和报告 参数。 优选地, 监控对象包括: 网关的广域网 WAN端口、 网关的局域网 LAN端口、 终 端外设、 网关软件模块, 或网关硬件模块。 优选地, 报告方式包括: 周期性上报和事件触发上报, 其中, 周期性上报设置有 包括预定的上报周期; 事件触发上报设置有至少一个事件定义, 其中, 事件定义包括: 事件标识和触发条件。 优选地, 同一个监控对象能够设置多种报告方式。 优选地, 网关对监控配置信息中的监控对象进行监控操作, 获得监控结果, 包括: 网关将监控任务保存在本地监控任务列表中; 网关按照监控任务列表对监控对象进行 监控, 获取监控对象的监控结果。
优选地, 所述上报模块, 用于如果所述终端外设未在所述网关注册, 向 M2M业 务平台或 M2M应用服务器上报监控对象不存在的监控结果。
优选地, 所述上报模块, 用于当所述报告方式为所述周期性上报时, 在所述监控 周期结束时,上报所述监控结果给 M2M业务平台或 M2M应用服务器;所述上报模块, 用于当所述报告方式为所述事件触发上报时, 在触发条件满足时, 上报所述监控结果 给 M2M业务平台或 M2M应用服务器。 根据本发明的另一实施例, 提供了一种监控装置, 位于网关, 包括: 监控模块, 设置为对监控配置信息中的监控对象进行监控操作, 获得监控结果; 上报模块, 设置 为根据监控配置信息中的报告配置向机器对机器 M2M业务平台或 M2M应用服务器上 报监控结果。 优选地, 该装置还包括: 获取模块, 设置为获取监控配置信息, 其中, 监控配置 信息是预先配置在网关上的,或者,是由网关从 M2M业务平台或 M2M应用服务器上 接收来的。 优选地, 监控配置信息包括一个监控任务或多个监控任务, 其中, 监控任务包括: 监控标识,用于唯一标识一个监控任务,是由 M2M业务平台或 M2M应用服务器或网 关分配的; 监控对象, 用于指示需要监控的对象; 报告配置, 包括: 报告方式和报告 参数。
优选地, 监控对象包括: 网关的广域网 WAN端口、 网关的局域网 LAN端口、 终 端外设、 网关软件模块, 或网关硬件模块。 优选地, 报告方式包括: 周期性上报和事件触发上报, 其中, 周期性上报设置有 包括预定的上报周期; 事件触发上报设置有至少一个事件定义, 其中, 事件定义包括: 事件标识和触发条件。 优选地, 同一个监控对象能够设置多种报告方式。 优选地, 监控模块包括: 保存单元, 设置为将监控任务保存在本地监控任务列表 中; 监控单元, 设置为按照监控任务列表对监控对象进行监控, 获取监控对象的监控 结果。 优选地,如果终端外设未在网关注册, 网关向 M2M业务平台或 M2M应用服务器 上报监控对象不存在的监控结果。 优选地, 当报告方式为周期性上报时, 在监控周期结束时, 网关上报监控结果给 M2M业务平台或 M2M应用服务器; 当报告方式为事件触发上报时, 在触发条件满足 时, 网关上报监控结果给 M2M业务平台或 M2M应用服务器。 通过本发明, 采用网关根据监控配置信息对 M2M设备进行监控操作, 获得监控 报告后并将监控报告上报的方式,解决了相关技术中网关无法为 M2M平台或 M2M应 用服务器提供 M2M应用执行状态、 网关软件和硬件运行状态、 终端外设的运行状态 等信息,也无法向 M2M平台或 M2M应用服务器提供统计数据和故障报警的问题,进 而达到了能够使 M2M网络能根据需求掌握各种状态参数进行统计, 同时还能根据配 置及时的获得故障报警信息, 及时做出相应的操作的效果。 附图说明 此处所说明的附图用来提供对本发明的进一步理解, 构成本申请的一部分, 本发 明的示意性实施例及其说明用于解释本发明, 并不构成对本发明的不当限定。 在附图 中- 图 1是根据本发明实施例的监控方法流程图; 图 2是根据本发明优选实施例一的监控流程图; 图 3是根据本发明优选实施例二的监控流程图;
图 4是根据本发明实施例的监控装置的结构框图; 以及 图 5是根据本发明优选实施例的监控装置的结构框图。 具体实施方式 下文中将参考附图并结合实施例来详细说明本发明。 需要说明的是, 在不冲突的 情况下, 本申请中的实施例及实施例中的特征可以相互组合。 图 1是根据本发明实施例的监控方法流程图, 如图 1所示, 该方法主要包括以下 步骤 (步骤 S 102-步骤 S 104): 步骤 S102, 网关对监控配置信息中的监控对象进行监控操作, 获得监控结果; 步骤 S104, 网关根据监控配置信息中的报告配置向机器对机器 M2M业务平台或 M2M应用服务器上报监控结果。 在本实施例中,在步骤 S102之前,该方法还包括: 网关获取监控配置信息,其中, 监控配置信息是预先配置在网关上的,或者,是由网关从 M2M业务平台或 M2M应用 服务器上接收来的。 在本实施例中, 监控配置信息包括一个监控任务或多个监控任务, 其中, 监控任 务包括: 监控标识, 用于唯一标识一个监控任务, 是由 M2M业务平台或 M2M应用服 务器或网关分配的; 监控对象, 用于指示需要监控的对象; 报告配置, 包括: 报告方 式和报告参数。 优选地, 监控对象包括: 网关的广域网 WAN端口、 网关的局域网 LAN端口、 终 端外设、 网关软件模块, 或网关硬件模块。 优选地, 报告方式包括: 周期性上报和事件触发上报, 其中, 周期性上报设置有 包括预定的上报周期; 事件触发上报设置有至少一个事件定义, 其中, 事件定义包括: 事件标识和触发条件。 在本实施例中, 同一个监控对象能够设置多种报告方式。 在本实施例中,步骤 S102可以采用这样的方式来实现: 网关将监控任务保存在本 地监控任务列表中; 网关按照监控任务列表对监控对象进行监控, 获取监控对象的监 控结果。
在本实施例中,如果终端外设未在网关注册, 网关向 M2M业务平台或 M2M应用 服务器上报监控对象不存在的监控结果。 在本实施例中, 当报告方式为周期性上报时, 在监控周期结束时, 网关上报监控 结果给 M2M业务平台或 M2M应用服务器; 当报告方式为事件触发上报时,在触发条 件满足时, 网关上报监控结果给 M2M业务平台或 M2M应用服务器。 下面结合图 2、 图 3与优选实施例一、 优选实例二对上述监控方法进行详细说明。 优选实施例一 图 2是根据本发明优选实施例一的监控流程图, 如图 2所示, 该流程包括以下步 骤 (步骤 S202-步骤 S206): 步骤 S202, M2M业务平台或 M2M应用服务器发送监控配置消息给网关。 监控配置消息包含的信息如表一所示: 表
下面对三个监控参数进行简要说明: 监控标识:用于唯一地标识一个监控任务, 由 M2M业务平台或 M2M应用服务器 分配; 监控对象: 用于指示需要监控的对象, 例如, 网关的 WAN端口 (广域网), 或网 关的 LAN (局域网), 或终端外设, 或网关软件模块, 或网关硬件模块; 报告配置: 包括报告方式和报告参数; 其中, 报告方式为: 周期性上报, 或事件 触发上报, 其中周期性上报设置周期时间, 事件触发上报设置事件定义, 包括设置事 件标识和触发条件;报告参数: 需要上报给 M2M业务平台或 M2M应用服务器的监控 结果。 这里需要说明的是, 针对同一个监控对象可以设置多种报告方式, 并且对事件触 发上报的方式还可以设置多个上报事件。
例如, 报告方式为"事件触发上报", 事件标识为"事件 A", 触发条件为" IP地址变 化", 报告参数为"网关标识, 时间, 事件", 那么网关就会在 IP地址改变的时候发送 包含网关标识,当前时间,事件标识的监控报告给 M2M业务平台或 M2M应用服务器。 监控配置举例一 (事件触发类监控任务), 如表二所示: 表二
监控配置举例二 (周期性触发类监控任务), 如表 表三
步骤 S204, 网关接收到监控配置消息后, 根据监控配置消息执行监控。 网关将监控配置中的监控任务保存在本地监控任务列表中, 并对监控配置中设置 的监控对象进行监控, 获取该监控对象的监控结果, 监控结果是根据监控配置的报告 配置中设置的报告参数来获取。 步骤 S206, 网关发送监控报告给 M2M业务平台或 M2M应用服务器。
( 1 )如果监控对象设置的终端外设未在网关注册, 网关应该向 M2M业务平台或 M2M应用报告监控对象不存在;
(2)如果报告配置指示为周期性上报, 则网关在监控周期定时器到时时, 将监控 结果发送给 M2M业务平台或 M2M应用服务器;监控结果即根据报告参数所获取的数 据。
( 3 ) 如果监控配置指示为事件触发上报, 则在事件发生后, 将监控结果发送给 M2M业务平台或 M2M应用服务器。 网关发送的监控报告包含的信息表四所示: 表四
参数
监控标识
监控结果 其中, 监控结果如表五所示: 表五
优选实施例二 图 3是根据本发明优选实施例二的监控流程图, 如图 3所示, 该流程包括以下步 骤 (步骤 S302-步骤 S306): 步骤 S302, 根据用户的需求, 网关可以预先在本地配置监控任务, 监控任务通过 设置监控配置消息来实现。 监控配置消息包含信息如表六所示: 表六
下面对三个监控参数进行简要说明: 监控标识: 用于唯一地标识一个监控任务, 由网关分配; 监控对象: 用于指示需要监控的对象, 例如, 网关的 WAN端口 (广域网), 或网 关的 LAN (局域网), 或终端外设, 或网关, 或网关软件模块, 或网关硬件模块。
报告配置: 包括报告方式和报告参数; 其中, 报告方式为: 周期性上报, 或事件 触发上报, 其中周期性上报设置周期时间, 事件触发上报设置事件定义, 包括设置事 件标识和触发条件;报告参数为: 需要上报给 M2M业务平台或 M2M应用服务器的监 控结果。 这里需要说明的是, 针对同一个监控对象可以设置多种报告方式, 并且对事件触 发上报方式还可以设置多个上报事件。 例如, 报告方式为"事件触发上报", 事件标识为"事件 A", 触发条件为" IP地址变 化", 报告参数为"网关标识, 时间, 事件", 那么网关就会在 IP地址改变的时候发送 包含网关标识,当前时间,事件标识的监控报告给 M2M业务平台或 M2M应用服务器。 步骤 S304, 网关根据监控配置消息执行监控。 网关将监控配置中的监控任务保存在本地监控任务列表中, 并对监控配置中设置 的监控对象进行监控, 获取该监控对象的监控结果, 监控结果是根据监控配置的报告 配置中设置的报告参数来获取。 步骤 S306, 网关发送监控报告给 M2M业务平台或 M2M应用服务器。 ( 1 )如果监控配置指示为周期性上报, 则在监控周期定时器到时时, 按照报告配 置中指定的报告参数将监控结果发送给 M2M业务平台或 M2M应用服务器;其中,监 控结果即根据报告参数所获取的数据。
(2)如果监控配置指示为事件触发上报, 则在事件发生后, 按照报告配置中指定 的报告参数将监控结果发送给 M2M业务平台或 M2M应用服务器;其中, 网关发送的 监控报告包含信息如表七所示: 表七
- 参数 _
监控标识
监控结果 采用上述实施例提供的监控方法, 解决了相关技术中网关无法为 M2M 平台或 M2M应用服务器提供 M2M应用执行状态、 网关软件和硬件运行状态、 终端外设的运 行状态等信息,也无法向 M2M平台或 M2M应用服务器提供统计数据和故障报警的问 题, 进而达到了能够使 M2M网络能根据需求掌握各种状态参数进行统计, 同时还能 根据配置及时的获得故障报警信息, 及时做出相应的操作的效果。
图 4是根据本发明实施例的监控装置的结构框图, 该装置位于网关, 用以实现上 述实施例提供的监控方法, 如图 4所示, 该装置主要包括: 监控模块 10和上报模块 20。 其中, 监控模块 10, 设置为对监控配置信息中的监控对象进行监控操作, 获得监 控结果; 上报模块 20, 连接至监控模块 10, 设置为根据监控配置信息中的报告配置向 机器对机器 M2M业务平台或 M2M应用服务器上报监控结果。 图 5是根据本发明优选实施例的监控装置的结构框图, 如图 5所示, 该装置还包 括: 获取模块 30, 与监控模块 10连接, 设置为获取监控配置信息, 其中, 监控配置 信息是预先配置在网关上的,或者,是由网关从 M2M业务平台或 M2M应用服务器上 接收来的。 在该优选实施例中, 监控配置信息包括一个监控任务或多个监控任务, 其中, 监 控任务包括: 监控标识, 用于唯一标识一个监控任务, 是由 M2M业务平台或 M2M应 用服务器或网关分配的; 监控对象, 用于指示需要监控的对象; 报告配置, 包括: 报 告方式和报告参数。 其中, 监控对象包括: 网关的广域网 WAN端口、 网关的局域网 LAN端口、 终端 外设、 网关软件模块, 或网关硬件模块。 其中, 报告方式包括: 周期性上报和事件触发上报, 其中, 周期性上报设置有包 括预定的上报周期; 事件触发上报设置有至少一个事件定义, 其中, 事件定义包括: 事件标识和触发条件。 优选地, 同一个监控对象能够设置多种报告方式。 在该优选实施例中, 监控模块 10包括: 保存单元 12, 设置为将监控任务保存在 本地监控任务列表中; 监控单元 14, 连接至保存单元 12, 设置为按照监控任务列表对 监控对象进行监控, 获取监控对象的监控结果。
在该优选实施例中, 所述上报模块, 用于如果所述终端外设未在所述网关注册, 向 M2M业务平台或 M2M应用服务器上报监控对象不存在的监控结果。
在该优选实施例中, 所述上报模块, 用于当所述报告方式为所述周期性上报时, 在所述监控周期结束时,上报所述监控结果给 M2M业务平台或 M2M应用服务器;所 述上报模块, 用于当所述报告方式为所述事件触发上报时, 在触发条件满足时, 上报 所述监控结果给 M2M业务平台或 M2M应用服务器。
采用上述实施例提供的监控装置, 解决了相关技术中网关无法为 M2M 平台或 M2M应用服务器提供 M2M应用执行状态、 网关软件和硬件运行状态、 终端外设的运 行状态等信息,也无法向 M2M平台或 M2M应用服务器提供统计数据和故障报警的问 题, 进而达到了能够使 M2M网络能根据需求掌握各种状态参数进行统计, 同时还能 根据配置及时的获得故障报警信息, 及时做出相应的操作的效果。 从以上的描述中, 可以看出, 本发明实现了如下技术效果: 采用网关根据监控配 置信息对 M2M设备进行监控操作, 获得监控报告后并将监控报告上报的方式, 可以 解决相关技术中网关无法为 M2M平台或 M2M应用服务器提供 M2M应用执行状态、 网关软件和硬件运行状态、 终端外设的运行状态等信息, 也无法向 M2M平台或 M2M 应用服务器提供统计数据和故障报警的问题, 进而达到了能够使 M2M网络能根据需 求掌握各种状态参数进行统计, 同时还能根据配置及时的获得故障报警信息, 及时做 出相应的操作的效果。 显然, 本领域的技术人员应该明白, 上述的本发明的各模块或各步骤可以用通用 的计算装置来实现, 它们可以集中在单个的计算装置上, 或者分布在多个计算装置所 组成的网络上, 可选地, 它们可以用计算装置可执行的程序代码来实现, 从而, 可以 将它们存储在存储装置中由计算装置来执行, 并且在某些情况下, 可以以不同于此处 的顺序执行所示出或描述的步骤, 或者将它们分别制作成各个集成电路模块, 或者将 它们中的多个模块或步骤制作成单个集成电路模块来实现。 这样, 本发明不限制于任 何特定的硬件和软件结合。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本领域的技 术人员来说, 本发明可以有各种更改和变化。 凡在本发明的精神和原则之内, 所作的 任何修改、 等同替换、 改进等, 均应包含在本发明的保护范围之内。
Claims
1. 一种监控方法, 包括:
网关对监控配置信息中的监控对象进行监控操作, 获得监控结果; 所述网关根据所述监控配置信息中的报告配置向机器对机器 M2M业务平 台或 M2M应用服务器上报所述监控结果。
2. 根据权利要求 1所述的方法, 其中, 在网关对监控配置信息中的监控对象进行 监控操作之前, 所述方法还包括:
所述网关获取所述监控配置信息, 其中, 所述监控配置信息是预先配置在 所述网关上的, 或者, 是由所述网关从所述 M2M业务平台或所述 M2M应用 服务器上接收来的。
3. 根据权利要求 2所述的方法, 其中, 所述监控配置信息包括一个监控任务或多 个监控任务, 其中, 所述监控任务包括:
监控标识, 用于唯一标识一个监控任务, 是由所述 M2M业务平台或所述 M2M应用服务器或所述网关分配的;
所述监控对象, 用于指示需要监控的对象;
所述报告配置, 包括: 报告方式和报告参数。
4. 根据权利要求 3所述的方法, 其中, 所述监控对象包括: 网关的广域网 WAN 端口、 网关的局域网 LAN端口、 终端外设、 网关软件模块, 或网关硬件模块。
5. 根据权利要求 3所述的方法, 其中, 所述报告方式包括: 周期性上报和事件触 发上报, 其中,
所述周期性上报设置有包括预定的上报周期;
所述事件触发上报设置有至少一个事件定义, 其中, 所述事件定义包括: 事件标识和触发条件。
6. 根据权利要求 5所述的方法, 其中, 同一个所述监控对象能够设置多种所述报 告方式。
7. 根据权利要求 3所述的方法, 其中, 网关对监控配置信息中的监控对象进行监 控操作, 获得监控结果, 包括:
所述网关将所述监控任务保存在本地监控任务列表中;
所述网关按照所述监控任务列表对所述监控对象进行监控, 获取所述监控 对象的监控结果。
8. 根据权利要求 4所述的方法, 其中,
如果所述终端外设未在所述网关注册,所述网关向 M2M业务平台或 M2M 应用服务器上报监控对象不存在的监控结果。
9. 根据权利要求 5所述的方法, 其中,
当所述报告方式为所述周期性上报时,
在所述监控周期结束时,网关上报所述监控结果给 M2M业务平台或 M2M 应用服务器;
当所述报告方式为所述事件触发上报时,
在触发条件满足时,所述网关上报所述监控结果给 M2M业务平台或 M2M 应用服务器。
10. 一种监控装置, 位于网关, 包括:
监控模块, 设置为对监控配置信息中的监控对象进行监控操作, 获得监控 结果;
上报模块,设置为根据所述监控配置信息中的报告配置向机器对机器 M2M 业务平台或 M2M应用服务器上报所述监控结果。
11. 根据权利要求 10所述的装置, 其中, 所述装置还包括:
获取模块, 设置为获取所述监控配置信息, 其中, 所述监控配置信息是预 先配置在所述网关上的,或者,是由所述网关从所述 M2M业务平台或所述 M2M 应用服务器上接收来的。
12. 根据权利要求 11所述的装置,其中,所述监控配置信息包括一个监控任务或多 个监控任务, 其中, 所述监控任务包括:
监控标识, 用于唯一标识一个监控任务, 是由所述 M2M业务平台或所述 M2M应用服务器或所述网关分配的;
所述监控对象, 用于指示需要监控的对象;
所述报告配置, 包括: 报告方式和报告参数。
13. 根据权利要求 12所述的装置, 其中, 所述监控对象包括: 网关的广域网 WAN 端口、 网关的局域网 LAN端口、 终端外设、 网关软件模块, 或网关硬件模块。
14. 根据权利要求 12所述的装置, 其中, 所述报告方式包括: 周期性上报和事件触 发上报, 其中,
所述周期性上报设置有包括预定的上报周期;
所述事件触发上报设置有至少一个事件定义, 其中, 所述事件定义包括: 事件标识和触发条件。
15. 根据权利要求 14所述的装置,其中, 同一个所述监控对象能够设置多种所述报 告方式。
16. 根据权利要求 12所述的装置, 其中, 所述监控模块包括:
保存单元, 设置为将所述监控任务保存在本地监控任务列表中; 监控单元, 设置为按照所述监控任务列表对所述监控对象进行监控, 获取 所述监控对象的所述监控结果。
17. 根据权利要求 13所述的装置, 其中,
所述上报模块, 用于如果所述终端外设未在所述网关注册, 向 M2M业务 平台或 M2M应用服务器上报监控对象不存在的监控结果。
18. 根据权利要求 14所述的装置, 其中,
所述上报模块, 用于当所述报告方式为所述周期性上报时, 在所述监控周 期结束时, 上报所述监控结果给 M2M业务平台或 M2M应用服务器;
所述上报模块, 用于当所述报告方式为所述事件触发上报时, 在触发条件 满足时, 上报所述监控结果给 M2M业务平台或 M2M应用服务器。
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP13845137.2A EP2911438A4 (en) | 2012-10-09 | 2013-08-12 | METHOD AND DEVICE FOR MONITORING |
US14/434,183 US20150382132A1 (en) | 2012-10-09 | 2013-08-12 | Method and Device for Monitoring |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201210379843.8 | 2012-10-09 | ||
CN201210379843.8A CN103716822A (zh) | 2012-10-09 | 2012-10-09 | 监控方法及装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2014056344A1 true WO2014056344A1 (zh) | 2014-04-17 |
Family
ID=50409287
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2013/081329 WO2014056344A1 (zh) | 2012-10-09 | 2013-08-12 | 监控方法及装置 |
Country Status (4)
Country | Link |
---|---|
US (1) | US20150382132A1 (zh) |
EP (1) | EP2911438A4 (zh) |
CN (1) | CN103716822A (zh) |
WO (1) | WO2014056344A1 (zh) |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN104407957A (zh) * | 2014-10-29 | 2015-03-11 | 中国建设银行股份有限公司 | 一种***健康检测方法及装置 |
EP3258644A4 (en) * | 2015-02-12 | 2018-04-11 | ZTE Corporation | Monitoring processing method and device |
EP3291592A4 (en) * | 2015-04-28 | 2018-04-18 | ZTE Corporation | Monitoring management method and apparatus |
EP3154238B1 (en) * | 2014-07-09 | 2020-05-13 | ZTE Corporation | Method and device for policy-based m2m terminal device monitoring and control |
Families Citing this family (16)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103518350A (zh) * | 2012-05-14 | 2014-01-15 | 华为技术有限公司 | 群组通信的方法、***、群组服务器和群组成员设备 |
CN103731870B (zh) * | 2012-10-12 | 2019-09-10 | 中兴通讯股份有限公司 | 监控任务的管理方法及装置 |
WO2015174916A1 (en) * | 2014-05-14 | 2015-11-19 | Telefonaktiebolaget L M Ericsson (Publ) | Periodic management stabilization for internet of things |
CN105228079A (zh) * | 2014-05-30 | 2016-01-06 | 中兴通讯股份有限公司 | M2m业务数据处理方法、装置及m2m终端设备 |
GB2530552B (en) * | 2014-09-26 | 2018-07-25 | Telit Tech Cyprus Ltd | System and method of controlling operation of connected devices |
CN104243297A (zh) * | 2014-10-16 | 2014-12-24 | 成都思迈科技发展有限责任公司 | 一种多业务以太网网关*** |
US9967903B2 (en) | 2015-02-19 | 2018-05-08 | Huawei Technologies Co., Ltd | System and method for traffic control for machine type communications in a wireless communications system |
CN107295554A (zh) * | 2016-03-30 | 2017-10-24 | 中兴通讯股份有限公司 | 一种管理应用状态的方法和装置 |
CN109218051B (zh) * | 2017-07-03 | 2022-04-01 | ***通信有限公司研究院 | 管理物联网终端的方法、管理服务器、物联网终端和*** |
CN107770756A (zh) * | 2017-10-23 | 2018-03-06 | 中兴通讯股份有限公司 | 一种监控方法、终端、服务器、网关设备以及*** |
CN108471625A (zh) * | 2018-07-03 | 2018-08-31 | 徐州立讯信息科技有限公司 | 物联网无线通信质量自动监测方法和实现该方法的设备 |
US20210165690A1 (en) * | 2018-08-14 | 2021-06-03 | Telefonaktiebolaget Lm Ericsson (Publ) | System and Method for Efficient Execution and Monitoring of Machine-to-Machine Device Management Tasks |
CN109818813B (zh) * | 2019-03-28 | 2021-09-14 | 深圳市丰润达科技有限公司 | 智能网关设备的维护方法、装置和计算机可读存储介质 |
CN110532148B (zh) * | 2019-08-12 | 2022-12-23 | 北京金堤科技有限公司 | 微服务***的监控方法及装置 |
CN111756599B (zh) * | 2020-06-23 | 2022-07-12 | 中国联合网络通信集团有限公司 | 一种业务监控方法及业务监控*** |
CN115102730B (zh) * | 2022-06-10 | 2023-08-11 | 深圳市众功软件有限公司 | 多种设备的一体化监控方法、装置及电子设备 |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102026215A (zh) * | 2009-09-21 | 2011-04-20 | ***通信集团公司 | 一种m2m网络的监控方法、装置及*** |
CN102056140A (zh) * | 2009-11-06 | 2011-05-11 | 中兴通讯股份有限公司 | 机器类通讯终端信息的获取方法和*** |
CN102238517A (zh) * | 2010-04-26 | 2011-11-09 | 中兴通讯股份有限公司 | 机器类通信事件上报方法、装置及*** |
CN102378226A (zh) * | 2010-08-26 | 2012-03-14 | 华为技术有限公司 | 一种m2m业务的优化方法及装置 |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6954712B2 (en) * | 2003-04-01 | 2005-10-11 | International Business Machines Corporation | Multi-mode SCSI diagnostic tool, system, and method |
US7969922B2 (en) * | 2006-01-31 | 2011-06-28 | Qualcomm Incorporated | Apparatus and methods for providing configurable task management of a wireless device |
US9049255B2 (en) * | 2008-02-29 | 2015-06-02 | Blackberry Limited | Visual event notification on a handheld communications device |
TWI519098B (zh) * | 2009-12-28 | 2016-01-21 | 內數位專利控股公司 | 機器對機器閘道架構 |
KR101167939B1 (ko) * | 2010-01-08 | 2012-08-02 | 엘지전자 주식회사 | 이동통신 시스템에서의 mtc 장치의 모니터링 방법 |
TWI569615B (zh) * | 2010-03-01 | 2017-02-01 | 內數位專利控股公司 | 機器對機器閘道器 |
US8438278B2 (en) * | 2010-05-03 | 2013-05-07 | Htc Corporation | Methods for monitoring and reporting MTC events |
CN102281513B (zh) * | 2010-06-13 | 2013-12-11 | 电信科学技术研究院 | 一种机器类通信监测处理方法及设备 |
KR20120091486A (ko) * | 2010-12-22 | 2012-08-20 | 한국전자통신연구원 | 사물통신 디바이스의 배터리 수명 모니터링 장치 및 방법 |
US9473935B2 (en) * | 2011-12-02 | 2016-10-18 | Telecommunication Systems, Inc. | Dynamic transmission of personal data to only trusted entities |
CN103517414A (zh) * | 2012-06-26 | 2014-01-15 | 中兴通讯股份有限公司 | 机器类型通信用户设备的寻呼方法及装置 |
CN103780663B (zh) * | 2012-10-26 | 2019-05-07 | 中兴通讯股份有限公司 | 一种终端外设的远程管理方法、装置和*** |
-
2012
- 2012-10-09 CN CN201210379843.8A patent/CN103716822A/zh active Pending
-
2013
- 2013-08-12 EP EP13845137.2A patent/EP2911438A4/en not_active Withdrawn
- 2013-08-12 US US14/434,183 patent/US20150382132A1/en not_active Abandoned
- 2013-08-12 WO PCT/CN2013/081329 patent/WO2014056344A1/zh active Application Filing
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102026215A (zh) * | 2009-09-21 | 2011-04-20 | ***通信集团公司 | 一种m2m网络的监控方法、装置及*** |
CN102056140A (zh) * | 2009-11-06 | 2011-05-11 | 中兴通讯股份有限公司 | 机器类通讯终端信息的获取方法和*** |
CN102238517A (zh) * | 2010-04-26 | 2011-11-09 | 中兴通讯股份有限公司 | 机器类通信事件上报方法、装置及*** |
CN102378226A (zh) * | 2010-08-26 | 2012-03-14 | 华为技术有限公司 | 一种m2m业务的优化方法及装置 |
Non-Patent Citations (1)
Title |
---|
See also references of EP2911438A4 * |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3154238B1 (en) * | 2014-07-09 | 2020-05-13 | ZTE Corporation | Method and device for policy-based m2m terminal device monitoring and control |
CN104407957A (zh) * | 2014-10-29 | 2015-03-11 | 中国建设银行股份有限公司 | 一种***健康检测方法及装置 |
EP3258644A4 (en) * | 2015-02-12 | 2018-04-11 | ZTE Corporation | Monitoring processing method and device |
US10419950B2 (en) | 2015-02-12 | 2019-09-17 | Zte Corporation | Monitoring processing method and device |
EP3291592A4 (en) * | 2015-04-28 | 2018-04-18 | ZTE Corporation | Monitoring management method and apparatus |
Also Published As
Publication number | Publication date |
---|---|
EP2911438A1 (en) | 2015-08-26 |
US20150382132A1 (en) | 2015-12-31 |
CN103716822A (zh) | 2014-04-09 |
EP2911438A4 (en) | 2015-12-16 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2014056344A1 (zh) | 监控方法及装置 | |
CN108886531B (zh) | 使用服务层能力进行网络和应用管理 | |
Kim et al. | M2M service platforms: Survey, issues, and enabling technologies | |
CN105580396B (zh) | 用于在m2m***中传送通知消息的方法及其装置 | |
KR101740449B1 (ko) | M2m(machine-to-machine)시스템에서 게이트웨이 변경 방법 및 이를 위한 장치 | |
WO2014056345A1 (zh) | 监控任务的管理方法及装置 | |
US20200326989A1 (en) | Building pool-based m2m service layer through nfv | |
CN106789606B (zh) | 一种网络通信***、其管理方法及通信方法 | |
JP2016511451A (ja) | ネットワーク機能を開くためのシステムおよび方法、ならびに関連するネットワーク要素 | |
US11700301B2 (en) | Service registration based on service capabilities requirements and preferences | |
WO2012171168A1 (zh) | 监控室内覆盖网络的方法、设备及*** | |
Azzara et al. | The icsi m2m middleware for iot-based intelligent transportation systems | |
CN104936202A (zh) | 基于CoAP协议的6LoWPAN无线传感网络管理*** | |
EP3332513B1 (en) | Service element host selection | |
US20160249206A1 (en) | Data transmission method and device | |
Cai et al. | Design and implementation of a WiFi sensor device management system | |
CN101729530B (zh) | 一种数据同步方法及*** | |
WO2014067313A1 (zh) | 终端外设的注销方法和装置 | |
CN104462235A (zh) | 一种基于Restful Web Service的物联网通用事件服务机制 | |
WO2014183369A1 (zh) | 监控处理方法、装置及m2m网关 | |
KR20220001797A (ko) | 무선 통신 네트워크에서 네트워크 분석 정보 제공 방법 및 장치 | |
CN103532800B (zh) | M2m家居网络及根据该网络进行智能处理的方法 | |
EP3370368B1 (en) | Communication system, networking method and controller for application-driven network | |
CN109314651B (zh) | 用于高效http管理流程的面向管理信息库的协议 | |
Apat et al. | SDN-Enabled Fog Computing Architecture |
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: 13845137 Country of ref document: EP Kind code of ref document: A1 |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2013845137 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 14434183 Country of ref document: US |