Event message transmission method, electronic equipment and monitoring system
By setting up a processing unit in the electronic device, and identifying and forwarding event messages based on message forwarding rules, the problem of poor real-time performance in traditional monitoring systems is solved, and efficient and real-time event message transmission is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- TP-LINK
- Filing Date
- 2026-01-26
- Publication Date
- 2026-04-28
AI Technical Summary
In traditional monitoring systems, event messages need to be processed by the software of the video recorder's main controller, resulting in poor real-time performance, high system resource consumption, and low flexibility and forwarding efficiency.
A processing unit is set up in the electronic device to receive event messages sent by the camera device, and to identify and forward them based on preset message forwarding rules, thereby avoiding the software processing flow of the main controller and directly forwarding the event messages to the cloud at the target forwarding address.
It improves the transmission efficiency and real-time performance of event messages, reduces latency, saves system resources, and maintains stable performance in high-concurrency scenarios.
Smart Images
Figure CN121940657A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of video surveillance technology, and in particular to an event message transmission method, electronic device and monitoring system. Background Technology
[0002] In traditional surveillance systems, video cameras (IPCs) capture video and generate event messages, which are then published to a network video recorder (NVR). The NVR, as the central node of the system, is responsible for local storage of received event messages, event logic processing, and forwarding messages based on subscription requests from the cloud or other clients. However, the event messages require software processing on the NVR's main controller, resulting in a cumulative processing delay and poor real-time performance. Summary of the Invention
[0003] According to various embodiments of this application, an event message transmission method, electronic device, and monitoring system are provided; these can improve the real-time performance of event message transmission.
[0004] In a first aspect, this application provides an event message transmission method applied to an electronic device, the electronic device including a processing unit, the method comprising:
[0005] The processing unit receives event messages sent by the camera device; based on preset message forwarding rules, the processing unit identifies the event messages and determines the target forwarding address corresponding to the event messages; the processing unit then sends the event messages to the cloud corresponding to the target forwarding address.
[0006] By setting up a processing unit in the electronic device and identifying and quickly forwarding received event messages based on message forwarding rules, the problem of poor real-time event transmission caused by the accumulated delay of the complex processing flow of traditional main control software is solved. Based on the independent processing of the processing unit, the interference of system load on event transmission is reduced, and the real-time performance and accuracy of event reporting are significantly improved. Stable low-latency performance can still be maintained in high-concurrency event scenarios. It has strong ease of use and practicality.
[0007] In one possible implementation of the first aspect, the electronic device further includes a main controller; and before receiving the event message sent by the camera device through the processing unit, the method further includes: The main controller sends a subscription request to the camera device, the subscription request containing subscription information and a reporting identifier; The subscription information is used to indicate the attributes of the event message, and the reporting identifier is used to indicate the resource identifier to which the camera device is subscribed.
[0008] In one possible implementation of the first aspect, the electronic device further includes a main controller; and before receiving the event message sent by the camera device through the processing unit, the method further includes: The main controller sends the message forwarding rule to the processing unit; the message forwarding rule is used to indicate the forwarding path of the event message by the processing unit.
[0009] In one possible implementation of the first aspect, the step of identifying the event message and determining the target forwarding address corresponding to the event message by the processing unit based on a preset message forwarding rule includes: Identify the event message and determine the source address and reporting identifier of the event message; In the message forwarding rule, the target forwarding address corresponding to the source address and the reporting identifier is determined.
[0010] In one possible implementation of the first aspect, the step of sending the event message from the processing unit to the cloud corresponding to the target forwarding address includes: The original destination address in the event message is modified to the target forwarding address, and the modified event message is sent to the cloud corresponding to the target forwarding address.
[0011] In one possible implementation of the first aspect, the method further includes: Receive one or more business subscription rules from the cloud, and generate the message forwarding rules based on the business subscription rules.
[0012] In one possible implementation of the first aspect, before sending the subscription request to the camera device via the main controller, the method further includes: Receive one or more business subscription rules from the cloud, and generate the subscription request based on the business subscription rules.
[0013] In one possible implementation of the first aspect, the method further includes: Upon receiving a new business subscription rule from the cloud, the message forwarding rule and the subscription request are updated based on the new business subscription rule. The updated message forwarding rules are sent to the processing unit and the updated subscription request is sent to the camera device.
[0014] Secondly, this application provides an event message transmission device, which includes: The receiving module is used to receive event messages sent by the camera device; The processing module is used to identify the event message based on a preset message forwarding rule and determine the target forwarding address corresponding to the event message; The sending module is used to send the event message to the cloud corresponding to the target forwarding address.
[0015] Thirdly, this application provides an electronic device including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the method described in any one of the first aspects.
[0016] Fourthly, this application provides a monitoring system, which includes a camera device, an electronic device, and a cloud platform; wherein the electronic device is equipped with a processing unit. The camera device is used to generate an event message and send the event message to the electronic device; The electronic device is configured to receive event messages sent by the camera device through the processing unit; identify the event messages based on preset message forwarding rules, determine the target forwarding address corresponding to the event messages; and send the event messages to the cloud corresponding to the target forwarding address. The cloud is used to receive the event messages sent by electronic devices through the processing unit.
[0017] Fifthly, this application provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the method described in any one of the first aspects.
[0018] Sixthly, this application provides a computer program product that, when run on a device, causes the device to perform the method described in any one of the first aspects above.
[0019] It is understood that the beneficial effects of the second to sixth aspects mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description
[0020] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0021] Figure 1 This is a schematic diagram of the architecture of the monitoring system provided in the embodiments of this application; Figure 2A schematic diagram illustrating the implementation flow of the event message transmission method provided in the embodiments of this application; Figure 3 A schematic diagram of the architecture of a network video recorder provided in an embodiment of this application; Figure 4 A schematic diagram of the event message reporting process provided in the embodiments of this application; Figure 5 A schematic diagram of the rule issuance process provided in the embodiments of this application; Figure 6 A schematic diagram of the rule update process provided in the embodiments of this application; Figure 7 This is a schematic diagram of the structure of the video frame rate control device provided in the embodiments of this application; Figure 8 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation
[0022] The embodiments of the technical solution of this application will now be described in detail with reference to the accompanying drawings. These embodiments are only used to more clearly illustrate the technical solution of this application and are therefore merely examples, and should not be used to limit the scope of protection of this application.
[0023] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains; the terminology used herein is for the purpose of describing particular embodiments only and is not intended to limit the application; the terms “comprising” and “having”, and any variations thereof, in the specification, claims, and foregoing description of the drawings are intended to cover non-exclusive inclusion.
[0024] In the description of the embodiments of this application, technical terms such as "first" and "second" are used only to distinguish different objects and should not be construed as indicating or implying relative importance or implicitly specifying the number, specific order, or primary and secondary relationship of the indicated technical features. In the description of the embodiments of this application, "multiple" means two or more, unless otherwise explicitly defined.
[0025] In this document, the term "embodiment" means that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places throughout the specification does not necessarily refer to the same embodiment, nor is it a separate or alternative embodiment mutually exclusive with other embodiments. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein can be combined with other embodiments.
[0026] In the description of the embodiments in this application, the term "and / or" is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.
[0027] In existing monitoring systems, cameras are responsible for capturing video streams, generating event messages, and publishing them to video recorders (VCRs). The VCR, as the central node, receives event messages from the cameras and performs a series of processes including local storage, event processing, and message forwarding. Event messages require processing through the complete software protocol stack on the VCR's main control unit (including network packet reception, protocol parsing, business logic processing, re-encapsulation, and network transmission), introducing significant software processing latency and resulting in poor real-time event reporting. The VCR needs to maintain complete subscription states for connected cameras, parse all event message content, and manage complex forwarding logic, consuming substantial main control unit computing resources and memory. This is especially problematic in scenarios with many connected cameras and frequent events, leading to wasted system resources and performance bottlenecks. Furthermore, the VCR's current architecture requires processing the content of event messages, limiting the system's flexibility and forwarding efficiency.
[0028] To address the above technical problems, this application provides an event message transmission method. By setting up a processing unit in an electronic device (such as a video recorder), the processing unit receives event messages sent by a camera device, identifies the event messages based on preset message forwarding rules, determines the target forwarding address corresponding to the event message, and forwards the event message to the cloud at the target forwarding address. Through this application, the main controller of the electronic device does not need to process the event messages through software. The processing unit identifies the event messages based on preset message forwarding rules and determines the target forwarding address, eliminating the need for further processing of the event message content. After determining the target forwarding address, the event message can be directly and losslessly forwarded to the cloud at the target forwarding address in its original message form, improving forwarding efficiency, reducing event transmission latency, and enhancing the real-time performance of event reporting.
[0029] The following examples illustrate the application scenario architecture of this event message transmission method.
[0030] Please see Figure 1 , Figure 1 This is a schematic diagram of the architecture of the monitoring system provided in an embodiment of this application. Figure 1As shown, the monitoring system includes camera devices, electronic devices, and a cloud platform. The camera devices can be Internet Protocol Cameras (IPCs), and the electronic devices can be Network Video Recorders (NVRs). The electronic devices include a processing unit, which can be a programmable hardware processing unit, such as a Field-Programmable Gate Array (FPGA) or a Complex Programmable Logic Device (CPLD).
[0031] The camera device captures video and generates corresponding event messages, which are then sent to an electronic device. The electronic device receives the event message through a processing unit and identifies it based on preset message forwarding rules, matching the target forwarding address corresponding to the event message. After determining the target forwarding address, the processing unit sends the event message to the cloud at that target forwarding address. This eliminates the need for complex software processing by the main controller of the electronic device, improving event transmission efficiency and the real-time nature of event reporting.
[0032] In addition, the electronic device can receive service subscription rules from the cloud. The electronic device generates message forwarding rules and subscription requests based on the service subscription rules through the main controller. The main controller of the electronic device transmits the message forwarding rules to the processing unit to instruct the processing unit to forward event messages. The subscription request is sent to the camera device to indicate the type of time message reported by the camera device and the address to which it is reported, where the address is the processing unit.
[0033] Based on the above application scenario architecture, the specific implementation process of this event message transmission method will be described below through an example.
[0034] Please see Figure 2 , Figure 2 This is a schematic diagram illustrating the implementation flow of the event message transmission method provided in the embodiments of this application. The execution entity of this method can be, for example, Figure 1 The electronic device shown is equipped with a processing unit; such as Figure 2 As shown, the method may include the following steps: S201, the electronic device receives the event message sent by the camera device through the processing unit.
[0035] In some embodiments, the camera device captures video of its surroundings in real time and performs intelligent analysis on the captured video; when the video meets pre-configured triggering conditions and the event type of the camera device is subscribed to by an electronic device, the camera device generates a standardized event message and sends the event message to the electronic device.
[0036] For example, the subscribed event type is motion detection, and the trigger condition is the appearance of a continuously moving object in the monitoring screen. The camera device captures video and analyzes the screen. When the screen change meets the trigger condition, it constructs an event message and sends it to the designated reporting address, such as the address of the processing unit set in the electronic device.
[0037] Among them, the event message can correspond to various event types, such as motion detection events, boundary crossing detection events, and area intrusion events; the electronic device can subscribe to different event types from the camera device, so that when the camera device detects that the video image meets the triggering conditions of the subscribed event type, it generates the corresponding event message and sends it to the address of the processing unit.
[0038] For example, such as Figure 3 As shown, the processing unit is located in the electronic device and is directly connected to the first interface of the electronic device (such as the local area network (LAN) interface). It receives event messages sent by the camera device through the first interface. The event messages are processed directly by the processing unit without going through the main controller of the electronic device (such as the NVR CPU), thus realizing hardware pass-through of the event messages. This eliminates the need to occupy the computing resources and memory of the main controller and improves the real-time performance of event reporting.
[0039] In some embodiments, the method further includes: an electronic device receiving one or more service subscription rules issued by the cloud, and generating message forwarding rules and subscription requests based on the service subscription rules.
[0040] For example, before receiving an event message, the electronic device, such as Figure 1 As shown by the dashed arrow, the main controller of the electronic device can receive one or more service subscription rules from the cloud; such as Figure 4 The service subscription rules issued by the cloud to the NVR are shown. These service subscription rules may include the cloud's service logic channel (such as channel 3), the type of event to be subscribed (such as motion detection), the path to be reported to the cloud (such as the Uniform Resource Identifier (URI), reporting address and reporting port), and the subscription mode (such as optional subscription).
[0041] Accordingly, after receiving the service subscription rules, the electronic device, through the main controller, generates a subscription request corresponding to the camera device and a message forwarding rule corresponding to the processing unit. That is, the main controller converts the service subscription rules into a subscription request that the camera device can recognize and a message forwarding rule that the processing unit can recognize. The subscription request indicates to the camera device the reporting channel, the type of event to be subscribed, the path to the electronic device, and the subscription mode; the message forwarding rule indicates the processing unit's logic for recognizing and forwarding event messages.
[0042] In some embodiments, the method further includes: the electronic device sending a subscription request to the camera device via a main controller, the subscription request including subscription information and a reporting identifier; wherein the subscription information is used to indicate the attributes of the event message, and the reporting identifier is used to indicate the resource identifier to which the camera device is subscribed.
[0043] For example, before receiving the event message sent by the camera device through the processing unit, such as Figure 1 As shown by the dashed arrow, the electronic device sends a subscription request to the camera device through the main controller; this subscription request may include subscription information and a reporting identifier, such as... Figure 4 The example of a rule sent by the NVR to the IPC shown includes subscription information that can include the electronic device's service logic channel (e.g., channel 1) and event type (e.g., motion detection), indicating the attributes of the event message; the reporting identifier can be the URI of the processing unit, indicating the address of the processing unit; additionally, the subscription request can also include the electronic device's reporting address and port, as well as the corresponding subscription mode (e.g., subscription). By sending a subscription request to the camera device, the camera device can start or stop generating a specified type of event and send it to a specified address.
[0044] The electronic device encapsulates the subscription request into an ONVIF protocol message that the camera device can understand, or other protocols used for device management, service discovery, and event notification; and sends the corresponding subscription request to camera devices located in different locations.
[0045] In some embodiments, the method further includes: the main controller sending a message forwarding rule to the processing unit; the message forwarding rule is used to indicate the forwarding path of the event message to the processing unit.
[0046] For example, before receiving the event message sent by the camera device through the processing unit, the main controller sends a message forwarding rule to the processing unit, such as... Figure 4The example shown is a rule sent from the NVR to the FPGA. This message forwarding rule can include event source information (such as the IP address and URI of the camera device), event forwarding information (such as the URI of the NVR, the address and port of the cloud), and the status of the rule (such as newly added).
[0047] like Figure 1 As shown, the main controller and processing unit can communicate via a Peripheral Component Interconnect Express (PCIe) bus. The main controller uses this PCIe bus to configure the processing unit's operating status, including adding, deleting, and modifying message forwarding rules, and to write these rules into the processing unit's rule table memory. The main controller can also configure the processing unit's operating mode via the PCIe bus, such as enabling or disabling its pass-through function and setting its matching mode. The processing unit can also use the PCIe bus to feedback its hardware status (such as temperature, voltage, and PCIe link status), rule table status (such as rule table utilization and the presence of matching conflicts), and traffic statistics to the main controller.
[0048] Among them, the event source information is used to identify the event message to determine whether the source of the event message matches the information in the message forwarding rules; the event forwarding information is used to determine the target forwarding address of the event message, that is, if the event source information matches, the target forwarding address is determined based on the event forwarding information corresponding to the event source information.
[0049] In some embodiments, the method further includes: upon receiving a new business subscription rule issued by the cloud, updating the message forwarding rule and the subscription request based on the new business subscription rule; sending the updated message forwarding rule to the processing unit and the updated subscription request to the camera device.
[0050] For example, each rule update process may include adding, deleting, and modifying rules. The addition process is as follows: Figure 4 The process of generating and issuing rules is shown; the deletion process is as follows: Figure 6 The process of generating and issuing rules shown in (a) is as follows; the process of changing information is as follows: Figure 6 The process of generating and issuing the rules shown in (b) is as follows.
[0051] For example, when it is necessary to cancel the subscription, the electronic device can receive new service subscription rules from the cloud, such as... Figure 6In example (a) shown in the figure, the rule sent from the cloud to the NVR has its corresponding subscription mode changed to unsubscribe. Accordingly, the electronic device generates a new subscription request through the main controller and sends it to the camera device to notify the camera device to unsubscribe from a certain type of event, such as the subscription mode of the corresponding rule example being unsubscribe. Accordingly, the main controller of the electronic device sends a new message forwarding rule to the processing unit to notify the processing unit to delete the event message of a certain event source information and no longer forward it.
[0052] For example, when information in the cloud is updated, the electronic device receives new business subscription rules from the cloud, such as... Figure 6 In the example of the rule sent from the cloud to the NVR shown in (b), the address and port of the corresponding cloud have been updated. The subscription request content sent by the electronic device to the camera device through the main controller remains unchanged, while the forwarding address and port in the message conversion rule sent to the processing unit are updated to the new cloud domain name and port; the corresponding rule status is newly added.
[0053] S202, based on preset message forwarding rules, the processing unit identifies the event message and determines the target forwarding address corresponding to the event message.
[0054] In some embodiments, the processing unit identifies the source information of the event message based on the message forwarding rules, and matches the identified source information with the event source information defined in the message forwarding rules; if there is matching event source information in the message forwarding rules, the corresponding target forwarding address is determined based on the event source information.
[0055] For example, the header field of an event message contains the source information of the event message. By parsing the header field and matching it with the event source information in the message forwarding rules, if they match, the target forwarding address of the event message can be determined based on the event forwarding information of the event source information in the message forwarding rules.
[0056] The event forwarding information in the message forwarding rule is the address information of the cloud in the business subscription rule issued by the cloud to the electronic device, such as the reporting URI of the NVR, the reporting address of the cloud, and the reporting port; based on the event source information that matches the event message in the message forwarding rule, the event forwarding information is determined, that is, the target forwarding address of the cloud, such as the URI of the NVR, the domain name of the cloud, and the port.
[0057] In some embodiments, based on preset message forwarding rules, the processing unit identifies the event message and determines the target forwarding address corresponding to the event message, including: Identify the event message and determine its source address and reporting identifier; in the message forwarding rules, determine the target forwarding address corresponding to the source address and reporting identifier.
[0058] For example, the header field of the event message received by the processing unit may include the reporting URI, such as Figure 5 The header field shown is “POST / msg / report_msg / chn1 / is_motionHTTP / 1.1”, and the reporting URI in that header field is “ / msg / report_msg / chn1 / is_motion”. After receiving this event message, the processing unit identifies its header fields and determines that the identified reporting URI matches the URI recorded in the message forwarding rules, such as… Figure 4 The reporting URI recorded in the rule example issued by the NVR to the IPC is the URI of the camera device.
[0059] For example, the event message received by the processing unit carries the source address of the event message, i.e., the IP address of the camera device. When the processing unit parses the reporting identifier " / msg / report_msg / chn1 / is_motion" in the event message header field and finds it to be the same as the event source URI, and matches the event source IP address that is the same as the event message source address, it determines that the match is successful. Then, based on the event source IP and event source URI, it determines the corresponding target forwarding address, i.e., the event forwarding information in the message forwarding rule example, such as the event forwarding URI, event forwarding address, and event forwarding port.
[0060] The processing unit only identifies and matches the header fields of the event message, without processing the content of the event message, thus improving the transmission efficiency of the event message. Furthermore, by identifying and matching the source address and reporting identifier of the event message, it can avoid confusion of the source of the event message when the processing unit is connected to multiple camera devices (multiple message forwarding rules have the same reporting address, but the multiple message forwarding rules correspond to different camera devices), which could lead to incorrect target forwarding addresses and improve the reliability of event message forwarding.
[0061] S203, the processing unit sends an event message to the cloud corresponding to the target forwarding address.
[0062] In some embodiments, the processing unit identifies the event message and determines the target forwarding address based on message forwarding rules, and then directly sends the event message to the cloud at that target forwarding address. For example... Figure 3As shown, the processing unit sends event messages to the cloud through a second interface (such as a wide area network (WAN) interface); or, when the electronic device is equipped with an interface, the second interface and the aforementioned first interface can be the same interface, used to receive event messages sent by the camera device and to forward event messages to the cloud.
[0063] Based on the hardware pass-through of event messages by the processing unit, the series of processing steps of the main controller's software protocol are completely bypassed, so that the event messages do not enter the protocol stack of the main controller of the electronic device. The processing unit sends the messages directly from the network interface of the electronic device based on the configured message forwarding rules, reducing the latency of event reporting and improving the real-time performance of the monitoring system. Regardless of whether the main controller's software system experiences a brief lag, it does not affect the performance of the event reporting link, improving the determinism and reliability of event message transmission. At the same time, it saves the main controller's computing resources and memory.
[0064] In some embodiments, the processing unit sends an event message to the cloud corresponding to the target forwarding address, including: Modify the original destination address in the event message to the target forwarding address, and send the modified event message to the cloud corresponding to the target forwarding address.
[0065] For example, after successfully matching the source address and reporting identifier of the event message, the processing unit modifies the original destination address in the original event message. This original destination address is the address of the processing unit, such as the IP address, port, and identifier of the electronic device. The processing unit then modifies this original destination address to the destination forwarding address, i.e., the address in the cloud; for example... Figure 5 The diagram shows how, in the event reporting process, the identifier of the camera device in the event message, “ / msg / report_msg / chn1 / is_motion”, is changed to the identifier of the NVR, “ / msg / report_msg / chn3 / is_motion”, and the modified event message is sent to the cloud's IP address (cloud domain name) and cloud port.
[0066] Compared to traditional event reporting methods in monitoring systems, this embodiment eliminates the need for software protocol processing steps such as complete reception, parsing, and reassembly of event messages by electronic devices, thus improving event message transmission efficiency. Rule distribution via electronic devices is simple, requiring only the source and destination addresses. The parsing process of event messages by the processing unit is straightforward, parsing only the reporting identifier within the event message, thereby increasing the pass-through rate. Furthermore, the electronic devices do not need to be aware of specific cloud subscription content or perform business adaptation; they can simply correspond based on the rules. Simultaneously, no modification to the event message protocol is required, ensuring compatibility with event messages from different camera devices.
[0067] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.
[0068] Corresponding to the event message transmission method provided in the above embodiments, such as Figure 7 The diagram shown is a schematic representation of the structure of the event message transmission device provided in this application embodiment. For ease of explanation, only the parts related to this application embodiment are shown.
[0069] The event message transmission device includes: The receiving module 71 is used to receive event messages sent by the camera device; Processing module 72 is used to identify the event message based on preset message forwarding rules and determine the target forwarding address corresponding to the event message; The sending module 73 is used to send the event message to the cloud corresponding to the target forwarding address.
[0070] In one possible implementation, the device further includes a main controller for sending a subscription request to the camera device, the subscription request including subscription information and a reporting identifier; wherein the subscription information is used to indicate the attributes of the event message, and the reporting identifier is used to indicate the address of the processing unit.
[0071] In one possible implementation, the main controller is further configured to send the message forwarding rule to the processing unit; the message forwarding rule is used to indicate the forwarding path of the event message by the processing unit.
[0072] In one possible implementation, the processing module 72 is further configured to identify the event message, determine the source address and reporting identifier of the event message, and determine the target forwarding address corresponding to the source address and the reporting identifier in the message forwarding rule.
[0073] In one possible implementation, the sending module 73 is further configured to modify the original destination address in the event message to the target forwarding address, and send the modified event message to the cloud corresponding to the target forwarding address.
[0074] In one possible implementation, the main controller is also configured to receive one or more business subscription rules issued by the cloud, and generate the message forwarding rules and subscription requests based on the business subscription rules.
[0075] In one possible implementation, the main controller is further configured to, upon receiving a new business subscription rule from the cloud, update the message forwarding rule and the subscription request based on the new business subscription rule; send the updated message forwarding rule to the processing unit and the updated subscription request to the camera device.
[0076] Compared to traditional event reporting methods in monitoring systems, this embodiment eliminates the need for software protocol processing steps such as complete reception, parsing, and reassembly of event messages by electronic devices, thus improving event message transmission efficiency. Rule distribution via electronic devices is simple, requiring only the source and destination addresses. The parsing process of event messages by the processing unit is straightforward, parsing only the reporting identifier within the event message, thereby increasing the pass-through rate. Furthermore, the electronic devices do not need to be aware of specific cloud subscription content or perform business adaptation; they can simply correspond based on the rules. Simultaneously, no modification to the event message protocol is required, ensuring compatibility with event messages from different camera devices.
[0077] Figure 8 A schematic diagram of the hardware structure of electronic device 8 is shown.
[0078] like Figure 8 As shown, the electronic device 8 of this embodiment includes: at least one processor 81 ( Figure 8 Only one is shown in the diagram), and a memory 82 stores a computer program 83 that can run on the processor 81. When the processor 81 executes the computer program 83, it implements the steps in the above method embodiments, for example... Figure 2 S201 to S203 are shown. Alternatively, when the processor 81 executes the computer program 83, it implements the functions of each module / unit in the above-described device embodiments.
[0079] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the electronic device 8. In other embodiments of this application, the electronic device 8 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
[0080] The electronic device 8 may include, but is not limited to, a processor 81 and a memory 82. Those skilled in the art will understand that... Figure 8 This is merely an example of electronic device 8 and does not constitute a limitation on electronic device 8. It may include more or fewer components than shown, or combine certain components, or different components. For example, the server may also include input sending devices, network access devices, buses, etc.
[0081] The processor 81 mentioned above can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.
[0082] The processor 81 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 81 is a cache memory. This memory can store instructions or data that the processor 81 has just used or that are used repeatedly. If the processor 81 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 81, and thus improves the efficiency of the system.
[0083] In some embodiments, the aforementioned memory 82 may be an internal storage unit of the electronic device 8, such as a hard disk or memory. The memory 82 may also be an external storage device of the electronic device 8, such as a plug-in hard disk, smart media card (SMC), secure digital card (SD), flash card, etc. Furthermore, the memory 82 may include both internal and external storage units of the electronic device 8. The memory 82 is used to store operating systems, applications, bootloaders, data, and other programs, such as program code for computer programs. The memory 82 can also be used to temporarily store data that has been sent or will be sent.
[0084] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.
[0085] It should be noted that the structure of the above-mentioned electronic device is only illustrative and may include other physical structures depending on the application scenario. The physical structure of the electronic device is not limited here.
[0086] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.
[0087] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the various method embodiments above.
[0088] This application provides a computer program product that, when run on a server, enables the server to execute the steps described in the above-described method embodiments.
[0089] If the integrated modules / units are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying computer program code, recording media, USB flash drives, portable hard drives, magnetic disks, optical disks, computer memory, read-only memory (ROM), random access memory (RAM), electrical carrier signals, telecommunication signals, and software distribution media, etc.
[0090] The electronic devices, computer storage media, and computer program products provided in the embodiments of this application are all used to execute the methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects corresponding to the methods provided above, and will not be repeated here.
[0091] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0092] It should be understood that the above description is merely to help those skilled in the art better understand the embodiments of this application, and is not intended to limit the scope of the embodiments of this application. Based on the examples given above, those skilled in the art can obviously make various equivalent modifications or changes. For example, some steps in the various embodiments of the above detection method may be unnecessary, or new steps may be added. Alternatively, any combination of two or more of the above embodiments may be used. Such modifications, changes, or combinations also fall within the scope of the embodiments of this application.
[0093] It should also be understood that the methods, situations, categories, and classifications of embodiments in this application are for the convenience of description only and should not constitute a special limitation. Various methods, categories, situations, and features in embodiments can be combined without contradiction.
[0094] It should also be understood that, in the various embodiments of this application, unless otherwise specified or in case of logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other, and the technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.
[0095] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.
[0096] In the embodiments provided in this application, it should be understood that the disclosed apparatus / network devices and methods can be implemented in other ways. For example, the apparatus / network device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.
[0097] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0098] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.
[0099] Finally, it should be noted that the above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. An event message transmission method, characterized in that, Applied to an electronic device, the electronic device including a processing unit; the method includes: The processing unit receives event messages sent by the camera device. Based on preset message forwarding rules, the processing unit identifies the event message and determines the target forwarding address corresponding to the event message; The processing unit sends the event message to the cloud corresponding to the target forwarding address.
2. The method according to claim 1, characterized in that, The electronic device further includes a main controller; prior to receiving the event message sent by the camera device through the processing unit, the method further includes: The main controller sends a subscription request to the camera device, the subscription request containing subscription information and a reporting identifier; The subscription information is used to indicate the attributes of the event message, and the reporting identifier is used to indicate the resource identifier to which the camera device is subscribed.
3. The method according to claim 1, characterized in that, The electronic device further includes a main controller; prior to receiving the event message sent by the camera device through the processing unit, the method further includes: The main controller sends the message forwarding rule to the processing unit; the message forwarding rule is used to indicate the forwarding path of the event message by the processing unit.
4. The method according to claim 1, characterized in that, The process, based on preset message forwarding rules, involves the processing unit identifying the event message and determining the target forwarding address corresponding to the event message, including: Identify the event message and determine the source address and reporting identifier of the event message; In the message forwarding rule, the target forwarding address corresponding to the source address and the reporting identifier is determined.
5. The method according to claim 1, characterized in that, The step of sending the event message from the processing unit to the cloud corresponding to the target forwarding address includes: The original destination address in the event message is modified to the target forwarding address, and the modified event message is sent to the cloud corresponding to the target forwarding address.
6. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Receive one or more business subscription rules from the cloud, and generate the message forwarding rules based on the business subscription rules.
7. The method according to claim 2, characterized in that, Before sending the subscription request to the camera device via the main controller, the method further includes: Receive one or more business subscription rules from the cloud, and generate the subscription request based on the business subscription rules.
8. The method according to claim 6 or 7, characterized in that, The method further includes: Upon receiving a new business subscription rule from the cloud, the message forwarding rule and the subscription request are updated based on the new business subscription rule. The updated message forwarding rules are sent to the processing unit and the updated subscription request is sent to the camera device.
9. An electronic device, characterized in that, It includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement the method of any one of claims 1 to 8.
10. A monitoring system, characterized in that, The monitoring system includes a camera device, a cloud platform, and an electronic device as described in claim 9; wherein the electronic device is equipped with a processing unit; The camera device is used to generate an event message and send the event message to the electronic device; The electronic device is configured to receive event messages sent by the camera device through the processing unit; identify the event messages based on preset message forwarding rules, determine the target forwarding address corresponding to the event messages; and send the event messages to the cloud corresponding to the target forwarding address. The cloud is used to receive the event messages sent by electronic devices through the processing unit.