Roadside equipment communication method and equipment
By developing drivers that support multiple communication standards in the vehicle-road collaboration system, unified access between user equipment and roadside equipment of different manufacturers is achieved, solving the problems of complex configuration and poor scalability of the user side, reducing access overhead and Improves the scalability of the system.
Patent Information
- Application Number
- CN202110790998.X
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-07-13
- Publication Date
- 2024-12-06
- Estimated Expiration
- 2041-07-13
AI Technical Summary
In vehicle-road collaboration system, when the user side needs to interact with roadside equipment provided by different manufacturers, it needs to make multiple configurations, resulting in poor scalability and large overhead, and lack of unified communication standards.
By developing multiple drivers, each program supports a unified first communication standard and a second communication standard of a specific manufacturer, the management and control equipment acquires and converts data packets, and realizes unified access between user equipment and roadside equipment of different manufacturers.
It reduces the overhead of accessing roadside equipment by the user terminal and realizes high-scaling access to roadside equipment. The user terminal can support the addition of new manufacturer equipment without modifying the communication standard. When adding equipment types, the communication standard only needs to be adapted to once.
Smart Images

Figure CN115623088B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the technical field of Internet of Things, and in particular to a roadside equipment communication method and equipment. Background Art
[0002] In the field of intelligent transportation, the vehicle-road cooperative system has been continuously developed. In simple terms, the so-called vehicle-road cooperative system uses advanced wireless communication and Internet technologies to implement all-round dynamic real-time information interaction between vehicles and roads, and on the basis of full-time and space dynamic traffic information collection and integration, it carries out active vehicle safety control and road cooperative management, fully realizes the effective coordination of people, vehicles and roads, ensures traffic safety, and improves traffic efficiency, thus forming a safe, efficient and environmentally friendly road traffic system.
[0003] In the vehicle-road cooperative system, a large number of roadside devices are deployed, such as speed limit signs, fog lights, roadside units (RSUs), lane controllers, etc. These roadside devices are generally provided by different manufacturers. Each equipment manufacturer implements communication protocols, data exchange formats, etc. based on the corresponding international or national standards and according to its own understanding. There is no industry standard.
[0004] In the traditional solution, if the user end (such as relevant traffic departments, certain traffic control applications, etc.) wants to interact with these roadside devices, the user end needs to be configured to correspond to different types of roadside devices provided by different manufacturers to support the communication standards of the roadside devices provided by different manufacturers, so as to be able to exchange information with the corresponding roadside devices. This way of connecting roadside devices to the user end has poor scalability and the user end has high overhead. Summary of the invention
[0005] The embodiments of the present invention provide a roadside equipment communication method and equipment, which can reduce the overhead of user-side access to the roadside equipment and achieve high-scalability access to the roadside equipment.
[0006] In a first aspect, an embodiment of the present invention provides a roadside device communication method, which is applied to a management and control device. The method includes:
[0007] Acquire roadside device identifiers corresponding to each of a plurality of drivers and first communication standard information supported by the plurality of drivers, wherein the plurality of drivers correspond to roadside devices of the same device type provided by a plurality of manufacturers, and one of the drivers further supports a second communication standard information, wherein the second communication standard information is adopted by a roadside device of the device type provided by one of the manufacturers;
[0008] Sending the first communication standard information to user equipment;
[0009] receiving a data packet sent by the user equipment based on the first communication standard information, wherein the data packet includes a target roadside equipment identifier;
[0010] Determining a target driver corresponding to the target roadside device identifier among the multiple drivers;
[0011] The data packet is sent to the target driver so that the target driver converts the data packet based on a second communication standard adopted by the target roadside device, and sends the converted data packet to the target roadside device.
[0012] In a second aspect, an embodiment of the present invention provides a roadside equipment communication device, located in a control device, the device comprising:
[0013] an acquisition module, used for acquiring roadside device identifiers corresponding to each of a plurality of drivers and first communication standard information supported by the plurality of drivers, wherein the plurality of drivers correspond to roadside devices of the same device type provided by a plurality of manufacturers, and one of the drivers further supports a second communication standard information, wherein the second communication standard information is adopted by a roadside device of the device type provided by one of the manufacturers;
[0014] A sending module, configured to send the first communication standard information to a user equipment;
[0015] A receiving module, configured to receive a data packet sent by the user equipment based on the first communication standard information, wherein the data packet includes a target roadside equipment identifier;
[0016] A determination module, configured to determine a target driver corresponding to the target roadside device identifier from among the multiple drivers;
[0017] The sending module is further used to send the data packet to the target driver, so that the target driver converts the data packet based on the second communication standard adopted by the target roadside device, and sends the converted data packet to the target roadside device.
[0018] In a third aspect, an embodiment of the present invention provides a management and control device, comprising: a memory, a processor, and a communication interface; wherein, the memory stores executable code, and when the executable code is executed by the processor, the processor can at least implement the roadside equipment communication method described in the first aspect.
[0019] In a fourth aspect, an embodiment of the present invention provides a non-temporary machine-readable storage medium having executable code stored thereon. When the executable code is executed by a processor of a management and control device, the processor can at least implement the roadside equipment communication method as described in the first aspect.
[0020] In a fifth aspect, an embodiment of the present invention provides a roadside equipment communication method, which is applied to a user equipment, and the method includes:
[0021] receiving a first communication standard supported by multiple drivers sent by a control device, wherein the multiple drivers correspond to roadside devices of the same device type provided by multiple manufacturers, and one of the drivers further supports a second communication standard information, wherein the second communication standard information is adopted by a roadside device of the device type provided by one of the manufacturers; the control device stores roadside device identifiers corresponding to each of the multiple drivers;
[0022] A data packet is sent to the control device based on the first communication standard information, the data packet including a target roadside device identifier, so that the control device determines a target driver corresponding to the target roadside device identifier from among the multiple drivers, sends the data packet to the target driver so that the target driver converts the data packet based on a second communication standard adopted by the target roadside device, and sends the converted data packet to the target roadside device.
[0023] In a sixth aspect, an embodiment of the present invention provides a roadside equipment communication device, located in a user equipment, the device comprising:
[0024] A receiving module, used for receiving a first communication standard supported by multiple drivers sent by a control device, wherein the multiple drivers correspond to roadside devices of the same device type provided by multiple manufacturers, and one of the drivers further supports a second communication standard information, wherein the second communication standard information is adopted by a roadside device of the device type provided by one of the manufacturers; the control device stores roadside device identifiers corresponding to each of the multiple drivers;
[0025] A sending module is used to send a data packet to the control device based on the first communication standard information, the data packet including a target roadside device identifier, so that the control device determines a target driver corresponding to the target roadside device identifier from the multiple drivers, sends the data packet to the target driver so that the target driver converts the data packet based on a second communication standard adopted by the target roadside device, and sends the converted data packet to the target roadside device.
[0026] In the seventh aspect, an embodiment of the present invention provides a user device, comprising: a memory, a processor, and a communication interface; wherein, an executable code is stored on the memory, and when the executable code is executed by the processor, the processor can at least implement the roadside equipment communication method as described in the fifth aspect.
[0027] In an eighth aspect, an embodiment of the present invention provides a non-temporary machine-readable storage medium having executable code stored thereon. When the executable code is executed by a processor of a user device, the processor can at least implement the roadside equipment communication method as described in the fifth aspect.
[0028] In a ninth aspect, an embodiment of the present invention provides a roadside device communication method, which is applied to a target driver, and the method includes:
[0029] Sending a target roadside device identifier corresponding to the target driver to a control device; the control device stores roadside device identifiers corresponding to multiple drivers, the target driver is one of the multiple drivers, and the multiple drivers correspond to roadside devices of the same device type provided by multiple manufacturers; the multiple drivers all support first communication standard information, one of the drivers also supports second communication standard information, and the second communication standard information is adopted by a roadside device of the device type provided by one of the manufacturers;
[0030] receiving a data packet sent by a control device, the data packet being sent by a user device according to the first communication standard information sent by the control device, the data packet including the target roadside device identifier, the control device determining the target driver corresponding to the target roadside device identifier from the multiple drivers, and sending the data packet to the target driver;
[0031] The data packet is converted based on a second communication standard adopted by the target roadside device, and the converted data packet is sent to the target roadside device.
[0032] In a tenth aspect, an embodiment of the present invention provides a roadside equipment communication device, located in a driving device, the device comprising:
[0033] A sending module, used for sending a target roadside device identifier corresponding to the target driver to a control device; the control device stores roadside device identifiers corresponding to multiple drivers, the target driver is one of the multiple drivers, and the multiple drivers correspond to roadside devices of the same device type provided by multiple manufacturers; the multiple drivers all support first communication standard information, one of the drivers also supports a second communication standard information, and the second communication standard information is adopted by a roadside device of the device type provided by one of the manufacturers;
[0034] a receiving module, configured to receive a data packet sent by a control device, wherein the data packet is sent by a user device according to the first communication standard information sent by the control device, and the data packet includes the target roadside device identifier; the control device determines the target driver corresponding to the target roadside device identifier from the multiple drivers, and sends the data packet to the target driver;
[0035] The sending module is further used to convert the data packet based on a second communication standard adopted by the target roadside device, and send the converted data packet to the target roadside device.
[0036] In the eleventh aspect, an embodiment of the present invention provides a driving device, comprising: a memory, a processor, and a communication interface; wherein a target driver is stored on the memory, and when the target driver is executed by the processor, the processor can at least implement the roadside equipment communication method as described in the ninth aspect.
[0037] In the twelfth aspect, an embodiment of the present invention provides a non-temporary machine-readable storage medium, on which a target driver is stored. When the target driver is executed by a processor of a driving device, the processor can at least implement the roadside equipment communication method as described in the ninth aspect.
[0038] In a thirteenth aspect, an embodiment of the present invention provides a roadside device driving apparatus, comprising a plurality of drivers, wherein the plurality of drivers all support first communication standard information, the plurality of drivers correspond to roadside devices of the same device type provided by a plurality of manufacturers, wherein one driver further supports a second communication standard information, the second communication standard information being adopted by a roadside device of the device type provided by one of the manufacturers;
[0039] A target driver among the multiple drivers is used to send a target roadside device identifier corresponding to the target driver to a control device; the control device stores roadside device identifiers corresponding to multiple drivers, and the target driver is one of the multiple drivers; a data packet sent by the control device is received, the data packet is sent by a user device according to the first communication standard information sent by the control device, the data packet includes the target roadside device identifier, the control device determines the target driver corresponding to the target roadside device identifier from the multiple drivers, and sends the data packet to the target driver; the data packet is converted based on a second communication standard adopted by the target roadside device, and the converted data packet is sent to the target roadside device.
[0040] In the solution provided by the embodiment of the present invention, the process of roadside equipment accessing user equipment is controlled by the control device in the cloud. For roadside equipment of the same device type provided by multiple manufacturers, multiple corresponding driver programs will be developed in advance. For example, if a certain type of roadside equipment is provided by five manufacturers in total, then five driver programs corresponding to this type of roadside equipment provided by these five manufacturers will be developed in advance, and one driver program corresponds to this type of roadside equipment provided by one of the manufacturers. In the process of generating these five driver programs, these five driver programs are all made to support the preset first communication standard information. In addition, one of the driver programs also supports the second communication standard information adopted by this type of roadside equipment provided by a corresponding manufacturer.
[0041] Based on the development of the above-mentioned multiple drivers, the management and control device can store the roadside device identification corresponding to each driver (used to indicate which type of roadside device is provided by which manufacturer), and also store the first communication standard information supported by the above-mentioned multiple drivers. The management and control device notifies the user device that it can use the unified first communication standard information when it needs to communicate with the roadside device of the above-mentioned device type. In this way, when the user device needs to communicate with the roadside device of this device type, it sends a data packet to the management and control device based on the first communication standard information, and the data packet includes the target roadside device identification. The management and control device determines the target driver corresponding to the target roadside device identification, sends the data packet to the target driver, and the target driver converts the data packet based on the second communication standard adopted by the target roadside device, and sends the converted data packet to the target roadside device.
[0042] It can be seen that in the above scheme, for the same type of roadside equipment provided by different manufacturers, drivers corresponding to different manufacturers of this type will be pre-generated. These drivers corresponding to the same device type provide a unified communication standard for the user end, and each is compatible with the communication standard adopted by the roadside equipment provided by the corresponding manufacturer. Based on this, when new roadside equipment provided by certain manufacturers is added to a certain device type, the user end does not need to modify the communication standard, and when a new device type is added, the user end only needs to adapt once to the unified communication standard corresponding to this device type. This reduces the overhead of the user end accessing the roadside device and realizes the access to the roadside device in a highly scalable manner. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0044] Figure 1 A schematic diagram of a roadside equipment communication system provided by an embodiment of the present invention;
[0045] Figure 2 A schematic diagram of a scenario of adding a new roadside device provided in an embodiment of the present invention;
[0046] Figure 3 An interactive flow chart of a roadside equipment communication method provided by an embodiment of the present invention;
[0047] Figure 4 A schematic diagram of another roadside equipment communication system provided by an embodiment of the present invention;
[0048] Figure 5 A schematic diagram of the structure of a roadside equipment communication device provided by an embodiment of the present invention;
[0049] Figure 6 For Figure 5 A schematic diagram of the structure of a control device corresponding to the roadside equipment communication device provided in the illustrated embodiment;
[0050] Figure 7 A schematic diagram of the structure of a roadside equipment communication device provided by an embodiment of the present invention;
[0051] Figure 8 For Figure 7 A schematic diagram of the structure of a user equipment corresponding to the roadside equipment communication device provided in the illustrated embodiment;
[0052] Fig. 9 A schematic diagram of the structure of a roadside equipment communication device provided by an embodiment of the present invention;
[0053] Fig.10 For Fig. 9 A schematic diagram of the structure of a driving device corresponding to the roadside equipment communication device provided in the illustrated embodiment. DETAILED DESCRIPTION
[0054] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0055] In addition, the step sequence in the following method embodiments is only an example and not a strict limitation.
[0056] Figure 1A schematic diagram of a roadside equipment communication system provided by an embodiment of the present invention is shown in FIG. Figure 1 As shown in , the system includes: control equipment, user equipment, driver program, and roadside equipment.
[0057] The control device may be a control center located in the cloud, and the roadside device is connected to the user device through the control device. In fact, the control device may be an independent physical machine, a virtual machine, or a cluster composed of multiple physical machines or virtual machines.
[0058] In addition, in actual applications, according to actual needs, various functions that need to be completed by the control device can be integrated into one device. In this case, this device serves as a control device; devices corresponding to different functions can also be set up. In this case, the control device is composed of devices corresponding to these functions.
[0059] User equipment is a device corresponding to the user end. In the embodiment of the present invention, the user end that has communication needs for the roadside equipment may be personnel of the relevant transportation department, or may be an application for implementing intelligent traffic management. Therefore, the user equipment may be a control system deployed by the transportation department and other departments for implementing traffic management, and the control system may be composed of one or more servers. Alternatively, the user equipment may also be a server or virtual machine running the above application.
[0060] Roadside equipment refers to various equipment deployed in the road environment, such as RSU, traffic lights, fog lights, information boards, lane controllers, speed limit signs, cameras, etc. In actual applications, the same type of roadside equipment may be provided by many different manufacturers. For example, some of the RSU type equipment installed on the road may be provided by manufacturer A, some by manufacturer B, and some by manufacturer C. These roadside equipment have communication capabilities, but the communication standards used by the same type of roadside equipment provided by different manufacturers may be different. For example, the communication protocol used by the above manufacturer A is http, and the data exchange format is json; the communication protocol used by the above manufacturer B is mqtt, and the data exchange format is protobuf; the communication protocol used by the above manufacturer C is websocket, and the data exchange format is json.
[0061] The above only describes the communication protocol and data exchange format in the adopted communication standard as an example. In fact, there will be other differences in the different communication standards adopted by different manufacturers, such as data structure. For example, in a certain communication standard, the representation of text is text, and in another communication standard, the representation of text may be content.
[0062] Driver refers to a device driver corresponding to a roadside device, which can be installed in a device independent of the corresponding roadside device, or in the corresponding roadside device. In an embodiment of the present invention, for roadside devices of the same device type, if there are multiple manufacturers providing this type of roadside device, a corresponding driver will be developed in advance for each type of roadside device provided by each manufacturer, so as to achieve communication and interaction with the corresponding roadside device through the driver. Still taking the above three manufacturers providing RSU as an example, based on this example, a driver a corresponding to the RSU provided by manufacturer A, a driver b corresponding to the RSU provided by manufacturer B, and a driver c corresponding to the RSU provided by manufacturer C will eventually be generated.
[0063] It should be noted that, on the one hand, these three drivers will support the same preset communication standard. That is to say, when the developer develops multiple drivers corresponding to the same device type, they will define these multiple drivers to use the same communication standard, such as communication protocol, data exchange format, and data structure, which are all consistent. For example, the developer designs the above three drivers to support a certain set communication standard, and the communication protocol included in the communication standard is, for example, http, and the data exchange format is, for example, json. On the other hand, each driver will also support the communication standard adopted by the roadside equipment produced by the corresponding manufacturer. For example, the above driver a will support the communication standard adopted by the above manufacturer A (the communication protocol is http, and the data exchange format is json); the above driver b will support the communication standard adopted by the above manufacturer B (the communication protocol is mqtt, and the data exchange format is protobuf); the above driver c will support the communication standard adopted by the above manufacturer C (the communication protocol is websocket, and the data exchange format is json).
[0064] To facilitate the description of the process of roadside equipment accessing user equipment, Figure 1 In the example, RSU is a type of roadside equipment. It is assumed that there are RSUs provided by the above three manufacturers, and the above three drivers are developed accordingly. Based on this assumption, the above three drivers can be started to send registration information to the management and control device, and the registration information can include the roadside equipment identification corresponding to the driver, so that the management device can store the roadside equipment identification corresponding to each of the three drivers.
[0065] In the embodiment of the present invention, the roadside device identification can optionally be composed of a device type identification and a device manufacturer identification. Of course, according to actual needs, the device identification (such as a device serial number) can also be included. Of course, the above registration information will also include the driver identification, so that the control device can store the driver identification and the roadside device identification accordingly.
[0066] In addition, the registration information may also include the first communication standard information and device type identifier supported by the driver. The first communication standard information refers to the description information of a communication standard supported by the three drivers. Figure 1 The first communication standard information including the communication protocol http and the data exchange format json is shown.
[0067] Of course, in actual applications, after the developers complete the development of each driver program, the first communication standard information and the device type identifier corresponding to multiple drivers of the same device type (specifically, one-to-one correspondence with multiple manufacturers of roadside equipment that generate this device type) can be uploaded to the management and control device.
[0068] like Figure 1 As shown in , after obtaining the above information, the control device can send the first communication standard information uniformly supported by the above three drivers and the corresponding device type identifier to the user device to inform the user device which unified communication standard can be used to communicate with a roadside device of a certain device type. It should be noted that the communication is not just the user device directly communicating with the roadside device of this device type.
[0069] In practical applications, the first communication standard information may be transmitted to the user device in the form of an interface document, that is, the interface document records the relevant information of the above-mentioned unified communication standard, such as communication protocol, data exchange format, data structure, etc. The above-mentioned three drivers are implemented according to the interface document, and the user device will also connect with the roadside device according to the interface document.
[0070] Afterwards, if Figure 1 As shown in, when the user equipment wants to communicate with a roadside device of the RSU type (such as controlling it or collecting its information), it can send a data packet to the management and control device based on the communication protocol, data exchange format, data structure, etc. described in the above-mentioned first communication standard information. The data packet may include a target roadside device identifier to indicate which type of roadside device it wants to communicate with.
[0071] In actual applications, optionally, the target roadside equipment identification may include an equipment type identification, and may also include an equipment manufacturer identification and / or equipment identification. In addition, in actual applications, the above-mentioned data packet may also include information characterizing the user terminal, such as the address information of the user terminal and the user identification. The above-mentioned data packet may also include an operation type and specific operation content, wherein the operation type is used to indicate what type of operation the user terminal wants to perform on the roadside equipment through the user device, such as information collection, status control, content distribution, etc. Among them, the operation content may be a default in certain operation types. In the operation type of content distribution, the corresponding operation content may be the relevant description information of the content to be distributed (such as what the content is, and what the font and format of the content are). In the operation type of status control, the operation content may be the corresponding control instruction content, such as on, off, light on, light off, etc.
[0072] After receiving the data packet sent by the user device, the control device parses the data packet to obtain the target roadside device identifier included therein, and then determines the target driver corresponding to the target roadside device identifier based on the correspondence between each driver identifier and the roadside device identifier stored locally, and sends the data packet to the target driver. Figure 1 In the example, it is assumed that the target driver is driver c.
[0073] The target driver c converts the data packet according to the second communication standard information supported by itself, converts the data packet into a data packet matching the second communication standard information, and sends the converted data packet to the target roadside device corresponding to the target roadside device identifier. Figure 1 In the case of an RSU type roadside device, the second communication standard information supported by the target driver c is the communication standard adopted by the RSU provided by the manufacturer C corresponding to the target driver.
[0074] In the above scheme, for the same type of roadside equipment provided by different manufacturers, drivers corresponding to different manufacturers of this type will be generated in advance. These drivers corresponding to the same type of equipment provide a unified communication standard for the user end, and each is compatible with the communication standard adopted by the roadside equipment provided by the corresponding manufacturer. In the form of driver management, the access of roadside equipment of different manufacturers and types is supported, that is, the user end can achieve communication docking with the roadside equipment through these developed drivers.
[0075] Moreover, since all drivers corresponding to the same device type provide a unified communication standard to the user end, even if some new manufacturers' roadside devices are added under this device type, it is only necessary to develop the corresponding driver and register the developed driver to the management and control device, without modifying the user end, that is, the user end does not need to adapt to support the communication standard adopted by the manufacturer. Similarly, when a new device type is added, the user end only needs to adapt once to the unified communication standard corresponding to this new device type. This reduces the overhead of docking between the user end and the roadside device, and realizes the access of the roadside device in a highly scalable manner.
[0076] Combine the following Figure 2 The following example illustrates the implementation of the process of connecting the user equipment with the roadside equipment when a roadside equipment provided by a manufacturer is added under a certain equipment type.
[0077] exist Figure 2 In this paper, we still take RSU as an example. Figure 1 On the basis of the illustrated embodiment, it is assumed that an RSU provided by manufacturer D is added. At this time, it is necessary to develop a corresponding driver program for the RSU provided by the new manufacturer, and it is assumed that a corresponding driver program d is developed. It can be understood that the driver program d is implemented according to the above-mentioned unified first communication standard, that is, the driver program d supports the first communication standard. In addition, the driver program d also supports the second communication standard adopted by the RSU provided by the corresponding manufacturer D. After the development of the driver program d is completed, the registration information of the driver program d will be sent to the control device, so that the corresponding storage driver program d and its corresponding roadside equipment identifier in the control device are: RSU provided by manufacturer D. Since only a roadside equipment of a certain manufacturer is newly added under the existing equipment type at this time, the control device can notify the user device of what the newly added roadside equipment identifier is under a certain equipment type for the user device to store, and the user device does not need to perform any modification operations related to the communication standard.
[0078] When the user device wants to control the RSU provided by manufacturer D, it can still send a data packet to the control device based on the first communication standard. The target roadside device identifier included in the data packet corresponds to the RSU of manufacturer D. After the control device determines the driver program d corresponding to the target roadside device identifier, the data packet is sent to the driver program d. The driver program d converts the data packet based on the second communication standard corresponding to manufacturer D, and sends the converted data packet to the corresponding target roadside device.
[0079] The above is a summary of the process of connecting the user equipment and the roadside equipment for communication. Figure 3 An optional execution process of communication between a user device and a roadside device is exemplified.
[0080] Figure 3 An interactive flow chart of a roadside equipment communication method provided by an embodiment of the present invention, such as Figure 3 As shown, the method may include the following steps:
[0081] 301. A management and control device obtains roadside device identifiers corresponding to multiple driver programs, operation types supported by each driver program, and first communication standard information supported by the multiple driver programs.
[0082] 302. The management and control device sends first communication standard information corresponding to the device type to the user equipment.
[0083] In this embodiment, it is still assumed that the multiple drivers correspond to roadside devices of the same device type provided by multiple manufacturers. In simple terms, the multiple drivers correspond one-to-one to the multiple manufacturers corresponding to a certain device type.
[0084] After developing the multiple drivers, the developers may write the first communication standard information corresponding to the user end and used uniformly by the multiple drivers into the control device, so that the control device can send it to the user device.
[0085] Optionally, developers can also register each driver to the control device. The registration process is simply to write the driver ID and the roadside device ID corresponding to the driver to the control device. Of course, optionally, the driver can also send its own registration information to the control device. For example, the target driver sends the target roadside device ID corresponding to the target driver to the control device, and of course, it will also send its own driver ID to the control device.
[0086] As mentioned above, one of the multiple drivers supports not only the first communication standard information but also a second communication standard information, and the second communication standard information is adopted by the roadside equipment of the device type provided by the manufacturer corresponding to the driver.
[0087] 303. The user equipment sends a data packet to the management and control equipment based on the first communication standard information, where the data packet includes a target roadside equipment identifier and a target operation type to be performed on the target roadside equipment.
[0088] 304. The control device authenticates the user device according to the target roadside device identifier and the target operation type. If it is determined that the user device has the authority to trigger the target operation type on the target roadside device, a target driver corresponding to the target roadside device identifier is determined from multiple drivers.
[0089] In this embodiment, after receiving a data packet including a target roadside device identifier and a target operation type sent by a user device, the control device needs to perform an authority check on the user device according to the target roadside device identifier and the target operation type. Specifically, it is to detect whether the user device has the authority to operate the target roadside device corresponding to the target roadside device identifier, and whether the user device can perform an operation corresponding to the target operation type on the target roadside device.
[0090] In fact, the control device may pre-store the operation authority information of different user terminals for the roadside equipment, so as to complete the above authentication process based on this.
[0091] For example, assuming that the user terminal is an advertiser, the operation permission information corresponding to the user terminal pre-stored in the control device may be: the advertiser can use billboards within a certain area to publish advertisements within a certain time range (such as two months). Based on this, assuming that the target roadside device identifier carried in the data packet sent by the advertiser to the control device through its corresponding user device is not the identifier corresponding to the billboard, but for example the identifier of the RSU, then the control device will determine that the user device does not have the authority to operate the target roadside device corresponding to the target roadside device identifier. For another example, even if the target roadside device identifier carried in the data packet triggered by the advertiser is indeed the identifier corresponding to the billboard, when the operation permission information stored in the control device indicates that the advertiser can only use billboards within a certain area, the control device determines the billboards within the area based on the location information of each billboard stored locally, and these billboards serve as the target roadside devices corresponding to the target roadside device identifier in the data packet. Based on this, it can be seen that in the authentication process, the target roadside device corresponding to the target roadside device identifier that the user device can operate can be further determined.
[0092] The above is an illustrative explanation of the authentication process of whether a user device can operate a certain roadside device. In terms of operation types, in fact, for a certain type of roadside equipment, multiple types of operations may be supported, but not all users can perform all types of operations on this type of roadside equipment. For example, for roadside equipment such as speed limit signs, generally only relevant departments such as traffic management have the authority to change the speed limit value of the speed limit sign, while other users only have the authority to read the speed limit value. In other words, relevant departments such as traffic management can perform two types of operations: reading and modifying, while other users can only perform this type of operation. The control device stores the operation type permission information of different users for different types of roadside equipment for authentication.
[0093] When the control device determines that the user device has the authority to trigger the target operation type for the target roadside device, the target driver corresponding to the target roadside device identifier is determined from multiple drivers. Conversely, when the control device determines that the user device does not have the authority to trigger the target operation type for the target roadside device, the processing of the data packet triggered by the user device is exited, and an error prompt information may be fed back to the user device.
[0094] The control device searches for a target driver corresponding to the target roadside device identifier according to the correspondence between each driver identifier and the roadside device identifier that has been stored locally.
[0095] In actual applications, the driver can be configured to send registration information to the control device after being started. If a driver has not been started, the control device may not obtain the registration information of the driver. Based on this, the control device may not be able to find the target driver corresponding to the target roadside device identifier in the stored driver registration information. At this time, assuming that the multiple drivers that have obtained registration information are drivers in a running state, if the target driver corresponding to the target roadside device identifier is not determined among the multiple drivers, the control device obtains the registration information of other drivers that are not running. If it is determined that there is a target driver corresponding to the target roadside device identifier among the other drivers, the target driver is started.
[0096] As mentioned above, the developed driver can be stored in a device independent of the corresponding roadside device, or installed in the corresponding roadside device. Regardless of where it is located, the device storing the driver will record relevant information about the driver, such as the corresponding roadside device identification. The control device can send a query instruction to the device to query whether there is a target driver corresponding to the target roadside device identification. If so, the target driver is started so that the data packet sent by the user device is sent to the target driver. In addition, the registration information of the target driver can be synchronized locally. If it does not exist, a driver generation task is generated, and the driver generation task indicates the generation of a driver corresponding to the target roadside device identification.
[0097] 305. The control device determines that the target driver supports the target operation type.
[0098] The control device, based on the correspondence between the driver identifications and roadside device identifications stored locally, if finds the target driver corresponding to the target roadside device identification, can optionally further determine whether the target driver supports the target operation type based on the target operation type contained in the data packet.
[0099] In actual applications, when a developer develops a driver corresponding to a certain device type and a certain manufacturer's roadside device, assuming that the roadside device provided by the manufacturer has multiple operation types, the driver can be configured to support all of these multiple operation types, or it can be configured to support only some of them. When only some operation types are supported, it means that if the target operation type triggered by the user does not match some of the operation types supported by the driver, the communication between the user device and the manufacturer's roadside device cannot be achieved through the driver.
[0100] Therefore, optionally, the control device may also store information on the types of operations supported by each driver. This information may be registered in the control device by the driver, or may be written into the control device by a developer.
[0101] When the control device determines that the target driver supports the above target operation type, the control device sends a data packet to the target driver.
[0102] 306. The control device sends the data packet to the target driver.
[0103] 307. The target driver converts the data packet based on the second communication standard adopted by the target roadside device.
[0104] 308. The target driver sends the converted data packet to the target roadside device.
[0105] For the related contents not described in detail in this embodiment, please refer to the related descriptions in the aforementioned embodiments and will not be repeated here.
[0106] As mentioned above, the control device in the above embodiment can actually be implemented as a plurality of entities with different functions. Figure 4 An exemplary embodiment of a composition form of a control device and a connection process between a roadside device and a user device under the composition form are described.
[0107] Figure 4 A schematic diagram of another roadside equipment communication system provided by an embodiment of the present invention, such as Figure 4 As shown in , the system includes: a management and control device, a user device, a driver, and a roadside device, wherein the management and control device may include a gateway node, a task queue, a routing node, and a working node.
[0108] The various nodes mentioned above may be physical devices or virtual machines, and the nodes may be located in different physical machines or partially in the same physical machine.
[0109] Gateway node: responsible for API exposure and user permission management, and implements permission control at the device and operation function granularity.
[0110] Task queue: You can use MySQL to store task queues, which can be used to store data packets triggered by user devices.
[0111] Routing node; communicates with the driver through the set communication protocol to maintain heartbeat and synchronize capabilities.
[0112] Worker node: used to process tasks in the task queue.
[0113] Driver: Supports regular reporting of equipment list and driving capability. The equipment list is composed of the roadside equipment identification corresponding to the driver, and the driving capability is the operation type supported by the driver.
[0114] The following describes how to use Figure 4 The system shown is an implementation scheme for connecting user equipment with roadside equipment.
[0115] like Figure 4 As shown in the figure, a driver corresponding to a certain type of roadside equipment provided by a certain manufacturer can send registration information to the routing node. The registration information may include the roadside equipment identification corresponding to the driver, the supported operation types performed on the roadside equipment, etc.
[0116] Assuming that the developer has uploaded the first communication standard information uniformly adopted by the driver corresponding to the above device type to the gateway node, the gateway node will send the first communication standard information to the user device.
[0117] The user device sends a data packet to the gateway node based on the first communication standard information, the gateway node stores the data packet in the task queue, the task queue feeds back a submission success message, and the gateway node feeds back a submission success message to the user device. The user device can then poll the processing result of the data packet according to the identifier of the data packet.
[0118] As described above, optionally, after receiving the data packet, the gateway node may perform the authentication process described above. When the data packet sent by the user equipment passes the authentication, the gateway node stores the data packet in the task queue.
[0119] The working node periodically polls the task queue to receive tasks, that is, the data packets stored in the task queue. After reading the above data packet, it parses it to obtain the target roadside device identifier and target operation type contained in the data packet. It queries the routing node for the driver that matches the target roadside device identifier and target operation type. Figure 5 The working node then sends the data packet to the driver, which converts the data packet based on the second communication standard adopted by the corresponding roadside device, and sends the converted data packet to the corresponding roadside device.
[0120] The roadside equipment performs the operation indicated in the data packet and feeds back the operation result to the working node. The working node feeds back the operation result to the gateway node, which then feeds back to the user equipment.
[0121] This solution abstracts the docking process between user equipment and roadside equipment into three parts: gateway node, task processing, and driver program. After developing the corresponding drivers for roadside equipment from different manufacturers, they are registered to the routing node through a unified communication protocol interface. The upper-layer application (i.e., the user end) can call the gateway node to send control information (i.e., data packets) to enter the task queue, and then based on the registration information of different drivers, the control information is executed to the roadside equipment through the corresponding driver program.
[0122] In summary, the embodiments of the present invention provide a scalable unified roadside equipment access framework, which can achieve user equipment-oriented protocol standardization for each type of roadside equipment, and does not require the user end to be compatible with the communication standards used by the roadside equipment provided by various manufacturers. In a driver management manner, it supports the access of roadside equipment of different manufacturers and different types. It enables the user end to communicate with more roadside equipment at a lower cost.
[0123] The following will describe in detail the roadside equipment communication device of one or more embodiments of the present invention. Those skilled in the art will appreciate that these devices can be configured using commercially available hardware components through the steps taught in this solution.
[0124] Figure 5 A schematic diagram of a roadside equipment communication device provided in an embodiment of the present invention, wherein the device is located in a control device, such as Figure 5 As shown, the device includes: an acquisition module 11, a sending module 12, a receiving module 13, and a determination module 14.
[0125] The acquisition module 11 is used to obtain the roadside device identifications corresponding to each of the multiple drivers and the first communication standard information supported by the multiple drivers, the multiple drivers correspond to roadside devices of the same device type provided by multiple manufacturers, one of the drivers also supports a second communication standard information, and the second communication standard information is adopted by the roadside device of the device type provided by one of the manufacturers.
[0126] The sending module 12 is configured to send the first communication standard information to a user equipment.
[0127] The receiving module 13 is configured to receive a data packet sent by the user equipment based on the first communication standard information, wherein the data packet includes a target roadside equipment identifier.
[0128] The determination module 14 is configured to determine a target driver corresponding to the target roadside device identifier from among the multiple drivers.
[0129] The sending module 12 is further used to send the data packet to the target driver, so that the target driver converts the data packet based on the second communication standard adopted by the target roadside device, and sends the converted data packet to the target roadside device.
[0130] Optionally, the acquisition module 11 is further used to: acquire the operation types supported by each of the multiple drivers; the data packet also includes the target operation type to be performed on the target roadside device. The sending module 12 is further used to send the data packet to the target driver if it is determined that the target driver supports the target operation type.
[0131] Optionally, the determination module 14 is also used to: authenticate the user device according to the target roadside device identifier and the target operation type; if it is determined that the user device has the authority to trigger the target operation type for the target roadside device, determine the target driver corresponding to the target roadside device identifier from the multiple drivers.
[0132] Optionally, the multiple drivers are drivers in a running state, and the determination module 14 is specifically used to: if the target driver corresponding to the target roadside device identifier is not determined among the multiple drivers, obtain the registration information of other drivers in a non-running state; if it is determined that there is a target driver corresponding to the target roadside device identifier among the other drivers, start the target driver; if it is determined that there is no target driver corresponding to the target roadside device identifier among the other drivers, generate a driver generation task, and the driver generation task indicates the generation of a driver corresponding to the target roadside device identifier.
[0133] Figure 5 The device shown can execute the steps executed by the control device in the aforementioned embodiment. For detailed execution process and technical effects, please refer to the description in the aforementioned embodiment and will not be repeated here.
[0134] In one possible design, the above Figure 5 The structure of the roadside equipment communication device shown can be implemented as a control device, such as Figure 6 As shown, the control device may include: a first processor 21, a first memory 22, and a first communication interface 23. The first memory 22 stores executable code, and when the executable code is executed by the first processor 21, the first processor 21 can at least implement the steps performed by the control device in the above-mentioned embodiment.
[0135] Figure 7 A schematic diagram of a roadside equipment communication device provided in an embodiment of the present invention, wherein the device is located in a user equipment, such as Figure 7 As shown, the device includes: a receiving module 31 and a sending module 32.
[0136] The receiving module 31 is used to receive a first communication standard supported by multiple drivers sent by a control device, wherein the multiple drivers correspond to roadside devices of the same device type provided by multiple manufacturers, and one of the drivers also supports a second communication standard information, which is adopted by the roadside device of the device type provided by one of the manufacturers; the control device stores the roadside device identifiers corresponding to each of the multiple drivers.
[0137] A sending module 32 is used to send a data packet to the control device based on the first communication standard information, wherein the data packet includes a target roadside device identifier, so that the control device determines a target driver corresponding to the target roadside device identifier from among the multiple drivers, sends the data packet to the target driver so that the target driver converts the data packet based on a second communication standard adopted by the target roadside device, and sends the converted data packet to the target roadside device.
[0138] Figure 7 The device shown can execute the steps executed by the user equipment in the aforementioned embodiment. For detailed execution process and technical effects, please refer to the description in the aforementioned embodiment, which will not be repeated here.
[0139] In one possible design, the above Figure 7 The structure of the roadside equipment communication device shown in the figure can be implemented as a user equipment, such as Figure 8 As shown, the user equipment may include: a second processor 41, a second memory 42, and a second communication interface 43. The second memory 42 stores executable code, and when the executable code is executed by the second processor 41, the second processor 41 can at least implement the steps performed by the user equipment in the above embodiment.
[0140] Fig. 9 A schematic diagram of the structure of a roadside equipment communication device provided by an embodiment of the present invention, the device is located in a driving device installed with a driver, such as Fig. 9 As shown, the device includes: a sending module 51 and a receiving module 52.
[0141] A sending module 51 is used to send a target roadside device identifier corresponding to the target driver to a control device; the control device stores roadside device identifiers corresponding to multiple drivers, the target driver is one of the multiple drivers, and the multiple drivers correspond to roadside devices of the same device type provided by multiple manufacturers; the multiple drivers all support first communication standard information, and one of the drivers also supports second communication standard information, and the second communication standard information is adopted by a roadside device of the device type provided by one of the manufacturers.
[0142] The receiving module 52 is used to receive a data packet sent by a control device, wherein the data packet is sent by a user device according to the first communication standard information sent by the control device, and the data packet includes the target roadside device identifier. The control device determines the target driver corresponding to the target roadside device identifier from the multiple drivers and sends the data packet to the target driver.
[0143] The sending module 51 is further configured to convert the data packet based on a second communication standard adopted by the target roadside device, and send the converted data packet to the target roadside device.
[0144] Optionally, the sending module 51 is further used to send the target operation type supported by the target driver to the control device; the data packet also includes the target operation type performed on the target roadside device. The receiving module 52 is specifically used to receive the data packet sent by the control device after determining that the target driver supports the target operation type.
[0145] Fig. 9 The device shown can execute the steps executed by the driver in the aforementioned embodiment. The detailed execution process and technical effects can be found in the description of the aforementioned embodiment, which will not be repeated here.
[0146] In one possible design, the above Fig. 9 The structure of the roadside equipment communication device shown can be implemented as a driving device, such as Fig.10 As shown, the driving device may include: a third processor 61, a third memory 62, and a third communication interface 63. The third memory 62 stores a driving program, and when the driving program is executed by the third processor 61, the third processor 61 can at least implement the steps corresponding to the driving program in the above-mentioned embodiment.
[0147] In addition, an embodiment of the present invention provides a non-temporary machine-readable storage medium, on which executable code is stored. When the executable code is executed by a processor of an electronic device, the processor can at least implement the roadside equipment communication method provided in the aforementioned embodiment.
[0148] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated. Some or all of the modules may be selected according to actual needs to achieve the purpose of the present embodiment. Those of ordinary skill in the art may understand and implement the present invention without creative effort.
[0149] Through the description of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by adding a necessary general hardware platform, and of course can also be implemented by combining hardware and software. Based on such an understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a computer product, and the present invention can be in 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 codes.
[0150] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, rather than to limit it. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention.
Claims
1. A roadside equipment communication method, characterized in that: Applied to a control device, the method includes: Acquire roadside device identifiers corresponding to each of a plurality of drivers and first communication standard information supported by the plurality of drivers, wherein the plurality of drivers correspond to roadside devices of the same device type provided by a plurality of manufacturers, and one of the drivers further supports a second communication standard information, wherein the second communication standard information is adopted by a roadside device of the device type provided by one of the manufacturers; Sending the first communication standard information to user equipment; receiving a data packet sent by the user equipment based on the first communication standard information, wherein the data packet includes a target roadside equipment identifier; Determining a target driver corresponding to the target roadside device identifier among the multiple drivers; The data packet is sent to the target driver so that the target driver converts the data packet based on a second communication standard adopted by the target roadside device, and sends the converted data packet to the target roadside device.
2. The method according to claim 1, characterized in that The method further comprises: Acquiring the operation types supported by each of the plurality of drivers; the data packet also includes the target operation type to be performed on the target roadside device; The step of sending the data packet to the target driver comprises: If it is determined that the target driver supports the target operation type, the data packet is sent to the target driver.
3. The method according to claim 2, characterized in that The step of determining a target driver corresponding to the target roadside device identifier from among the multiple drivers includes: authenticating the user equipment according to the target roadside equipment identifier and the target operation type; If it is determined that the user equipment has the authority to trigger the target operation type on the target roadside equipment, a target driver corresponding to the target roadside equipment identifier is determined from the multiple drivers.
4. The method according to claim 1, characterized in that: The plurality of drivers are drivers in a running state; The step of determining a target driver corresponding to the target roadside device identifier from among the multiple drivers includes: If a target driver corresponding to the target roadside device identifier is not determined among the multiple drivers, obtaining registration information of other drivers that are not in operation; If it is determined that a target driver corresponding to the target roadside device identifier exists in the other drivers, the target driver is started.
5. The method according to claim 4, characterized in that The method further comprises: If it is determined that the target driver corresponding to the target roadside device identifier does not exist in the other drivers, a driver generation task is generated, wherein the driver generation task indicates generation of a driver corresponding to the target roadside device identifier.
6. A roadside equipment communication method, characterized in that: Applied to user equipment, the method comprises: receiving a first communication standard supported by multiple drivers sent by a control device, wherein the multiple drivers correspond to roadside devices of the same device type provided by multiple manufacturers, and one of the drivers further supports a second communication standard information, wherein the second communication standard information is adopted by a roadside device of the device type provided by one of the manufacturers; the control device stores roadside device identifiers corresponding to each of the multiple drivers; A data packet is sent to the control device based on the first communication standard information, the data packet including a target roadside device identifier, so that the control device determines a target driver corresponding to the target roadside device identifier from among the multiple drivers, sends the data packet to the target driver so that the target driver converts the data packet based on a second communication standard adopted by the target roadside device, and sends the converted data packet to the target roadside device.
7. A roadside equipment communication method, characterized in that: Applied to a target drive device, the target drive device includes a target driver program, and the method includes: Sending a target roadside device identifier corresponding to the target driver to a control device; the control device stores roadside device identifiers corresponding to multiple drivers, the target driver is one of the multiple drivers, and the multiple drivers correspond to roadside devices of the same device type provided by multiple manufacturers; the multiple drivers all support first communication standard information, one of the drivers also supports second communication standard information, and the second communication standard information is adopted by a roadside device of the device type provided by one of the manufacturers; receiving a data packet sent by a control device, the data packet being sent by a user device according to the first communication standard information sent by the control device, the data packet including the target roadside device identifier, the control device determining the target driver corresponding to the target roadside device identifier from the multiple drivers, and sending the data packet to the target driver; The data packet is converted based on a second communication standard adopted by the target roadside device, and the converted data packet is sent to the target roadside device.
8. The method according to claim 7, characterized in that The method further comprises: Sending the target operation type supported by the target driver to the control device; the data packet also includes the target operation type performed on the target roadside device; The receiving of the data packet sent by the control device includes: The data packet is received after the control device determines that the target driver supports the target operation type.
9. A control device, characterized in that: include: A memory, a processor, and a communication interface; wherein the memory stores executable code, and when the executable code is executed by the processor, the processor executes the roadside equipment communication method as described in any one of claims 1 to 5.
10. A user equipment, characterized in that: include: A memory, a processor, and a communication interface; wherein the memory stores executable code, and when the executable code is executed by the processor, the processor executes the roadside equipment communication method as described in claim 6.
11. A driving device, characterized in that: include: A memory, a processor, and a communication interface; wherein a target driver is stored on the memory, and when the target driver is executed by the processor, the processor executes the roadside equipment communication method as described in claim 7 or 8.
Citation Information
Patent Citations
Intelligent home furnishing equipment control method, system, storage medium and computer equipment
CN107608225A
Rail transit unified data acquisition platform
CN111737329A
Unsupervised Real-to-Virtual Domain Unification for End-to-End Highway Driving
US20190171223A1
