WO2018170684A1 - 监控云平台的故障定位方法及*** - Google Patents

监控云平台的故障定位方法及*** Download PDF

Info

Publication number
WO2018170684A1
WO2018170684A1 PCT/CN2017/077331 CN2017077331W WO2018170684A1 WO 2018170684 A1 WO2018170684 A1 WO 2018170684A1 CN 2017077331 W CN2017077331 W CN 2017077331W WO 2018170684 A1 WO2018170684 A1 WO 2018170684A1
Authority
WO
WIPO (PCT)
Prior art keywords
camera
message
fault
monitoring
set time
Prior art date
Application number
PCT/CN2017/077331
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 PCT/CN2017/077331 priority Critical patent/WO2018170684A1/zh
Publication of WO2018170684A1 publication Critical patent/WO2018170684A1/zh

Links

Definitions

  • the present invention relates to the field of monitoring, and in particular, to a fault location method and system for monitoring a cloud platform.
  • the monitoring system consists of 5 parts: camera, transmission, control, display, and record registration.
  • the camera transmits the video image to the control host through the coaxial video cable, and the control host distributes the video signal to each monitor and recording device, and simultaneously records the voice signal to be transmitted into the recorder.
  • the operator can issue commands to control the up, down, left, and right movements of the pan/tilt and focus the zoom on the lens, and can be implemented in the multi-channel camera and the pan/tilt by the control host. Switch between. With special recording processing mode, images can be recorded, played back, processed, etc., so that the recording effect is optimal.
  • the application provides a fault location method for monitoring a cloud platform.
  • the invention solves the defects of high cost and low efficiency of the technical solutions of the prior art.
  • a method for monitoring a fault location of a cloud platform comprising the following steps:
  • the monitoring cloud platform When the monitoring cloud platform does not receive the heartbeat message of the first camera within the set time, sending a confirmation message to the first camera;
  • the other device that monitors the cloud platform is instructed to send the acknowledgment again. If the response message of the acknowledgment message is still not received within the set time, the first camera is determined. malfunction.
  • the method further includes:
  • the time when the heartbeat message of the first camera is received last time is recorded as the fault start time.
  • the method further includes:
  • the monitoring cloud platform sends a fault message of the first camera to the maintenance platform, where the fault message carries the identifier and coordinates of the first camera.
  • a fault location system for monitoring a cloud platform comprising:
  • a receiving unit configured to receive a heartbeat message broadcast by the camera
  • a processing unit configured to send an acknowledgement message to the first camera when the heartbeat message of the first camera is not received within the set time, and when the response message of the confirmation message is not received within the set time, indicating to monitor the cloud platform A device sends an acknowledgment again, and if the response message of the acknowledgment message is still not received within the set time, the first camera is determined to be faulty.
  • system further includes:
  • the processing unit is configured to record, as the first camera failure, the time when the heartbeat message of the first camera is received last time as the fault start time.
  • system further includes:
  • a sending unit configured to send, to the maintenance platform, a fault message of the first camera, where the fault message carries an identifier of the first camera and coordinates.
  • a monitoring system including: a processor, a wireless transceiver, a memory, and a bus, wherein the processor, the wireless transceiver, and the memory are connected by a bus.
  • the wireless transceiver is configured to receive a heartbeat message broadcast by a camera
  • the processor is configured to send an acknowledgement message to the first camera when the heartbeat message of the first camera is not received within the set time, and notify the monitoring cloud platform when the response message of the confirmation message is not received within the set time
  • Another device sends an acknowledgment again, such as a response message that the acknowledgment message has not been received within the set time, determining that the first camera is faulty.
  • the processor is specifically configured to record, as the first camera fault, the time when the heartbeat message of the first camera is received last time as the fault start time.
  • the transceiver is configured to send a fault message of the first camera to the service platform, where the fault message carries the identifier and coordinates of the first camera.
  • the technical solution provided by the present invention automatically determines the fault detection by transmitting an acknowledgement message, so that it has the advantage of low cost.
  • FIG. 1 is a flowchart of a fault location method for monitoring a cloud platform according to a first preferred embodiment of the present invention
  • FIG. 2 is a structural diagram of a fault location system for monitoring a cloud platform according to a second preferred embodiment of the present invention.
  • FIG. 3 is a hardware structural diagram of a monitoring system according to a second preferred embodiment of the present invention.
  • FIG. 1 is a schematic diagram of a fault location method for monitoring a cloud platform according to a first preferred embodiment of the present invention. The method is as shown in FIG.
  • Step S101 The monitoring cloud platform receives a heartbeat message broadcast by the camera.
  • Step S102 When the monitoring cloud platform does not receive the heartbeat message of the first camera within the set time, send an acknowledgement message to the first camera.
  • Step S103 When the monitoring cloud platform does not receive the response message of the acknowledgment message within the set time, the other device that monitors the cloud platform is instructed to send the acknowledgment again, if the response message of the acknowledgment message is still not received within the set time, determining The first camera is faulty.
  • the technical solution provided by the present invention automatically determines the fault detection by transmitting an acknowledgement message, so that it has the advantage of low cost.
  • the time when the heartbeat message of the first camera is received last time is recorded as the fault start time.
  • the monitoring cloud platform sends a fault message of the first camera to the maintenance platform, where the fault message carries the identifier and coordinates of the first camera.
  • FIG. 2 is a schematic diagram of a fault location system for monitoring a cloud platform according to a second preferred embodiment of the present invention. The system is as shown in FIG.
  • the receiving unit 201 is configured to receive a heartbeat message broadcast by the camera;
  • the processing unit 202 is configured to: when the heartbeat message of the first camera is not received within the set time, send an acknowledgement message to the first camera, and when the response message of the acknowledgement message is not received within the set time, indicate that the cloud platform is monitored. The other device sends an acknowledgment again, and if the response message of the acknowledgment message is still not received within the set time, the first camera failure is determined.
  • the technical solution provided by the present invention automatically determines the fault detection by transmitting an acknowledgement message, so that it has the advantage of low cost.
  • the system may further include: a processing unit 202, configured to record, as the first camera fault, the time when the heartbeat message of the first camera is received last time as the fault start time.
  • a processing unit 202 configured to record, as the first camera fault, the time when the heartbeat message of the first camera is received last time as the fault start time.
  • the sending unit 203 is configured to send, to the service platform, a fault message of the first camera, where the fault message carries the identifier of the first camera and coordinates.
  • FIG. 3 is a monitoring system 30, including: a processor 301, a wireless transceiver 302, a memory 303, and a bus 304.
  • the wireless transceiver 302 is configured to transmit and receive data with and from an external device.
  • the number of processors 301 can be one or more.
  • processor 301, memory 302, and transceiver 303 may be connected by bus 304 or other means.
  • Monitoring system 30 can be used to perform the steps of FIG. For the meaning and examples of the terms involved in the embodiment, reference may be made to the corresponding embodiment of FIG. 1. I will not repeat them here.
  • the wireless transceiver 302 is configured to receive a heartbeat message broadcast by the camera.
  • the program code is stored in the memory 303.
  • the processor 901 is configured to call the program code stored in the memory 903 for performing the following operations:
  • the processor 301 is configured to: when the heartbeat message of the first camera is not received within the set time, send an acknowledgement message to the first camera, and when the response message of the confirmation message is not received within the set time, indicate to monitor the cloud platform.
  • the other device sends an acknowledgment again, and if the response message of the acknowledgment message is still not received within the set time, the first camera failure is determined.
  • the processor 301 herein may be a processing component or a general term of multiple processing components.
  • the processing element can be a central processor (Central) Processing Unit, CPU), or a specific integrated circuit (Application Specific Integrated) Circuit, ASIC), or one or more integrated circuits configured to implement embodiments of the present application, such as one or more microprocessors (digital singnal Processor, DSP), or one or more Field Programmable Gate Arrays (FPGAs).
  • CPU central processor
  • ASIC Application Specific Integrated Circuit
  • DSP digital singnal Processor
  • FPGAs Field Programmable Gate Arrays
  • the memory 303 may be a storage device or a collective name of a plurality of storage elements, and is used to store executable program code or parameters, data, and the like required for the application running device to operate. And the memory 303 may include random access memory (RAM), and may also include non-volatile memory (non-volatile memory) Memory), such as disk storage, flash (Flash), etc.
  • RAM random access memory
  • non-volatile memory non-volatile memory
  • flash flash
  • Bus 304 can be an industry standard architecture (Industry Standard Architecture, ISA) bus, Peripheral Component (PCI) bus or extended industry standard architecture (Extended Industry Standard Architecture, EISA) bus, etc.
  • the bus can be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, only one thick line is shown in Figure 3, but it does not mean that there is only one bus or one type of bus.
  • the terminal may further include input and output means connected to the bus 304 for connection to other parts such as the processor 301 via the bus.
  • the input/output device can provide an input interface for the operator, so that the operator can select the control item through the input interface, and can also be other interfaces through which other devices can be externally connected.
  • the program may be stored in a computer readable storage medium, and the storage medium may include: Flash drive, read-only memory (English: Read-Only Memory, referred to as: ROM), random accessor (English: Random Access Memory, referred to as: RAM), disk or CD.
  • ROM Read-Only Memory
  • RAM Random Access Memory

Landscapes

  • Alarm Systems (AREA)

Abstract

本发明公开了一种监控云平台的故障定位方法,所述方法包括如下步骤:监控云平台接收摄像头广播的心跳消息;监控云平台在设定时间内未收到第一摄像头的心跳消息时,向第一摄像头发送确认消息;监控云平台在设定时间内未收到确认消息的响应消息时,指示监控云平台的另一设备再次发送确认,如在设定时间内仍然未收到确认消息的响应消息,确定第一摄像头故障。本发明提供的技术方案具有成本低的优点。

Description

监控云平台的故障定位方法及*** 技术领域
本发明涉及监控领域,尤其涉及一种监控云平台的故障定位方法及***。
背景技术
监控***是由摄像、传输、控制、显示、记录登记5大部分组成。摄像机通过同轴视频电缆将视频图像传输到控制主机,控制主机再将视频信号分配到各监视器及录像设备,同时可将需要传输的语音信号同步录入到录像机内。 通过控制主机,操作人员可发出指令,对云台的上、下、左、右的动作进行控制及对镜头进行调焦变倍的操作,并可通过控制主机实现在多路摄像机及云台之间的切换。利用特殊的录像处理模式,可对图像进行录入、回放、处理等操作,使录像效果达到最佳。
现有的监控***的故障定位基于人工检查,其方案成本高,并且效率低。
技术问题
本申请提供一种监控云平台的故障定位方法。其解决现有技术的技术方案成本高,效率低的缺点。
技术解决方案
一方面,提供一种监控云平台的故障定位方法,所述方法包括如下步骤:
监控云平台接收摄像头广播的心跳消息;
监控云平台在设定时间内未收到第一摄像头的心跳消息时,向第一摄像头发送确认消息;
监控云平台在设定时间内未收到确认消息的响应消息时,指示监控云平台的另一设备再次发送确认,如在设定时间内仍然未收到确认消息的响应消息,确定第一摄像头故障。
可选的,所述方法还包括:
如第一摄像头故障,将最后一次接收到第一摄像头的心跳消息的时间记录为故障起始时间。
可选的,所述方法还包括:
监控云平台向维修平台发送第一摄像头的故障消息,该故障消息携带第一摄像头的标识以及坐标。
第二方面,提供一种监控云平台的故障定位***,所述***包括:
接收单元,用于接收摄像头广播的心跳消息;
处理单元,用于在设定时间内未收到第一摄像头的心跳消息时,向第一摄像头发送确认消息,在设定时间内未收到确认消息的响应消息时,指示监控云平台的另一设备再次发送确认,如在设定时间内仍然未收到确认消息的响应消息,确定第一摄像头故障。
可选的,所述***还包括:
处理单元,用于如第一摄像头故障,将最后一次接收到第一摄像头的心跳消息的时间记录为故障起始时间。
可选的,所述***还包括:
发送单元,用于向维修平台发送第一摄像头的故障消息,该故障消息携带第一摄像头的标识以及坐标。
第三方面,提供一种监控***,包括:处理器、无线收发器、存储器和总线,所述处理器、无线收发器、存储器通过总线连接,
所述无线收发器,用于接收摄像头广播的心跳消息;
所述处理器,用于在设定时间内未收到第一摄像头的心跳消息时,向第一摄像头发送确认消息,在设定时间内未收到确认消息的响应消息时,指示监控云平台的另一设备再次发送确认,如在设定时间内仍然未收到确认消息的响应消息,确定第一摄像头故障。
可选的,述处理器,具体用于如第一摄像头故障,将最后一次接收到第一摄像头的心跳消息的时间记录为故障起始时间。
可选的,所述收发器,用于向维修平台发送第一摄像头的故障消息,该故障消息携带第一摄像头的标识以及坐标。
有益效果
本发明提供的技术方案通过发送确认消息来确定是否故障,自动实现故障的检测,所以其具有成本低的优点。
附图说明
为了更清楚地说明本发明实施例的技术方案,下面将对实施例描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1为本发明第一较佳实施方式提供的一种监控云平台的故障定位方法的流程图;
图2为本发明第二较佳实施方式提供的一种监控云平台的故障定位***的结构图。
图3为本发明第二较佳实施方式提供的一种监控***的硬件结构图。
本发明的实施方式
下面将结合本发明实施例中的附图,对本发明实施例中的技术方案进行清楚、完整地描述,显然,所描述的实施例是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例,都属于本发明保护的范围。
请参考图1,图1是本发明第一较佳实施方式提出的一种监控云平台的故障定位方法,该方法如图1所示,包括如下步骤:
步骤S101、监控云平台接收摄像头广播的心跳消息。
步骤S102、监控云平台在设定时间内未收到第一摄像头的心跳消息时,向第一摄像头发送确认消息。
步骤S103、监控云平台在设定时间内未收到确认消息的响应消息时,指示监控云平台的另一设备再次发送确认,如在设定时间内仍然未收到确认消息的响应消息,确定第一摄像头故障。
本发明提供的技术方案通过发送确认消息来确定是否故障,自动实现故障的检测,所以其具有成本低的优点。
可选的,如第一摄像头故障,将最后一次接收到第一摄像头的心跳消息的时间记录为故障起始时间。
可选的,监控云平台向维修平台发送第一摄像头的故障消息,该故障消息携带第一摄像头的标识以及坐标。
请参考图2,图2是本发明第二较佳实施方式提出的一种监控云平台的故障定位***,该***如图2所示,包括:
接收单元201,用于接收摄像头广播的心跳消息;
处理单元202,用于在设定时间内未收到第一摄像头的心跳消息时,向第一摄像头发送确认消息,在设定时间内未收到确认消息的响应消息时,指示监控云平台的另一设备再次发送确认,如在设定时间内仍然未收到确认消息的响应消息,确定第一摄像头故障。
本发明提供的技术方案通过发送确认消息来确定是否故障,自动实现故障的检测,所以其具有成本低的优点。
可选的,***还可以包括:处理单元202,用于如第一摄像头故障,将最后一次接收到第一摄像头的心跳消息的时间记录为故障起始时间。
可选的,发送单元203,用于向维修平台发送第一摄像头的故障消息,该故障消息携带第一摄像头的标识以及坐标。
参阅图3,图3为一种监控***30,包括:处理器301、无线收发器302、存储器303和总线304,无线收发器302用于与外部设备之间收发数据。处理器301的数量可以是一个或多个。本申请的一些实施例中,处理器301、存储器302和收发器303可通过总线304或其他方式连接。监控***30可以用于执行图1的步骤。关于本实施例涉及的术语的含义以及举例,可以参考图1对应的实施例。此处不再赘述。
无线收发器302,用于接收摄像头广播的心跳消息。
其中,存储器303中存储程序代码。处理器901用于调用存储器903中存储的程序代码,用于执行以下操作:
处理器301,用于在设定时间内未收到第一摄像头的心跳消息时,向第一摄像头发送确认消息,在设定时间内未收到确认消息的响应消息时,指示监控云平台的另一设备再次发送确认,如在设定时间内仍然未收到确认消息的响应消息,确定第一摄像头故障。
需要说明的是,这里的处理器301可以是一个处理元件,也可以是多个处理元件的统称。例如,该处理元件可以是中央处理器(Central Processing Unit,CPU),也可以是特定集成电路(Application Specific Integrated Circuit,ASIC),或者是被配置成实施本申请实施例的一个或多个集成电路,例如:一个或多个微处理器(digital singnal processor,DSP),或,一个或者多个现场可编程门阵列(Field Programmable Gate Array, FPGA)。
存储器303可以是一个存储装置,也可以是多个存储元件的统称,且用于存储可执行程序代码或应用程序运行装置运行所需要参数、数据等。且存储器303可以包括随机存储器(RAM),也可以包括非易失性存储器(non-volatile memory),例如磁盘存储器,闪存(Flash)等。
总线304可以是工业标准体系结构(Industry Standard Architecture,ISA)总线、外部设备互连(Peripheral Component,PCI)总线或扩展工业标准体系结构(Extended Industry Standard Architecture,EISA)总线等。该总线可以分为地址总线、数据总线、控制总线等。为便于表示,图3中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
该终端还可以包括输入输出装置,连接于总线304,以通过总线与处理器301等其它部分连接。该输入输出装置可以为操作人员提供一输入界面,以便操作人员通过该输入界面选择布控项,还可以是其它接口,可通过该接口外接其它设备。
需要说明的是,对于前述的各个方法实施例,为了简单描述,故将其都表述为一系列的动作组合,但是本领域技术人员应该知悉,本发明并不受所描述的动作顺序的限制,因为依据本发明,某一些步骤可以采用其他顺序或者同时进行。其次,本领域技术人员也应该知悉,说明书中所描述的实施例均属于优选实施例,所涉及的动作和模块并不一定是本发明所必须的。
在上述实施例中,对各个实施例的描述都各有侧重,某个实施例中没有详细描述的部分,可以参见其他实施例的相关描述。
本领域普通技术人员可以理解上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成,该程序可以存储于一计算机可读存储介质中,存储介质可以包括:闪存盘、只读存储器(英文:Read-Only Memory ,简称:ROM)、随机存取器(英文:Random Access Memory,简称:RAM)、磁盘或光盘等。
以上对本发明实施例所提供的内容下载方法及相关设备、***进行了详细介绍,本文中应用了具体个例对本发明的原理及实施方式进行了阐述,以上实施例的说明只是用于帮助理解本发明的方法及其核心思想;同时,对于本领域的一般技术人员,依据本发明的思想,在具体实施方式及应用范围上均会有改变之处,综上所述,本说明书内容不应理解为对本发明的限制。

Claims (9)

  1. 一种监控云平台的故障定位方法,其特征在于,所述方法包括如下步骤:
    监控云平台接收摄像头广播的心跳消息;
    监控云平台在设定时间内未收到第一摄像头的心跳消息时,向第一摄像头发送确认消息;
    监控云平台在设定时间内未收到确认消息的响应消息时,指示监控云平台的另一设备再次发送确认,如在设定时间内仍然未收到确认消息的响应消息,确定第一摄像头故障。
  2. 根据权利要求1所述的方法,其特征在于,所述方法还包括:
    如第一摄像头故障,将最后一次接收到第一摄像头的心跳消息的时间记录为故障起始时间。
  3. 根据权要求1所述的方法,其特征在于,所述方法还包括:
    监控云平台向维修平台发送第一摄像头的故障消息,该故障消息携带第一摄像头的标识以及坐标。
  4. 一种监控云平台的故障定位***,其特征在于,所述***包括:
    接收单元,用于接收摄像头广播的心跳消息;
    处理单元,用于在设定时间内未收到第一摄像头的心跳消息时,向第一摄像头发送确认消息,在设定时间内未收到确认消息的响应消息时,指示监控云平台的另一设备再次发送确认,如在设定时间内仍然未收到确认消息的响应消息,确定第一摄像头故障。
  5. 根据权利要求4所述的***,其特征在于,所述***还包括:
    处理单元,用于如第一摄像头故障,将最后一次接收到第一摄像头的心跳消息的时间记录为故障起始时间。
  6. 根据权利要求5所述的***,其特征在于,所述***还包括:
    发送单元,用于向维修平台发送第一摄像头的故障消息,该故障消息携带第一摄像头的标识以及坐标。
  7. 一种监控***,包括:处理器、无线收发器、存储器和总线,所述处理器、无线收发器、存储器通过总线连接,其特征在于,
    所述无线收发器,用于接收摄像头广播的心跳消息;
    所述处理器,用于在设定时间内未收到第一摄像头的心跳消息时,向第一摄像头发送确认消息,在设定时间内未收到确认消息的响应消息时,指示监控云平台的另一设备再次发送确认,如在设定时间内仍然未收到确认消息的响应消息,确定第一摄像头故障。
  8. 根据权利要求7所述的监控***,其特征在于,所述处理器,具体用于如第一摄像头故障,将最后一次接收到第一摄像头的心跳消息的时间记录为故障起始时间。
  9. 根据权利要求7所述的监控***,其特征在于,所述收发器,用于向维修平台发送第一摄像头的故障消息,该故障消息携带第一摄像头的标识以及坐标。
PCT/CN2017/077331 2017-03-20 2017-03-20 监控云平台的故障定位方法及*** WO2018170684A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/077331 WO2018170684A1 (zh) 2017-03-20 2017-03-20 监控云平台的故障定位方法及***

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2017/077331 WO2018170684A1 (zh) 2017-03-20 2017-03-20 监控云平台的故障定位方法及***

Publications (1)

Publication Number Publication Date
WO2018170684A1 true WO2018170684A1 (zh) 2018-09-27

Family

ID=63584001

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/077331 WO2018170684A1 (zh) 2017-03-20 2017-03-20 监控云平台的故障定位方法及***

Country Status (1)

Country Link
WO (1) WO2018170684A1 (zh)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080005626A1 (en) * 2005-03-25 2008-01-03 Schaff Glen D Monitoring system
CN202364292U (zh) * 2011-12-09 2012-08-01 天津市亚安科技股份有限公司 可自动监测重新启动并恢复摄像机参数的云台
CN102984501A (zh) * 2012-11-15 2013-03-20 杭州瑞网广通信息技术有限公司 一种网络视频录像集群***
CN104104723A (zh) * 2014-07-19 2014-10-15 福州大学 一种分布式协同监控***
CN105408944A (zh) * 2013-07-22 2016-03-16 因特立维森技术公司 用于可扩展视频云服务的***和方法
CN105872391A (zh) * 2016-06-15 2016-08-17 华为技术有限公司 网络摄像机的控制方法、装置及***

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080005626A1 (en) * 2005-03-25 2008-01-03 Schaff Glen D Monitoring system
CN202364292U (zh) * 2011-12-09 2012-08-01 天津市亚安科技股份有限公司 可自动监测重新启动并恢复摄像机参数的云台
CN102984501A (zh) * 2012-11-15 2013-03-20 杭州瑞网广通信息技术有限公司 一种网络视频录像集群***
CN105408944A (zh) * 2013-07-22 2016-03-16 因特立维森技术公司 用于可扩展视频云服务的***和方法
CN104104723A (zh) * 2014-07-19 2014-10-15 福州大学 一种分布式协同监控***
CN105872391A (zh) * 2016-06-15 2016-08-17 华为技术有限公司 网络摄像机的控制方法、装置及***

Similar Documents

Publication Publication Date Title
WO2013165088A1 (en) Distributed transcoding apparatus and method using multiple servers
JP2009512021A (ja) データを転送するためのシステムおよび方法
WO2018176390A1 (zh) 绕线机的安全防备方法及***
EP2564551A2 (en) Method and apparatus for transmitting content to plurality of devices
US20190306320A1 (en) Transmission apparatus, teleconference system, information processing method, and recording medium
WO2018170684A1 (zh) 监控云平台的故障定位方法及***
WO2018223354A1 (zh) 基于定位的考勤记录方法及***
WO2014088156A1 (en) Apparatus and circuit for processing data
WO2017124292A1 (zh) 一种视频网络会议会场连接的方法及***
WO2018161342A1 (zh) 监控云平台分布式***的选举方法及***
WO2018170683A1 (zh) 监控***中云服务的任务分配方法及***
WO2018161220A1 (zh) 监控***中云平台的分组任务分配方法及***
WO2018161219A1 (zh) 监控视频大数据的管理方法及***
WO2018170685A1 (zh) 监控云平台的视频拼接方法及***
WO2018209586A1 (zh) 蓝牙的定位方法及***
CN105704422B (zh) 一种视频会议组网***及其方法
WO2019061384A1 (zh) 分布式爬虫***中任务管理器的选举方法及***
WO2018223375A1 (zh) 终端流量的控制提醒方法及***
CN112839243B (zh) 码流中转方法、装置、电子设备及存储介质
WO2018184152A1 (zh) 基于绕线机的错误修改方法及***
WO2018176449A1 (zh) 绕线机的进度统计和分配方法及***
WO2018165837A1 (zh) 网上信息抓取方法及***
WO2018223371A1 (zh) 终端热点的接入控制方法及***
WO2018209549A1 (zh) 终端视频区间划分方法及***
WO2018209550A1 (zh) 终端的***更新方法及***

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17902455

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 20.01.2020)

122 Ep: pct application non-entry in european phase

Ref document number: 17902455

Country of ref document: EP

Kind code of ref document: A1