Equipment starting method and device, storage medium and electronic equipment

Abstract

The invention discloses an equipment starting method and device, a storage medium and electronic equipment. The method comprises the steps that a target obtaining request sent by target equipment is received, the target obtaining request is used for requesting a target mirror image file of the target equipment, and the target mirror image file is used for starting the target equipment; a target mirror image file is determined based on the target acquisition request, the target mirror image file is pre-stored in network video recording equipment, the network video recording equipment hierarchically stores the target mirror image file of the equipment according to equipment information and program information, the equipment comprises target equipment, and the equipment information at least comprises an equipment category; the program information comprises at least one of a program category, a program name and a program version; and sending the target mirror image file to the target equipment to start the target equipment. The technical problem that the efficiency of obtaining the mirror image file used for starting the equipment is low, so that the equipment is started slowly is solved.

Description

Technical Field

[0001] This application relates to the field of computers, and more specifically, to a method and apparatus for starting a device, a storage medium, and an electronic device. Background Technology

[0002] In a local area network (LAN) environment, devices such as network cameras and servers typically store boot images on their local storage media (e.g., FLASH) to enable self-booting. However, with the increasing functionality and continuous iteration of program versions, the size of boot image files has gradually increased, posing a serious challenge to the device's local storage resources. On the one hand, the device's FLASH storage space is limited, and frequent program updates can lead to insufficient storage space; on the other hand, large boot images have long loading times, severely impacting the device's boot speed and response efficiency. In network environments with diverse device architectures and varying hardware configurations, the existing inefficient image file acquisition mechanisms contribute to the technical problem of slow device booting.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This application provides a device startup method and apparatus, storage medium and electronic device to at least solve the technical problem of slow device startup caused by low efficiency in obtaining image files for startup.

[0005] According to one aspect of the embodiments of this application, a device startup method is provided, comprising: receiving a target acquisition request sent by a target device, wherein the target acquisition request is used to request a target image file of the target device, and the target image file is used to start the target device; determining the target image file based on the target acquisition request, wherein the target image file is pre-stored in a network video recording device, the network video recording device hierarchically storing the target image file of the device according to device information and program information, the device including the target device, the device information including at least a device category, and the program information including at least one of a program category, a program name, and a program version; and sending the target image file to the target device to start the target device.

[0006] According to one aspect of the embodiments of this application, a device startup method is also provided, comprising: sending a target acquisition request to a network video recording device, wherein the target acquisition request is used to acquire a target image file of a target device; receiving the target image file sent by the network video recording device, wherein the network video recording device is used to hierarchically store the target image file of the device according to device information and program information, the device includes the target device, the device information includes at least a device category, and the program information includes at least one of a program category, a program name, and a program version; and loading the target image file.

[0007] According to another aspect of the embodiments of this application, a device startup apparatus is also provided, comprising: a first receiving module, configured to receive a target acquisition request sent by a target device, wherein the target acquisition request is used to request a target image file of the target device; a determining module, configured to determine the target image file based on the target acquisition request, wherein the target image file is pre-stored in a network video recording device, the network video recording device hierarchically storing the target image file of the device according to device information and program information, the device including the target device, the device information including at least a device category, and the program information including at least one of a program category, a program name, and a program version; and a first sending module, configured to send the target image file to the target device to start the target device.

[0008] According to another aspect of the embodiments of this application, a device startup apparatus is also provided, comprising: a second sending module, configured to send a target acquisition request to a network video recording device, wherein the target acquisition request is used to acquire a target image file of a target device; a second receiving module, configured to receive the target image file sent by the network video recording device, wherein the network video recording device is configured to store the target image file of the device hierarchically according to device information and program information, the device including the target device, the device information including at least a device category, and the program information including at least one of a program category, a program name, and a program version; and a loading module, configured to load the target image file.

[0009] In one exemplary embodiment, the apparatus is configured to determine the target image file based on the target acquisition request by: parsing the target acquisition request, determining target device parameters and target program parameters, wherein the target device parameters are used to indicate the target device category of the target device, and the target program parameters are used to indicate at least one of the target program category, target program name, and target program version of the target device; and determining the target image file from an initial image file according to the target device parameters and the target program parameters.

[0010] In an exemplary embodiment, the apparatus is configured to determine the target image file from the initial image file according to the target device parameters and the target program parameters in the following manner: determining a first image file from the initial image file according to the target device parameters, wherein the device category corresponding to the first image file is the target device category; determining a second image file from the first image file according to the target program parameters, wherein the program category corresponding to the second image file is the target program category; determining a third image file from the second image file according to the target program parameters, wherein the program name corresponding to the third image file is the target program name; and determining the target image file from the third image file according to the target program parameters, wherein the program version corresponding to the target image file is the target program version.

[0011] In one exemplary embodiment, the apparatus is further configured to: update the target image file to obtain an updated image file; determine an update storage path based on at least one of the program category, program type, program name, and program version corresponding to the updated image file; store the updated image file in the update storage path; and, upon receiving a device update request from the target device, send the updated image file to the target device.

[0012] In an exemplary embodiment, the apparatus is further configured to: send a target request message to a first network video recording device when the target image file is not found in the local storage space of the target network video recording device, wherein the target network video recording device receives the target acquisition request, the target request message is used to acquire the target image file, and there is a communication link between the first network video recording device and the target network video recording device; receive the target image file sent by the first network video recording device; determine a target storage path according to at least one of the program category, program type, program name, and program version corresponding to the target image file; store the target image file in the target storage path, and send the target image file to the target device.

[0013] According to another aspect of the embodiments of this application, a computer-readable storage medium is also provided, wherein a computer program is stored in the computer-readable storage medium, and the computer program is configured to execute the above-described device startup method when it is run.

[0014] According to another aspect of the embodiments of this application, a computer program product or computer program is provided, which includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the startup method of the device described above.

[0015] According to another aspect of the embodiments of this application, an electronic device is also provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the device startup method through the computer program.

[0016] In this embodiment, a target acquisition request is received from a target device, wherein the target acquisition request is used to request a target image file of the target device, and the target image file is used to start the target device; the target image file is determined based on the target acquisition request, wherein the target image file is pre-stored in a network video recording device, and the network video recording device stores the target image files of the device hierarchically according to device information and program information, the device includes the target device, the device information includes at least the device category, and the program information includes at least one of the program category, program name, and program version; the target image file is sent to the target device to start the target device. By constructing a highly organized image file database and an efficient request-response mechanism, the purpose of quickly locating and distributing the startup image file is achieved, thereby realizing the technical effect of improving device startup speed and network deployment flexibility. This solves the technical problems of low efficiency in obtaining image files for starting devices under traditional methods, resulting in slow device startup and difficulty in adapting to the network deployment needs of multi-architecture devices. Attached Figure Description

[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0018] Figure 1 This is a schematic diagram of an application environment for an optional device startup method according to an embodiment of this application;

[0019] Figure 2 This is a flowchart illustrating an optional device startup method according to an embodiment of this application;

[0020] Figure 3 This is a schematic diagram of an optional device startup method according to an embodiment of this application;

[0021] Figure 4This is a schematic diagram of another optional device startup method according to an embodiment of this application;

[0022] Figure 5 This is a schematic diagram of another optional device startup method according to an embodiment of this application;

[0023] Figure 6 This is a schematic diagram of another optional device startup method according to an embodiment of this application;

[0024] Figure 7 This is a schematic diagram of the structure of an optional device starting device according to an embodiment of this application;

[0025] Figure 8 This is a schematic diagram of the structure of an optional electronic device according to an embodiment of this application. Detailed Implementation

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

[0027] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application 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 this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover 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.

[0028] The present application will be described below with reference to embodiments:

[0029] According to one aspect of the embodiments of this application, a method for starting a device is provided.

[0030] Optionally, in this embodiment, the above-mentioned device startup method can be applied to multiple fields such as network monitoring, the Internet of Things (IoT), and smart buildings. It is suitable for scenarios requiring rapid deployment and efficient management of a large number of devices with different architectures, such as large-scale security detection networks, industrial automation systems, or smart city infrastructure. Specifically, it can be used in scenarios such as... Figure 1 The illustrated method describes the startup of the aforementioned devices within a hardware environment comprised of a server (e.g., NVR server 101) and terminal devices (e.g., cameras, access control systems, sensors 103, etc.). In this environment, server 101 plays the role of centrally managing and distributing startup image files, while terminal devices 103 rely on the image files provided by the server to complete network startup or software update processes.

[0031] Furthermore, combined Figure 1 As shown, the startup method of the above-mentioned device can be implemented by the terminal device 103 or the server 101 respectively, or by the terminal device 103 and the server 101 together. This application embodiment does not limit this.

[0032] It should be noted that the aforementioned server 101 is connected to the terminal device 103 via a network and can be used to provide services for the terminal device or the application 107 installed on the terminal device to implement the aforementioned device startup method. A database 105 can also be set up on or independently of the server 101 to provide data storage services for implementing the aforementioned device startup method. Specifically:

[0033] The aforementioned server 101 and terminal device 103 can be any node in a distributed system, such as a blockchain system. This blockchain system can be formed by connecting multiple nodes through network communication. The nodes can form any type of network, and any type of computing device, such as any electronic device, can become a node in this distributed system by joining the network formed between the nodes.

[0034] The aforementioned server 101 can be a single server, a server cluster consisting of multiple servers, or a cloud server.

[0035] The aforementioned networks may include, but are not limited to, wired networks and wireless networks. The wired networks include local area networks (LANs), metropolitan area networks (MANs), and wide area networks (WANs). The wireless networks include Bluetooth, Wi-Fi, and other networks that enable wireless communication.

[0036] The aforementioned terminal device 103 may be a terminal configured with an application, and may include, but is not limited to, at least one of the following: mobile phones (such as Android phones, iOS phones, etc.), laptops, tablets, handheld computers, MID (Mobile Internet Devices), PADs, desktop computers, smart TVs, smart voice interaction devices, smart home appliances, vehicle terminals, aircraft, virtual reality (VR) terminals, augmented reality (AR) terminals, mixed reality (MR) terminals, and other computer devices.

[0037] Alternatively, as an optional implementation, such as Figure 2 As shown, the network video recording device, as the executing entity, performs the following startup method:

[0038] S202, Receive a target acquisition request sent by the target device, wherein the target acquisition request is used to request the target image file of the target device, and the target image file is used to start the target device;

[0039] Optionally, in this embodiment, the target device includes, but is not limited to, a network camera, an access control unit, and a smart sensor, which needs to acquire a specific image file to load the corresponding program and configuration during startup. A target acquisition request refers to an request initiated by the terminal device to a server (such as an NVR) during the network startup phase, requesting files containing necessary startup information, which are essential for the normal startup and operation of the device.

[0040] Optionally, in this embodiment of the application, the target image file refers to a set of files that are precisely matched according to the request information of the target device and contain all the software and configuration information required for the device to start and run, including but not limited to operating system images, application images and configuration files.

[0041] Optionally, in this embodiment, the target acquisition request includes a list of startup files. An example of a startup file list is shown below, which may include, but is not limited to, device category, program category, program name, and program version information:

[0042] {"Devices" :[ [ "IPC", "1.00" ]],

[0043] "Program" :[ [ "HX3XXX", "1.00" ]],

[0044] "Name" :[ [ "Camera_English_PN", "1.00" ]],

[0045] "Version" :[ [ "V2.860.00AT001.0.R.030925", "1.00" ]],};

[0046] It should be noted that the type and content of the target image file vary depending on the specific needs of the target device, and may include the device's bootloader, operating system kernel, applications, or any other resources required for booting. The terminal device can be any device with network communication capabilities that needs to obtain a boot image via the network to complete the boot process. This application does not limit this and aims to cover all possible network terminal devices and their image file requirements during the boot process.

[0047] For example, taking a camera as the target device, in the camera's Flash memory, this embodiment does not need to store the image file in the Flash as in the prior art. Instead, it only needs to store a file system in the Flash. The purpose of the file system is to establish a communication link with other network devices, such as an NVR server (network video recording device). This file system is different from the prior art. It only contains uboot, kernel, and a trimmed file system, and does not contain the device's business code and the kernel driver module that supports this business code.

[0048] Then, after the target device boots up, the file system runs, and the file system broadcasts the target acquisition request to the network.

[0049] S204, Determine the target image file based on the target acquisition request, wherein the target image file is pre-stored in the network video recording device, and the network video recording device stores the target image file of the device in a hierarchical manner according to device information and program information. The device includes the target device, the device information includes at least the device category, and the program information includes at least one of the program category, program name, and program version.

[0050] Optionally, in this embodiment, the aforementioned network video recording device refers to a device with large-capacity storage and network communication capabilities, serving as a centralized storage and distribution center for image files, including but not limited to an NVR server. Device category is an identifier used to classify terminal devices, categorized based on their function, purpose, or hardware platform, covering various terminal devices from simple to complex. Program category, program name, and program version together constitute the basis for determining a specific target image file. The program category can refer to a specific type of software or firmware, the program name is a unique identifier for the software or firmware, and the program version reflects the update status of the software or firmware. This information, combined, ensures a high degree of matching between the target image file and the target device.

[0051] It should be noted that network video recording devices are not limited to traditional NVRs, but can also be any network device capable of centrally storing and distributing image files, such as edge computing servers and cloud storage nodes. The scope of device information is not limited to device category, but can also include additional information such as manufacturer, hardware version, and network parameters to further refine the search criteria for image files. Similarly, the types of program information can be very broad, including not only program category, name, and version, but also compatibility identifiers, encryption keys, etc., which are not limited in this application.

[0052] For example, such as Figure 3 As shown, the distribution management system on the NVR is responsible for managing and updating the boot images of all architectures within the local area network. Taking the camera as an example, after the communication channel between the network video recording device and the camera is established, the camera will request the boot image from the NVR that established the communication channel according to its own boot file list. The network video recording device pre-stores the image files required for the boot of each device.

[0053] For example, such as Figure 4 As shown, after the minimum system of device A (the aforementioned file system) starts, device A will request startup file A from the NVR-B (the aforementioned network video recording device) with which it has established a communication path, based on its own startup file list; similarly, device B will request startup file B from the NVR-B with which it has established a communication path; device A' has established a communication path with NVR-A (the aforementioned network video recording device), and when it starts, it will request startup file A' from NVR-A.

[0054] Similarly, all devices within the network request the boot image they need from the NVR terminal with which they have established a communication path within the local area network, based on their own boot file list, and complete the device boot process.

[0055] When the NVR with which it has established a communication path does not have the required boot image, the NVR will broadcast a request to other NVRs in the network, requesting the missing boot image. When other NVRs in the network have the boot image, they will respond to the request and send the boot image back.

[0056] For example, device B requests a required boot image from its connected NVR-B. If NVR-B does not have the required boot image, device B will broadcast a request for the missing boot image. If NVR-A has the boot image, it will reply to the request and send back the missing boot image. NVR-B will then receive the boot image and send it back to device B, allowing device B to boot successfully. Simultaneously, NVR-B will store the missing boot image, so that device B can directly retrieve it from NVR-B the next time it boots.

[0057] S206, Send the target image file to the target device to start the target device.

[0058] It should be noted that the target image file can be transmitted in various ways. Depending on the network environment and device requirements, protocols such as TCP / IP, HTTP, and FTP can be used. This application does not limit this, aiming to ensure that the target image file can be transmitted stably and quickly to the target device, thereby supporting the efficient startup of the device.

[0059] Similarly, the way the target device receives and uses the target image file can be very flexible, including but not limited to memory loading, immediate execution, or execution after temporary storage. The purpose is to ensure that the device can effectively utilize the received image file to complete the boot process according to its own hardware characteristics.

[0060] In one exemplary embodiment, taking a security monitoring network application scenario as an example:

[0061] S1, the network video recording device (NVR) receives a target acquisition request from the network camera. The request carries device category information as well as specific program name and version information, indicating that the camera needs to acquire a specific image file that matches its hardware and software configuration in order to complete the startup.

[0062] S2, based on the received target acquisition request, the NVR queries its internal pre-hierarchical storage directory of image files and quickly locates the target image file that matches the request information.

[0063] S3, the NVR sends the target image file to the network camera via the network. After receiving the image file, the camera loads it into memory, starts executing the program code in the image, completes the initialization settings and system startup, and thus puts the device into normal working state.

[0064] Optionally, as an alternative implementation, the target device executes the above-mentioned device startup method, which includes: sending a target acquisition request to a network video recording device, wherein the target acquisition request is used to acquire a target image file of the target device; receiving the target image file sent by the network video recording device, wherein the network video recording device is used to hierarchically store the target image file of the device according to device information and program information, the device includes the target device, the device information includes at least a device category, and the program information includes at least one of a program category, a program name, and a program version; and loading the target image file.

[0065] In one exemplary embodiment, taking the application scenario of an intelligent traffic monitoring system as an example:

[0066] S1, when a high-definition network camera (target device) is powered on, its built-in minimal system begins to run and immediately sends a target acquisition request to the network video recording device (NVR) connected to it. This request contains detailed device information, such as the device category "traffic monitoring camera", and the required program information, including the program category, program name, and current program version number of the "high-definition video capture program", in order to obtain a specific target image file for startup.

[0067] Upon receiving the target acquisition request, the NVR immediately searches its pre-tiered image file library based on the device category and program information in the request. The NVR's storage strategy categorizes and organizes images according to device and program information, meaning it can quickly locate the latest version image file of the high-definition video capture program compatible with the traffic monitoring camera.

[0068] S3, after locating the target image file, the NVR sends the file back to the network camera via the network. Upon receiving the target image file, the camera decompresses it and loads it into memory.

[0069] S4. After the network camera loads the target image file, it begins to execute the program code in the file, completes the device initialization settings and startup process, and finally enters normal working state, ready to perform high-definition video capture and transmission tasks.

[0070] Through the embodiments of this application, a target acquisition request sent by a target device is received. The target acquisition request is used to request a target image file of the target device, and the target image file is used to start the target device. The target image file is determined based on the target acquisition request. The target image file is pre-stored in a network video recording device. The network video recording device stores the target image files of the device hierarchically according to device information and program information. The device includes the target device, and the device information includes at least the device category. The program information includes at least one of the program category, program name, and program version. The target image file is sent to the target device to start the target device. By constructing a highly organized image file database and an efficient request-response mechanism, the purpose of quickly locating and distributing the startup image file is achieved. This achieves the technical effect of improving device startup speed and network deployment flexibility, and solves the technical problems of low efficiency in obtaining image files for starting devices in traditional methods, resulting in slow device startup and difficulty in adapting to the network deployment needs of multi-architecture devices.

[0071] As an optional approach, determining the target image file based on the target acquisition request includes: parsing the target acquisition request, determining target device parameters and target program parameters, wherein the target device parameters are used to indicate the target device category of the target device, and the target program parameters are used to indicate at least one of the target program category, target program name, and target program version of the target device; and determining the target image file from the initial image file according to the target device parameters and the target program parameters.

[0072] Optionally, in this embodiment, target device parameters refer to the set of parameters provided by the target device to the server during the network startup phase to identify its category and configuration, including but not limited to device type, manufacturer, hardware version, etc. Target program parameters are parameters used to specify the program characteristics required by the device, and at least cover one of the program category, name, and version.

[0073] It should be noted that the format and transmission method of device parameters can be diverse, including but not limited to JSON, XML or other customized data structures, and network communication protocols such as TCP / IP, UDP, and HTTP. This application does not limit these methods. Similarly, the range of program parameters can be expanded according to actual needs, such as adding compatibility tags or security authentication information to further refine the selection criteria for the target image.

[0074] For example, the target acquisition request is parsed to extract the target device parameters and target program parameters. Based on these two sets of parameters, the target image file is searched and determined in the initial image file library. The network video recording device has parsing and mapping capabilities, which can transform abstract device and program requirements into specific image file location instructions, thereby achieving accurate file retrieval and distribution.

[0075] In one exemplary embodiment, the startup process of a security network camera is taken as an example:

[0076] S1, the network camera sends a target acquisition request to the NVR server. This request contains specific target device parameters and target program parameters, namely the device category and the category, name and version of the required program.

[0077] S2, the NVR server parses the parameters in the request and quickly locates the corresponding target image file in the storage pool. This process relies on the server-side's efficient indexing and retrieval mechanism.

[0078] S3, the NVR server sends the target image file it finds to the camera via the network. The camera receives and loads the file, completing the transformation from a minimal system to a fully functional system and enabling device startup.

[0079] By parsing the target acquisition request and determining the device parameters and program parameters through the embodiments of this application, the technical effect of accurately finding and matching the target image file from the initial image file library is achieved. This ensures that network cameras and other devices can acquire and load the startup resources most suitable for their own architecture and needs during startup, thereby guaranteeing the efficiency of device startup and the overall stability of the network system.

[0080] As an optional approach, determining the target image file from the initial image file according to the target device parameters and the target program parameters includes: determining a first image file from the initial image file according to the target device parameters, wherein the device category corresponding to the first image file is the target device category; determining a second image file from the first image file according to the target program parameters, wherein the program category corresponding to the second image file is the target program category; determining a third image file from the second image file according to the target program parameters, wherein the program name corresponding to the third image file is the target program name; and determining the target image file from the third image file according to the target program parameters, wherein the program version corresponding to the target image file is the target program version.

[0081] It should be noted that the extraction process of the first image file, the second image file, the third image file, and the final target image file can be implemented through multi-level indexing or hierarchical search algorithms to improve retrieval efficiency and accuracy. The matching criteria for parameters such as device category, program category, name, and version can be adjusted according to the complexity of the actual application scenario, such as introducing fuzzy matching or version compatibility assessment; this application does not impose any limitations on this.

[0082] For example, a first image file matching the device category is selected from the initial image file library based on the target device parameters; then, a second image file is obtained from the first image file based on the target program category; subsequently, a third image file is determined from the second image file based on the target program name; finally, the required target image file is obtained by accurately matching the target program version from the third image file.

[0083] For example, the devices include sensing cameras, NVRs, access control systems, and switches of different architectures that are interconnected via a local area network (LAN). The network video recording equipment service integrates a distribution and management system responsible for storing, distributing, and updating boot images of devices with different architectures. These boot images are categorized and stored according to device type, program type, etc. This distribution and management system ensures fast response to boot file lookup requests from various devices; updates archived devices with new programs, facilitating program updates upon the next device startup; and when a device requests a boot image from an NVR with which it has established a communication path after startup, if that NVR does not contain the boot image, it can broadcast a packet to other NVRs within the LAN to request and return the boot image.

[0084] Specifically, in each NVR device in the local area network, the program is classified according to the device category. The classification of device categories is based on the field in which the device is used. According to whether the device is used in a transportation scenario, shopping mall scenario, enterprise, etc., it is divided into device category A, device category B, ... device category N, etc.

[0085] Next, under the device category, the programs are classified according to the complexity of their functions, and then classified into program category A, program category B, ..., program category N, etc., according to the complexity of their functions.

[0086] Furthermore, based on the program category, it is further categorized by program name and version. Following the categorization method shown above, the startup file list example is as follows, containing device category, program category, program name, and program version information. After the device's minimum system starts running, it broadcasts a request packet to the network, requesting to establish a communication path with the NVR in the network. After establishing the communication path, it requests startup files from the NVR according to the startup file list, which contains these four pieces of information—device category, program category, program name, and program version. When the NVR receives this information, the distribution management system first searches by device category, then by program category, then by program name, and finally finds the corresponding version of the program, completing the rapid program search process. The search process can be described as follows: Figure 5 As shown.

[0087] In one exemplary embodiment, the startup process of a smart camera in an industrial monitoring network is taken as an example:

[0088] S1. After the smart camera is powered on, its minimum system automatically sends a target acquisition request to the network video recording device (NVR). The request carries the camera's device category identifier and the category, name, and version information of the required program.

[0089] S2, the NVR server parses requests and locates the first image file from the initial image file in the storage pool based on the device category. This first image file contains a collection of software compatible with all device categories.

[0090] S3, the server further analyzes the target program category and selects a second image file that meets the condition from the first image file.

[0091] S4. Based on the target program name, accurately locate the third image file from the second image file. This file contains the software image of the specific program name.

[0092] S5. Finally, the server refers to the target program version information and determines the final target image file from the third image file, which is the startup image that fully matches the camera hardware and software requirements.

[0093] This application's embodiments enable the hierarchical location of target image files from the initial image file library, ensuring that devices within the network can quickly and accurately obtain program resources best suited to their architecture and configuration upon startup. This technology significantly improves startup efficiency, enhances network flexibility and reliability, and achieves the goal of seamless startup and upgrades for devices with different architectures in complex network environments.

[0094] As an optional approach, the method further includes: updating the target image file to obtain an updated image file; determining an update storage path based on at least one of the program category, program type, program name, and program version corresponding to the updated image file; storing the updated image file in the update storage path; and, upon receiving a device update request from the target device, sending the updated image file to the target device.

[0095] Optionally, in this embodiment, updating the image file refers to a new version file generated after software upgrades or patching of the target image file, including but not limited to operating system updates, application software upgrades, or security patches. The device update request is sent by the network device to obtain the latest version of the software image file to enable device software updates or functional enhancements.

[0096] It should be noted that the determination of the update storage path can be based on various strategies, including but not limited to creating subdirectories by device category, program category name or version number, or using a database for entry classification and storage. This application does not limit these strategies, and the purpose is to ensure that the update image file can be quickly located and retrieved.

[0097] For example, after receiving a software update package, the network video recording device updates the target image file to obtain an updated image file; it determines the storage path of its internal storage space based on the program category, name, and version information of the updated image file; and stores the updated image file in that path. When it receives a device update request from the target device, the network video recording device can quickly retrieve the latest image file from the update storage path and send it to the requesting device to support its software update.

[0098] When a device with a specific architecture needs a program update, it should be archived according to device category, program category, program name, and version number. Specifically, for example, if device category A_program category A_program name a needs a program update, then the corresponding version of the program should be saved in that path. When programs in other categories need an update, they should be archived sequentially using the same method.

[0099] After the device starts up, you can see the updated program version on the web interface. When you need to update the program, simply select the new version. This will update the program version number in the startup file list on the device. The next time you start the device, it will request the new version of the program and complete the program update and upgrade.

[0100] In one exemplary embodiment, the software upgrade of a network camera within a security local area network is taken as an example:

[0101] S1, the NVR server receives a software update package provided by the manufacturer, which includes a new operating system image, video encoding applications, and security patches.

[0102] S2, the server updates the existing target image file, generates an updated image file, and determines the update storage path according to the program category, name, and version number.

[0103] S3, the updated image file is stored in the corresponding update storage path, forming an update version index.

[0104] S4: The network camera sends a device update request to the NVR server through the web interface.

[0105] S5: The NVR server retrieves the corresponding update image file from the update storage path based on the parameters requested by the device and sends it to the network camera via the network.

[0106] S6: The network camera receives and loads the updated image file, completing the software version upgrade.

[0107] Through the embodiments of this application, a technical solution is adopted that involves updating the image file, determining the update storage path, storing the update image file, and responding to device update requests. This enables remote automatic upgrades of device software, ensuring that all devices in the network can obtain the latest version of software resources in a timely and accurate manner.

[0108] As an optional approach, the method further includes: when the target image file is not found in the local storage space of the target network video recording device, sending a target request message to the first network video recording device, wherein the target network video recording device receives the target acquisition request, the target request message is used to acquire the target image file, and there is a communication link between the first network video recording device and the target network video recording device; receiving the target image file sent by the first network video recording device; determining a target storage path based on at least one of the program category, program type, program name, and program version corresponding to the target image file; storing the target image file in the target storage path; and sending the target image file to the target device.

[0109] It should be noted that the type and transmission rate of the communication link can be diverse, such as using Gigabit Ethernet, Wi-Fi, or direct fiber optic connection. This application does not limit this, as long as it can ensure the timely transmission of the target request message and the rapid download of the target image file. Furthermore, the storage format and encryption method of the target image file can also be flexibly adjusted according to actual needs, ensuring both security and transmission efficiency.

[0110] For example, when a target network video recording device cannot find a matching target image file in its local storage space, it sends a target request message to a first network video recording device with which it has a communication link, requesting to obtain the target image file. The first network video recording device responds to the target request message and transmits the target image file to the target network video recording device through the link. After receiving the file, the latter determines the target storage path based on the program type, name, and version information, stores the file in the corresponding location, and forwards it to the target device immediately, ensuring that the device can start up and run smoothly.

[0111] Furthermore, when the boot image for the target device cannot be found, a broadcast request can be sent to other NVRs within the local area network, requesting the boot image. Once the boot image is received, it is saved and archived locally on the target network video recording device and returned to the target. When the target device requests the boot image from an NVR with which it has established a communication path, and that NVR does not have the boot image saved, it will send a request message to other NVRs in the network, requesting the boot image. If an NVR has the boot image, it will respond to the boot request and return the boot image. At this point, the NVR with which it has established a communication path will save the boot image and distribute it to the requesting device.

[0112] For example, such as Figure 6 As shown, when the target device starts up, it requests a startup file from the connected NVR-A (the aforementioned target network video recording device). Since NVR-A does not have the startup file, it sends request messages to the connected NVR-B (the aforementioned first network video recording device) and NVR-C (the aforementioned first network video recording device). NVR-B does not have the required startup file, and since no other NVR is connected to it besides NVR-A, it does not reply to the request message. Upon receiving the request message, NVR-C searches and finds that it also does not have the required startup file. Therefore, it continues to send a request message to the connected NVR-D (the aforementioned first network video recording device). After receiving the request message, NVR-D finds the startup file and responds to the request, sending the startup file back to NVR-C. NVR-C then sends it back to NVR-A, which finally sends the startup file back to the device. Simultaneously, NVR-A saves the startup image of the device, which will be directly returned to the device the next time it starts up.

[0113] In one exemplary embodiment, taking the scenario of a camera failing to start in a security network as an example:

[0114] S1, the camera (target device) sends a target acquisition request to the NVR-A (target network video recording device), the request including the device category and the specific category, name and version information of the required program.

[0115] The S2 and NVR-A attempted to search for the target image file in their local storage, but due to a recent software update, the required file was not updated locally in time, and the search failed.

[0116] S3, NVR-A sends a target request message to NVR-B (the first network video recording device), the request containing information about the camera's device type and the required program, and the two maintain a communication link via Gigabit Ethernet.

[0117] S4, after receiving the request, NVR-B retrieves the target image file from its local storage and sends it to NVR-A via the communication link.

[0118] S5, NVR-A determines the storage path of the target image file, which is based on the device category of the target device and the requested program category, name, and version information.

[0119] S6, NVR-A stores the target image file to the target storage path and immediately forwards it to the camera. The camera loads the new file and then starts up.

[0120] This application's embodiments employ a mechanism that requests the target image file from the first network video recording device when it is not found in local storage. This achieves efficient sharing and rapid distribution of the target image file in a distributed network environment. It significantly improves the success rate of device startup and the utilization rate of network resources, thereby enhancing network resilience and optimizing the device startup experience.

[0121] In summary, in the above-described device startup method, when there are numerous network cameras with different architectures within the network, the startup images for each architecture differ. A distribution management system manages the startup images for all architectures within the network. Each device requests its startup image from the distribution management system based on its own startup file list, thus completing the device startup. This solution is compatible with devices of different architectures within the network, ensuring that all network cameras of different architectures can successfully request the required startup image and complete the network startup.

[0122] Furthermore, based on the above-mentioned device startup method, an image library distribution and management system is built on the NVR server for network startup of multi-architecture devices within the security LAN, including but not limited to:

[0123] 1) Distribution and management system, which stores boot image files of various models of devices connected to the NVR and establishes communication channels with the devices through network interfaces;

[0124] 2) When the device starts up, it sends a list of startup files to the NVR server via standard network protocols (DHCP or TFTP). The list of startup files includes the device category, program category, program name, and program version information.

[0125] 3) The NVR server retrieves and distributes the corresponding boot image based on the boot file list. The device receives the boot image and completes the boot process. Essential technical features include an image library distribution management system, a boot file list parsing module, and a network transmission module.

[0126] Furthermore, the image library distribution management system's rapid search response to requests for a list of startup files may include, but is not limited to, image caching mechanisms and fault recovery functions to improve startup reliability and efficiency.

[0127] By employing an image library distribution management system to uniformly manage the program packages required by devices of various architectures, the system saves FLASH space for cameras across the entire network, significantly reducing the hardware cost of network cameras. It ensures that all devices with different architectures within the network can successfully obtain the required boot image and complete the startup process. Given the diverse device architectures and significant hardware differences in the network camera industry, this system greatly improves hardware compatibility, guaranteeing that all devices within the local area network can successfully obtain the required boot image and complete network startup. Furthermore, program upgrades and updates are more convenient; only the program packages managed by the distribution management system need to be updated, and the devices automatically obtain the new program and complete the update upon startup.

[0128] It is understood that in the specific embodiments of this application, data such as user information are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0129] It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps may be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0130] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method.

[0131] Based on this understanding, the technical solution of this application, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory (ROM) / random access memory (RAM), magnetic disk, optical disk), and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0132] According to another aspect of the embodiments of this application, a device startup apparatus for implementing the above-described device startup method is also provided. This device startup apparatus can be used to implement the device startup method provided in the above embodiments, and details already described will not be repeated. As used below, the term "module" can refer to a combination of software and / or hardware that implements a predetermined function. Although the apparatus described in the following embodiments is preferably implemented in software, hardware implementation, or a combination of software and hardware, is also possible and contemplated.

[0133] Figure 7 This is a structural block diagram of an optional device startup device according to an embodiment of this application, providing a device startup device for a network video recording device, such as... Figure 7 As shown, the device's starting mechanism includes:

[0134] The first receiving module 702 is used to receive a target acquisition request sent by the target device, wherein the target acquisition request is used to request the target image file of the target device;

[0135] The determination module 704 is used to determine the target image file based on the target acquisition request. The target image file is pre-stored in the network video recording device. The network video recording device stores the target image file of the device in a hierarchical manner according to device information and program information. The device includes the target device. The device information includes at least the device category. The program information includes at least one of the program category, program name and program version.

[0136] The first sending module 706 is used to send the target image file to the target device to start the target device.

[0137] According to another aspect of the embodiments of this application, a device start-up device is also provided for the target device, comprising:

[0138] The second sending module is used to send a target acquisition request to the network video recording device, wherein the target acquisition request is used to acquire the target image file of the target device;

[0139] The second receiving module is used to receive the target image file sent by the network video recording device. The network video recording device is used to store the target image file of the device hierarchically according to device information and program information. The device includes the target device, the device information includes at least the device category, and the program information includes at least one of the program category, program name, and program version.

[0140] The loading module is used to load the target image file.

[0141] In one exemplary embodiment, the apparatus is configured to determine a target image file based on a target acquisition request by: parsing the target acquisition request, determining target device parameters and target program parameters, wherein the target device parameters are used to indicate the target device category of the target device, and the target program parameters are used to indicate at least one of the target program category, target program name, and target program version of the target device; and determining the target image file from an initial image file according to the target device parameters and the target program parameters.

[0142] In one exemplary embodiment, the apparatus is configured to determine a target image file from an initial image file according to target device parameters and target program parameters in the following manner: determining a first image file from the initial image file according to the target device parameters, wherein the device category corresponding to the first image file is a target device category; determining a second image file from the first image file according to the target program parameters, wherein the program category corresponding to the second image file is a target program category; determining a third image file from the second image file according to the target program parameters, wherein the program name corresponding to the third image file is a target program name; and determining a target image file from the third image file according to the target program parameters, wherein the program version corresponding to the target image file is a target program version.

[0143] In one exemplary embodiment, the apparatus is further configured to: update a target image file to obtain an updated image file; determine an update storage path based on at least one of the program category, program type, program name, and program version corresponding to the updated image file; store the updated image file in the update storage path; and, upon receiving a device update request from a target device, send the updated image file to the target device.

[0144] In one exemplary embodiment, the apparatus is further configured to: send a target request message to a first network video recording device when the target image file is not found in the local storage space of the target network video recording device, wherein the target network video recording device receives a target acquisition request, the target request message is used to acquire the target image file, and there is a communication link between the first network video recording device and the target network video recording device; receive the target image file sent by the first network video recording device; determine a target storage path based on at least one of the program category, program type, program name, and program version corresponding to the target image file; store the target image file in the target storage path; and send the target image file to the target device.

[0145] Regarding the apparatus in the above embodiments, the terms "module" or "unit" refer to a computer program or part of a computer program with a predetermined function, which works together with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit. The specific manner in which each module performs its operations has been described in detail in the embodiments relating to the method, and will not be elaborated upon here.

[0146] According to another aspect of the embodiments of this application, an electronic device is provided.

[0147] The electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. The processor is configured to perform the steps in any of the above method embodiments via the computer program. In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor. Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0148] According to one aspect of this application, a computer program product is also provided, which includes a computer program.

[0149] The computer program product includes a computer program / instructions containing program code for performing the methods shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via communication section 809, and / or installed from removable media 811. When the computer program is executed by central processing unit 801, it performs various functions provided in the embodiments of this application. The sequence numbers of the embodiments of this application above are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0150] Figure 8 A schematic block diagram of a computer system architecture for implementing embodiments of the present application is shown. Figure 8As shown, the computer system 800 includes a Central Processing Unit (CPU) 801, which can perform various appropriate actions and processes based on programs stored in ROM 802 or programs loaded into RAM 803 from storage section 808. Random access memory 803 also stores various programs and data required for system operation. The CPU 801, ROM 802, and RAM 803 are interconnected via bus 804. Input / output (I / O) interface 805 is also connected to bus 804.

[0151] The following components are connected to I / O interface 805: an input section 806 including a keyboard, mouse, etc.; an output section 807 including a cathode ray tube (CRT), liquid crystal display (LCD), and speakers, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card, such as a local area network card or modem, etc. The communication section 809 performs communication processing via a network such as the Internet. A drive 810 is also connected to I / O interface 805 as needed. Removable media 811, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 810 as needed so that computer programs read from them can be installed into storage section 808 as needed.

[0152] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0153] Specifically, according to embodiments of this application, the processes described in the various method flowcharts can be implemented as computer programs / instructions. For example, embodiments of this application include a computer program / instruction comprising a computer program carried on a computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via a communication portion, and / or installed from a removable medium. When the computer program is executed by a central processing unit, it performs various functions defined in the system of this application. In such embodiments, the computer program / instruction can be downloaded and installed from a network via a communication portion, and / or installed from a removable medium. When the computer program / instruction is executed by a central processing unit, it performs the aforementioned device startup method.

[0154] According to one aspect of this application, a computer-readable storage medium is also provided.

[0155] The processor of the aforementioned electronic device can read the computer instructions from a computer-readable storage medium, and the processor executes the computer instructions to cause the electronic device to perform the device startup method provided in the various optional implementations of the device startup aspect.

[0156] Optionally, in this embodiment, the computer-readable storage medium described above may be configured to store methods for performing the embodiments of this application.

[0157] Optionally, in this embodiment, those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing the hardware related to the terminal device. The program can be stored in a computer-readable storage medium, which may include: flash drive, read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0158] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0159] If the integrated units in the above embodiments are implemented as software functional units and sold or used as independent products, they can be stored in the aforementioned computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause one or more electronic devices to execute all or part of the steps of the methods described in the various embodiments of this application.

[0160] In the several embodiments provided in this application, it should be understood that the disclosed application can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of 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 displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between units or modules may be electrical or other forms.

[0161] 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.

[0162] 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.

[0163] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method for starting a device, characterized in that, include: Receive a target acquisition request sent by the target device, wherein the target acquisition request is used to request a target image file of the target device, and the target image file is used to start the target device; The target image file is determined based on the target acquisition request, wherein the target image file is pre-stored in a network video recording device, and the network video recording device stores the target image file of the device hierarchically according to device information and program information. The device includes the target device, and the device information includes at least the device category. The program information includes at least one of the program category, program name, and program version. The target image file is sent to the target device to start the target device.

2. The method according to claim 1, characterized in that, Determining the target image file based on the target acquisition request includes: Parse the target acquisition request to determine the target device parameters and target program parameters, wherein the target device parameters are used to indicate the target device category of the target device, and the target program parameters are used to indicate at least one of the target program category, target program name, and target program version of the target device; The target image file is determined from the initial image file according to the target device parameters and the target program parameters.

3. The method according to claim 2, characterized in that, The step of determining the target image file from the initial image file according to the target device parameters and the target program parameters includes: A first image file is determined from the initial image file according to the target device parameters, wherein the device category corresponding to the first image file is the target device category; A second image file is determined from the first image file according to the target program parameters, wherein the program category corresponding to the second image file is the target program category; A third image file is determined from the second image file according to the target program parameters, wherein the program name corresponding to the third image file is the target program name; The target image file is determined from the third image file according to the target program parameters, wherein the program version corresponding to the target image file is the target program version.

4. The method according to claim 1, characterized in that, The method further includes: Update the target image file to obtain an updated image file; The update storage path is determined based on at least one of the program category, program name, and program version corresponding to the update image file; Store the updated image file in the updated storage path; Upon receiving a device update request from the target device, the update image file is sent to the target device.

5. The method according to claim 1, characterized in that, The method further includes: If the target image file is not found in the local storage space of the target network video recording device, a target request message is sent to the first network video recording device. The target network video recording device receives the target acquisition request. The target request message is used to acquire the target image file. There is a communication link between the first network video recording device and the target network video recording device. Receive the target image file sent by the first network video recording device; The target storage path is determined based on at least one of the following: program category, program name, and program version corresponding to the target image file; The target image file is stored in the target storage path and then sent to the target device.

6. A method for starting a device, characterized in that, include: Send a target acquisition request to the network video recording device, wherein the target acquisition request is used to acquire the target image file of the target device; The network video recording device receives the target image file sent by the network video recording device, wherein the network video recording device is used to store the target image file of the device hierarchically according to device information and program information, the device includes the target device, the device information includes at least the device category, and the program information includes at least one of the program category, program name, and program version; Load the target image file.

7. A starting device for an apparatus, characterized in that, include: The first receiving module is configured to receive a target acquisition request sent by the target device, wherein the target acquisition request is used to request a target image file of the target device; The determination module is used to determine the target image file based on the target acquisition request, wherein the target image file is pre-stored in a network video recording device, the network video recording device stores the target image file of the device hierarchically according to device information and program information, the device includes the target device, the device information includes at least a device category, and the program information includes at least one of program category, program name, and program version; The first sending module is used to send the target image file to the target device to start the target device.

8. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method according to any one of claims 1 to 5 or 6.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method according to any one of claims 1 to 5 or 6.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5 or 6.

Images