Video recorder service scheduling method and device based on a hon gming system, equipment and medium

Abstract

The application discloses a kind of based on the video recorder service scheduling method, device and equipment of hyper system and medium.The method comprises: in response to the service request operation of user to target video recorder, target request message is sent to interface layer by application layer;Through interface layer, the target request message is classified based on pre-set service classification table, and the service classification result matched with the target request message is obtained, and the target request message is sent to framework layer based on the service classification result;The target request message is encapsulated by the framework layer, and the encapsulated target request message is sent to system service layer;The target request message is parsed by the system service layer, and based on the analysis result, each service module of target video recorder is executed scheduling operation.Through the technical scheme of the application, the service scheduling of hyper system video recorder can be realized, and the service scheduling efficiency of video recorder is improved.

Description

Technical Field

[0001] This invention relates to the field of video surveillance technology, and in particular to a video recorder service scheduling method, device, equipment and medium based on the HarmonyOS system. Background Technology

[0002] In existing technologies, the scheduling of video recorders for police equipment mainly adopts a traditional integrated architecture, resulting in low scheduling efficiency. At the interface level, the implementation of video recorder functions involves multiple heterogeneous interfaces. For example, image transmission uses the HTTP protocol, PTZ control parameters use the MQTT protocol, siren light control calls the manufacturer's private SDK, and video stream retrieval relies on the RTSP protocol. Each business module directly interfaces with the upper-layer application through different technical protocols, resulting in severe interface fragmentation, high complexity of application function integration, and request messages needing to undergo multiple protocol conversions before entering the business processing flow, leading to reduced efficiency in video recorder scheduling.

[0003] At the business architecture level, traditional video recorder services are typically deployed as a single backend service on a fixed disk, centrally implementing all business functions such as IPC management, video access, and recording management. The various business modules are highly coupled at the code level, with intertwined internal processing logic and a lack of effective isolation mechanisms. When a business request is received, all business logic must be traversed for matching, making it impossible to quickly locate the target business module, resulting in significant scheduling response delays. Furthermore, when an anomaly occurs in one business module, the fault can easily propagate to the entire service process, creating a single point of failure that risks impacting the overall business operation. The system must be restarted to recover, leading to reduced efficiency in video recorder service scheduling.

[0004] At the resource scheduling level, the traditional architecture adopts a centralized resource allocation model. Video encoding and decoding, recording and storage services continuously consume a large amount of CPU, memory and storage resources, while intelligent recognition, platform access and other services are in a state of resource starvation for a long time. Each service module cannot dynamically apply for and release resources according to the actual load, resulting in low overall resource utilization. High-load services are processed slowly, and low-load services cannot obtain resources in time, thus reducing the efficiency of recorder service scheduling.

[0005] In summary, existing video recorder service scheduling methods suffer from low service scheduling efficiency. Summary of the Invention

[0006] This invention provides a video recorder service scheduling method, device, equipment, and medium based on the HarmonyOS system, which can solve the problem of low service scheduling efficiency in existing video recorder service scheduling methods.

[0007] In a first aspect, embodiments of the present invention provide a video recorder service scheduling method based on the HarmonyOS system, executed by a video recorder service system comprising an application layer, an interface layer, a framework layer, and a system service layer connected in sequence, the method comprising: In response to a user's business request operation for a target recorder, a target request message is sent from the application layer to the interface layer, wherein the target recorder includes at least one business module; The interface layer performs business classification on the target request message based on a pre-defined business classification table to obtain a business classification result that matches the target request message, and sends the target request message to the framework layer based on the business classification result. The framework layer encapsulates the target request message and sends the encapsulated target request message to the system service layer. The system service layer parses the target request message and performs scheduling operations on each service module of the target recorder based on the parsing results.

[0008] Secondly, embodiments of the present invention provide a video recorder service scheduling device based on the HarmonyOS system, executed by a video recorder service system comprising an application layer, an interface layer, a framework layer, and a system service layer connected in sequence. The device includes: The message sending module is used to respond to user service request operations for the target recorder by sending a target request message to the interface layer through the application layer. The target recorder includes at least one service module. The message classification module is used to classify the target request message according to a pre-defined service classification table through the interface layer, obtain the service classification result that matches the target request message, and send the target request message to the framework layer based on the service classification result. The encapsulation module is used to encapsulate the target request message through the framework layer and send the encapsulated target request message to the system service layer. The scheduling module is used to parse the target request message through the system service layer and perform scheduling operations on each service module of the target recorder based on the parsing results.

[0009] Thirdly, embodiments of the present invention provide an electronic device, the electronic device comprising: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, and the computer program is executed by the at least one processor to enable the at least one processor to execute a video recorder service scheduling method based on the HarmonyOS system according to any embodiment of the present invention.

[0010] Fourthly, embodiments of the present invention provide a computer-readable storage medium storing computer instructions, which are used to cause a processor to execute a video recorder service scheduling method based on the HarmonyOS system as described in any embodiment of the present invention.

[0011] The technical solution of this invention addresses the issue of low service scheduling efficiency in existing recorder service scheduling methods. It enables service scheduling of recorders within the HarmonyOS system, thereby improving service scheduling efficiency.

[0012] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0013] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0014] Figure 1 This is a flowchart of a video recorder service scheduling method based on the HarmonyOS system provided in Embodiment 1 of the present invention; Figure 2 This is a flowchart of a video recorder service scheduling method based on the HarmonyOS system provided in Embodiment 2 of the present invention; Figure 3 This is a schematic diagram of the structure of a video recorder service scheduling device based on the HarmonyOS system according to Embodiment 3 of the present invention; Figure 4 This is a schematic diagram of the structure of an electronic device that implements the video recorder service scheduling method based on the HarmonyOS system according to an embodiment of the present invention. Detailed Implementation

[0015] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0016] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, any variations of the terms "comprising" and "having" are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0017] Example 1 Figure 1 This is a flowchart of a video recorder service scheduling method based on the HarmonyOS system provided in Embodiment 1 of the present invention. This embodiment is applicable to the situation of video recorder service scheduling on the HarmonyOS system. The method can be executed by a video recorder service scheduling device based on the HarmonyOS system. The video recorder service scheduling device based on the HarmonyOS system can be implemented in hardware and / or software. The video recorder service scheduling device based on the HarmonyOS system can be configured in a video recorder service system with video recorder service scheduling function based on the HarmonyOS system.

[0018] like Figure 1 As shown, the method includes: S110. In response to the user's business request operation for the target recorder, send the target request message to the interface layer through the application layer.

[0019] The target video recorder includes at least one service module.

[0020] Furthermore, in this embodiment, the target video recorder is a network video recorder deployed in a police law enforcement scenario, used to realize functions such as video access, storage management, and platform integration of front-end camera equipment; specifically, the business modules include, but are not limited to: IPC management module, video access module, recording management module, GB28181 platform access module, GA1400 platform access module, intelligent recognition module, and hardware management module, each business module undertaking independent business functions.

[0021] Furthermore, the application layer is a human-computer interaction layer deployed on the HarmonyOS system terminal side, which may include police HarmonyOS business applications or Web service front-ends, used to generate the business request operation in response to user touch commands or remote operation commands.

[0022] Optionally, the service request operation includes real-time video viewing requests, video recording query and retrieval requests, alarm light control requests, or device parameter configuration requests, etc.; wherein, the target request message is a standardized data structure carrying a service function field and a target recorder identifier, the service function field being used to characterize the specific service type of the user request; the target recorder identifier being used to uniquely identify the target recorder device to be scheduled.

[0023] S120. The target request message is classified by the interface layer based on a pre-defined service classification table to obtain a service classification result that matches the target request message, and the target request message is sent to the framework layer based on the service classification result.

[0024] The interface layer includes at least one standard application programming interface (API). Specifically, the standard API is a set of interfaces built based on the HarmonyOS NAPI specification, used to realize standardized data interaction between the application layer and the framework layer. For example, the standard API includes a real-time video stream acquisition interface, a historical video retrieval interface, a device parameter configuration interface, and a warning light control interface, each interface corresponding to a preset function label.

[0025] The process involves: classifying the target request message based on a pre-defined business classification table at the interface layer to obtain a business classification result matching the target request message; and sending the target request message to the framework layer based on the business classification result. This includes: parsing the target request message at the interface layer to obtain a target function field matching the target request message; searching for a target function tag matching the target function field in the business classification table, where the business classification table records the mapping relationship between each request function field and each function tag; determining a target standard application interface (API) among various standard application interfaces based on the target function tag; and sending the target request message to the framework layer through the target API based on the business classification result.

[0026] Specifically, the business classification table is a structured data table pre-installed in the interface layer. For example, the business classification table may specifically include the mapping relationship between the request function fields "0x01" to "0x06" and the function tags "VIDEO_STREAM", "RECORD_QUERY", "PTZ_CONTROL", "ALARM_LIGHT", "DEVICE_STATUS", and "INTELLIGENT_CAPTURE", respectively. Based on the above example, the search process may involve comparing the parsed target function field "0x03" with each request function field in the business classification table one by one, and extracting the corresponding target function tag "PTZ_CONTROL" after a match is found.

[0027] The business classification result includes the target function label, the interface identifier of the target standard application interface, and routing priority information.

[0028] S130. The target request message is encapsulated through the framework layer and the encapsulated target request message is sent to the system service layer.

[0029] The framework layer is a runtime environment deployed in the middleware layer of the HarmonyOS system, used to realize protocol conversion and data adaptation between standard application programming interfaces (APIs) and system service instances. Specifically, the framework layer is built based on the ArkUI-X or Native framework of the HarmonyOS system, carries the adaptation and encapsulation logic of the NAPI interface, connects to the standard application programming interfaces of the interface layer above, and calls the system service instances of the system service layer below.

[0030] The encapsulation operation of the target request message through the framework layer includes: parsing the target request message to obtain caller identity information and business function type information matching the target request message; obtaining a pre-stored interface adaptation mapping table, which stores information on each business function type and the corresponding interface adaptation rules; searching for a target interface adaptation rule matching the business function type information in the interface adaptation mapping table, and encapsulating the target request message based on the target interface adaptation rule.

[0031] Specifically, the caller identity information includes the caller application identifier, caller permission level, and session token. For example, if the caller application identifier is "com.police.nvr.client", it represents an NVR business application on the police law enforcement terminal side. The caller permission level includes three levels: ordinary user, administrator, and super administrator, used for subsequent permission verification. The session token is an encrypted string generated based on the HarmonyOS HUK (Hardware Unique Key) to ensure communication link security. Further, the business function type information includes a business domain code, function subtype, and data format identifier. For example, the business domain code "0x10" represents video-related services, the function subtype "0x03" represents PTZ control, and the data format identifier "JSON" indicates that the request payload uses JSON serialization format.

[0032] Furthermore, the interface adaptation mapping table is used to store information on each business function type and the corresponding interface adaptation rules for each business function type. The interface adaptation rules include interface parameter conversion rules, data format standardization rules, and call sequence specification rules.

[0033] Furthermore, the encapsulation includes: performing parameter format conversion according to the interface parameter conversion rules, performing serialization format conversion according to the data format standardization rules, and generating a standardized service message header including the target system service instance code and inter-process communication identifier.

[0034] Those skilled in the art should understand that encapsulating messages under the premise of knowing the target interface adaptation rules is a mature existing technology, and the specific encapsulation steps will not be described in detail in this embodiment.

[0035] S140. The system service layer parses the target request message and performs scheduling operations on each service module of the target recorder based on the parsing result.

[0036] The system service layer includes at least one system service instance.

[0037] Furthermore, the aforementioned system service instances are the smallest service units that are independently deployed and run within the HarmonyOS system service layer. Each system service instance interacts with data through a standard inter-process communication mechanism and independently requests system resources. For example, the system service instances may specifically include camera management SA service, video recording management SA service, intelligent snapshot SA service, GB28181 platform access SA service, and GA1400 platform access SA service. Each SA service corresponds to a different business module of the target recorder, so as to achieve independent scheduling and control of each business module.

[0038] The technical solution of this invention involves the video recorder service system responding to a user's service request operation for a target video recorder. The application layer sends a target request message to the interface layer. The interface layer then classifies the target request message based on a pre-defined service classification table, obtaining a service classification result that matches the target request message. Based on the service classification result, the target request message is sent to the framework layer. The framework layer then encapsulates the target request message and sends the encapsulated message to the system service layer. Finally, the system service layer parses the target request message and performs scheduling operations on each service module of the target video recorder based on the parsing result. This achieves service scheduling for the video recorder within the HarmonyOS system, improving the service scheduling efficiency of the video recorder.

[0039] Example 2 Figure 2 This is a flowchart of a video recorder service scheduling method based on the HarmonyOS system provided in Embodiment 2 of the present invention. This embodiment is a refinement based on the above embodiment. In this embodiment, the method of parsing the target request message through the system service layer and performing scheduling operations on each service module of the target video recorder based on the parsing result is specifically refined.

[0040] like Figure 2 As shown, the method includes: S210, In response to the user's business request operation for the target recorder, send a target request message to the interface layer through the application layer.

[0041] The target video recorder includes at least one service module.

[0042] S220. The target request message is classified by the interface layer based on a pre-defined service classification table to obtain a service classification result that matches the target request message, and the target request message is sent to the framework layer based on the service classification result.

[0043] The interface layer includes at least one standard application programming interface (API).

[0044] S230. The target request message is encapsulated through the framework layer, and the encapsulated target request message is sent to the system service layer.

[0045] S240. The target request message is parsed by the system service layer to obtain the target function enumeration identifier.

[0046] The target function enumeration identifier is a predefined business function code, used to uniquely represent the business type of the request.

[0047] S250: Obtain the pre-stored service routing table through the system service layer.

[0048] The service routing table is used to store the enumeration identifiers of each function and the system service instances corresponding to each function enumeration identifier.

[0049] Furthermore, the service routing table is a hash mapping table or index array pre-installed in the system service layer; for example, the service routing table may specifically include: the mapping relationship between the function enumeration identifier "0xA001" and the camera management SA service, and the mapping relationship between the function enumeration identifier "0xA002" and the video recording management SA service, etc.

[0050] S260. The system service layer searches the service routing table for a target system service instance that matches the target function enumeration identifier.

[0051] The system service layer includes at least one system service instance.

[0052] S270. The target request message is processed through the target system service instance to perform scheduling operations on each service module of the target recorder.

[0053] The processing of the target request message includes: invoking the corresponding native service or HarmonyOS native system service for the target system service instance, and executing business logic matching the target request message; for example, when the target system service instance is a camera management SA service, the processing includes invoking the video access native service to complete real-time video stream retrieval; when the target system service instance is a video recording management SA service, the processing includes invoking the storage management native service to complete video file retrieval and playback.

[0054] Optionally, before processing the target request message through the target system service instance, the method further includes: obtaining a pre-stored vendor adaptation configuration library, wherein the vendor adaptation configuration library is used to store adaptation configuration information of at least one vendor service software development kit and the hardware device identifier corresponding to each adaptation configuration information; parsing the target request message to obtain the target hardware device identifier and the target business function identifier that match the target request message; querying the vendor adaptation configuration library for target adaptation configuration information that matches the target request message based on the target hardware device identifier; and updating the target request message based on the target adaptation configuration information.

[0055] In this embodiment, the target request message is updated based on the target adaptation configuration information, so as to achieve unified encapsulation and interface unification with the vendor's service software development kit through the hardware abstraction layer based on the HarmonyOS standard hardware device framework; wherein, the hardware abstraction layer shields the interface differences, calling logic and underlying hardware differences of various vendors' SDKs from the bottom up, and outputs standardized calling interfaces from the top up.

[0056] Optionally, after processing the target request message through the target system service instance to perform scheduling operations on each business module of the target recorder, the process further includes: receiving the execution results returned by each business module of the target recorder through the system service layer, the execution results including: the business module identifier, execution status information, and execution timestamp of each business module; sending the execution results to the framework layer through the target system service instance; performing reverse interface adaptation on the execution results through the framework layer, and sending the reverse-adapted execution results to the target standard application interface of the interface layer; and sending the execution results to the application layer through the target standard application interface.

[0057] The execution status information includes success, failure, or partial success; the execution timestamp is the system time when each business module completes processing; the reverse interface adaptation is the process by which the framework layer converts the internal data format of the system service layer into the data format required by the standard application interface according to the reverse conversion rules in the interface adaptation mapping table.

[0058] The technical solution of this invention involves a video recorder business system responding to a user's business request operation for a target video recorder. The system sends a target request message to the interface layer through the application layer. The interface layer then classifies the target request message based on a pre-defined business classification table, obtaining a business classification result that matches the target request message. Based on this classification result, the target request message is sent to the framework layer. The framework layer then encapsulates the target request message and sends it to the system service layer. The system service layer parses the target request message to obtain a target function enumeration identifier and retrieves a pre-stored service routing table. It then searches the service routing table for a target system service instance that matches the target function enumeration identifier and processes the target request message using that instance to perform scheduling operations on various business modules of the target video recorder. This achieves business scheduling for the video recorder within the HarmonyOS system, improving the efficiency of video recorder business scheduling.

[0059] Example 3 Figure 3 This is a schematic diagram of a video recorder service scheduling device based on the HarmonyOS system provided in Embodiment 3 of the present invention.

[0060] like Figure 3 As shown, the device includes: The message sending module 310 is used to respond to a user's service request operation for the target recorder by sending a target request message to the interface layer through the application layer. The target recorder includes at least one service module. The message classification module 320 is used to classify the target request message according to a pre-defined service classification table through the interface layer, obtain a service classification result that matches the target request message, and send the target request message to the framework layer based on the service classification result. The encapsulation module 330 is used to encapsulate the target request message through the framework layer and send the encapsulated target request message to the system service layer. The scheduling module 340 is used to parse the target request message through the system service layer and perform scheduling operations on each service module of the target recorder based on the parsing result.

[0061] The technical solution of this invention involves the video recorder service system responding to a user's service request operation for a target video recorder. The application layer sends a target request message to the interface layer. The interface layer then classifies the target request message based on a pre-defined service classification table, obtaining a service classification result that matches the target request message. Based on the service classification result, the target request message is sent to the framework layer. The framework layer then encapsulates the target request message and sends the encapsulated message to the system service layer. Finally, the system service layer parses the target request message and performs scheduling operations on each service module of the target video recorder based on the parsing result. This achieves service scheduling for the video recorder within the HarmonyOS system, improving the service scheduling efficiency of the video recorder.

[0062] Based on the above embodiments, the message classification module 320 includes: The first parsing unit is used to parse the target request message through the interface layer to obtain the target function field that matches the target request message; The function tag lookup unit is used to look up the target function tag that matches the target function field in the business classification table. The business classification table is used to record the mapping relationship between each request function field and each function tag. The interface determination unit is used to determine the target standard application interface among the standard application interfaces according to the target function label, and send the target request message to the framework layer through the target standard application interface based on the business classification result.

[0063] Based on the above embodiments, the encapsulation module 330 includes: The second parsing unit is used to parse the target request message to obtain the caller identity information and business function type information that match the target request message; The rule invocation unit is used to obtain a pre-stored interface adaptation mapping table, which is used to store information on each business function type and the interface adaptation rules corresponding to each business function type. The message encapsulation unit is used to search for a target interface adaptation rule that matches the business function type information in the interface adaptation mapping table, and encapsulate the target request message based on the target interface adaptation rule.

[0064] Based on the above embodiments, the scheduling module 340 includes: The third parsing unit is used to parse the target request message to obtain the target function enumeration identifier; The routing table acquisition unit is used to acquire a pre-stored service routing table, which is used to store the enumeration identifiers of each function and the system service instances corresponding to each function enumeration identifier. An instance lookup unit is used to search the service routing table for a target system service instance that matches the target function enumeration identifier. The module scheduling unit is used to process the target request message through the target system service instance in order to perform scheduling operations on each service module of the target recorder.

[0065] Based on the above embodiments, the module scheduling unit is further configured to: before processing the target request message through the target system service instance, obtain a pre-stored vendor adaptation configuration library, wherein the vendor adaptation configuration library is used to store adaptation configuration information of at least one vendor service software development kit and hardware device identifiers corresponding to each adaptation configuration information; parse the target request message to obtain a target hardware device identifier and a target business function identifier that match the target request message; query the vendor adaptation configuration library for target adaptation configuration information that matches the target request message based on the target hardware device identifier; and update the target request message based on the target adaptation configuration information.

[0066] Based on the above embodiments, the module scheduling unit is further configured to: process the target request message through the target system service instance to perform scheduling operations on each business module of the target recorder; receive the execution results returned by each business module of the target recorder through the system service layer, wherein the execution results include: the business module identifier, execution status information and execution timestamp of each business module; send the execution results to the framework layer through the target system service instance; perform reverse interface adaptation on the execution results through the framework layer, and send the reverse adapted execution results to the target standard application interface of the interface layer; and send the execution results to the application layer through the target standard application interface.

[0067] The video recorder service scheduling device based on HarmonyOS provided in this embodiment of the invention can execute the video recorder service scheduling method based on HarmonyOS provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0068] Example 4 Figure 4A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0069] like Figure 4 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 can also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0070] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0071] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 executes the various methods and processes described above, such as the video recorder service scheduling method based on the HarmonyOS system.

[0072] Accordingly, the method includes: In response to a user's business request operation for a target recorder, a target request message is sent from the application layer to the interface layer, wherein the target recorder includes at least one business module; The interface layer performs business classification on the target request message based on a pre-defined business classification table to obtain a business classification result that matches the target request message, and sends the target request message to the framework layer based on the business classification result. The framework layer encapsulates the target request message and sends the encapsulated target request message to the system service layer. The system service layer parses the target request message and performs scheduling operations on each service module of the target recorder based on the parsing results.

[0073] In some embodiments, the video recorder service scheduling method based on HarmonyOS can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the video recorder service scheduling method based on HarmonyOS described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to execute the video recorder service scheduling method based on HarmonyOS by any other suitable means (e.g., by means of firmware).

[0074] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0075] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0076] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0077] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0078] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0079] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0080] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

Claims

1. A video recorder service scheduling method based on the HarmonyOS system, executed by a video recorder service system comprising sequentially connected application layer, interface layer, framework layer, and system service layer, characterized in that... include: In response to a user's business request operation for a target recorder, a target request message is sent from the application layer to the interface layer, wherein the target recorder includes at least one business module; The interface layer performs business classification on the target request message based on a pre-defined business classification table to obtain a business classification result that matches the target request message, and sends the target request message to the framework layer based on the business classification result. The framework layer encapsulates the target request message and sends the encapsulated target request message to the system service layer. The system service layer parses the target request message and performs scheduling operations on each service module of the target recorder based on the parsing results.

2. The method according to claim 1, characterized in that, The interface layer includes: at least one standard application programming interface; The system service layer includes at least one system service instance.

3. The method according to any one of claims 1-2, characterized in that, The interface layer performs business classification on the target request message based on a pre-defined business classification table to obtain a business classification result that matches the target request message, and sends the target request message to the framework layer based on the business classification result, including: The target request message is parsed through the interface layer to obtain the target function field that matches the target request message; The target function tag that matches the target function field is found in the business classification table. The business classification table is used to record the mapping relationship between each request function field and each function tag. Based on the target function label, the target standard application interface is determined among the various standard application interfaces, and based on the business classification result, the target request message is sent to the framework layer through the target standard application interface.

4. The method according to claim 1, characterized in that, The framework layer encapsulates the target request message, including: Parse the target request message to obtain the caller identity information and business function type information that match the target request message; Obtain a pre-stored interface adaptation mapping table, which is used to store information on each business function type and the interface adaptation rules corresponding to each business function type. The target interface adaptation rule that matches the business function type information is found in the interface adaptation mapping table, and the target request message is encapsulated based on the target interface adaptation rule.

5. The method according to any one of claims 1-2, characterized in that, The system service layer parses the target request message and performs scheduling operations on each service module of the target recorder based on the parsing results, including: Parse the target request message to obtain the target function enumeration identifier; Obtain the pre-stored service routing table, which is used to store the enumeration identifiers of each function and the system service instances corresponding to each function enumeration identifier; Search the service routing table for a target system service instance that matches the target function enumeration identifier; The target request message is processed through the target system service instance to perform scheduling operations on each service module of the target recorder.

6. The method according to claim 5, characterized in that, Before processing the target request message through the target system service instance, the process further includes: Obtain a pre-stored vendor adaptation configuration library, which is used to store adaptation configuration information of at least one vendor service software development kit and the hardware device identifier corresponding to each adaptation configuration information. Parse the target request message to obtain the target hardware device identifier and the target service function identifier that match the target request message; Based on the target hardware device identifier, query the vendor's adaptation configuration library for target adaptation configuration information that matches the target request message; The target request message is updated based on the target adaptation configuration information.

7. The method according to claim 5, characterized in that, After processing the target request message through the target system service instance to perform scheduling operations on each service module of the target recorder, the process further includes: The system service layer receives the execution results returned by each business module of the target recorder. The execution results include: the business module identifier, execution status information and execution timestamp of each business module. The execution result is sent to the framework layer through the target system service instance; The execution result is reverse-engineered and adapted through the framework layer, and the reverse-engineered execution result is sent to the target standard application interface of the interface layer. The execution result is sent to the application layer through the target standard application programming interface.

8. A video recorder service scheduling device based on the HarmonyOS system, executed by a video recorder service system comprising an application layer, an interface layer, a framework layer, and a system service layer connected in sequence, characterized in that, include: The message sending module is used to respond to user service request operations for the target recorder by sending a target request message to the interface layer through the application layer. The target recorder includes at least one service module. The message classification module is used to classify the target request message according to a pre-defined service classification table through the interface layer, obtain the service classification result that matches the target request message, and send the target request message to the framework layer based on the service classification result. The encapsulation module is used to encapsulate the target request message through the framework layer and send the encapsulated target request message to the system service layer. The scheduling module is used to parse the target request message through the system service layer and perform scheduling operations on each service module of the target recorder based on the parsing results.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and A memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to execute a video recorder service scheduling method based on the HarmonyOS system according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that are used to cause a processor to execute the video recorder service scheduling method based on the HarmonyOS system according to any one of claims 1-7.

Images