CN115623088B - Roadside equipment communication method and equipment - Google Patents

The embodiment of the invention provides a method and equipment for communication of road side equipment, wherein the method comprises the following steps: the management and control equipment acquires the road side equipment identifiers corresponding to the multiple drivers and the first communication standard information supported by the multiple drivers, wherein the multiple drivers correspond to road side equipment of the same equipment type provided by multiple manufacturers. The management and control equipment sends first communication standard information to the user equipment, receives a data packet sent by the user equipment based on the first communication standard information, wherein the data packet comprises a target road side equipment identifier, determines a target driving program corresponding to the target road side equipment identifier, and sends the data packet to the target driving program so that the target driving program converts the data packet based on a second communication standard adopted by the target road side equipment, and sends the converted data packet to the target road side equipment. When the road side equipment provided by a certain manufacturer is newly added, only a corresponding driver program needs to be developed, and the user side does not need to modify the communication standard, so that the expansibility of equipment access is improved.

Roadside equipment communication method and equipment

Technical Field

The invention relates to the technical field of the internet of things, in particular to a communication method and device for road side equipment.

Background

In the field of intelligent transportation, vehicle-road cooperative systems are continuously developed. The vehicle-road cooperative system simply adopts advanced wireless communication, internet and other technologies to implement vehicle-vehicle and vehicle-road dynamic real-time information interaction in all directions, and on the basis of full-time empty dynamic traffic information acquisition and fusion, vehicle active safety control and road cooperative management are developed, so that effective cooperation of human-vehicle roads is fully realized, traffic safety is ensured, traffic efficiency is improved, and a safe, efficient and environment-friendly road traffic system is formed.

In a vehicle-Road cooperative system, a large number of Road Side devices, such as speed limit signs, fog lights, road Side Units (RSUs), lane controllers, and the like, are deployed. The road side equipment is generally provided by different manufacturers, and each equipment manufacturer realizes communication protocols, data exchange formats and the like according to own understanding based on corresponding international or national standards, and does not have any industry standard.

In the conventional scheme, a user side (such as a related traffic department, a certain traffic control application program, etc.) needs to interact with the road side devices, and the user side needs to perform configuration corresponding to different types of road side devices provided by different manufacturers so as to support communication standards of the road side devices provided by different manufacturers, so that information interaction with the corresponding road side devices can be performed. The way of accessing the road side equipment to the user side has poor expandability and high expenditure of the user side.

Disclosure of Invention

The embodiment of the invention provides a communication method and equipment for road side equipment, which can reduce the expenditure of a user side for accessing road side equipment and realize high-expansibility access of the road side equipment.

In a first aspect, an embodiment of the present invention provides a method for communication between road side devices, where the method is applied to a management and control device, and the method includes:

Acquiring a road side device identifier corresponding to each of a plurality of drivers and first communication standard information supported by the drivers, wherein the drivers correspond to road side devices of the same device type provided by a plurality of manufacturers, one driver also supports second communication standard information, and the second communication standard information is adopted by the road side devices of the device type provided by one manufacturer;

Transmitting 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 comprises a target road side equipment identifier;

Determining a target driver corresponding to the target roadside equipment identifier in the plurality of drivers;

And sending the data packet to the target driving program so that the target driving program converts the data packet based on a second communication standard adopted by target road side equipment, and sending the converted data packet to the target road side equipment.

In a second aspect, an embodiment of the present invention provides a communication apparatus for a roadside device, located in a management and control device, where the apparatus includes:

The device comprises an acquisition module, a storage module and a control module, wherein the acquisition module is used for acquiring a road side device identifier corresponding to each of a plurality of drivers and first communication standard information supported by the drivers, the drivers correspond to road side devices of the same device type provided by a plurality of manufacturers, one driver also supports second communication standard information, and the second communication standard information is adopted by the road side devices of the device type provided by one manufacturer;

a sending module, configured to send the first communication standard information to a user equipment;

The receiving module is used for receiving a data packet sent by the user equipment based on the first communication standard information, wherein the data packet comprises a target road side equipment identifier;

The determining module is used for determining a target driving program corresponding to the target road side equipment identifier in the plurality of driving programs;

The sending module is further configured to send 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.

In a third aspect, an embodiment of the present invention provides a management and control device, including a memory, a processor, and a communications interface, where the memory stores executable code, and when the executable code is executed by the processor, the processor is enabled to at least implement a roadside device communications method as described in the first aspect.

In a fourth aspect, embodiments of the present invention provide a non-transitory machine-readable storage medium having executable code stored thereon, which when executed by a processor of a management device, causes the processor to at least implement a roadside device communication method as described in the first aspect.

In a fifth aspect, an embodiment of the present invention provides a method for communication between a road side device, where the method is applied to a user device, and the method includes:

Receiving a first communication standard supported by a plurality of drivers sent by a management and control device, wherein the drivers correspond to road side devices of the same device type provided by a plurality of manufacturers, one driver also supports second communication standard information, and the second communication standard information is adopted by the road side devices of the device type provided by one manufacturer;

And transmitting a data packet to the control device based on the first communication standard information, wherein the data packet comprises a target road side device identifier, so that the control device determines a target driving program corresponding to the target road side device identifier in the plurality of driving programs, transmits the data packet to the target driving program, converts the data packet based on a second communication standard adopted by the target road side device by the target driving program, and transmits the converted data packet to the target road side device.

In a sixth aspect, an embodiment of the present invention provides a communications apparatus for a roadside device, located in a user equipment, where the apparatus includes:

the system comprises a receiving module, a control device, a control module and a control module, wherein the receiving module is used for receiving a first communication standard supported by a plurality of drivers sent by the control device, the drivers correspond to road side devices of the same device type provided by a plurality of manufacturers, one driver also supports second communication standard information, and the second communication standard information is adopted by the road side devices of the device type provided by one manufacturer;

and the sending module is used for sending a data packet to the management and control equipment based on the first communication standard information, wherein the data packet comprises a target road side equipment identifier, so that the management and control equipment determines a target driving program corresponding to the target road side equipment identifier in the plurality of driving programs, sends the data packet to the target driving program, enables the target driving program to convert the data packet based on a second communication standard adopted by the target road side equipment, and sends the converted data packet to the target road side equipment.

In a seventh aspect, an embodiment of the present invention provides a user equipment, including a memory, a processor, and a communications interface, where the memory stores executable code, and when the executable code is executed by the processor, the processor is enabled to at least implement a roadside device communications method according to the fifth aspect.

In an eighth aspect, embodiments of the present invention provide a non-transitory machine-readable storage medium having stored thereon executable code, which when executed by a processor of a user equipment, causes the processor to at least implement a roadside device communication method as described in the fifth aspect.

In a ninth aspect, an embodiment of the present invention provides a method for communicating a roadside device, which is applied to a target driver, and the method includes:

The method comprises the steps of sending a target road side equipment identifier corresponding to a target driving program to a management and control device, wherein the management and control device stores road side equipment identifiers corresponding to a plurality of driving programs respectively, the target driving program is one of the driving programs, and the driving programs correspond to road side equipment of the same equipment type provided by a plurality of manufacturers;

Receiving a data packet sent by a management and control device, wherein the data packet is sent by a user device according to the first communication standard information sent by the management and control device, the data packet comprises the target road side device identifier, the management and control device determines the target driver corresponding to the target road side device identifier from the multiple drivers, and sends the data packet to the target driver;

And converting the data packet based on a second communication standard adopted by the target road side equipment, and sending the converted data packet to the target road side equipment.

In a tenth aspect, an embodiment of the present invention provides a communication apparatus for a roadside device, located in a driving device, including:

The system comprises a management and control device, a sending module, a first communication standard information and a second communication standard information, wherein the management and control device is used for storing the road side device identifiers corresponding to a plurality of drivers, the target driver is one of the drivers and corresponds to the road side device of the same device type provided by a plurality of manufacturers, and the drivers support the first communication standard information;

The receiving module is used for receiving a data packet sent by the management and control equipment, wherein the data packet is sent by the user equipment according to the first communication standard information sent by the management and control equipment, the data packet comprises the target road side equipment identifier, the management and control equipment determines the target driver corresponding to the target road side equipment identifier from the multiple drivers, and sends the data packet to the target driver;

The sending module 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.

In an eleventh aspect, an embodiment of the present invention provides a driving device, including a memory, a processor, and a communication interface, where the memory stores a target driver, and when the target driver is executed by the processor, the processor is enabled to at least implement a roadside device communication method according to the ninth aspect.

In a twelfth aspect, an embodiment of the present invention provides a non-transitory machine-readable storage medium, where a target driver is stored, where the target driver, when executed by a processor of a driving device, makes the processor at least possible to implement a roadside device communication method according to the ninth aspect.

In a thirteenth aspect, an embodiment of the present invention provides a driving apparatus for a roadside device, including a plurality of drivers, where the plurality of drivers each support first communication standard information, the plurality of drivers corresponding to a roadside device of a same device type provided by a plurality of vendors, and one driver further supports second communication standard information, where the second communication standard information is adopted by a roadside device of the device type provided by one of the vendors;

The method comprises the steps of receiving a data packet sent by a management and control device, wherein the data packet is sent by user equipment according to first communication standard information sent by the management and control device, the data packet comprises the target road side device identification, the management and control device determines the target driving program corresponding to the target road side device identification in the plurality of driving programs and sends the data packet to the target driving program, and the data packet is converted based on second communication standard adopted by the target road side device and sent to the target road side device.

In the scheme provided by the embodiment of the invention, the process of accessing the road side equipment into the user equipment is controlled by the cloud management and control equipment. For the roadside devices of the same device type provided by multiple manufacturers, multiple drivers corresponding to the same device type may be developed in advance, for example, a certain type of roadside device is provided by five manufacturers in total, then five drivers corresponding to the type of roadside device provided by the five manufacturers, and one driver corresponding to the type of roadside device provided by one manufacturer, may be developed in advance. In the process of generating the five drivers, the five drivers are enabled to support preset first communication standard information, and in addition, one driver also supports second communication standard information adopted by the road side equipment of the type provided by a manufacturer corresponding to the first communication standard information.

Based on the development of the multiple drivers, the management and control device may store a roadside device identifier (for characterizing what type of roadside device is provided by which vendor) corresponding to each driver, and further store first communication standard information supported by the multiple drivers. The management and control device informs the user device that unified information of the first communication standard can be adopted when the user device needs to communicate with the road side device of the device type. In this way, when the user equipment needs to communicate with the road side equipment of the equipment type, a data packet is sent to the management and control equipment based on the first communication standard information, and the data packet comprises the target road side equipment identifier. The management and control equipment determines a target driving program corresponding to the target road side equipment identifier, sends the data packet to the target driving program, converts the data packet based on a second communication standard adopted by the target road side equipment, and sends the converted data packet to the target road side equipment.

Therefore, in the above scheme, for the same type of road side equipment provided by different manufacturers, drivers corresponding to different manufacturers of the type are generated in advance, and the drivers corresponding to the same equipment type provide unified communication standards for the user side, and are respectively compatible with the communication standards adopted by the road side equipment provided by the corresponding manufacturer. Based on this, when some vendor provided roadside devices are newly added under a certain device type, the user side does not need to modify the communication standard, and when a new device type is added, the user side only needs to perform the adaptation of the unified communication standard corresponding to the device type once. Therefore, the cost of accessing the user side to the road side equipment is reduced, and the access of the road side equipment is realized in a highly-expansibility mode.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings required for the description of the embodiments will be briefly described below, and it is obvious that the drawings in the following description are some embodiments of the present invention, and other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a schematic diagram of a communication system of a roadside device according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a situation of an added roadside device according to an embodiment of the present invention;

Fig. 3 is an interaction flow chart of a communication method of a road side device according to an embodiment of the present invention;

fig. 4 is a schematic diagram of another communication system of a roadside device according to an embodiment of the present invention;

fig. 5 is a schematic structural diagram of a communication device of a roadside apparatus according to an embodiment of the present invention;

fig. 6 is a schematic structural diagram of a management and control device corresponding to the communication apparatus of the roadside device provided in the embodiment shown in fig. 5;

fig. 7 is a schematic structural diagram of a communication device of a roadside apparatus according to an embodiment of the present invention;

fig. 8 is a schematic structural diagram of a user equipment corresponding to the communication device of the roadside device provided in the embodiment shown in fig. 7;

fig. 9 is a schematic structural diagram of a communication device of a roadside apparatus according to an embodiment of the present invention;

Fig. 10 is a schematic structural diagram of a driving device corresponding to the communication apparatus of the road side device according to the embodiment shown in fig. 9.

Detailed Description

For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.

In addition, the sequence of steps in the method embodiments described below is only an example and is not strictly limited.

Fig. 1 is a schematic diagram of a communication system of a road side device according to an embodiment of the present invention, where, as shown in fig. 1, the system includes a management and control device, a user device, a driver, and a road side device.

The management and control equipment can be a management and control center located at the cloud end, and access of the road side equipment to the user equipment is completed through the management and control equipment. In practice, the management and control device may be an independent physical machine, a virtual machine, or a cluster formed by a plurality of physical machines or virtual machines.

In addition, in practical application, various functions to be completed by the control device can be integrated into one device according to practical requirements, at the moment, the one device is used as the control device, and devices corresponding to different functions can be set, and at the moment, the control device is formed by the devices corresponding to the functions.

The user equipment is equipment corresponding to the user side. In the embodiment of the invention, the user side with the communication requirement on the road side equipment can be the personnel of the related traffic departments, and can also be some application program for realizing intelligent traffic management. Thus, the user device may be a control system deployed by a department of transportation or the like for implementing traffic management, which may be constituted by one or more servers. Or the user device may be a server or virtual machine running the application program described above.

Roadside devices refer to various devices deployed in a road environment, and may include RSUs, traffic lights, fog lights, information boards, lane controllers, speed limit signs, cameras, and the like, for example. In practice, the same type of roadside equipment may be provided by many different vendors. For example, road-mounted RSUs of this type may be provided by some vendor a, some vendor B, and some vendor C. These roadside devices have communication capabilities, but the communication standards employed by the same type of roadside devices provided by different vendors may vary. For example, the communication protocol adopted by the manufacturer a is http, the data exchange format is json, the communication protocol adopted by the manufacturer B is mqtt, the data exchange format is protobuf, the communication protocol adopted by the manufacturer C is websocket, and the data exchange format is json.

The above description has been given by taking the communication standard in which the communication protocol and the data exchange format are described as examples, and in fact, there may be other differences in different communication standards employed by different manufacturers, such as a data structure, for example, text is represented in a certain communication standard, and content may be represented in another communication standard.

A driver (driver) is a device driver corresponding to a road side device, and can be installed in a device independent of the corresponding road side device, and can be installed in the corresponding road side device. In the embodiment of the invention, if a plurality of manufacturers provide the road side equipment of the same equipment type, a driver corresponding to the road side equipment of the type provided by each manufacturer is developed in advance so as to realize communication interaction with the corresponding road side equipment through the driver. Taking the example of the road side device of the type that the three vendors provide RSUs as still, based on the example situation, a driver a corresponding to the RSU provided by the vendor a, a driver B corresponding to the RSU provided by the vendor B, and a driver C corresponding to the RSU provided by the vendor C are finally generated.

It should be noted that, on the one hand, all the three drivers support the same preset communication standard. That is, when developing multiple drivers corresponding to the same device type, a developer defines that the multiple drivers are consistent using the same communication standard, such as a communication protocol, a data exchange format, and a data structure. For example, a developer designs that each of the three drivers supports 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 also supports the communication standard adopted by the road side equipment produced by the corresponding manufacturer. For example, the driver a may support the communication standard (the communication protocol is http and the data exchange format is json) adopted by the vendor a, the driver B may support the communication standard (the communication protocol is mqtt and the data exchange format is protobuf) adopted by the vendor B, and the driver C may support the communication standard (the communication protocol is websocket and the data exchange format is json) adopted by the vendor C.

In order to facilitate the description of the procedure of the access of the road side equipment to the user equipment, in fig. 1, taking an RSU of this type as an example, it is assumed that there are RSUs provided by the above three vendors, and accordingly, the above three drivers are developed. Based on this assumption, the three drivers may be started to send registration information to the management device, where the registration information may include the roadside device identifiers corresponding to the drivers, so that the management device may store the roadside device identifiers corresponding to the three drivers.

In the embodiment of the present invention, optionally, the roadside device identifier may be composed of a device type identifier and a device manufacturer identifier, and of course, according to actual requirements, the device identifier may also be included (e.g. a device serial number). Of course, the registration information also includes the driver identifier, so that the management and control device can correspondingly store the driver identifier and the roadside device identifier.

In addition, optionally, the registration information may also include first communication standard information supported by the driver and a device type identifier. The first communication standard information refers to description information of one communication standard that is uniformly supported by the three drivers, for example, the first communication standard information including a communication protocol http and a data exchange format json illustrated in fig. 1.

Of course, in practical application, after the developer finishes developing each driver, the first communication standard information and the device type identifier corresponding to the plurality of drivers of the same device type (specifically, corresponding to a plurality of manufacturers of the road side device generating the device type in a one-to-one manner) may be uploaded to the management and control device.

As shown in fig. 1, after obtaining the information, the management and control device may send the first communication standard information and the corresponding device type identifier that are uniformly supported by the three drivers to the user device, so as to inform the user device which uniform communication standard may be used to communicate with a roadside device of a certain device type. It should be noted that the communication is not just that the user equipment communicates directly with the roadside equipment of this equipment type.

In practical applications, the first communication standard information may be transmitted to the user equipment in the form of an interface document, i.e. the interface document records related information of the unified communication standard, such as a communication protocol, a data exchange format, a data structure, etc. The three drivers are implemented according to the interface document, and the user equipment interfaces with the road side equipment according to the interface document.

Thereafter, as shown in fig. 1, when the user equipment wants to communicate with (e.g. control or collect information from) a road side equipment of the RSU type, a data packet may be sent to the management and control equipment based on the communication protocol, the data exchange format, the data structure, etc. described in the first communication standard information, where the data packet may include a destination road side equipment identifier to characterize which type of road side equipment is wanted to communicate with.

In practical applications, optionally, the target roadside device identifier may include a device type identifier, and may further include a device vendor identifier and/or a device identifier. In addition, in practical application, the data packet may further include address information of the user side, information characterizing the user side, such as a user identifier. The data packet may further include an operation type and specific operation content, where the operation type is used to indicate which type of operation the user side device wants to perform on the road side device through the user device, such as information collection, state control, content distribution, and so on. Wherein the content of the operation may be default under certain operation types. In the case of content delivery of this type of operation, the corresponding operation content may be related description information of the content to be delivered (e.g., what the content is, what the font, format, etc. of the content is). In the case of the state control of this operation type, the operation contents may be corresponding control instruction contents such as on, off, lighting-off, and the like.

After receiving the data packet sent by the user equipment, the management and control equipment analyzes the data packet to obtain a target road side equipment identifier contained in the data packet, and further determines a target driver corresponding to the target road side equipment identifier according to the corresponding relation between each locally stored driver identifier and the road side equipment identifier, and sends the data packet to the target driver. In fig. 1, it is assumed that the target driver is driver c.

The target driver c converts the data packet according to the second communication standard information supported by the target driver c, converts the data packet into a data packet matched with the second communication standard information, and sends the converted data packet to the target road side equipment corresponding to the target road side equipment identifier. In the case of the RSU type road side device illustrated in fig. 1, the second communication standard information supported by the target driver C is the communication standard adopted by the RSU provided by the vendor C corresponding to the target driver.

In the above scheme, for the same type of road side equipment provided by different manufacturers, drivers corresponding to different manufacturers of the type are generated in advance, and the drivers corresponding to the same equipment type provide unified communication standards for the user side, and have communication standards adopted by the road side equipment respectively compatible with the corresponding manufacturers. And in a drive management mode, access of different manufacturers and different types of road side equipment is supported, namely, the user side realizes communication docking with the road side equipment through the developed drive programs.

Moreover, since all the drivers corresponding to the same equipment type provide unified communication standards for the user terminal, even if some manufacturer's road side equipment is newly added under the equipment type, only development of the corresponding drivers is needed, and the developed drivers are registered in the management and control equipment, so that the user terminal does not need to modify the user terminal, i.e. the user terminal does not need to adaptively support the communication standards adopted by the manufacturer. Similarly, when a new device type is added, the user side only needs to adapt to the unified communication standard corresponding to the new device type once. Therefore, the cost of the butt joint of the user side and the road side equipment is reduced, and the access of the road side equipment is realized in a highly-expansile mode.

The following describes an example of a process of interfacing a user device with a roadside device when a vendor-provided roadside device is newly added under a certain device type with reference to fig. 2.

In fig. 2, an RSU of this type is still taken as an example, and on the basis of the embodiment shown in fig. 1, it is assumed that an RSU provided by a vendor D is added. At this time, it is necessary to develop a corresponding driver for the RSU provided by the new manufacturer, and it is assumed that a corresponding driver d is developed. It will be appreciated that driver D is implemented according to the unified first communication standard described above, i.e. driver D supports the first communication standard, and in addition, driver D also supports the second communication standard adopted by RSUs provided by vendor D corresponding thereto. After the development of the driver D is completed, the registration information of the driver D is sent to the management and control device, so that the driver D and the corresponding road side device identifier thereof are stored in the management and control device, namely the RSU provided by the manufacturer D. Because only the road side equipment of a certain manufacturer is newly added under the existing equipment type, the management and control equipment can inform the user equipment what the newly added road side equipment identifier is under the certain equipment type for the user equipment to store, and the user equipment does not need to carry out any modification operation related to the communication standard.

When the user equipment wants to control the RSU provided by the vendor D, a data packet may still be sent to the management and control device based on the first communication standard, where the target roadside device identifier included in the data packet corresponds to the RSU of the vendor D, after the management and control device determines the driver D corresponding to the target roadside device identifier, the data packet is sent to the driver D, the driver D converts the data packet based on the second communication standard corresponding to the vendor D, and the converted data packet is sent to the corresponding target roadside device.

The above general description of the process of interfacing a user device with a roadside device for communication is provided, and an alternative implementation of the process of interfacing a user device with a roadside device is illustrated below in connection with fig. 3.

Fig. 3 is an interaction flow chart of a communication method of a road side device according to an embodiment of the present invention, where, as shown in fig. 3, the method may include the following steps:

301. the management and control equipment acquires the corresponding road side equipment identifiers of the plurality of drivers, the operation types supported by the drivers and the first communication standard information supported by the drivers.

302. And the management and control equipment sends first communication standard information corresponding to the equipment type to the user equipment.

In this embodiment, it is still assumed that the plurality of drivers correspond to roadside devices of the same device type provided by a plurality of vendors, that is, the plurality of drivers correspond to a plurality of vendors corresponding to a certain device type one by one.

After the plurality of drivers are developed, the developer can write the first communication standard information corresponding to the user side, which is uniformly used by the plurality of drivers, into the management and control device so that the management and control device can send the first communication standard information to the user device.

Alternatively, the developer may register each driver in the management and control device, where the registration process simply writes the driver identifier and the roadside device identifier corresponding to the driver in the management and control device. Of course, alternatively, the driver may send its own registration information to the management and control device. For example, the target driver sends the target roadside device identifier corresponding to the target driver to the management and control device, and of course, the driver identifier of the target driver is also sent to the management and control device.

As described above, one of the plurality of drivers supports, in addition to the first communication standard information, a second communication standard information that is used by the roadside device of the device type provided by the vendor to which the one driver corresponds.

303. And the user equipment sends a data packet to the management and control equipment based on the first communication standard information, wherein the data packet comprises a target road side equipment identifier and a target operation type executed on the target road side equipment.

304. And the management and control equipment authenticates the user equipment according to the target road side equipment identifier and the target operation type, and if the user equipment is determined to have the authority of triggering the target operation type for the target road side equipment, a target driver corresponding to the target road side equipment identifier is determined in a plurality of drivers.

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 management and control device needs to perform authority check on the user device according to the target roadside device identifier and the target operation type. Specifically, whether the user equipment has the authority of operating the target road side equipment corresponding to the target road side equipment identifier or not is detected, and whether the user equipment can execute the operation corresponding to the target operation type on the target road side equipment or not is detected.

In practice, the management and control device may store operation authority information of different user ends to the roadside device in advance, so as to complete the authentication process based on the operation authority information.

For example, if the client is an advertiser, the operation authority information corresponding to the client stored in the management and control device in advance may be that the advertiser may use the advertisement board in a certain area range in a certain time range (such as two months) to issue the advertisement. Based on this, assuming that the target roadside device identifier carried in the data packet sent by the advertiser to the management and control device through the corresponding user device is not the identifier corresponding to the billboard, but is, for example, the identifier of the RSU, the management and control device may 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 destination roadside device identifier carried in the data packet triggered by the advertiser is actually an identifier corresponding to a billboard, when the operation authority information stored in the management and control device indicates that the advertiser can only use the billboard within a certain area, the management and control device determines the billboard within the area from the position information of each billboard stored locally, and the billboard serves as the destination roadside device corresponding to the destination roadside device identifier in the data packet. Based on the above, in the authentication process, it may be further determined that the user equipment can operate the target roadside device corresponding to the target roadside device identifier.

The above describes an exemplary procedure for authenticating whether a user equipment can operate a certain roadside device. For an operation type, in practice, multiple types of operations may be supported for a certain type of roadside device, but not all users may perform all operation types of operations for that type of roadside device. For example, road side devices of the type of speed limit sign generally have only the authority of the relevant departments such as traffic management to change the upper speed limit value of the speed limit sign, and other users have only the authority to read the speed limit value. That is, the related departments of traffic management and the like can perform both types of operations of reading and modifying, and other users can perform only the type of operations of reading. The management and control equipment stores the operation type authority information of different users to different types of road side equipment so as to authenticate.

When the control device determines that the user device has the right to trigger the target operation type for the target road side device, determining a target driver corresponding to the target road side device identification from a plurality of drivers. Otherwise, when the control device determines that the user device does not have the authority to trigger the target operation type for the target road side device, the control device exits the processing of the data packet triggered by the user device, and can feed back error prompt information to the user device.

And the management and control equipment searches the target driver corresponding to the target road side equipment identifier according to the corresponding relation between the locally stored driver identifiers and the road side equipment identifiers.

In practical applications, the driver may be configured to send registration information to the management and control device after being started and run, if a certain driver is not started, the management and control device may not obtain the registration information of the driver, and based on this, the management and control device may not query the stored registration information of the driver for the target driver corresponding to the target roadside device identifier. At this time, assuming that the plurality of drivers for which registration information has been obtained are drivers in an operating state, if a target driver corresponding to a target roadside device identifier is not determined among the plurality of drivers, the management and control device acquires registration information of other drivers in an unoperated state, and if it is determined that there is a target driver corresponding to the target roadside device identifier in the other drivers, the target driver is started.

As described above, the developed driver may be stored in a device independent of the corresponding roadside device, or may be installed in the corresponding roadside device, and the device storing the driver may have information about the driver recorded therein, such as a corresponding roadside device identifier, wherever the driver is located. The management and control device may send a query instruction to the device to query whether a target driver corresponding to the target roadside device identifier exists, and if so, start the target driver, so as to send a data packet sent by the user device to the target driver, and in addition, may synchronize registration information of the target driver to the local. If not, a driver generation task is generated, and the driver generation task instructs to generate a driver corresponding to the target roadside device identifier.

305. The management and control device determines that the target driver supports the target operation type.

And if the management and control equipment finds the target driver corresponding to the target road side equipment identifier according to the corresponding relation between the locally stored driver identifiers and the road side equipment identifiers, optionally, further determining whether the target driver supports the target operation type based on the target operation type contained in the data packet.

In practical applications, when a developer develops a driver corresponding to a roadside device of a vendor of a certain device type, the driver may be configured to support all of the multiple operation types, and may also be configured to support only some of the operation types, assuming that the roadside device provided by the vendor has multiple operation types. When only part of the operation types are supported, it means that if the target operation type triggered by the user does not match the part of the operation types supported by the driver, communication between the user equipment and the vendor's roadside equipment cannot be achieved by the driver.

Therefore, optionally, the management and control device may further store operation type information supported by each driver, where the information may be registered in the management and control device by the driver, or may be written in the management and control device by a developer.

When the control device determines that the target driver supports the target operation type, the control device sends the data packet to the target driver.

306. The management and control device sends the data packet to the target driver.

307. The target driver converts the data packets based on a second communication standard employed by the target roadside device.

308. And the target driver program sends the converted data packet to the target road side equipment.

The relevant content of the embodiment, which is not described in the present embodiment, may refer to the relevant description in the foregoing embodiment, which is not repeated here.

As described above, the management and control apparatus in the above-described embodiments may be actually implemented to be composed of a plurality of bodies having different functions, and one composition form of the management and control apparatus and a docking process of the roadside apparatus with the user apparatus under the composition form are exemplarily described below with reference to fig. 4.

Fig. 4 is a schematic diagram of another communication system of a roadside device according to an embodiment of the present invention, where, as shown in fig. 4, the system includes a management and control device, a user device, a driver, and a roadside device, where the management and control device may include a gateway node, a task queue, a routing node, and a working node.

The various nodes may be physical devices or virtual machines. The nodes may be located in different physical machines or may be partially located in the same physical machine.

And the gateway node is responsible for API exposure and user authority management, and realizes the authority management and control of the granularity of equipment and operation functions.

And the task queue can be used for storing the task queue by using mysql and can be used for storing the data packet triggered by the user equipment.

And communicating with the driver through a set communication protocol to perform heartbeat maintenance and capacity synchronization.

And the working node is used for carrying out task processing in the task queue.

And the driver program supports the timing report and the driving capability report of the device list. The device list is composed of the road side device identifiers corresponding to the drivers, and the driving capability is the operation type supported by the drivers.

One implementation of interfacing user equipment with roadside equipment using the system shown in fig. 4 is described below.

As shown in fig. 4, a driver corresponding to a roadside device provided by a manufacturer, which is illustrated in a certain diagram, may send registration information to a routing node, where the registration information may include a roadside device identifier corresponding to the driver, a supported operation type performed on the roadside device, and so on.

Assuming that the developer has uploaded the first communication standard information unified adopted by the driver corresponding to the device type to the gateway node, the gateway node will send the first communication standard information to the user device.

The user equipment sends a data packet to the gateway node based on the first communication standard information, the gateway node stores the data packet into a task queue, the task queue feeds back successful information of submission, and the gateway node feeds back successful information of submission to the user equipment. The user equipment may then poll the result of processing the data packet according to the identification of the data packet.

As described above, optionally, the gateway node may perform the authentication procedure described above after receiving the data packet, and the gateway node stores the data packet sent by the ue in the task queue after the data packet passes the authentication.

The work node periodically polls the task queue to get the task, i.e. the data packet stored in the task queue. And after the data packet is read, analyzing to obtain the target road side equipment identifier and the target operation type contained in the data packet. The routing node is queried for a driver matching the target roadside device identifier and the target operation type, which is assumed to be the driver illustrated in fig. 5. The working node further sends the data packet to the driver, the driver converts the data packet based on a second communication standard adopted by the corresponding road side device, and the converted data packet is sent to the corresponding road side device.

And the road side equipment executes 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 for the gateway node to feed back to the user equipment.

The scheme abstracts the butt joint flow of the user equipment and the road side equipment into the processing procedures of a gateway node, task processing and a driving program. After developing the corresponding driving program of the road side equipment of different manufacturers, registering the driving program on 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. a data packet) to enter a task queue, and then based on the registration information of different drivers, the control information is executed to the road side equipment through the corresponding drivers.

In summary, the embodiment of the invention provides a unified extensible access framework for road side equipment, and for each type of road side equipment, protocol standardization for user equipment can be realized without the need of a user side to be compatible with communication standards adopted by the road side equipment provided by various manufacturers. And in a drive management mode, different manufacturers and different types of road side equipment are supported to be accessed. So that the user terminal can realize the communication with more paths of side devices at lower cost.

The roadside device communication apparatus of one or more embodiments of the present invention will be described in detail below. Those skilled in the art will appreciate that these means may be configured by the steps taught by the present solution using commercially available hardware components.

Fig. 5 is a schematic structural diagram of a communication device of a roadside apparatus according to an embodiment of the present invention, where the device is located in a management and control apparatus, and as shown in fig. 5, the device includes an obtaining module 11, a sending module 12, a receiving module 13, and a determining module 14.

The obtaining module 11 is configured to obtain a roadside device identifier corresponding to each of a plurality of drivers and first communication standard information supported by each of the plurality of drivers, where the plurality of drivers correspond to roadside devices of a same device type provided by a plurality of vendors, and one of the drivers further supports second communication standard information, where the second communication standard information is adopted by the roadside device of the device type provided by one of the vendors.

A sending module 12, configured to send the first communication standard information to a user equipment.

And the receiving module 13 is configured to receive a data packet sent by the user equipment based on the first communication standard information, where the data packet includes a target roadside device identifier.

A determining module 14, configured to determine a target driver corresponding to the target roadside device identifier from the multiple drivers.

The sending module 12 is further configured to send 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.

Optionally, the obtaining module 11 is further configured to obtain operation types supported by each of the plurality of drivers, and the data packet further includes a target operation type executed on the target roadside device. The sending module 12 is further configured to send the data packet to the target driver if it is determined that the target driver supports the target operation type.

Optionally, the determining module 14 is further configured to authenticate the user equipment according to the target roadside device identifier and the target operation type, and determine a target driver corresponding to the target roadside device identifier from the multiple drivers if it is determined that the user equipment has authority to trigger the target operation type for the target roadside device.

Optionally, the multiple drivers are drivers in an operating state, and the determining module 14 is specifically configured to obtain registration information of other drivers in an unoperated state if a target driver corresponding to the target roadside device identifier is not determined in the multiple drivers, start the target driver if it is determined that the target driver corresponding to the target roadside device identifier exists in the other drivers, and generate a driver generation task if it is determined that the target driver corresponding to the target roadside device identifier does not exist in the other drivers, where the driver generation task indicates to generate a driver corresponding to the target roadside device identifier.

The apparatus shown in fig. 5 may perform the steps performed by the control device in the foregoing embodiments, and the detailed performing process and technical effects are referred to the descriptions in the foregoing embodiments, which are not repeated herein.

In one possible design, the configuration of the roadside device communication apparatus shown in fig. 5 may be implemented as a management device, which may include a first processor 21, a first memory 22, and a first communication interface 23, as shown in fig. 6. Wherein the first memory 22 has stored thereon executable code which, when executed by the first processor 21, causes the first processor 21 to at least perform the steps performed by the managing device in the previous embodiments.

Fig. 7 is a schematic structural diagram of a communication device of a roadside apparatus according to an embodiment of the present invention, where the device is located in a user equipment, and as shown in fig. 7, the device includes a receiving module 31 and a transmitting module 32.

The receiving module 31 is configured to receive a first communication standard supported by each of a plurality of drivers sent by a management and control device, where the plurality of drivers correspond to a roadside device of a same device type provided by a plurality of vendors, one of the drivers further supports a second communication standard information, where the second communication standard information is adopted by the roadside device of the device type provided by one of the vendors, and the management and control device stores a roadside device identifier corresponding to each of the plurality of drivers.

And the sending module 32 is configured to send a data packet to the management and control device based on the first communication standard information, where the data packet includes a target roadside device identifier, so that the management and control device determines, from the multiple drivers, a target driver corresponding to the target roadside device identifier, send 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 send the converted data packet to the target roadside device.

The apparatus shown in fig. 7 may perform the steps performed by the ue in the foregoing embodiments, and the detailed performing process and the technical effects are referred to the descriptions in the foregoing embodiments and are not repeated herein.

In one possible design, the configuration of the roadside device communication apparatus shown in fig. 7 may be implemented as a user device, which may include a second processor 41, a second memory 42, and a second communication interface 43, as shown in fig. 8. Wherein the second memory 42 has stored thereon executable code which, when executed by the second processor 41, causes the second processor 41 to at least perform the steps performed by the user equipment as in the previous embodiments.

Fig. 9 is a schematic structural diagram of a communication device of a road side device according to an embodiment of the present invention, where the device is located in a driving device installed with a driving program, and as shown in fig. 9, the device includes a sending module 51 and a receiving module 52.

The sending module 51 is configured to send, to a management and control device, a target roadside device identifier corresponding to the target driver, where the management and control device stores roadside device identifiers corresponding to multiple drivers, where the target driver is one of the multiple drivers, the multiple drivers correspond to roadside devices of a same device type provided by multiple vendors, and each of the multiple drivers supports first communication standard information, where one of the drivers also supports second communication standard information, where the second communication standard information is adopted by the roadside device of the device type provided by one of the vendors.

The receiving module 52 is configured to receive a data packet sent by a management and control device, where the data packet is sent by a user device according to the first communication standard information sent by the management and control device, the data packet includes the target roadside device identifier, and the management and control device determines, from the multiple drivers, the target driver corresponding to the target roadside device identifier, and sends the data packet to the target driver.

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.

Optionally, the sending module 51 is further configured to send, to the management and control device, a target operation type supported by the target driver, where the data packet further includes the target operation type executed on the target roadside device. The receiving module 52 is specifically configured to receive the data packet sent by the control device after determining that the target driver supports the target operation type.

The device shown in fig. 9 may perform the steps performed by the driver in the foregoing embodiments, and the detailed execution process and technical effects are referred to the description in the foregoing embodiments, which are not repeated herein.

In one possible design, the configuration of the roadside device communication apparatus shown in fig. 9 may be implemented as a driving device, and as shown in fig. 10, 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 driver, which when executed by the third processor 61, enables the third processor 61 to at least implement steps corresponding to the driver in the foregoing embodiments.

In addition, embodiments of the present invention provide a non-transitory machine-readable storage medium having executable code stored thereon, which when executed by a processor of an electronic device, causes the processor to at least implement a roadside device communication method as provided in the previous embodiments.

The apparatus embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separate. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art will understand and implement the present invention without undue burden.

From the above description of the embodiments, it will be apparent to those skilled in the art that the embodiments may be implemented by adding necessary general purpose hardware platforms, or may be implemented by a combination of hardware and software. Based on such understanding, the foregoing aspects, in essence and portions contributing to the art, may be embodied in the form of a computer program product, which may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

It should be noted that the above-mentioned embodiments are merely for illustrating the technical solution of the present invention, and not for limiting the same, and although the present invention has been described in detail with reference to the above-mentioned embodiments, it should be understood by those skilled in the art that the technical solution described in the above-mentioned embodiments may be modified or some technical features may be equivalently replaced, and these modifications or substitutions do not make the essence of the corresponding technical solution deviate from the spirit and scope of the technical solution of the embodiments of the present invention.