Automatic driving domain management method and device, electronic equipment, chip and medium

Abstract

The invention provides an automatic driving domain management method and device, electronic equipment, a chip and a medium, and relates to the technical field of automatic driving. The automatic driving domain management method comprises the following steps: obtaining an operation request of a first webpage end on a first rack of an automatic driving domain and the use duration of the first rack, wherein the automatic driving domain at least comprises two racks; countdown is started according to the use duration, the use permission of the first rack is distributed to the first webpage end, and the first webpage end operates the first rack within the use duration; and releasing the use permission of the first rack when the countdown of the use duration ends or an end instruction is received. Through the technical scheme provided by the invention, the problem that the rack is difficult to share and use is solved, and the resource utilization rate and usability of the rack are improved.

Description

Technical Field

[0001] The present disclosure relates to the field of autonomous driving, and in particular to an autonomous driving domain management method, device, electronic device, chip and medium. Background Art

[0002] The test bench refers to a vehicle terminal installed on the vehicle's driving platform, which has multiple functions such as Electronic Toll Collection (ETC), third generation (3G) or higher wireless communication, online navigation, traffic information, travel guide, shopping, entertainment and audio-visual, etc. During the test bench and experiment process, the test bench is difficult to share, and users have to go through many steps to access the Full Self-Driving (FSD) equipment; the FSD equipment upgrade process is cumbersome; and it is inconvenient to restart the FSD equipment after it crashes. Summary of the invention

[0003] The present disclosure provides an autonomous driving domain management method, device, electronic device, chip and medium to solve the problem of difficulty in sharing and using a test bench. The web page terminal requests the use of the test bench and the duration of use from the web page server that manages the autonomous driving domain, and the web page server allocates the use rights and duration of the test bench to the web page terminal, thereby improving the resource utilization and ease of use of the test bench.

[0004] A first aspect of the present disclosure provides an autonomous driving domain management method, which is executed by a web server, and the autonomous driving domain management system is deployed on the web server. The method includes:

[0005] Obtaining an operation request from a first web page to a first rack in an autonomous driving domain and a usage time of the first rack, where the autonomous driving domain includes at least two racks;

[0006] A countdown is started according to the usage time, and the usage right of the first rack is allocated to the first web page terminal, and the first web page terminal operates the first rack within the usage time;

[0007] When the usage time countdown ends or an end command is received, the usage rights of the first rack are released.

[0008] In one embodiment of the present disclosure, the method further includes:

[0009] Establishing a connection with the proxy terminal server through the web socket security protocol according to the preset network address and the preset port number;

[0010] Through the proxy terminal server, a session interaction is performed with the first rack according to the secure shell protocol.

[0011] In one embodiment of the present disclosure, performing a session interaction with the first rack according to the secure shell protocol through the proxy terminal server includes at least one of the following:

[0012] sending the first instruction to the first rack via the proxy terminal server according to the secure shell protocol;

[0013] The first result after the first rack executes the first instruction is received according to the secure shell protocol through the proxy terminal server.

[0014] In one embodiment of the present disclosure, the method further includes:

[0015] Receiving an upgrade instruction from the first web page to the first rack;

[0016] In response to the upgrade instruction, obtaining firmware version information of the first rack from a version library through an application program interface service of the autonomous driving;

[0017] According to the firmware version information and the device number of the first rack, an upgrade instruction is sent to the proxy upgrade server;

[0018] Writing a first firmware upgrade package into the first rack through the proxy upgrade server, the first firmware upgrade package being obtained from the version library by the proxy upgrade server;

[0019] Restart the first rack and reset the network address of the first rack to the preset network address.

[0020] In one embodiment of the present disclosure, the method further includes:

[0021] Enable the port forwarding function of the first rack;

[0022] A remote connection is made to the first rack via a secure shell protocol, wherein a first port of the first rack is connected to a second port of a proxy forwarding server, and a second port of the proxy forwarding server is connected to a web server.

[0023] In one embodiment of the present disclosure, the method further includes:

[0024] Obtaining a mapping table from a database of the web server, the mapping table including a mapping relationship between one or more test benches in the autonomous driving domain and a network relay;

[0025] Determine the first network relay corresponding to the first rack from the mapping table;

[0026] Through the first network relay, the first rack is closed or opened.

[0027] A second aspect of the present disclosure provides an autonomous driving domain management device, which is applied to a web server and includes:

[0028] An acquisition module is used to obtain an operation request from a first web page to a first rack in an autonomous driving domain and a usage time of the first rack, where the autonomous driving domain includes at least two racks;

[0029] The permission allocation module is used to start the countdown according to the usage time, allocate the usage permission of the first rack to the first web page end, and the first web page end operates the first rack within the usage time;

[0030] The permission release module is used to release the permission to use the first rack when the usage time countdown ends or an end instruction is received.

[0031] The third aspect embodiment of the present disclosure proposes an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute any one of the methods in the first aspect embodiment of the present disclosure.

[0032] The fourth aspect embodiment of the present disclosure proposes a non-transitory computer-readable storage medium storing computer instructions, characterized in that the computer instructions are used to enable a computer to execute the method in the first aspect embodiment of the present disclosure.

[0033] The fifth aspect embodiment of the present disclosure proposes a computer program product, characterized in that it includes a computer program, and when the computer program is executed by a processor, it implements any method in the first aspect embodiment of the present disclosure.

[0034] The sixth aspect embodiment of the present disclosure proposes a chip, comprising at least one processor and a communication interface; the communication interface is used to receive signals input into the chip or signals output from the chip, the processor communicates with the communication interface and implements any one of the methods in the first aspect embodiment of the present disclosure through logic circuits or execution code instructions.

[0035] In summary, according to the autonomous driving domain management method proposed in the present disclosure, the operation request of the first web page terminal to the first rack of the autonomous driving domain and the usage time of the first rack are obtained, and the autonomous driving domain includes at least two racks, so that the user can apply to the web server that manages the autonomous driving domain for the use of the rack through the web page terminal; the countdown starts according to the usage time, and the use rights of the first rack are allocated to the first web page terminal. The first web page terminal operates the first rack within the usage time, and the user obtains the use rights of the first rack on the web page terminal within the usage time, and obtains the rack permission allocation; when the usage time countdown ends or an end instruction is received, the use rights of the first rack are released. After the use ends, the use rights of the first rack are automatically released, which facilitates other users to apply for the use of the first rack and improves the resource utilization and ease of use of the rack.

[0036] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0038] Figure 1 This is a flowchart of an autonomous driving domain management method according to an embodiment of the present disclosure;

[0039] Figure 2 A flowchart of a platform sharing in an autonomous driving domain according to an embodiment of the present disclosure;

[0040] Figure 3 A schematic diagram of a bench rental in an autonomous driving domain according to an embodiment of the present disclosure;

[0041] Figure 4 This is a flowchart of an autonomous driving domain management method according to an embodiment of the present disclosure;

[0042] Figure 5 A schematic diagram of establishing a conversation interaction between a first web page and an FSD stand in this embodiment;

[0043] Figure 6 This is a schematic diagram of a session interaction established between a first web page and an FSD stand in this embodiment;

[0044] Figure 7 A schematic diagram of a network link between a web server and an FSD rack in this embodiment;

[0045] Figure 8 This is a schematic diagram of a management page for selecting an FSD stand on a first web page according to the present embodiment;

[0046] Fig. 9 It is a flow chart of an embodiment of the present disclosure, which performs a session interaction with a first rack through a proxy terminal server according to a secure shell protocol;

[0047] Fig.10 This is a flowchart of an autonomous driving domain management method according to an embodiment of the present disclosure;

[0048] Fig.11 This is a schematic diagram of a firmware upgrade process in an autonomous driving domain of this embodiment;

[0049] Fig.12 This is a schematic diagram of a firmware upgrade package list in a firmware library of an autonomous driving domain according to this embodiment;

[0050] Fig.13 This is a flowchart of an autonomous driving domain management method according to an embodiment of the present disclosure;

[0051] Fig.14 This is a schematic diagram of a remote connection process of an autonomous driving domain according to this embodiment;

[0052] Fig.15 This is a flowchart of an autonomous driving domain management method according to an embodiment of the present disclosure;

[0053] Fig.16 A schematic diagram of an autonomous driving domain management method according to an embodiment of the present disclosure;

[0054] Fig.17 It is a structural schematic diagram of an autonomous driving domain management device according to an embodiment of the present disclosure;

[0055] Fig.18 is a block diagram of an electronic device for implementing the autonomous driving domain management method disclosed herein according to an exemplary embodiment;

[0056] Fig.19 It is a schematic diagram of the structure of the chip of the embodiment of the present disclosure. DETAILED DESCRIPTION

[0057] Embodiments of the present disclosure are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout identify the same or similar originals or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be construed as limiting the present disclosure.

[0058] In the field of autonomous driving technology, the FSD bench refers to equipment used to test autonomous driving systems. It is usually composed of sensors, computers, controllers, etc. It can simulate various complex driving scenarios to help developers better understand and improve the performance of autonomous driving systems. The autonomous driving domain is divided into two cores, Orin1 and Orin2, which are independent devices.

[0059] In the related technology, the management of FSD uses a PC to mount a set of FSD racks. Several obvious problems will be encountered during use: 1. It is very troublesome to share the racks. Each jump server maintains a different username and password. The team must inform someone that they are using the rack through document sharing or other means. 2. The overall equipment maintenance workload increases linearly with the growth of equipment; 3. If a user wants to access the FSD device, he must first log in to the jump server and then log in to the FSD device. The overall operation steps are very cumbersome; 4. To upgrade the FSD device, you need to manually download the upgrade package and then run the script. The whole process is very cumbersome; 5. If the FSD device goes down, you need to manually plug and unplug the power to restart it.

[0060] The method proposed in the present disclosure is intended to solve the above problems and is applied to the management scenario of autonomous driving equipment, and can be used in the fields of unmanned driving, assisted driving, autonomous driving systems, etc. The application scenario is not limited in the embodiments of the present disclosure.

[0061] The autonomous driving domain management method provided in this application is described in detail below with reference to the accompanying drawings.

[0062] Figure 1 FIG. 1 is a flow chart of an autonomous driving domain management method according to an embodiment of the present disclosure. Figure 1 The embodiment shown is executed by a web server, and the autonomous driving domain management system is deployed on the web server. The autonomous driving domain management method includes:

[0063] Step 101, obtaining an operation request of a first web page to a first rack in an autonomous driving domain and a usage time of the first rack, wherein the autonomous driving domain includes at least two racks.

[0064] In this embodiment, the web server provides autonomous driving domain management. The first web page is a browser, or a client, preferably a browser, which is used to provide users with services for autonomous driving domain management provided by the web server. The first test bench is an FSD test bench. The FSD test bench refers to a device used to test an autonomous driving system. It is a device that simulates a vehicle driving environment and can simulate various complex road conditions, such as curves, ramps, intersections, etc. The FSD test bench can help developers better understand the performance and limitations of the autonomous driving system and make necessary improvements. The autonomous driving domain includes at least two test benches. After receiving the operation request from the first web page, the web server records the user of the first web page, as well as the FSD test bench specified by the user and the duration of use.

[0065] Step 102, starting a countdown according to the usage time, allocating usage rights of the first rack to the first web page terminal, and the first web page terminal operates the first rack within the usage time.

[0066] In this embodiment, according to the FSD stand and usage time specified by the user, the web server immediately starts the usage time countdown and allocates the usage rights of the first stand to the user of the first web page. The rights ensure that the user of the first web page can operate the FSD stand within the usage time.

[0067] Step 103: When the usage time countdown ends or an end instruction is received, the usage right of the first rack is released.

[0068] In this embodiment, when the usage time countdown ends or an end instruction is received from the user of the first web page, the web server releases the user's permission to use the FSD stand. At this time, the user of the first web page cannot use the FSD stand, and the permission to use can be allocated to users of other web pages.

[0069] Figure 2 This is a flow chart of a rack sharing in an autonomous driving domain according to an embodiment of the present disclosure. In this embodiment, the user rents equipment on the first web page and sets the rental duration and remarks. After the web server (autonomous driving API Server) receives the operation request for the first rack in the autonomous driving domain and the usage duration of the first rack from the first web page, the rental countdown starts immediately. At the same time, the rental message queue (Message Queue, MQ) is sent to update the device information, that is, to update the device information that is not currently occupied and available for rent. The end time of the equipment rental is recorded in the database DB. When the countdown for the rental time ends, the automatic release service of the web server is activated, the message queue receives the new rental MQ message, and at the same time, the use rights of the first rack equipment are released regularly, and the information of the released equipment is updated in the database DB.

[0070] Figure 3 This is a schematic diagram of a platform rental in an autonomous driving domain in an embodiment of the present disclosure. In this embodiment, a user applies to a web server for equipment rental on a first web page, and needs to specify the equipment to be rented and the rental duration, and add a note to explain the purpose of the rental. By clicking the confirmation button, the message queue for the rental equipment can be submitted.

[0071] In summary, according to the autonomous driving domain management method proposed in the present invention, the sharing of test benches is realized, which facilitates multiple users to apply for the use of the first test bench, and improves the resource utilization and ease of use of the test bench.

[0072] Figure 4 This is a flowchart of an autonomous driving domain management method according to an embodiment of the present disclosure. Figure 4 Yes Figure 1 Further explanation, based on Figure 4 The embodiment shown comprises the following steps:

[0073] Step 401, establishing a connection with a proxy terminal server through a web socket security protocol according to a preset network address and a preset port number.

[0074] In this embodiment, the proxy terminal server is a proxy server for transmitting instructions and feedback of results between the web server and the FSD stand. The preset network address is the Internet Protocol address (IP) of the proxy terminal server, and the preset port number is the communication port number reserved by the proxy terminal server for the web terminal server. The web socket security protocol is a security certificate for the communication between the web server and the proxy terminal server. The web server establishes a connection with the proxy terminal server through the web socket (WSS) protocol according to the IP address and port of the proxy terminal server. Send a login instruction to the proxy terminal server for login.

[0075] Step 402: Conducting a session interaction with the first rack through the proxy terminal server according to the secure shell protocol.

[0076] In this embodiment, the proxy terminal server establishes a session with the FSD rack using a contextual session mode through the Secure Shell (SSH) protocol, and the session can return the output result to the web server, which is then sent by the web server to the first web end with the current permission of the first rack user. Thus, the output result of the FSD rack is displayed on the first web end. Remote control of the first rack by the first web end is realized.

[0077] Figure 5 This is a schematic diagram of establishing a session interaction between a first web page and an FSD stand in this embodiment. In this implementation, after the user (first web page) rents a device to log in to the autonomous driving laboratory Web (web page server), it obtains the address of the Terminal Server (terminal server) from the autonomous driving laboratory Api Server, and the Api Server returns the IP address of the proxy terminal server Terminal. The web page server uses the IP address to establish a long connection with the proxy terminal server Agent Terminal Service using the WSS method. The web page server sends an SSH instruction to the proxy terminal server Agent TerminalService, and the proxy terminal server sends the SSH instruction to the FSD for execution, and receives the execution result of the SSH command in the FSD, and the proxy terminal server sends the execution result to the web page server.

[0078] Figure 6This is a schematic diagram of a session interaction established between a first web page and an FSD bench in this embodiment. In this embodiment, user 1 has logged into the intelligent driving laboratory and successfully connected to the FSD bench using the connect button through the IP address and port number, user name and password in the connection information. Below the connect button and the close button is a session interaction window, in which commands can be entered and executed in the connected FSD bench.

[0079] Figure 7 The figure is a schematic diagram of a network link between a web server and an FSD rack in this embodiment. In this embodiment, the web server initiates a connection request to the web server PC with an IP of 172.31.60.XXX through the laboratory network access port. The connection request is transmitted to the switch through the network cable. The switch is set to Trunk mode to ignore the VLAN isolation of VLAN60 used by the FSD rack network. The switch is simultaneously connected to all FSD racks in the laboratory. According to the IP address and port number of the ORIN1 chip or ORIN2 chip in the dual-core of the specified FSD rack device, the FSD rack can be directly selected through the web server.

[0080] Figure 8 This is a schematic diagram of a management page for selecting an FSD rack on the first web page of this embodiment. In this embodiment, according to the ID of the FSD rack, the device names of all FSD racks, and the IP addresses and version information of ORIN1 and ORIN2 are listed. The FSD1 rack is selected as the experimental equipment, the user is user 1, and the current usage rights are owned by user 1. The FSD1 rack device can be released, renewed, and details can be viewed. For the FSD2 rack and FSD3 rack, they can be occupied.

[0081] For the session between the proxy terminal server and the first rack, the specific implementation process is as follows.

[0082] Fig. 9 The present invention is a flowchart of an embodiment of the present invention, which uses a proxy terminal server to perform session interaction with a first rack according to a secure shell protocol. Fig. 9 Yes Figure 4 Step 402 is further described based on Fig. 9 The embodiment shown comprises the following steps:

[0083] Step 901, sending a first instruction to a first rack through a proxy terminal server according to a secure shell protocol.

[0084] In this embodiment, the user issues an operation instruction for the FSD rack on the first web page, and after the web page server receives the instruction, it sends it to the proxy terminal server through SSH. The proxy terminal server sends the first instruction to the FSD rack.

[0085] Step 902: receiving, through the proxy terminal server, a first result after the first rack executes the first instruction according to the secure shell protocol.

[0086] In this embodiment, after the first instruction is executed on the FSD test bench, the first result is obtained and sent to the proxy terminal server, the proxy terminal server sends the first result to the web server, and the web server sends the first result to the first web terminal, completing the remote control of the first test bench by the first web terminal. Since the firmware of the FSD test bench needs to be frequently upgraded and tested, the upgrade of the FSD test bench by the autonomous driving domain needs to be convenient and easy to use.

[0087] Fig.10 This is a flowchart of an autonomous driving domain management method according to an embodiment of the present disclosure. Fig.10 Yes Figure 4 Further specific description, based on Fig.10 The embodiment shown comprises the following steps:

[0088] Step 1001, receiving an upgrade instruction for a first rack from a first web page.

[0089] In this embodiment, the user issues a firmware upgrade instruction for the first rack device on the first web page, and the web server receives the upgrade instruction for the first rack from the first web page.

[0090] Step 1002, in response to the upgrade instruction, obtain the firmware version information of the first rack from the version library through the autonomous driving application program interface service.

[0091] In this embodiment, the version library stores multiple versions of the autonomous driving system firmware. After the web server receives the upgrade command issued by the user on the first web page, it determines the firmware suitable for the current FSD bench upgrade from the version library through the autonomous driving application program interface (API) service. Among them, the autonomous driving API service is an interface service provided by the autonomous driving laboratory to realize various functions of autonomous driving testing, including firmware upgrade service.

[0092] Step 1003: Send an upgrade instruction to the proxy upgrade server according to the firmware version information and the device number of the first rack.

[0093] In this embodiment, the proxy upgrade server is a server that controls the first rack to perform firmware upgrade. The web server sends an upgrade instruction to the proxy upgrade server according to the determined firmware version number to be upgraded and the device number of the first rack.

[0094] Step 1004: write a first firmware upgrade package into the first rack through the proxy upgrade server, where the first firmware upgrade package is obtained from the version library by the proxy upgrade server.

[0095] In this embodiment, the first firmware upgrade package is a firmware upgrade package applicable to the first rack downloaded from the version library after the upgrade instruction is executed in the proxy upgrade server. The proxy upgrade server executes the upgrade script to flash the first firmware upgrade package to the first rack.

[0096] Step 1005: restart the first rack and reset the network address of the first rack to a preset network address.

[0097] In this embodiment, after the first firmware upgrade package of the first rack is flashed, the first rack is restarted through the upgrade script to reset the IP address of the first rack to the preset network address, ensuring that the IP address remains unchanged after the system update for subsequent use.

[0098] Through this embodiment, the user can easily complete the upgrade of the FSD stand firmware on the first web page without having to complete the upgrade through a large amount of manual intervention through card flashing or wire flashing, which greatly reduces the complexity of the firmware upgrade and reduces the upgrade cost.

[0099] Fig.11 The figure is a schematic diagram of the firmware upgrade process in an autonomous driving domain of the present embodiment. In the present embodiment, a user triggers an upgrade request to a web server on a first web page, and the web server obtains the firmware version information of the first rack from the version library through the autonomous driving application program interface service. In response to the upgrade instruction, the firmware version information of the first rack is obtained from the version library through the autonomous driving application program interface service. According to the firmware version information and the device number of the first rack, an upgrade instruction is sent to the agent upgrade service. The agent upgrade server executes the FSD upgrade script, downloads the determined firmware upgrade package in the version library, and then starts to flash the firmware upgrade package to the FSD rack. A quick upgrade of the FSD rack firmware in the autonomous driving domain is achieved.

[0100] Fig.12Schematic diagram of a firmware upgrade package list in a firmware library of an autonomous driving domain in this embodiment. In this embodiment, different firmware upgrade packages with different version numbers are listed in the firmware library, and each firmware upgrade package contains the microcontroller unit MCU1 and system on chip SOC1 of ORIN1, the microcontroller unit MCU2 and system on chip SOC2 of ORIN2, and the upgrade packages of FC and FD. Through the upgrade button, the current firmware upgrade package can be downloaded to the FSD bench.

[0101] Fig.13 This is a flowchart of an autonomous driving domain management method according to an embodiment of the present disclosure. Fig.13 Yes Figure 1 Specific description, based on Fig.13 The embodiment shown comprises the following steps:

[0102] Step 1301, enable the port forwarding function of the first rack.

[0103] Enable port forwarding on the first rack.

[0104] Step 1302, remotely connect to the first rack through the secure shell protocol, wherein the first port of the first rack is connected to the second port of the proxy forwarding server, and the second port of the proxy forwarding server is connected to the web server.

[0105] In this embodiment, the web server is remotely connected to the first rack via SSH, the web server is connected to the second port of the proxy forwarding server, and the first port of the first rack is connected to the second port of the proxy forwarding server. Preferably, the first port of the first rack is port 22. Port 22 is mounted on the second port of the proxy forwarding server. The remote connection between the web server and the FSD rack is realized, which greatly facilitates the user's control of the FSD rack.

[0106] Fig.14 The figure is a flowchart of a remote connection of an autonomous driving domain in the present embodiment. In the present embodiment, the user turns on the port forwarding function of the first rack through the Proxy page, mounts the first port of the FSD rack to the X port of the proxy forwarding server Agent Proxy, and the proxy forwarding server Agent Proxy is connected to the first web page of the user through SSH to realize the remote connection between the user's first web page and the FSD rack through port forwarding. The user obtains the access right of the FSD rack by connecting to the proxy forwarding server through SSH through the web server connected to the first web page, and realizes the remote connection to the FSD rack. When the FSD rack needs to be turned on or off, it can be quickly turned on and off through the network relay.

[0107] Fig.15This is a flowchart of an autonomous driving domain management method according to an embodiment of the present disclosure. Fig.15 Yes Figure 1 Specific description, based on Fig.15 The embodiment shown comprises the following steps:

[0108] Step 1501, obtain a mapping table from a database of a web server, where the mapping table includes a mapping relationship between one or more test benches in an autonomous driving domain and a network relay.

[0109] In this embodiment, the mapping table is a form or table in the database, which stores the mapping relationship between one or more FSD test benches and network relays in the autonomous driving domain. By controlling the network relay, the power switch of the FSD test bench corresponding to different ports of the network relay can be controlled.

[0110] Step 1502, determining the first network relay corresponding to the first rack from the mapping table.

[0111] In this embodiment, the first network relay is a relay for controlling the power supply of the first rack. According to the mapping table, the port of the first network relay corresponding to the current first rack can be determined.

[0112] Step 1503, closing or opening the first rack through the first network relay.

[0113] In this embodiment, the first rack can be turned off or on by shutting down the port of the first network relay corresponding to the first rack. This prevents the cumbersome operation of manually plugging and unplugging the power supply to restart the FSD rack after the FSD rack is down, thereby realizing quick and convenient control of the FSD rack.

[0114] Fig.16 The figure is a schematic diagram of an autonomous driving domain management method of an embodiment of the present disclosure. In this embodiment, through multiple sets of automobile FSD hardware, a set of two-layer switches supporting trunk mode, a personal computer (PC), a set of FSD management platform software, the software includes an autonomous driving laboratory Web platform, an autonomous driving laboratory ServerApi service, an autonomous driving laboratory equipment release service, an agent forwarding server Agent proxy server, an agent terminal server Agent Web terminal server, an agent upgrade server Agent FSD upgrade server, and a set of network relays, the autonomous driving domain management system can be formed.

[0115] Users rent equipment through the PC access control page. First, they log in to the autonomous driving laboratory Web (web server). The web server is linked to the autonomous driving laboratory Server API and sends the equipment rental message queue MQ. When the equipment reaches the release time or the release is triggered, the autonomous driving equipment release server subscribes to the equipment rental message from the rental message queue MQ to release the equipment in time. The office network switch is connected to the autonomous driving equipment release server and the autonomous driving laboratory API server, and is also connected to the agent forwarding server Agent Proxy Server, the agent terminal server AgentWeb Terminal Server, the agent upgrade server Agent FSD upgrade Server and the FSD online agent PC. The agent forwarding server, the agent terminal server, the agent upgrade server and the FSD online agent PC all have dual network cards, namely network card 1 and network card 2. Network card 1 is connected to the office network switch, and network card 2 is connected to the gigabit switch of the autonomous driving laboratory. The network of the laboratory is set as FSD domain VLAN60. The gigabit switch of the autonomous driving laboratory is connected to 4 sets of FSD racks. Each FSD rack has two IPs. Each FSD rack is independently connected to the port of the network relay, and the network relay is connected to the gigabit switch. The Gigabit switch is connected to a Network Attached Storage (NAS). Each FSD rack deploys firmware via a Docker container.

[0116] In this embodiment, the operation request of the first web page end to the first rack of the autonomous driving domain and the usage time of the first rack are obtained. The autonomous driving domain includes at least two racks, so that the user applies to the web server that manages the autonomous driving domain to use the rack through the web page end; the countdown starts according to the usage time, and the use right of the first rack is allocated to the first web page end. The first web page end operates the first rack within the usage time, and the user obtains the use right of the first rack on the web page end within the usage time, and obtains the rack permission allocation; when the usage time countdown ends or an end instruction is received, the use right of the first rack is released. After the use ends, the use right of the first rack is automatically released, which facilitates other users to apply to use the first rack and improves the resource utilization and ease of use of the rack.

[0117] Corresponding to the methods provided in the above-mentioned embodiments, the present disclosure also provides an autonomous driving domain management device. Since the device provided in the embodiments of the present disclosure corresponds to the methods provided in the above-mentioned embodiments, the implementation method of the method is also applicable to the device provided in this embodiment and will not be described in detail in this embodiment.

[0118] Fig.17FIG. 1 is a schematic diagram of the structure of an autonomous driving domain management device 1700 according to an embodiment of the present disclosure. The device is applied to a web server, such as Fig.17 As shown, the autonomous driving domain management device includes:

[0119] An acquisition module 1710 is used to acquire an operation request from a first web page to a first rack in an autonomous driving domain and a usage time of the first rack, where the autonomous driving domain includes at least two racks;

[0120] The permission allocation module 1720 is used to allocate the permission to use the first rack to the first web page terminal according to the countdown of the usage time, and the first web page terminal operates the first rack within the usage time;

[0121] The permission releasing module 1730 is used to release the permission to use the first rack when the usage time countdown ends or an end instruction is received.

[0122] In some embodiments, the autonomous driving domain management device is further used to:

[0123] Establishing a connection with the proxy terminal server through the web socket security protocol according to the preset network address and the preset port number;

[0124] Through the proxy terminal server, a session interaction is performed with the first rack according to the secure shell protocol.

[0125] In some implementations, performing session interaction with the first rack according to the secure shell protocol through the proxy terminal server includes at least one of the following:

[0126] sending the first instruction to the first rack via the proxy terminal server according to the secure shell protocol;

[0127] The first result after the first rack executes the first instruction is received according to the secure shell protocol through the proxy terminal server.

[0128] In some embodiments, the autonomous driving domain management device is further used to:

[0129] Receiving an upgrade instruction from the first web page to the first rack;

[0130] In response to the upgrade instruction, obtaining firmware version information of the first rack from a version library through an application program interface service of the autonomous driving;

[0131] According to the firmware version information and the device number of the first rack, an upgrade instruction is sent to the proxy upgrade server;

[0132] Writing a first firmware upgrade package into the first rack through the proxy upgrade server, the first firmware upgrade package being obtained from the version library by the proxy upgrade server;

[0133] Restart the first rack and reset the network address of the first rack to the preset network address.

[0134] In some embodiments, the autonomous driving domain management device is further used to:

[0135] Enable the port forwarding function of the first rack;

[0136] A remote connection is made to the first rack via a secure shell protocol, wherein a first port of the first rack is connected to a second port of a proxy forwarding server, and a second port of the proxy forwarding server is connected to a web server.

[0137] In some embodiments, the autonomous driving domain management device is further used to:

[0138] Obtaining a mapping table from a database of the web server, the mapping table including a mapping relationship between one or more test benches in the autonomous driving domain and a network relay;

[0139] Determine the first network relay corresponding to the first rack from the mapping table;

[0140] Through the first network relay, the first rack is closed or opened.

[0141] In summary, through the autonomous driving domain management device, the operation request of the first web page terminal to the first rack of the autonomous driving domain and the usage time of the first rack are obtained. The autonomous driving domain includes at least two racks, so that the user can apply to the web server that manages the autonomous driving domain for the use of the rack through the web page terminal; according to the usage time, the countdown starts, and the use rights of the first rack are allocated to the first web page terminal. The first web page terminal operates the first rack within the usage time, and the user obtains the use rights of the first rack on the web page terminal within the usage time, and obtains the rack permission allocation; when the usage time countdown ends or the end instruction is received, the use rights of the first rack are released. After the use ends, the use rights of the first rack are automatically released, which facilitates other users to apply for the use of the first rack and improves the resource utilization and ease of use of the rack. This device solves the problem of difficulty in sharing the rack and improves the resource utilization and ease of use of the rack.

[0142] In the embodiments provided in the present application, the methods and devices provided in the embodiments of the present application are introduced. In order to implement the functions in the methods provided in the embodiments of the present application, the electronic device may include a hardware structure and a software module, and implement the functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. A function of the functions may be executed in the form of a hardware structure, a software module, or a hardware structure plus a software module.

[0143] Fig.18It is a block diagram of an electronic device 1800 for implementing the above-mentioned autonomous driving domain management method according to an exemplary embodiment.

[0144] For example, the electronic device 1800 may be a mobile phone, a computer, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0145] Reference Fig.18 , the electronic device 1800 may include one or more of the following components: a processing component 1802 , a memory 1804 , a power component 1806 , a multimedia component 1808 , an audio component 1810 , an input / output (I / O) interface 1812 , a sensor component 1814 , and a communication component 1816 .

[0146] The processing component 1802 generally controls the overall operation of the electronic device 1800, such as operations associated with display, phone calls, data communications, camera operations, and recording operations. The processing component 1802 may include one or more processors 1820 to execute instructions to complete all or part of the steps of the above-mentioned method. In addition, the processing component 1802 may include one or more modules to facilitate the interaction between the processing component 1802 and other components. For example, the processing component 1802 may include a multimedia module to facilitate the interaction between the multimedia component 1808 and the processing component 1802.

[0147] The memory 1804 is configured to store various types of data to support operations on the electronic device 600. Examples of such data include instructions for any application or method operating on the electronic device 1800, contact data, phone book data, messages, pictures, videos, etc. The memory 1804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk or optical disk.

[0148] The power supply component 1806 provides power to the various components of the electronic device 1800. The power supply component 1806 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to the electronic device 1800.

[0149] The multimedia component 1808 includes a screen that provides an output interface between the electronic device 1800 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 1808 includes a front camera and / or a rear camera. When the electronic device 1800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.

[0150] The audio component 1810 is configured to output and / or input audio signals. For example, the audio component 1810 includes a microphone (MIC), and when the electronic device 1800 is in an operation mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 1804 or sent via the communication component 1816. In some embodiments, the audio component 1810 also includes a speaker for outputting audio signals.

[0151] I / O interface 1812 provides an interface between processing component 1802 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.

[0152] The sensor assembly 1814 includes one or more sensors for providing various aspects of status assessment for the electronic device 1800. For example, the sensor assembly 1814 can detect the open / closed state of the electronic device 1800, the relative positioning of components, such as the display and keypad of the electronic device 1800, and the sensor assembly 1814 can also detect the position change of the electronic device 1800 or a component of the electronic device 1800, the presence or absence of user contact with the electronic device 1800, the orientation or acceleration / deceleration of the electronic device 1800, and the temperature change of the electronic device 1800. The sensor assembly 1814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 1814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1814 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0153] The communication component 1816 is configured to facilitate wired or wireless communication between the electronic device 1800 and other devices. The electronic device 1800 can access a wireless network based on a communication standard, such as WiFi, 2G or 3G, 4G LTE, 5G NR (NewRadio) or a combination thereof. In an exemplary embodiment, the communication component 1816 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 1816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.

[0154] In an exemplary embodiment, the electronic device A00 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to perform the above method.

[0155] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1804 including instructions, and the instructions can be executed by a processor 1820 of an electronic device 1800 to perform the above method. For example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.

[0156] An embodiment of the present disclosure also proposes a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute the autonomous driving domain management method described in the above embodiments of the present disclosure.

[0157] An embodiment of the present disclosure further proposes a computer program product, including a computer program, which executes the autonomous driving domain management method described in the above embodiment of the present disclosure when a processor is used to execute the computer program.

[0158] Fig.19 It is a structural schematic diagram of a chip 1900 for implementing the above-mentioned autonomous driving domain management method according to an exemplary embodiment.

[0159] Reference Fig.19, chip 1900 includes at least one communication interface 1901 and a processor 1902; the communication interface 1901 is used to receive signals input to the chip 1900 or signals output from the chip 1900, and the processor 1902 communicates with the communication interface 1901 and implements the autonomous driving domain management method described in the above embodiment through logic circuits or execution code instructions.

[0160] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0161] In the description of this specification, the description with reference to the terms "one embodiment", "some embodiments", "illustrative embodiments", "examples", "specific examples" or "some examples" etc. means that the specific features, structures, materials or characteristics described in conjunction with the embodiments or examples are included in at least one embodiment or example of the present disclosure. In this specification, the schematic representations of the above terms do not necessarily refer to the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described may be combined in any one or more embodiments or examples in a suitable manner.

[0162] Any process or method description in a flowchart or otherwise described herein may be understood to represent a module, segment or portion of code that includes one or more executable instructions for implementing the steps of a specific logical function or process, and the scope of the preferred embodiments of the present disclosure includes alternative implementations in which functions may not be performed in the order shown or discussed, including performing functions in a substantially simultaneous manner or in the reverse order depending on the functions involved, which should be understood by those skilled in the art to which the embodiments of the present disclosure belong.

[0163] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as an ordered list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by an instruction execution system, device or apparatus (such as a computer-based system, a system including a processing module, or other system that can fetch instructions from an instruction execution system, device or apparatus and execute instructions), or in combination with these instruction execution systems, devices or apparatuses. For the purposes of this specification, "computer-readable medium" can be any device that can contain, store, communicate, propagate or transmit a program for use by an instruction execution system, device or apparatus, or in combination with these instruction execution systems, devices or apparatuses. More specific examples of computer-readable media (a non-exhaustive list) include the following: an electrical connection with one or more wires (control method), a portable computer disk box (magnetic device), a random access memory (RAM), a read-only memory (ROM), an erasable and programmable read-only memory (EPROM or flash memory), a fiber optic device, and a portable compact disk read-only memory (CDROM). In addition, the computer-readable medium may even be paper or other suitable medium on which the program is printed, since the program may be obtained electronically, for example, by optically scanning the paper or other medium and then editing, interpreting or otherwise processing in a suitable manner if necessary, and then stored in a computer memory.

[0164] It should be understood that the various parts of the embodiments of the present disclosure can be implemented by hardware, software, firmware or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, it can be implemented by any one of the following technologies known in the art or their combination: a discrete logic circuit having a logic gate circuit for implementing a logic function for a data signal, a dedicated integrated circuit having a suitable combination of logic gate circuits, a programmable gate array (PGA), a field programmable gate array (FPGA), etc.

[0165] A person skilled in the art may understand that all or part of the steps in the method for implementing the above-mentioned embodiment may be completed by instructing related hardware through a program, and the program may be stored in a computer-readable storage medium, which, when executed, includes one or a combination of the steps of the method embodiment.

[0166] In addition, each functional unit in each embodiment of the present disclosure may be integrated into a processing module, or each unit may exist physically separately, or two or more units may be integrated into one module. The above-mentioned integrated module may be implemented in the form of hardware or in the form of a software functional module. If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it may also be stored in a computer-readable storage medium. The above-mentioned storage medium may be a read-only memory, a disk or an optical disk, etc.

[0167] Although the embodiments of the present disclosure have been shown and described above, it is to be understood that the above embodiments are exemplary and are not to be construed as limitations of the present disclosure. A person skilled in the art may make changes, modifications, substitutions and variations to the above embodiments within the scope of the present disclosure.

Claims

1. A method for managing an autonomous driving domain, characterized in that: The method is executed by a web server, and the autonomous driving domain management system is deployed on the web server. The method includes: Obtaining an operation request from a first web page to a first rack in an autonomous driving domain and a usage time of the first rack; Starting a countdown according to the usage time, allocating the use right of the first rack to the first web page end, and the first web page end operates the first rack within the usage time; When the usage time countdown ends or an end instruction is received, the usage right of the first rack is released.

2. The method according to claim 1, characterized in that The method further comprises: Establishing a connection with the proxy terminal server through the web socket security protocol according to the preset network address and the preset port number; Through the proxy terminal server, a session interaction is performed with the first stand according to a secure shell protocol.

3. The method according to claim 2, characterized in that The performing session interaction with the first rack through the proxy terminal server according to the secure shell protocol comprises at least one of the following: sending a first instruction to the first rack according to the secure shell protocol through the proxy terminal server; The first result after the first gantry executes the first instruction is received through the proxy terminal server according to the secure shell protocol.

4. The method according to claim 2, characterized in that: The method further comprises: Receiving an upgrade instruction from the first web page to the first rack; In response to the upgrade instruction, obtaining the firmware version information of the first frame from a version library through an autonomous driving application program interface service; Sending the upgrade instruction to the proxy upgrade server according to the firmware version information and the device number of the first rack; Writing a first firmware upgrade package into the first rack through the proxy upgrade server, wherein the first firmware upgrade package is obtained by the proxy upgrade server from the version library; Restart the first rack and reset the network address of the first rack to the preset network address.

5. The method according to claim 1, characterized in that The method further comprises: Enable the port forwarding function of the first rack; A remote connection is established with the first rack via a secure shell protocol, wherein a first port of the first rack is connected to a second port of a proxy forwarding server, and a second port of the proxy forwarding server is connected to the web server.

6. The method according to claim 1, characterized in that The method further comprises: Acquire a mapping table from a database of the web server, wherein the mapping table includes a mapping relationship between one or more test benches in the autonomous driving domain and a network relay; Determine a first network relay corresponding to the first rack from the mapping table; The first rack is closed or opened through the first network relay.

7. An autonomous driving domain management device, characterized in that: Applied to a web server, the device comprises: An acquisition module, configured to acquire an operation request from a first web page to a first rack in an autonomous driving domain and a usage time of the first rack, wherein the autonomous driving domain includes at least two racks; a permission allocation module, configured to start a countdown according to the usage duration, allocate a permission to use the first rack to the first web page end, and the first web page end operates the first rack within the usage duration; The permission releasing module is used to release the permission to use the first rack when the usage time countdown ends or an end instruction is received.

8. An electronic device, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 6.

9. A non-transitory computer-readable storage medium storing computer instructions, characterized in that: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-6.

10. A computer program product, characterized in that The invention comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 6.

11. A chip, characterized in that: It includes at least one processor and a communication interface; the communication interface is used to receive a signal input to the chip or a signal output from the chip, and the processor communicates with the communication interface and implements the method according to any one of claims 1-6 through a logic circuit or executing code instructions.

Images