Configuration file management method and device, electronic equipment and storage medium

Abstract

The invention discloses a configuration file management method and device, electronic equipment and a storage medium, and the method comprises the steps: issuing a configuration file to a roadside base station, the configuration file carrying public configuration for managing the roadside base station; in response to differential configuration of the configuration file in the roadside base station, modifying public configuration of the roadside base station into base station configuration; receiving a request of the MEC equipment in the roadside base station, and issuing a configuration file of the MEC equipment to the MEC equipment in the roadside base station; and responding to a parameterized starting result of the configuration file of the MEC equipment in the MEC equipment in the roadside base station, so as to start the MEC equipment in the roadside base station to operate. According to the method and the device, on one hand, efficient configuration of the configuration file is realized, and on the other hand, starting of the remote MEC equipment is realized.

Description

Technical Field

[0001] The present application relates to the technical field of roadside equipment operation and maintenance, and in particular to a configuration file management method, device, electronic device, and storage medium. Background Art

[0002] MEC (Multi-Access Edge Computing) devices / servers are the core computing units of roadside equipment. The stable operation of each process node depends on its configuration file. With the large-scale construction of smart roads, the number of MECs deployed is very considerable. However, the software configuration of current MEC devices is completed by manual login, which is inefficient and prone to errors, and has serious security issues. When problems occur, they cannot be traced back. Summary of the invention

[0003] The embodiments of the present application provide a configuration file management method, device, electronic device, and storage medium to achieve management and maintenance of configuration files.

[0004] The present application embodiment adopts the following technical solutions:

[0005] In a first aspect, an embodiment of the present application provides a configuration file management method, wherein the method is executed by a cloud, and the method includes:

[0006] Sending a configuration file to a roadside base station, the configuration file carrying a common configuration for managing a plurality of the roadside base stations;

[0007] In response to the differential configuration of the configuration file in the roadside base station, modifying the common configuration of the roadside base station into a base station configuration;

[0008] Receiving a request from the MEC device in the roadside base station, and sending a configuration file of the MEC device to the MEC device in the roadside base station;

[0009] In response to the parameterized startup result of the MEC device in the roadside base station by the configuration file of the MEC device, the MEC device in the roadside base station is started and operated.

[0010] In some embodiments, the public configuration includes a configuration file name, a slot, a node type, and configuration content.

[0011] The configuration file name is used to distinguish different public configurations;

[0012] The slots are used to configure the perception scenarios corresponding to different sensors in the roadside base station;

[0013] The node type is used to characterize the types of different nodes in the corresponding scenarios;

[0014] The configured content is used to carry information including at least the device IP address, account, password, and sensing distance threshold.

[0015] In some embodiments, the base station configuration includes the differential item configuration of the base station. The iterative request of the roadside base station is received, and the differential item configuration of the base station that needs to add or modify configuration items is synchronized to the public configuration.

[0016] In some embodiments, modifying the public configuration of the roadside base station to the base station configuration in response to the differential configuration of the configuration file in the roadside base station includes:

[0017] In response to the differential configuration of the configuration file in the roadside base station, determine the priority of the base station configuration and the public configuration based on the viewing request, and replace the variable parameters in the public configuration with the actual device information in the roadside base station.

[0018] In some embodiments, receiving the request of the MEC device in the roadside base station and sending the configuration file of the MEC device to the MEC device in the roadside base station includes:

[0019] Receive the configuration pull request of the MEC device in the roadside base station, and send the configuration file of the MEC device to the MEC device in the roadside base station to start the MEC device in the roadside base station to record this pull operation at the same time;

[0020] When the configuration file of the MEC device is modified, push the modified configuration file of the MEC device to the MEC device in the roadside base station.

[0021] In some embodiments, the method further includes:

[0022] According to the viewing request of the configuration file of the MEC device, send a viewing instruction to the MEC device to view the corresponding configuration file of the MEC device.

[0023] In some embodiments, the method further includes:

[0024] Periodically poll the MEC device to obtain the configuration file of the MEC device;

[0025] Compare the configuration file of the MEC device with the pre-saved MEC historical configuration file;

[0026] When the configuration file of the MEC device is inconsistent with the pre-saved MEC historical configuration file, send an alarm.

[0027] Second aspect, an embodiment of the present application further provides a configuration file management device, which is executed by the cloud, and the device includes:

[0028] A first module, configured to send a configuration file to a roadside base station, where the configuration file carries a common configuration for managing multiple roadside base stations;

[0029] A second module, configured to modify the common configuration of the roadside base station to a base station configuration in response to the differential configuration of the configuration file in the roadside base station;

[0030] A third module, configured to receive a request from a MEC device in the roadside base station, and send the configuration file of the MEC device to the MEC device in the roadside base station;

[0031] A fourth module, configured to start and run the MEC device in the roadside base station in response to the parameterized start result of the configuration file of the MEC device in the MEC device in the roadside base station.

[0032] Third aspect, an embodiment of the present application further provides an electronic device, including: a processor; and a memory arranged to store computer-executable instructions, where the executable instructions, when executed, cause the processor to execute the above method.

[0033] Fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, where the computer-readable storage medium stores one or more programs, and when the one or more programs are executed by an electronic device including multiple application programs, the electronic device is caused to execute the above method.

[0034] At least one of the above technical solutions adopted in the embodiments of the present application can achieve the following beneficial effects: sending a configuration file to a roadside base station, where the configuration file carries a common configuration for managing the roadside base station, and modifying the common configuration of the roadside base station to a base station configuration in response to the differential configuration of the configuration file in the roadside base station. Since the common configuration and the base station configuration are adopted and the base station configuration inherits from the common configuration, the same configuration file only needs to be entered once to be synchronized to all base stations, thus achieving efficient configuration. Receiving a request from a MEC device in the roadside base station, sending the configuration file of the MEC device to the MEC device in the roadside base station, and starting and running the MEC device in the roadside base station in response to the parameterized start result of the configuration file of the MEC device in the MEC device in the roadside base station. Completing the configuration of the configuration file in the cloud and pushing it to the MEC device of the roadside base station to achieve initialization and hot loading, and improving security. Description of the Drawings

[0035] The accompanying drawings described herein are used to provide a further understanding of the present application, and constitute a part of the present application. The schematic embodiments of the present application and their descriptions are used to explain the present application, and do not constitute an improper limitation to the present application. In the drawings:

[0036] Figure 1 is a schematic flowchart of the configuration file management method in an embodiment of the present application;

[0037] Figure 2 is a schematic structural diagram of the configuration file management device in an embodiment of the present application;

[0038] Figure 3 is a schematic implementation architecture diagram of the configuration file management method in an embodiment of the present application;

[0039] Figure 4 is a schematic structural diagram of an electronic device in an embodiment of the present application. Detailed Description of the Embodiments

[0040] To make the objectives, technical solutions, and advantages of the present application clearer, the technical solutions of the present application will be clearly and completely described below in conjunction with the specific embodiments of the present application and the corresponding accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. All other embodiments obtained by those of ordinary skill in the art based on the embodiments in the present application without creative efforts shall fall within the scope of protection of the present application.

[0041] The following will describe in detail the technical solutions provided by each embodiment of the present application with reference to the accompanying drawings.

[0042] An embodiment of the present application provides a configuration file management method. As Figure 1 shown, a schematic flowchart of the configuration file management method in an embodiment of the present application is provided. The method at least includes the following steps S110 to step S140:

[0043] Step S110: Send the configuration file to the roadside base station, and the configuration file carries the public configuration for managing the roadside base station.

[0044] For the roadside base station, the configuration file can implement the function configuration of the roadside base station.

[0045] In the "roadside base station" in the embodiment of the present application, it refers to the roadside poles deployed at intersections and sections according to service requirements. Multiple types of sensors are deployed on the roadside poles, including but not limited to vision sensors, radar sensors, etc. Specifically, the vision sensors use bullet cameras, fish-eye cameras, and cameras, etc. The radar sensors use lidar, millimeter-wave radar, etc. In addition, the deployment method of the sensors is also related to the lane traffic flow direction, such as reverse traffic cameras, forward traffic cameras, reverse traffic lidar, forward traffic lidar, etc. AsFigure 3 As shown, it includes multiple roadside base stations, which can be batch-deployed through the cloud. Each of the roadside base stations includes an MEC and sensors. The sensors are used for sensing, and the MEC is used to provide computing power to achieve data sensing and data fusion.

[0046] When configuring the configuration file in the cloud, it carries the common configuration for managing multiple roadside base stations. The cloud automatically synchronizes the common configuration items of each base station to all base stations through inheritance by entering the common configuration items, and supports variable substitution. Each roadside base station can meet the requirements in most scenarios without modifying the configuration file, and at the same time, it also supports the base station to modify the configuration to meet the requirements of special scenarios.

[0047] In practical applications, since the types and formats of the configuration files of roadside base stations of the same model are basically the same, the differences are in the IP addresses of the sensing devices and the sensing distance thresholds in the configuration content. Therefore, it can be based on the common configuration for distribution, and then realize the differential base station configuration on the basis of the common configuration.

[0048] Step S120, in response to the differential configuration of the configuration file in the roadside base station, modify the common configuration of the roadside base station to the base station configuration.

[0049] After the configuration file is distributed to multiple roadside base stations as the common configuration, in the cloud, in response to the differential configuration of the configuration file in the roadside base station, modify the common configuration of the roadside base station to the base station configuration. That is to say, in the cloud, according to the differential configuration request, modify the common configuration of the roadside base station to the differential base station configuration, and the deployment of the configuration file of the roadside base station can be completed.

[0050] Step S130, receive the request of the MEC device in the roadside base station, and send the configuration file of the MEC device to the MEC device in the roadside base station.

[0051] There is at least one MEC device in the roadside base station. According to actual business needs, multiple MEC devices can be deployed. For example, at intersections where the traffic flow is large, multiple MEC devices need to be deployed to provide more computing power for sensing and fusion. The cloud sends the configuration file of the MEC device to the MEC device in the roadside base station. After the MEC device successfully pulls it, the computing power node is started. The computing power node includes a sensing node, a fusion node, etc.

[0052] Step S140, in response to the parameterized startup result of the configuration file of the MEC device in the MEC device in the roadside base station, start and run the MEC device in the roadside base station.

[0053] In the embodiment of the present application, "parameterized startup" includes but is not limited to the startup of perception parameters, fusion parameters, and initialization parameters in the MEC device, and different nodes have their own parameterized startup methods.

[0054] When it is necessary to provide roadside base station perception and fusion services, the configuration file of the MEC device is sent to the MEC device through the cloud, and then the MEC device in the roadside base station is started in response to the initialization of the parameterized startup result of the MEC device. It can be understood that the MEC device will start the corresponding computing node according to the configuration file of the MEC device.

[0055] Preferably, the MEC devices can be deployed in batches to enable batch MEC device startup and operation.

[0056] Through the above method, differential configuration of configuration files is achieved through public configuration, so that corresponding base station configuration is achieved on each roadside base station, and efficient configuration is achieved. Through the above method, the MEC device in the roadside base station pulls the configuration file of the MEC device, and obtains the parameterized startup result of the MEC device in the roadside base station, so that the MEC device in the roadside base station starts running, thereby realizing the management of the configuration file of the MEC device in the cloud.

[0057] Different from the related art, when manual login is used to log into the MEC device in the roadside base station, the problem of insufficient security is caused. The configuration file of the MEC device is sent through the cloud, and parameterized startup is realized through the configuration file of the MEC device to start the MEC device in the roadside base station.

[0058] In one embodiment of the present application, the public configuration includes a configuration file name, a slot, a node type, and a configuration content, wherein the configuration file name is used to distinguish different public configurations; the slot is used to configure the perception scenarios corresponding to different sensors in the roadside base station; the node type is used to characterize the types of different nodes in the corresponding scenarios; the configuration content is used to carry information including at least the device IP address, account number, password, and perception distance threshold.

[0059] The configuration file name in the public configuration can distinguish different public configurations.

[0060] The slot refers to the installation location of the sensing equipment on the roadside pole, such as the camera in the opposite lane and the lidar in the corresponding lane.

[0061] The node type to which it belongs, according to the type of different nodes, the corresponding data is parsed to the MEC device. For example, camera perception node, camera driver node, fusion node.

[0062] Configuration content includes the configuration file, node type, sensing range, account number, and password of the roadside base station.

[0063] Note that the configuration file content supports entering variables. For example, variables such as the IP address of the sensing device can be entered as $ <ip>In addition, the variables also include account, password, and range threshold.

[0064] In one embodiment of the present application, the base station configuration includes the differential item configuration of the base station, receives the iterative request of the roadside base station, and synchronizes the differential item configuration of the base station that needs to add or modify configuration items to the public configuration.

[0065] All public configuration files sent from the cloud are automatically synchronized to all roadside base stations. Each roadside base station additionally supports differential configuration, that is, the configuration file synchronized from the public configuration can be modified. After modification, the differential item configuration of the base station is recorded to obtain the base station configuration. If it is necessary to perform iterative calculation nodes of the MEC device in the roadside base station and add or modify configuration items, the public configuration can be directly modified and then synchronized to all base stations.

[0066] In one embodiment of the present application, modifying the public configuration of the roadside base station to the base station configuration in response to the differential configuration of the configuration file in the roadside base station includes: in response to the differential configuration of the configuration file in the roadside base station, modifying the variable parameters in the public configuration according to the priority.

[0067] The key value of the public configuration can be used as a flag to distinguish different types of configuration files. When viewing the base station configuration file, it is achieved by integrating the public configuration and the base station differential configuration. When there are the same keys, the differential configuration of the base station has a higher priority. Additionally, when viewing the configuration, the variables are automatically replaced with the device information under the roadside base station. For example, $ <ip>Replace it with the IP address of the base station device. Of course, it also includes other variables, such as the sensing distance threshold.

[0068] In one embodiment of the present application, receiving the request of the MEC device in the roadside base station and sending the configuration file of the MEC device to the MEC device in the roadside base station includes: receiving the configuration pull request of the MEC device in the roadside base station, sending the configuration file of the MEC device to the MEC device in the roadside base station to start the MEC device in the roadside base station, and recording this pull operation at the same time; when the configuration file of the MEC device is modified, pushing the modified configuration file of the MEC device to the MEC device in the roadside base station.

[0069] The MEC device in the roadside base station starts to pull the configuration. When the MEC device starts, the interaction center actively pulls the configuration from the cloud through gRPC. After successful pulling, the computing power node is started, and the pulling history is recorded in the cloud. After the cloud modifies the configuration, it supports active push. The interaction center of the MEC device is called through gRPC to actively push the configuration file and record the push history. The MEC device needs to parse and obtain the configuration information as the parsing results of different nodes.

[0070] It should be noted that "gRPC" is a high-performance, open-source and general RPC (Remote Procedure Call) framework, which supports multiple programming languages and uses Protocol Buffers (protobuf) as the interface definition language and communication protocol. It is mainly used for remote calls in the embodiments of the present application.

[0071] Considering that the nodes in the roadside base station do not have the ability to interact with the cloud, an interaction center is encapsulated to be responsible for pulling the configuration from the platform or outputting from the node to the cloud. The interaction center is used to communicate with the cloud and pull or synchronize the configuration file in the roadside base station.

[0072] In one embodiment of the present application, the method further includes: sending a viewing instruction to the MEC device according to the viewing request of the configuration file of the MEC device to view the corresponding configuration file of the MEC device.

[0073] The cloud can support the remote management mode to view the configuration file of the MEC device. By sending a viewing instruction to the interaction center of the MEC device, the content of the specified configuration file can be viewed.

[0074] In one embodiment of the present application, the method further includes: regularly polling the MEC device to obtain the configuration file of the MEC device; comparing the configuration file of the MEC device with the pre-saved MEC historical configuration file; and sending an alarm when the configuration file of the MEC device is inconsistent with the pre-saved MEC historical configuration file.

[0075] The cloud configures the inspection mode. The cloud conducts an inspection once within a set fixed period. And the cloud polls the MEC devices to obtain the configuration files on each MEC device, compares them with the historical content of the MEC devices recorded by the platform. If they are inconsistent, an email or SMS will be sent for alarm.

[0076] The embodiment of the present application also provides a configuration file management device 200, as Figure 2 shown, which provides a structural schematic diagram of the configuration file management device in the embodiment of the present application. The configuration file management device 200 at least includes: a first module 210, a second module 220, a third module 230, and a fourth module 240, where:

[0077] In an embodiment of the present application, the first module 210 is specifically configured to: send the configuration file to the roadside base station, and the configuration file carries the public configuration for managing the roadside base station.

[0078] For the roadside base station, the configuration file can implement the function configuration of the roadside base station.

[0079] The "roadside base station" in the embodiment of the present application refers to the roadside poles deployed at intersections and road sections according to service requirements. Multiple types of sensors are deployed on the roadside poles, including but not limited to vision sensors, radar sensors, etc. Specifically, the vision sensors adopt bullet cameras, fish-eye cameras, and cameras, etc. The radar sensors adopt lidar, millimeter-wave radar, etc. In addition, the deployment method of the sensors is also related to the lane traffic flow direction, such as reverse traffic cameras, forward traffic cameras, reverse traffic lidar, forward traffic lidar, etc.

[0080] When the cloud configures the configuration file, it carries the public configuration for managing multiple roadside base stations. The cloud automatically synchronizes the common configuration items of each base station to all base stations through the inheritance relationship and supports variable substitution. Each roadside base station can meet the requirements in most scenarios without modifying the configuration file, and at the same time, it also supports the base station to modify the configuration to meet the requirements of special scenarios.

[0081] In practical applications, since the configuration file types and formats of the roadside base stations of the same model are almost the same, the differences are the IP addresses of the sensing devices and the sensing distance thresholds in the configuration content. Therefore, it is possible to issue based on the public configuration and then implement the differential base station configuration on the basis of the public configuration.

[0082] In an embodiment of the present application, the second module 220 is specifically configured to: in response to the differential configuration of the configuration file in the roadside base station, modify the public configuration of the roadside base station to the base station configuration.

[0083] After the configuration file is sent to multiple roadside base stations as a common configuration, the cloud responds to the differentiated configuration of the configuration file in the roadside base station and modifies the common configuration of the roadside base station into the base station configuration. In other words, the configuration file deployment of the roadside base station can be completed by modifying the common configuration of the roadside base station into the differentiated base station configuration according to the differentiated configuration request in the cloud.

[0084] In one embodiment of the present application, the third module 230 is specifically used to: receive a request from the MEC device in the roadside base station, and send the configuration file of the MEC device to the MEC device in the roadside base station.

[0085] There is at least one MEC device in the roadside base station. Multiple MEC devices can be deployed according to actual business needs. For example, due to the large traffic volume at the intersection, multiple MEC devices need to be deployed to provide more computing power for perception and fusion. The cloud sends the configuration file of the MEC device to the MEC device in the roadside base station. After the MEC device successfully pulls it, it starts the computing node. The computing nodes include perception nodes, fusion nodes, etc.

[0086] In one embodiment of the present application, the fourth module 240 is specifically used to: respond to the parameterized startup result of the MEC device in the roadside base station in response to the configuration file of the MEC device, so as to start the operation of the MEC device in the roadside base station.

[0087] In the embodiment of the present application, "parameterized startup" includes but is not limited to the startup of perception parameters, fusion parameters, and initialization parameters in the MEC device, and different nodes have their own parameterized startup methods.

[0088] When it is necessary to provide roadside base station perception and fusion services, the configuration file of the MEC device is sent to the MEC device through the cloud, and then the MEC device in the roadside base station is started in response to the initialization of the parameterized startup result of the MEC device. It can be understood that the MEC device will start the corresponding computing node according to the configuration file of the MEC device.

[0089] Preferably, the MEC devices can be deployed in batches to enable batch MEC device startup and operation.

[0090] In one embodiment of the present application, the public configuration includes a configuration file name, a slot, a node type, and configuration content.

[0091] The configuration file name is used to distinguish different public configurations;

[0092] The slots are used to configure the perception scenarios corresponding to different sensors in the roadside base station;

[0093] The node type belongs to is used to characterize the types of different nodes in the corresponding scenario;

[0094] The configuration content is used to carry information including at least the device IP address, account, password, and sensing distance threshold.

[0095] In an embodiment of the present application, the base station configuration includes the differential item configuration of the base station, receives the iterative request of the roadside base station, and synchronizes the differential item configuration of the base station that needs to add or modify configuration items to the public configuration.

[0096] In an embodiment of the present application, the second module 220 is further used for

[0097] In response to the differential configuration of the configuration file in the roadside base station, determine the priority of the base station configuration and the public configuration based on the viewing request, and replace the variable parameters in the public configuration with the actual device information in the roadside base station.

[0098] In an embodiment of the present application, the third module 230 is further used for

[0099] Receive the configuration pull request of the MEC device in the roadside base station, and send the configuration file of the MEC device to the MEC device in the roadside base station to start the MEC device in the roadside base station to record this pull operation at the same time;

[0100] When the configuration file of the MEC device is modified, push the modified configuration file of the MEC device to the MEC device in the roadside base station.

[0101] In an embodiment of the present application, it further includes: a remote viewing module, which is used for

[0102] According to the viewing request of the configuration file of the MEC device, send a viewing instruction to the MEC device to view the corresponding configuration file of the MEC device.

[0103] In an embodiment of the present application, it further includes: an inspection module, which is used for

[0104] Periodically poll the MEC device to obtain the configuration file of the MEC device;

[0105] Compare the configuration file of the MEC device with the pre-saved MEC historical configuration file;

[0106] When the configuration file of the MEC device is inconsistent with the pre-saved MEC historical configuration file, send an alarm.

[0107] It can be understood that the above configuration file management device can implement each step of the configuration file management method provided in the foregoing embodiments. The relevant explanations regarding the configuration file management method are applicable to the configuration file management device and will not be elaborated here.

[0108] Figure 4 It is a schematic structural diagram of an electronic device according to an embodiment of the present application. Please refer to Figure 4 , at the hardware level, the electronic device includes a processor, and optionally also includes an internal bus, a network interface, and a memory. Among them, the memory may include a memory, such as a high-speed random access memory (RAM), and may also include a non-volatile memory, such as at least one disk memory, etc. Of course, the electronic device may also include other hardware required for other services.

[0109] The processor, network interface, and memory can be interconnected through an internal bus. The internal bus can be an ISA (Industry Standard Architecture) bus, a PCI (Peripheral Component Interconnect) bus, or an EISA (Extended Industry Standard Architecture) bus, etc. The bus can be divided into an address bus, a data bus, a control bus, etc. For the sake of representation, Figure 4 only a two-way arrow is used in

[0110] The memory is used to store programs. Specifically, the program may include program code, and the program code includes computer operation instructions. The memory may include a memory and a non-volatile memory, and provide instructions and data to the processor.

[0111] The processor reads the corresponding computer program from the non-volatile memory into the memory and then runs it, forming a configuration file management device at the logical level. The processor executes the program stored in the memory and is specifically used to perform the following operations:

[0112] Send the configuration file to the roadside base station, and the configuration file carries the common configuration for managing multiple roadside base stations;

[0113] In response to the differential configuration of the configuration file in the roadside base station, modify the common configuration of the roadside base station to the base station configuration;

[0114] Receive the request of the MEC device in the roadside base station, and send the configuration file of the MEC device to the MEC device in the roadside base station;

[0115] In response to the parametric startup result of the configuration file of the MEC device in the MEC device of the roadside base station, start and run the MEC device in the roadside base station.

[0116] The above as in this application Figure 1 The method executed by the configuration file management device disclosed in the embodiments shown in this application can be applied to or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the processor or the instructions in the form of software. The above processor may be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it may also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of this application can be directly embodied as being executed and completed by the hardware decoding processor, or executed and completed by the combination of the hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory, and the processor reads the information in the memory and combines its hardware to complete the steps of the above method.

[0117] This electronic device can also execute Figure 1 the method executed by the configuration file management device in Figure 1 and implement the functions of the configuration file management device in the embodiments shown in this application. The embodiments of this application will not be elaborated here.

[0118] The embodiments of this application also propose a computer-readable storage medium. The computer-readable storage medium stores one or more programs. The one or more programs include instructions that, when executed by an electronic device including multiple application programs, can enable the electronic device to execute Figure 1 The method executed by the configuration file management device in the illustrated embodiment, and specifically used to execute:

[0119] Send the configuration file to the roadside base station, where the configuration file carries the common configuration for managing multiple roadside base stations;

[0120] In response to the differential configuration of the configuration file in the roadside base station, modify the common configuration of the roadside base station to the base station configuration;

[0121] Receive the request of the MEC device in the roadside base station, and send the configuration file of the MEC device to the MEC device in the roadside base station;

[0122] In response to the parameterized startup result of the configuration file of the MEC device in the MEC device in the roadside base station, start and run the MEC device in the roadside base station.

[0123] Those skilled in the art should understand that the embodiments of the present invention can be provided as a method, a system, or a computer program product. Therefore, the present invention can adopt the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present invention can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0124] The present invention is described with reference to the flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to the embodiments of the present invention. It should be understood that each process and / or block in the flowchart and / or block diagram, and the combination of processes and / or blocks in the flowchart and / or block diagram, can be realized by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices generate a device for realizing the specified function in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0125] These computer program instructions can also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory generate a manufactured article including an instruction device, and the instruction device realizes the specified function in Figure 1 one process or multiple processes and / or blocks Figure 1 one block or multiple blocks.

[0126] These computer program instructions can also be loaded onto a computer or other programmable data processing device, so that a series of operation steps are executed on the computer or other programmable device to generate a computer-implemented process, and thus the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one process Figure 1 one process or multiple processes and / or blocks Figure 1 steps of the functions specified in one block or multiple blocks.

[0127] In a typical configuration, a computing device includes one or more processors (CPUs), an input / output interface, a network interface, and a memory.

[0128] The memory may include non-permanent memory in the computer-readable medium, in the form of random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.

[0129] Computer-readable media includes permanent and non-permanent, removable and non-removable media and can be implemented by any method or technology for information storage. The information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette tapes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.

[0130] It should also be noted that the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements not only includes those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. Without further limitation, an element defined by the statement "including one..." does not exclude the existence of another identical element in the process, method, commodity or device including the said element.

[0131] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a system or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware aspects. Moreover, the present application can take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0132] The above are only the embodiments of the present application and are not intended to limit the present application. For those skilled in the art, various changes and modifications can be made to the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included within the scope of the claims of the present application.< / ip> < / ip>

Claims

1. A configuration file management method, wherein: Executed by the cloud, the method includes: Sending a configuration file to a roadside base station, the configuration file carrying a common configuration for managing the roadside base station; In response to the differential configuration of the configuration file in the roadside base station, modifying the common configuration of the roadside base station into a base station configuration; Receiving a request from the MEC device in the roadside base station, and sending a configuration file of the MEC device to the MEC device in the roadside base station; In response to the parameterized startup result of the MEC device in the roadside base station by the configuration file of the MEC device, the MEC device in the roadside base station is started and operated.

2. The method of claim 1, wherein: The public configuration includes the configuration file name, slot, node type, and configuration content. The configuration file name is used to distinguish different public configurations; The slots are used to configure the perception scenarios corresponding to different sensors in the roadside base station; The node type is used to characterize the types of different nodes in the corresponding scenarios; The configuration content is used to carry information including at least the device IP address, account number, password and perception distance threshold.

3. The method of claim 2, wherein: The base station configuration includes a difference item configuration of the base station, receives an iteration request of the roadside base station, and synchronizes the difference item configuration of the base station that needs to add configuration items or modify configuration items to the public configuration.

4. The method of claim 1, wherein: The modifying the common configuration of the roadside base station to a base station configuration in response to the differentiated configuration of the configuration file in the roadside base station comprises: In response to the differentiated configuration of the configuration file in the roadside base station, the variable parameters in the common configuration are modified according to the priority.

5. The method of claim 1, wherein: The receiving a request from the MEC device in the roadside base station and sending a configuration file of the MEC device to the MEC device in the roadside base station includes: Receiving a configuration pull request from the MEC device in the roadside base station, sending the configuration file of the MEC device to the MEC device in the roadside base station, so as to start the MEC device in the roadside base station and record the pull operation at the same time; When the configuration file of the MEC device is modified, the modified configuration file of the MEC device is pushed to the MEC device in the roadside base station.

6. The method according to any one of claims 1 to 5, wherein: The method further comprises: According to the viewing request of the configuration file of the MEC device, a viewing instruction is sent to the MEC device to view the configuration file of the corresponding MEC device.

7. The method according to any one of claims 1 to 5, wherein: The method further comprises: Periodically polling the MEC device to obtain a configuration file of the MEC device; Comparing the configuration file of the MEC device with a pre-saved MEC historical configuration file; When the configuration file of the MEC device is compared with a pre-saved MEC historical configuration file and is found to be inconsistent, an alarm is sent.

8. A configuration file management device, wherein: Executed by the cloud, the device includes: The first module is used to send a configuration file to a roadside base station, where the configuration file carries a common configuration for managing a plurality of the roadside base stations; A second module is configured to modify the common configuration of the roadside base station into a base station configuration in response to the differentiated configuration of the configuration file in the roadside base station; The third module is used to receive a request from the MEC device in the roadside base station and send a configuration file of the MEC device to the MEC device in the roadside base station; The fourth module is used to start the MEC device in the roadside base station in response to the parameterized startup result of the MEC device in the roadside base station by the configuration file of the MEC device.

9. An electronic device, comprising: processor; as well as A memory arranged to store computer executable instructions, which when executed cause the processor to perform the method of any one of claims 1 to 7.

10. A computer-readable storage medium storing one or more programs, which, when executed by an electronic device including a plurality of application programs, causes the electronic device to execute any one of the methods of claims 1 to 7.

Images