WO2016127895A1 - 一种车路信息交互方法、设备及系统 - Google Patents

一种车路信息交互方法、设备及系统 Download PDF

Info

Publication number
WO2016127895A1
WO2016127895A1 PCT/CN2016/073362 CN2016073362W WO2016127895A1 WO 2016127895 A1 WO2016127895 A1 WO 2016127895A1 CN 2016073362 W CN2016073362 W CN 2016073362W WO 2016127895 A1 WO2016127895 A1 WO 2016127895A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
roadside device
vehicle terminal
identifier
vehicle
Prior art date
Application number
PCT/CN2016/073362
Other languages
English (en)
French (fr)
Inventor
林琳
房家奕
李凤
Original Assignee
电信科学技术研究院
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 电信科学技术研究院 filed Critical 电信科学技术研究院
Publication of WO2016127895A1 publication Critical patent/WO2016127895A1/zh

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40Support for services or applications

Definitions

  • the present invention relates to the field of communications technologies, and in particular, to a vehicle road information interaction method, device and system.
  • vehicle communication is an important part of it.
  • the main body of communication is the Service Provider and the Service User. If the service provider is a roadside device and the service user is an in-vehicle terminal, the main body of the communication is a roadside device and an in-vehicle terminal.
  • the main communication scenarios of the vehicle terminal and the roadside device include the roadside device providing the traffic life service and the management service to the vehicle terminal.
  • the specific service provided by the roadside device to the vehicle terminal in the scenario may include a traffic alert service and an entertainment life service, wherein the traffic alert service may be a road congestion situation, The wet and slippery situation, the wading situation, the road construction situation, the accident handling situation, the speed limit situation, etc., the entertainment life business can be weather, audio and video on demand, catering accommodation, ticket information, and the like.
  • the traffic alert service may be a road congestion situation, The wet and slippery situation, the wading situation, the road construction situation, the accident handling situation, the speed limit situation, etc.
  • the entertainment life business can be weather, audio and video on demand, catering accommodation, ticket information, and the like.
  • the roadside device provides management services to the vehicle terminal: in such a scenario, the roadside device manages the vehicle by technical means, and may include vehicle inspection, electronic charging, information statistics, and the like.
  • the vehicle road information interaction process in the above communication scenario includes an initialization process and a service interaction process.
  • the initialization process is sent by the roadside device to send an announcement message, and is divided into two cases as shown in FIG. 1 and FIG. 2 according to whether the vehicle terminal performs feedback.
  • the business data interaction process is the road.
  • the side device actively initiates; after the initialization process of the vehicle terminal without feedback is completed, the service data interaction process is initiated by the vehicle terminal.
  • the specific interaction methods are broadcast and unicast.
  • the first step the roadside device 1 sends a service advertisement message (SAM) including a service list to the in-vehicle terminal A, where the service list includes an identifier of the service;
  • SAM service advertisement message
  • the function of the above SAM is to let the in-vehicle terminal A know the service that the roadside device 1 can provide;
  • the second step the vehicle terminal A receives the SAM sent by the roadside device 1, matches the identifier of the service in the service list with the identifier of the service of the vehicle terminal A, and obtains a matching result;
  • the above matching result is the intersection of the service provided by the roadside device 1 and the service of the in-vehicle terminal A.
  • the third step the vehicle terminal A carries the matching result in the CTX (Service Context Messages) to the roadside device 1;
  • the fourth step the roadside device 1 transmits the service data to the in-vehicle terminal A according to the matching result.
  • a service interaction is performed between the subsequent roadside device and the in-vehicle terminal.
  • the in-vehicle terminal receives the REQW (Request message, response message expected)
  • the RES response message, acknowledging a REQW
  • the REQN REquest message, no response message expected
  • the first step the roadside device 1 sends an announcement message containing the service list to the vehicle terminal A;
  • the second step the vehicle terminal A receives the announcement message sent by the roadside device 1, and matches the identifier of the service in the service list with the identifier of the service of the vehicle terminal A, to obtain a matching result;
  • the third step the vehicle terminal A sends a service data request to the roadside device 1 according to the matching result;
  • the fourth step the roadside device 1 transmits a service data response to the vehicle terminal A.
  • the RES is fed back to the in-vehicle terminal; when the roadside device receives the REQN, it does not feed back to the in-vehicle terminal.
  • the above two ways of information interaction can provide a vehicle-interested service to the in-vehicle terminal within the coverage to a certain extent.
  • the two types of information interaction methods are in the initialization process.
  • Each time the vehicle terminal passes through a roadside device it needs to receive the service announcement sent by the roadside device and perform a large number of matching work, which will take a long time.
  • the length of time when the vehicle in which the vehicle terminal is located runs faster and/or the coverage of the roadside device is small, it is likely that the matching result is not sent to the roadside device when the vehicle has exited the coverage area.
  • the service data of the roadside device is still not received; in addition, for the service with high timeliness, even after receiving the service data sent by the roadside device according to the matching result after a long time, the service data is likely to be Has lost use value.
  • the existing vehicle road information interaction methods have the problems that the initialization process takes a long time and the business data interaction is delayed.
  • the embodiments of the present invention provide a method, a device, and a system for interacting with a vehicle road, which are used to solve the problem that the initialization process takes a long time and delays the interaction of service data in the prior art.
  • a method for interacting with a vehicle road information includes:
  • the service The demand matching information includes: an identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and a service that is interested in the in-vehicle terminal that each roadside device can provide Identification
  • the service data corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the roadside device is obtained from the roadside device. .
  • the service data corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the roadside device is obtained from the roadside device, including:
  • the service requirement matching information further includes: an identifier of each service that is interested in the in-vehicle terminal that can be provided by the roadside device Corresponding business interaction priority;
  • the service data request Transmitting, by the service data request, the service interaction priority corresponding to the part or all of the service and the identifier of the service that is interested in the in-vehicle device that is provided by the roadside device to the roadside device, so that the roadside
  • the device sequentially provides corresponding service data to the in-vehicle terminal according to the priority of the service interaction corresponding to the identifier from high to low.
  • the service data corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the roadside device is obtained from the roadside device, including:
  • the service requirement matching information further includes: an identifier of each service that is interested in the in-vehicle terminal that can be provided by the roadside device Corresponding business interaction priority;
  • the roadside device Sending, to the roadside device, the identifier of part or all of the services of the in-vehicle terminal that can be provided by the roadside device in the service requirement matching information, including:
  • the service interaction priority corresponding to the identifier and the identifier of the service is sent to the roadside device, so that the roadside device sequentially provides the corresponding service data to the vehicle terminal according to the service interaction priority corresponding to the identifier from high to low.
  • the method also includes:
  • the service requirement matching information further includes: a service interaction priority corresponding to the identifier of each service that is interested in the in-vehicle terminal;
  • the service data corresponding to the identifier of the service that the in-vehicle terminal is interested in including:
  • the service data request carrying the identifier of the service of the in-vehicle terminal that can be provided by the roadside device is sent to the roadside device in the order of the service interaction priority corresponding to the service identifier, and the roadside device is received.
  • the transmitted service data, the service data is determined by the roadside device according to the identifier of the service that the in-vehicle terminal is interested in.
  • the vehicle terminal determines the service demand matching information by any one of the following methods:
  • the service demand matching information is a coverage area of each roadside device that identifies the travel information and the service of interest and the stored roadside device The identification of the service that can be provided is matched;
  • the driving information and the identifier of the service are matched with the coverage area of the locally stored roadside device and the identifier of the service that can be provided, and the service demand matching information is obtained.
  • a method for interacting with a vehicle road information includes:
  • the vehicle terminal transmits the identification, driving information and sense of the vehicle terminal to the road interactive business management center
  • the identification of the service of interest so that the road interaction business management center determines the service demand matching information of the vehicle terminal according to the driving information and the identifier of the service of interest, and the service demand matching information includes: possible driving of the vehicle terminal An identifier of each roadside device on the route that can provide part or all of the services of interest to the in-vehicle terminal, and an identifier of a service that the in-vehicle terminal can provide provided by each roadside device;
  • the service data sent by the roadside device is received, and the service data is The roadside device is determined according to the identification of the vehicle terminal and the service demand matching information delivered by the road interaction service management center.
  • a vehicle road information interaction method includes:
  • the roadside device receives the identifier of the vehicle-mounted terminal and the service demand matching information of the vehicle-mounted terminal, and the service demand matching information includes: the vehicle-side terminal may provide the The identifier of each roadside device of part or all of the services of interest to the in-vehicle terminal, and the identification of the service of interest to the in-vehicle terminal that each roadside device can provide;
  • the service data corresponding to the service of the in-vehicle terminal that can be provided by the in-vehicle terminal can be transmitted to the in-vehicle terminal according to the service demand matching information.
  • the service demand matching information further includes: corresponding services of the in-vehicle terminal that the roadside device can provide Business interaction priority;
  • the service data corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the in-vehicle terminal including:
  • the service data corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the in-vehicle terminal is transmitted to the in-vehicle terminal in the order of the highest priority of the service interaction corresponding to each service.
  • the service that is interested in the in-vehicle terminal includes a management-type service
  • the service data that is of interest to the in-vehicle terminal is a management-regulated file transfer request
  • the method further includes:
  • the first management control type file transfer request sent by the identifier of the management control type service, where the first management control type file transfer request carries the identifier of the service server and the file identifier of the file requested for transmission;
  • the service data corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the in-vehicle terminal including:
  • the method further includes:
  • the fourth aspect relates to a vehicle road information interaction method, including:
  • the vehicle road interactive service management center receives the identifier of the vehicle terminal, the driving information of the vehicle terminal, and the identifier of the service of interest;
  • the service requirement matching information includes: The identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and the identifier of the service that the in-vehicle terminal can provide provided by each roadside device;
  • the driving information and the identifier of the service are matched with the stored coverage area of the roadside device and the identifier of the service that can be provided, and the service demand matching information of the vehicle terminal is obtained, including:
  • the identified identification of part or all of the services of interest to the in-vehicle terminal and the identification of the roadside device that can be provided by the roadside device are used as service demand matching information.
  • the service requirement matching information further includes: an identifier of each service that is interested in the in-vehicle terminal that can be provided by the roadside device Corresponding business interaction priority.
  • each roadside device in the process of matching the driving information and the identifier of the service of interest with the stored coverage area of each roadside device and the identifier of the service that can be provided, it is determined that each roadside device can be provided:
  • each service of interest of the in-vehicle terminal determining the number of roadside devices on the driving route where the roadside device is located, and providing the service
  • the service interaction priority is set for the identifier of the service of the roadside device according to the principle that the number of the roadside devices that can provide the service is lower.
  • an in-vehicle terminal includes:
  • the service requirement matching information includes: an identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and each roadside device can The identification of the service that is of interest to the in-vehicle terminal;
  • An obtaining module configured to: when the determining module determines that the identifier of the roadside device is included in an identifier of a roadside device capable of providing a service of interest to the in-vehicle terminal, acquiring, from the roadside device, an interested in-vehicle terminal The business data corresponding to the identity of the service.
  • the obtaining module includes: a first sending submodule and a first receiving submodule;
  • the first sending sub-module is configured to send, by the service data request, the identifier of part or all of the services of the in-vehicle terminal that the roadside device can provide in the service requirement matching information to the roadside device;
  • the first receiving submodule receives the service data sent by the roadside device, and the service data is determined by the roadside device according to the service data request.
  • the service requirement matching information further includes: an identifier of each service that is interested in the in-vehicle terminal that can be provided by the roadside device Corresponding business interaction priority;
  • the first sending sub-module is specifically configured to: through the service data request, the service interaction priority corresponding to part or all of the identification and the identifier of the service that is interested in the in-vehicle terminal that can be provided by the roadside device in the service requirement matching information.
  • the roadside device is sent to the in-vehicle terminal to provide corresponding service data in descending order of the service interaction priority corresponding to the identifier.
  • the acquiring module includes: a second sending submodule and a second receiving submodule;
  • the second sending sub-module is configured to send, to the roadside device, an identifier of all or part of services that are interested in the in-vehicle terminal that can be provided by the roadside device in the service requirement matching information;
  • the second receiving submodule is configured to receive service data sent by the roadside device, where the service The data is determined by the roadside device according to the identification of the service of interest to the in-vehicle terminal.
  • the service requirement matching information further includes: an identifier of each service that is interested in the in-vehicle terminal that can be provided by the roadside device Corresponding business interaction priority;
  • the second sending sub-module is specifically configured to send, to the service demand matching information, a service interaction priority corresponding to the identifier and the identifier of the part or all services of the in-vehicle terminal that the roadside device can provide, to the road
  • the side device is configured to enable the roadside device to provide corresponding service data to the in-vehicle terminal in descending order of the service interaction priority corresponding to the identifier.
  • the second sending sub-module is further configured to: after transmitting, to the roadside device, an identifier of a service that is interested in the in-vehicle terminal that can be provided by the roadside device in the service requirement matching information, Before the service data sent by the roadside device, the service data request is sent to the roadside device.
  • the service demand matching information further includes: a service interaction priority corresponding to the identifier of each service that is interested in the in-vehicle terminal;
  • the obtaining module includes: a third sending submodule and a third receiving submodule;
  • the third sending sub-module is configured to send, to the roadside device, an identifier of a service that is interested in the in-vehicle terminal that can be provided by the roadside device, in order of the service interaction priority corresponding to the identifier of the service, in descending order Business data request;
  • the third receiving sub-module is configured to receive service data sent by the roadside device, where the service data is determined by the roadside device according to the identifier of the service that the in-vehicle terminal is interested in.
  • the in-vehicle terminal further includes:
  • a determining module configured to send the driving information and the identifier of the service of interest to the road interaction business management center; receive the service demand matching information sent by the road interaction service management center, where the service demand matching information is the vehicle road interaction service management
  • the center obtains the driving information and the identifier of the service of interest and the stored coverage area of each roadside device and the identifier of the service that can be provided; or the driving information and the identification of the service of interest, and local storage
  • the coverage area of each roadside device is matched with the identifier of the service that can be provided, and the service requirement matching information is obtained.
  • an in-vehicle terminal includes:
  • the service demand matching information includes: an identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and a roadside device capable of providing The identification of the service of interest to the vehicle terminal;
  • a receiving module configured to receive the roadside device after the in-vehicle terminal establishes a connection with the roadside device indicated by the identifier of the roadside device that can provide part or all of the services of interest to the in-vehicle terminal.
  • the service data is sent, and the service data is determined by the roadside device according to the service demand matching information of the vehicle terminal delivered by the road interaction service management center.
  • a roadside device includes:
  • a receiving module configured to receive an identifier of the in-vehicle terminal delivered by the road inter-service management center and service matching information of the in-vehicle terminal, where the service demand matching information includes: an energy that may pass on the possible driving route of the in-vehicle terminal Providing an identifier of each roadside device of part or all of the services of interest to the in-vehicle terminal, and an identifier of a service of interest to the in-vehicle terminal that each roadside device can provide;
  • a transmission module configured to: after the roadside device establishes a connection with the in-vehicle terminal indicated by the identifier of the in-vehicle terminal, transmit, according to the service demand matching information, to the in-vehicle terminal, interested in the in-vehicle terminal that can be provided by the in-vehicle terminal The business data corresponding to the identity of the service.
  • the service demand matching information further includes: corresponding services of the in-vehicle terminal that the roadside device can provide Business interaction priority;
  • the transmission module is specifically configured to send, to the in-vehicle terminal, the service data corresponding to the identifier of the service that the in-vehicle terminal is interested in, according to the order in which the service interaction priorities of the services are from high to low.
  • the service of interest to the in-vehicle terminal includes a management control type service and the service data of interest to the in-vehicle terminal is a management control type file transmission request;
  • the receiving module is further configured to receive, by the service server, a first management control type file transmission request sent by the vehicle interaction service management center to send an identifier of the management control type service of the in-vehicle terminal, the first The management control file transfer request carries the identifier of the service server and the file identifier of the file requested for transmission;
  • the transmission module is specifically configured to send a second management control type file transmission request to the in-vehicle terminal, where the second management control type file transmission request carries the file identifier carried in the received first management control type file transmission request Receiving a second management control type file transmission response sent by the vehicle-mounted terminal, where the second management control type file transmission response carries file data corresponding to each of the file identifiers;
  • the transmitting module is further configured to: after receiving the second management-regulated file transmission response sent by the in-vehicle terminal, obtain the first control mode file transmission request from the second management-regulation file transmission response The file data corresponding to the file identifier in the management type file transfer request is sent, and the obtained data is sent to the service server indicated by the identifier of the service server in the first management type file transfer request.
  • a vehicle interaction business management center includes:
  • a receiving module configured to receive an identifier of the vehicle-mounted terminal, driving information of the vehicle-mounted terminal, and an identifier of the service of interest;
  • a matching module configured to match the driving information and the identifier of the service of interest with the stored coverage area of each roadside device and the identifier of the service that can be provided, to obtain service demand matching information of the vehicle terminal, the service
  • the demand matching information includes: an identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and a service that is interested in the in-vehicle terminal that each roadside device can provide Identification
  • a sending module configured to send the identifier of the in-vehicle terminal and the service demand matching information of the in-vehicle terminal to the roadside device indicated by the identifier of each roadside device, so that the roadside devices are determined to be in the vehicle
  • the service data is transmitted to the in-vehicle terminal according to the service demand matching information of the in-vehicle terminal.
  • the matching module is specifically configured to determine, according to the driving information, an in-vehicle terminal. For each determined driving route, the following operations are performed: determining the identification of the roadside device in the coverage area including the driving route and the identification of the service that each roadside device can provide; for each road on the driving route The side device determines whether the identifier of the part or all of the service of the in-vehicle terminal is included in the identifier of the service that the roadside device can provide; if the identifier of the service that can be provided by the roadside device is included in the identifier of the service provided by the roadside device, determining the roadside The identification of part or all of the services of interest to the in-vehicle terminal that the device can provide; the identification of the part or all of the services of the in-vehicle terminal that can be provided by the roadside device and the identification of the roadside device as the service demand matching information .
  • the service requirement matching information further includes: an identifier of each service that is interested in the in-vehicle terminal that can be provided by the roadside device Corresponding business interaction priority.
  • the matching module is specifically configured to determine, according to the following manner, a service interaction priority corresponding to an identifier of each service that the in-vehicle terminal can provide by each roadside device: for each capable of providing the in-vehicle terminal.
  • the roadside device with the number of services greater than one performs the following operations: for each roadside device capable of providing each service of interest to the in-vehicle terminal, determining the road side on the driving route where the roadside device is located to provide the service
  • the number of the devices is set according to the principle that the number of the roadside devices that can provide the service is lower, and the corresponding service interaction priority is set for the identity of the service of the roadside device.
  • a ninth aspect is a vehicle road information interaction system, the fifth aspect of the vehicle-mounted terminal and at least one roadside device.
  • a tenth aspect a vehicle road information interaction system, comprising: the vehicle-mounted terminal according to the sixth aspect, the roadway interactive service management center according to the eighth aspect, and the at least one roadside device according to any one of the seventh aspects.
  • an in-vehicle terminal includes: a processor, a transceiver, and a memory;
  • the transceiver is configured to receive and transmit data under control of a processor
  • the processor is configured to read a program in the memory and perform the following process:
  • the service requirement matching information includes: an identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and each road The identifier of the service that is interested in the in-vehicle terminal that can be provided by the side device; if it is determined that the identifier of the roadside device is included in the identifier of the roadside device capable of providing the service of interest to the in-vehicle terminal, then the transceiver is used from the roadside device Obtain the business data corresponding to the identifier of the service that the in-vehicle terminal is interested in.
  • an in-vehicle terminal comprising: a processor, a transceiver, and a memory;
  • the transceiver is configured to receive and transmit data under control of a processor
  • the processor is configured to read a program in the memory and perform the following process:
  • the service demand matching information includes: an identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and each roadside device The identifier of the service that can be provided by the in-vehicle terminal;
  • the service data sent by the roadside device is received by the transceiver,
  • the service data is determined by the roadside device according to the identification of the vehicle terminal and the service demand matching information delivered by the roadway interaction service management center.
  • a roadside device comprising: a processor, a transceiver, and a memory;
  • the transceiver is configured to receive and transmit data under control of a processor
  • the processor is configured to read a program in the memory and perform the following process:
  • the service demand matching information includes: the possible passing on the possible driving route of the in-vehicle terminal The identification of each roadside device of the part or all of the services of interest to the in-vehicle terminal, and the identification of the service of the in-vehicle terminal that can be provided by each of the roadside devices; establishing a connection with the in-vehicle terminal indicated by the identification of the in-vehicle terminal After, according to the business needs The matching information is transmitted to the in-vehicle terminal through the transceiver to transmit the service data corresponding to the identifier of the service that the in-vehicle terminal is interested in.
  • a vehicle interaction service management center includes: a processor, a transceiver, and a memory;
  • the transceiver is configured to receive and transmit data under control of a processor
  • the processor is configured to read a program in the memory and perform the following process:
  • the service requirement matching information includes: The identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and the identifier of the service that the in-vehicle terminal can provide provided by each roadside device;
  • the in-vehicle terminal After establishing the connection, the in-vehicle terminal transmits the service data to the in-vehicle terminal through the transceiver according to the matching information of the in-vehicle terminal service demand.
  • the service requirement matching information since the service requirement matching information has been determined in advance, before the service data interaction process is performed, the service announcement message of the roadside device is not required, and the long-time matching work is not required, and the reduction is performed.
  • Business interaction complexity and latency ensure that subsequent business data interaction processes can be performed in a timely and efficient manner.
  • FIG. 1 is a schematic diagram of a flow of vehicle road information interaction provided by the background art of the present invention.
  • FIG. 2 is a second schematic diagram of a vehicle road information interaction process provided by the background art of the present invention.
  • FIG. 3 is a flowchart of one of vehicle road information interaction methods according to an embodiment of the present invention.
  • FIG. 4 is a schematic diagram of determining a service requirement matching information according to an embodiment of the present invention.
  • FIG. 5( a) is a flowchart of a second method for interacting with a vehicle road information according to an embodiment of the present invention
  • FIG. 5(b) is a flowchart of a second method of vehicle road information interaction according to an embodiment of the present invention.
  • FIG. 6 is a schematic diagram of interaction between a roadside device and an in-vehicle terminal according to an embodiment of the present invention
  • FIG. 7 is a second schematic diagram of interaction between a roadside device and an in-vehicle terminal according to an embodiment of the present invention.
  • FIG. 8 is a third schematic diagram of interaction between a roadside device and an in-vehicle terminal according to an embodiment of the present invention.
  • FIG. 9 is a schematic structural diagram of an information interaction system according to an embodiment of the present invention.
  • FIG. 10 is a flowchart of a third method of vehicle road information interaction according to an embodiment of the present invention.
  • FIG. 11 is a flowchart of a fourth method of vehicle road information interaction according to an embodiment of the present invention.
  • FIG. 12 is a flowchart of a fifth method of vehicle road information interaction according to an embodiment of the present invention.
  • FIG. 13 is a fourth schematic diagram of interaction between a roadside device and an in-vehicle terminal according to an embodiment of the present invention.
  • FIG. 14 is a schematic structural diagram of an in-vehicle terminal according to an embodiment of the present invention.
  • FIG. 15 is a schematic structural diagram of a specific implementation of an in-vehicle terminal according to an embodiment of the present disclosure.
  • FIG. 16 is a second schematic diagram of a specific implementation structure of an in-vehicle terminal according to an embodiment of the present disclosure.
  • FIG. 17 is a third schematic structural diagram of a specific implementation of an in-vehicle terminal according to an embodiment of the present invention.
  • FIG. 18 is a schematic structural diagram of another vehicle-mounted terminal according to an embodiment of the present disclosure.
  • FIG. 19 is a schematic structural diagram of another roadside device according to an embodiment of the present invention.
  • FIG. 20 is a schematic structural diagram of a vehicle road interaction service management center according to an embodiment of the present invention.
  • FIG. 21 is a schematic structural diagram of hardware of an in-vehicle terminal according to an embodiment of the present disclosure.
  • FIG. 22 is a schematic structural diagram of another hardware of an in-vehicle terminal according to an embodiment of the present disclosure.
  • FIG. 23 is a schematic structural diagram of hardware of a roadside device according to an embodiment of the present disclosure.
  • FIG. 24 is a schematic structural diagram of hardware of a vehicle road interactive service management center according to an embodiment of the present invention.
  • the in-vehicle terminal or the roadside device determines the service demand matching information of the in-vehicle terminal in advance, and the service demand matching information includes: a part of the service route on the possible driving route of the in-vehicle terminal, which can provide part or all of the services of interest to the in-vehicle terminal.
  • the identifier of each roadside device and the identifier of the service that the in-vehicle terminal can provide provided by each roadside device; if the in-vehicle terminal determines the service demand matching information in advance, after the in-vehicle terminal establishes a connection with the roadside device, the in-vehicle terminal Determining whether the identifier of the roadside device is included in the identifier of the roadside device capable of providing part or all of the services of interest to the in-vehicle terminal, and determining that the identifier of the roadside device is included in the roadside capable of providing the service interested in the in-vehicle terminal
  • the service data corresponding to the identifier of the service that the in-vehicle terminal can provide is obtained from the roadside device, and since the roadside device establishes a connection with the in-vehicle terminal, it does not need to take longer in real time.
  • the matching operation directly obtains the service data from the roadside device according to the service demand matching information, because The business interaction complexity and delay are reduced, and the subsequent business data interaction process can be performed in a timely and efficient manner; if the roadside device determines the service demand matching information of the vehicle terminal in advance, it is represented by the identifier of the vehicle terminal. After the in-vehicle terminal establishes the connection, the roadside device directly transmits the service data corresponding to the service identifier of the service that the in-vehicle terminal can provide to the in-vehicle terminal according to the service demand matching information, and does not need to take longer in real time.
  • the matching work actively transmits the service data to the vehicle terminal, which also reduces the complexity and delay of the business interaction, and ensures that the subsequent business data interaction process can be performed in a timely and efficient manner.
  • the solution of the embodiment of the present invention is also applicable to the interaction between the generalized Service User and the Service Provider.
  • the two parties of the interaction we refer to the two parties of the interaction as the vehicle terminal and the roadside device, and the reader and the engineering technician can They are understood as the more general Service User and Service Provider.
  • the first type of vehicle road information is delivered.
  • the mutual method first describes the scheme with the vehicle-mounted terminal as the execution subject, and then describes the scheme with the road-side device as the execution subject, and finally describes the interaction process between the vehicle-mounted terminal and the road-side device;
  • the system for implementing the method will be described, and then the vehicle body, the roadside device, and the roadside interactive service management center will be described as the execution subject respectively, and finally the interaction process between the vehicle terminal and the roadside device will be described.
  • the first type of vehicle road information interaction method is a vehicle road information interaction method
  • one of the vehicle road information interaction methods provided by the embodiment of the present invention is described by using the vehicle-mounted terminal as an execution subject, and specifically includes the following steps:
  • Step 301 After establishing the connection between the in-vehicle terminal and the roadside device, determining, according to the determined service requirement matching information, whether the identifier of the roadside device is included in the identifier of the roadside device capable of providing part or all of the services of interest to the in-vehicle terminal, If the determination result is yes, step 302 is performed; if the determination result is no, step 303 is performed.
  • the service requirement matching information includes: an identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and a sense of the in-vehicle terminal that each roadside device can provide The identity of the business of interest.
  • the in-vehicle terminal may determine the service requirement matching information by using any one of the following manners or manners 2:
  • the driving information and the identification of the business of interest are transmitted to the road interactive business management center, and the driving information includes a driving route, or a departure place and destination information.
  • the service demand matching information is a coverage area of each roadside device that identifies the travel information and the service of interest and the stored roadside device The identity of the service that can be provided is matched.
  • the driving information and the identifier of the service are matched with the coverage area of the locally stored roadside device and the identifier of the service that can be provided, and the service demand matching information is obtained.
  • the essence of the above method 1 is online matching, and the essence of the second method is to perform matching locally.
  • the specific matching process can be the same.
  • the vehicle road interactive service management center and the vehicle-mounted terminal may have the function of navigating the map, so as to facilitate the inquiry of the driving route according to the departure place and the destination, and after the specific route is determined,
  • the roadside device with overlapping coverage area and the driving route may be first determined, and then the identification of the service that the roadside device can provide and the service interested in the in-vehicle terminal are determined for each determined roadside device.
  • the identification is matched to obtain an identifier of a service that is interested in the in-vehicle terminal that the roadside device can provide.
  • the service matching information may be determined for each driving route, and then the vehicle terminal may select a driving route according to the matching service demand matching information corresponding to the driving route.
  • the specific selection method may be determined according to actual needs. For example, the driving route corresponding to the service demand matching information with the most demanded services may be selected, and the driving route corresponding to the service demand matching information of a certain service capable of continuously providing the demand may be selected. It is also possible to select the driving route corresponding to the most reliable business demand matching information of one or several services that can provide the demand, etc.; the determination of the business demand matching information will be described below using FIG.
  • Step 302 Obtain, from the roadside device, service data corresponding to the identifier of the service that the in-vehicle terminal is interested in.
  • Step 303 the end.
  • step 302 can be implemented by using any one of the following manners: 1, 2, and 3:
  • Mode 1 including the following steps A1 and B1:
  • Step A1 Send the identifier of part or all of the services of the in-vehicle terminal that the roadside device can provide in the service requirement matching information to the roadside device through the service data request.
  • Step B1 Receive service data sent by the roadside device, where the service data is determined by the roadside device according to the service data request.
  • the in-vehicle terminal has completed the interaction of a certain service, the service data corresponding to the completed service is obtained, and it is determined that it is no longer necessary to be completed with other roadside devices.
  • the service identifier may not be carried in the service request when the service data request is sent to other roadside devices that can provide the service.
  • the service demand matching information further includes: corresponding to the identifier of each service that the in-vehicle terminal can provide by the roadside device Business interaction priority.
  • step A1 specifically includes:
  • the service interaction priority corresponding to the part or all of the service and the identifier of the service that the in-vehicle terminal is able to provide, to the roadside device, so that the roadside device corresponds to the identifier according to the identifier.
  • the service interaction priorities are sequentially supplied to the in-vehicle terminal to provide corresponding service data in descending order.
  • the above-mentioned service interaction priority may also be determined based on the priority specified by the vehicle-mounted terminal, so as to meet the demand of the vehicle-mounted terminal for the service of interest.
  • Mode 2 including the following steps A2 and B2:
  • Step A2 Send, to the roadside device, an identifier of all or part of services that are interested in the in-vehicle terminal that can be provided by the roadside device in the service requirement matching information.
  • Step B2 Receive service data sent by the roadside device, where the service data is determined by the roadside device according to the identifier of the service that is interested in the in-vehicle terminal.
  • the in-vehicle terminal has completed the interaction of a certain service, the service data corresponding to the completed service is obtained, and it is determined that the other roadside devices are no longer required to interact with the completed service. Then, when the identifier of the service is sent to the other roadside device that can provide the service, the identifier of the completed service may not be sent to the other roadside device.
  • the service demand matching information further includes: corresponding to the identifier of each service that the in-vehicle terminal can provide by the roadside device Business interaction priority.
  • step A2 specifically includes:
  • the service interaction priority corresponding to the identifier and the identifier of the part or all the services of the in-vehicle terminal that can be provided by the roadside device to the roadside device, so that the roadside device corresponds to the identifier according to the identifier.
  • the service interaction priorities are sequentially supplied to the in-vehicle terminal to provide corresponding service data in descending order.
  • the method further includes:
  • Step C2 Send a service data request to the roadside device.
  • the solution for obtaining the service data from the roadside device implemented by the step A2, the step C2, and the step B2 is that after the vehicle-mounted terminal sends the service identifier to the roadside device, it may not be determined whether the roadside device needs to provide the service data. For the subsequent determination, the roadside device can be provided immediately. Therefore, the above step A2 is performed first, so that the roadside device can determine or prepare the service data in time, and then the vehicle terminal can immediately determine when the step C2 is performed.
  • the service data is sent to the in-vehicle terminal, and the in-vehicle terminal can obtain the service data by performing step B2 relatively quickly, thereby improving the efficiency of the business data interaction.
  • step B3 when the number of services of the in-vehicle terminal that can be provided by the roadside device is greater than 1, and the service requirement matching information further includes the service interaction priority corresponding to the identifier of each service that is interested in the in-vehicle terminal, the following steps are included.
  • step A3 the service data request carrying the identifier of the service of the in-vehicle terminal that can be provided by the roadside device is sent to the roadside device in the order of the service interaction priority corresponding to the service identifier.
  • Step B3 Receive service data sent by the roadside device, where the service data is determined by the roadside device according to the identifier of the service that is interested in the vehicle terminal.
  • a specific implementation manner of the foregoing steps A3 and B3 may be that the in-vehicle terminal sends an identifier of a service with a higher service interaction priority. After receiving the identifier of the service, the service interaction priority is sent again.
  • the service of the lower level or the service with the same priority as that of the last sent identity the specific process is: obtaining the service of the in-vehicle terminal that the roadside device can provide from the service requirement matching information
  • the identifier of the service with the highest priority of the service interaction is carried in the service data request and sent to the roadside device; the service data sent by the roadside device according to the identifier of the service received by the roadside device is received;
  • the service identifier of the service with the second highest priority is carried in the service data request and sent to the roadside device; the service data sent by the roadside device according to the identifier of the service received by the roadside device is received; and so on, until the corresponding The service data corresponding to the service with the lowest priority of the business
  • Another specific implementation manner of the foregoing steps A3 and B3 may be that the service identifiers are sent according to the service interaction priority order, regardless of whether the service data corresponding to the identifier of the sent service is received.
  • the service of interest to the in-vehicle terminal may include management of the control type service
  • the service data of interest to the in-vehicle terminal at this time is a management control type file transmission request
  • different management regulations may require the vehicle terminal to provide different files.
  • all the files are provided to the roadside device at one time.
  • the method further includes: receiving a second management control type file transmission request sent by the roadside device, where the second management The control file transfer request carries at least two file identifiers; determines file data corresponding to each file identifier in the at least two file identifiers; and sends a second management control file transfer response to the roadside device, the second management The control file transfer response carries file data corresponding to each of the file identifiers.
  • the services that the roadside device 00001 can provide are: service 1, service 3, service 5, service 6, and service 7.
  • the services that the roadside device 00002 can provide are: service 2, service 3, service 5, service 7, and service. 9;
  • the service that the roadside device 00003 can provide is: service 2, service 7, service 9, service 15;
  • the services that the roadside device 00004 can provide are: service 1, service 2, service 6, service 9; roadside device 00005
  • the services that can be provided are: business 1, business 3, business 8, and business 14.
  • the service requirement matching information corresponding to the path P1 is obtained by matching the identifiers of the services of the in-vehicle terminal to the service-side matching information of the road-side device 00001 and the road-side device 00002 on the path P1.
  • the roadside device 0001 can provide service 1, service 3, and the roadside device 0002 can provide service 2 and service 3.
  • the service requirement matching information corresponding to the path P2 is obtained by matching the identifiers of the services of the in-vehicle terminal with the traffic of the service provided by the roadside device 00001 and the roadside device 0003.
  • the roadside device 0001 can provide the service 1
  • the service 3 can provide the service 2
  • the roadside device 0005 can provide the service 1 and the service 3.
  • the service requirement matching information corresponding to the path P3 is obtained by matching the identifiers of the services of the in-vehicle terminal to the service side information of the service provided by the roadside device 00004 and the roadside device 00005.
  • the roadside device 0004 can provide service 1, service 2 and the roadside device 0005 can provide service 1, service 3.
  • business requirement matching information may further include:
  • the recommended order of the service interaction with the roadside device 0001 is the service 1, 3, that is, the service interaction priority corresponding to the service 1 is the highest, and the service interaction priority corresponding to the service 3 is the second highest. This is because the subsequent roadside equipment 0002 can provide service 3, but cannot provide service 1.
  • the recommended order of the service of the service with the roadside device 0004 is the service 2, 1, that is, the service interaction priority corresponding to the service 2 is the highest, and the service interaction priority corresponding to the service 1 is the second highest. This is because the subsequent roadside device 0005 can provide service 1, but cannot provide service 2.
  • both the roadside device 0001 and the roadside device 0005 can provide the service 1 and the service 3. Therefore, the recommended sequence of interaction with the roadside device 0001 and the roadside device 0005 is to avoid the road route.
  • the side device provides a certain service, but the situation is missed because the business interaction sequence is improperly arranged. Therefore, it is not necessary to set the corresponding service interaction priority for the service that each roadside device can provide.
  • the coverage area of the roadside device 0001 overlaps with the area where the path P2 is located. According to the statistical result, under the coverage of the roadside device 0001, most of the vehicle-mounted terminals only interact with the service 1, but have not had time to interact.
  • the recommended order of the service for the roadside device 00005 is the service 3, 1, that is, the service interaction priority corresponding to the service 3 is the highest, and the service interaction priority corresponding to the service 1 is the second highest.
  • the service requirement matching information is not limited to the foregoing content, and may include other content, such as the number of services of interest provided by the roadside device on the path, the average number of roadside devices providing each service of interest, and the roadside device coverage.
  • the scope the location of the roadside equipment that can provide a certain service, and so on.
  • the vehicle terminal determines that the roadside device 0001 can provide The service of interest to itself is service 1 and service 3, and then sends a data service request carrying service 1 and service 3 to the roadside device 0001 or transmits service 1 and service 3 to the roadside device; finally, receiving the roadside device 0001
  • the transmitted service data 1 assumes that the service data 3 is received in the future, and the vehicle in which the vehicle-mounted terminal is located has already exited the coverage of the roadside device 0001.
  • the vehicle-mounted terminal can record that the service 3 is not received in the service of interest.
  • the roadside device 0001 can also record the service data that the in-vehicle terminal does not receive the service 3.
  • the in-vehicle terminal starts to enter the coverage of the roadside device 0003, and establishes a connection with the roadside device 0003.
  • the in-vehicle terminal determines that the service of interest that the roadside device 0003 can provide is the service 2, and then sends the carrier to the roadside device 0003.
  • the in-vehicle terminal starts to enter the coverage of the roadside device 0005, and establishes a connection with the roadside device 0005.
  • the in-vehicle terminal determines that the service of interest to the roadside device 0005 can be service 1 and service 3, at this time, Since the service data of the service 1 has been obtained from the roadside device 0001, but the service data of the service 3 has not been obtained, the service data of the service 3 only needs to be obtained from the roadside device 0005, and the vehicle terminal can go to the road at this time.
  • the side device 0005 transmits a data service request carrying only the service 3 or transmits the service 3 to the roadside device; finally, the receiving roadside device 0005 transmits the service data of the service 3.
  • the service identifiers are the same, but the areas are different, and the corresponding service data may be different.
  • the terminal does not need to record whether the service has been obtained, and obtains, from the service requirement matching information, the identifier of the service that all the in-vehicle terminals can provide by the roadside device; and sends the service request carrying the identifier of the acquired service to the roadside device or The identifier of the acquired service may be sent to the roadside device.
  • the service of interest to the in-vehicle terminal may change, for example, one or several of the services of interest are added, and/or one or several are reduced.
  • the service information that the roadside equipment can provide may also change, for example, the service provided is increased by one or several, and/or reduced by one or several;
  • the in-vehicle terminal may perform processing according to a specific situation, for example, may choose not to process, or may send a service request or a service of interest to the roadside device for the change of the service of interest.
  • the change of the situation is reported to the roadside device, and the roadside device transmits the service data corresponding to the changed service of interest to the in-vehicle terminal according to the change of the service of interest to the in-vehicle terminal and the service of interest of the in-vehicle terminal that has been known.
  • the roadside device can process according to the specific situation. For example, the device can be selected or not, or the affected vehicle terminal can be determined first, and then the service change information provided is notified to the received device. The influential vehicle terminal or the service change information is notified to all the vehicle terminals in the coverage area, so that the subsequent vehicle terminal can send a service request to the roadside device according to the received service change information.
  • FIG. 5(a) and FIG. 5(b) a flow chart of the second method of vehicle road information interaction according to an embodiment of the present invention uses a roadside device as an execution subject, and FIG. 5(a) includes:
  • Step 501a The roadside device receives a service data request that is sent by the in-vehicle terminal and carries an identifier of part or all of the services of interest to the in-vehicle terminal;
  • Step 502a Determine service data corresponding to the received identifier of the service.
  • Step 503a Send the determined service data to the in-vehicle terminal.
  • Step 501b The roadside device receives the identifier of part or all of the services that are interested in receiving the in-vehicle terminal sent by the in-vehicle terminal;
  • Step 502b Determine service data corresponding to the received identifier of the service.
  • Step 503b Send the determined service data to the in-vehicle terminal.
  • the method further includes:
  • the traffic information request may not carry the identifier of part or all of the services of interest to the in-vehicle terminal, as the roadside device has already obtained the service identifier of the part or all of the services of the in-vehicle terminal.
  • step 503b specifically includes:
  • the determined service data is transmitted to the in-vehicle terminal.
  • the foregoing step 502b may specifically query the service data corresponding to the service identifier from the service server connected to the roadside device, and may also query the service corresponding to the service identifier locally from the roadside device when the service data is stored locally on the roadside device. After the data is queried, the service data may be stored in the cache of the roadside device to efficiently transmit the service data to the vehicle terminal when receiving the service data request.
  • the step 501a includes:
  • Step 502a and step 503a at this time specifically include: prior to the service interaction corresponding to the identifier
  • the service data is sequentially determined from high to low, and the corresponding service data is sequentially provided to the vehicle terminal.
  • the step 501b includes:
  • the step 502b and the step 503b specifically include: determining the service data in order from the highest to the lowest according to the service interaction priority corresponding to the identifier, and sequentially providing the corresponding service data to the vehicle terminal.
  • the spectrum resources of the vehicle-mounted terminal are reduced.
  • the number of times, in particular, the number of times the service of the small data volume that needs to establish a connection frequently occupies the spectrum resource is used.
  • the method further includes:
  • the service server 1 and the service server 2 respectively require the vehicle-mounted terminal to transmit the file 1 and the file 2 to itself, and the road-side device can request the transmission of the file 1 and the file 2 to the vehicle-mounted terminal in the same data transmission request, and the vehicle-mounted terminal packages
  • the file 1 and the file 2 are transmitted to the roadside device, and the roadside device transmits the file 1 and the file 2 to the service server 1 and the service server 2, respectively.
  • FIG. 6 is a schematic diagram of interaction between a roadside device and an in-vehicle terminal according to an embodiment of the present invention.
  • the vehicle terminal determines the service demand matching information in advance, and the vehicle terminal actively initiates a service interaction with the roadside device.
  • there is no initialization phase and the hollowing out initialization phase of FIG. 6 is for comparison with the background art, and It does not indicate that it is waiting for the length of the initialization phase in the background technology to perform business interaction.
  • the initialization phase is not required, and no business interaction is required without waiting.
  • FIG. 7 is a second schematic diagram of interaction between a roadside device and an in-vehicle terminal according to an embodiment of the present invention.
  • the corresponding initialization phase only needs the vehicle-mounted terminal to send the identifier of the service of the in-vehicle terminal that the roadside device can provide to the roadside device, and the specific implementation may be adopted.
  • the form of the service list is short in time, and is only used for comparison with the initialization phase in the background art, and the transmission service list may not be used as an initialization stage, since the roadside device has learned the identity of the service required by the vehicle terminal. Therefore, the business interaction phase is initiated by the roadside device.
  • FIG. 8 is a third schematic diagram of interaction between a roadside device and an in-vehicle terminal according to an embodiment of the present invention.
  • the vehicle-mounted terminal extracts the service-matching information, and reports the service-interesting list to the road-side device.
  • the service interaction initialization phase only includes the reporting of the service list, and the service interaction phase is initiated by the vehicle terminal.
  • REQW in FIG. 6, FIG. 7 and FIG. 8 represents a request message that needs to respond, and the emphasis is on indicating that a response is needed, that is, it needs to return YES, and the specific message is a request message or a service data. It is determined according to the above description, which is not limited herein. Of course, only REQW is illustrated in FIG. 6, FIG. 7, and FIG. 8, and REQN is not illustrated, and does not indicate the in-vehicle terminal and the road in the embodiment of the present invention. You cannot use REQN for service interaction between side devices.
  • the second type of vehicle road information interaction method is a vehicle road information interaction method
  • FIG. 9 it is a schematic structural diagram of an information interaction system according to an embodiment of the present invention, including a roadside device 91, an in-vehicle terminal 92, and a vehicle road interactive service management center 93.
  • the roadside device 91 is configured to register its own device identification, location, and coverage area with the vehicle road interaction service management center 93, and register information of services that can be provided by itself; this belongs to the infrastructure registration, and may not be updated; and the vehicle terminal Perform business data interaction.
  • the vehicle-mounted terminal 92 is configured to send the driving information and the third parameter information of the service of interest to the road-side interactive service management center 93, receive the service demand matching information sent by the road-side interactive service management center, and perform service data with the roadside device. Interaction.
  • the vehicle road interaction service management center 93 is configured to accept the registration and cancellation of the roadside device, receive the information of the service provided by the roadside device, provide the query to the vehicle terminal, and perform the matching of the service demand information.
  • the information interaction system may further include a service server 94.
  • the roadside device may not register the service information that can be provided by the roadside interaction service management center. It is executed by the service server connected to the roadside device.
  • the service server 94 is configured to register with the road-side interaction service management center which services are provided by the road-side devices, and update them in time; if the road-side device fails, delete the services provided at the road-side device. When the service server no longer provides services for the in-vehicle terminal through the roadside device, the service is deleted from the road interaction service management center.
  • the roadside device fails, and can be represented by a service update provided by the service server at the roadside device, such as deleting or temporarily not providing.
  • the third method of vehicle road information interaction provided by the embodiment of the present invention is described by using an in-vehicle terminal as an execution subject, and specifically includes the following steps:
  • Step 1001 The vehicle-mounted terminal sends the identification of the vehicle-mounted terminal, the driving information, and the identifier of the service of interest to the vehicle-side interactive service management center, so that the road-road interaction service management center determines the driving information according to the traveling information and the identifier of the service of interest.
  • the business needs of the vehicle terminal match the information.
  • Step 1002 Part or all of the industry that is interested in providing the vehicle terminal through the driving route After the roadside device indicated by the identifier of the roadside device establishes a connection, the service data sent by the roadside device is received, and the service data is the vehicle that is sent by the roadside device according to the roadway interaction service management center. The identity of the terminal and the service requirement matching information are determined.
  • the driving information includes a driving route, or a departure destination and destination information, where the service demand matching information includes: a part of the possible driving route of the in-vehicle terminal that can provide some or all of the services of interest to the in-vehicle terminal.
  • the delivery may be performed directly by the service server or the corresponding roadside device. In this case, there is no initialization phase, and the service interaction phase is initiated by the roadside device.
  • the vehicle road interaction service management center may notify the vehicle-mounted terminal of the service demand matching information, or may not notify the vehicle-mounted terminal; when notifying the vehicle-mounted terminal, the vehicle-mounted terminal may also actively send the service data to the roadside device.
  • Business data when receiving the identification of the data service request or the service, sends the identifier of the service that is inferred to the in-vehicle terminal issued by the vehicle interaction service management center to the in-vehicle terminal.
  • the fourth embodiment of the vehicle road information interaction method provided by the embodiment of the present invention is described by using the road side device as an execution subject, and specifically includes:
  • Step 1101 The roadside device receives the identifier of the vehicle-mounted terminal and the service demand matching information of the vehicle-mounted terminal, and the service demand matching information includes: the possible driving route of the vehicle-mounted terminal.
  • Step 1102 After establishing a connection with the in-vehicle terminal indicated by the identifier of the in-vehicle terminal, according to the service demand matching information, transmit, to the in-vehicle terminal, the service data corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the in-vehicle terminal. .
  • the service demand matching information further includes: corresponding services of the in-vehicle terminal that the roadside device can provide Business interaction priority.
  • the service data corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the in-vehicle terminal is transmitted to the in-vehicle terminal, including:
  • the service data corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the in-vehicle terminal is transmitted to the in-vehicle terminal according to the order of the service interaction priority corresponding to each service.
  • the service that is interested in the in-vehicle terminal includes a management-type service
  • the service data that is of interest to the in-vehicle terminal is a management-regulated file transfer request
  • the method further includes:
  • each service server Receiving, by each service server, a first management-regulation file transmission request sent by the vehicle-side interactive service management center to send an identifier of the management-type control service of the in-vehicle terminal, where the first management-regulation file transmission request is carried There is an identification of the business server and a file identifier of the file requested for transmission.
  • the service data corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the in-vehicle terminal is transmitted to the in-vehicle terminal, including:
  • the method further includes:
  • the fifth method of the vehicle road information interaction method provided by the embodiment of the present invention is described by the vehicle road interaction service management center as an execution subject, which specifically includes:
  • Step 1200 The road interaction service management center receives the identifier of the vehicle terminal, the driving information of the vehicle terminal, and the identifier of the service of interest.
  • the driving information of the vehicle terminal received by the road interactive business management center here
  • the identifier of the service of interest may be sent by the vehicle terminal, or may be sent by other terminals, for example, a mobile phone terminal, a computer terminal, or the like, which is not limited by the embodiment of the present invention.
  • Step 1201 Match the driving information and the identifier of the service with the stored coverage area of each roadside device and the identifier of the service that can be provided, and obtain service demand matching information of the vehicle terminal, where the service requirement matches.
  • the information includes: an identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and an identifier of a service that is interested in the in-vehicle terminal that can be provided by each roadside device .
  • Step 1202 Send the identifier of the in-vehicle terminal and the service requirement matching information of the in-vehicle terminal to the roadside device indicated by the identifier of each roadside device, so that each roadside device determines the in-vehicle terminal.
  • the service data is transmitted to the in-vehicle terminal according to the service demand matching information of the in-vehicle terminal.
  • the driving information and the identifier of the service are matched with the stored coverage area of the roadside device and the identifier of the service that can be provided, and the service demand matching information of the vehicle terminal is obtained, including:
  • the coverage area includes the identification of the roadside device of the driving route and the identification of the service that each roadside device can provide.
  • the service requirement matching information further includes: an identifier of each service that is interested in the in-vehicle terminal that can be provided by the roadside device Corresponding business interaction priority.
  • each roadside device in the process of matching the driving information and the identifier of the service of interest with the stored coverage area of each roadside device and the identifier of the service that can be provided, it is determined that each roadside device can be provided:
  • each service of interest it is possible to provide each service of interest to the in-vehicle terminal, determine the number of roadside devices on the driving route where the roadside device is located, and provide the roadside device capable of providing the service; The lower the number, the higher the priority of the service interaction, and the corresponding service interaction priority is set for the identity of the service of the roadside device.
  • the vehicle road interaction service management center can refer to FIG. 4 and the foregoing description of FIG. 4, and details are not described herein again.
  • FIG. 13 is a fourth schematic diagram of interaction between a roadside device and an in-vehicle terminal according to an embodiment of the present invention.
  • the vehicle road interaction management center sends the service demand matching information of the vehicle terminal to the corresponding roadside device in advance, and the delivery may be directly delivered, or may be sent to the corresponding road through each service server.
  • the side device has no initialization phase in this case, and the service interaction phase is initiated by the roadside device.
  • the REQW in FIG. 13 indicates that there is a request message that needs to be responded, and the focus is to indicate that a response is required, that is, it needs to return YES.
  • the message is a request message or a service data, which can be determined according to the above description, which is not true here. It is limited.
  • the REQW is only illustrated in FIG. 13 and does not indicate the REQN. It does not indicate that the REQN cannot be used for service interaction between the in-vehicle terminal and the roadside device in the embodiment of the present invention.
  • the roadside device when the roadside device knows or determines the in-vehicle terminal service demand matching information in advance, the roadside device may be based on the service when the service is not differentiated or the service is not distinguished but the vehicle terminal is not distinguished.
  • the number of interested in-vehicle terminals is determined to be transmitted in a unicast or multicast manner. If the number of in-vehicle terminals exceeds a certain threshold, the roadside device may Establish a multicast group for multicast transmission.
  • the embodiment of the present invention further provides an in-vehicle terminal, a roadside device, a roadway interactive service management center, and a vehicle road information interaction system, because the vehicle-mounted terminal, the roadside device, and the roadway interactive service management center and the vehicle road
  • the principle of the problem solved by the information interaction system is similar to the foregoing information interaction method. Therefore, the implementation of the vehicle-mounted terminal, the roadside device, and the road-side interactive service management center can be referred to the implementation of the foregoing method, and the repeated description is not repeated.
  • FIG. 14 is a schematic structural diagram of an in-vehicle terminal according to an embodiment of the present invention, including:
  • the determining module 1401 is configured to determine, according to the determined service requirement matching information, whether the identifier of the roadside device is included in a path capable of providing part or all of services of interest to the in-vehicle terminal, after the in-vehicle terminal establishes a connection with the roadside device.
  • the service requirement matching information includes: an identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and each roadside device The identification of the service that can be provided by the in-vehicle terminal.
  • the obtaining module 1402 is configured to: when the determining module determines that the identifier of the roadside device is included in the identifier of the roadside device capable of providing the service of interest to the in-vehicle terminal, acquiring, from the roadside device, the interested in-vehicle terminal The identity of the business corresponds to the business data.
  • the specific implementation of the vehicle-mounted terminal can be divided into three different structures, as shown in FIG. 15 and FIG. 16 respectively. As shown in Figure 17, the following are introduced separately:
  • the obtaining module 1402 includes: a first sending submodule and a first receiving submodule.
  • the first sending sub-module is configured to send, by the service data request, the identifier of part or all of the services of the in-vehicle terminal that the roadside device can provide in the service requirement matching information to the roadside device.
  • the first receiving submodule is configured to receive service data sent by the roadside device, where the service data is determined by the roadside device according to the service data request.
  • the service demand matching information further includes: a label of each service that is interested in the in-vehicle terminal that the roadside device can provide Identify the corresponding business interaction priorities.
  • the first sending sub-module is specifically configured to pass the service interaction priority corresponding to part or all of the identifiers and identifiers of the services of the in-vehicle terminal that the roadside device can provide in the service requirement matching information.
  • the service data request is sent to the roadside device, so that the roadside device sequentially provides the corresponding service data to the in-vehicle terminal according to the priority of the service interaction corresponding to the identifier from high to low.
  • the obtaining module 1402 includes: a second sending submodule and a second receiving submodule.
  • the second sending sub-module is configured to send, to the roadside device, an identifier of all or part of services that are interested in the in-vehicle terminal that can be provided by the roadside device in the service requirement matching information.
  • the second receiving submodule is configured to receive service data sent by the roadside device, where the service data is determined by the roadside device according to the identifier of the service that is interested in the in-vehicle terminal.
  • the service requirement matching information further includes: an identifier of each service that is interested in the in-vehicle terminal that can be provided by the roadside device Corresponding business interaction priority.
  • the second sending sub-module is specifically configured to send, in the service requirement matching information, a service interaction priority corresponding to the identifier and the identifier of the part or all services of the in-vehicle terminal that the roadside device can provide.
  • the roadside device is provided to the roadside device to provide corresponding service data to the vehicle terminal in descending order of the service interaction priority corresponding to the identifier.
  • the second sending sub-module is further configured to: after transmitting, to the roadside device, an identifier of a service that is interested in the in-vehicle terminal that can be provided by the roadside device in the service requirement matching information, Before the service data sent by the roadside device, the service data request is sent to the roadside device.
  • the obtaining module 1402 includes: a third sending submodule and a third receiving submodule. 17 is a service interaction matching priority corresponding to the identifier of each service that is interested in the in-vehicle terminal when the number of services of the in-vehicle terminal that the roadside device can provide is greater than one; Schematic diagram of the structure of the terminal.
  • the third sending sub-module is configured to send, to the roadside device, the in-vehicle terminal that can be provided by the roadside device according to the order of the service interaction priority corresponding to the service identifier from high to low. Interesting business identification of business data requests.
  • the third receiving sub-module is configured to receive service data sent by the roadside device, where the service data is determined by the roadside device according to the identifier of the service that the in-vehicle terminal is interested in.
  • the in-vehicle terminal further includes: a determining module 1403, configured to send the driving information and the identifier of the service of interest to the roadway interaction service management center; and receive the service requirement matching information sent by the roadway interaction service management center,
  • the service demand matching information is obtained by the vehicle road interaction service management center matching the driving information and the identifier of the service of interest with the stored coverage area of each roadside device and the identifier of the service that can be provided; or
  • the information and the identifier of the service of interest are matched with the coverage area of the locally stored roadside device and the identifier of the service that can be provided, and the service demand matching information is obtained.
  • the embodiment of the present invention further provides a vehicle road information interaction system, which includes any of the above-mentioned vehicle-mounted terminals (as shown in FIG. 14, FIG. 15, FIG. 16, FIG. 17) and At least one roadside device, where the roadside device may be a roadside device of the prior art.
  • FIG. 18 is a schematic structural diagram of another vehicle-mounted terminal according to an embodiment of the present invention, including:
  • the sending module 1801 is configured to send, to the road interaction service management center, the identifier of the vehicle terminal, the driving information, and the identifier of the service of interest, so that the road interaction service management center determines the driving information according to the traveling information and the identifier of the service of interest.
  • the service demand matching information of the in-vehicle terminal includes: an identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and each road The identification of the service of interest to the in-vehicle terminal that the side device can provide.
  • the receiving module 1802 is configured to receive the roadside device after establishing the connection between the vehicle-side terminal and the roadside device indicated by the identifier of the roadside device that can provide part or all of the services of interest to the vehicle-mounted terminal.
  • the service data sent by the device is determined by the roadside device according to the identifier of the vehicle-mounted terminal and the service requirement matching information delivered by the roadway interaction service management center.
  • FIG. 19 is a schematic structural diagram of a roadside device according to an embodiment of the present invention, including:
  • the receiving module 1901 is configured to receive the identifier of the in-vehicle terminal and the service demand matching information of the in-vehicle terminal, where the service demand matching information includes: the possible driving route of the in-vehicle terminal The identification of each roadside device capable of providing part or all of the services of interest to the in-vehicle terminal, and the identification of the service of interest to the in-vehicle terminal that each roadside device can provide.
  • the transmission module 1902 is configured to: after the roadside device establishes a connection with the in-vehicle terminal indicated by the identifier of the in-vehicle terminal, according to the service demand matching information, transmit, to the in-vehicle terminal, an interested in-vehicle terminal that can be provided by the in-vehicle terminal The identity of the business corresponds to the business data.
  • the service demand matching information further includes: corresponding services of the in-vehicle terminal that the roadside device can provide Business interaction priority.
  • the transmission module 1902 is specifically configured to send, according to the order of the service interaction priority corresponding to each service, the service data corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the in-vehicle terminal.
  • the service of interest to the in-vehicle terminal comprises a management-type service and the service data of interest to the in-vehicle terminal is a management-regulated file transfer request.
  • the receiving module 1901 is further configured to receive, by each service server, a first management control type file transmission request that is sent according to an identifier of a management and control type service of interest of the in-vehicle terminal issued by the road interaction service management center, where The first management control type file transmission request carries an identifier of the service server and a file identifier of the file requested to be transmitted.
  • the transmission module 1902 is specifically configured to send a second management control type file transmission request to the in-vehicle terminal, where the second management control type file transmission request carries the received file in the first management control type file transmission request. And receiving the second management control type file transmission response sent by the vehicle-mounted terminal, where the second management control type file transmission response carries the file data corresponding to each of the file identifiers.
  • the transmission module 1902 is further configured to: after receiving the second management-regulation type file transmission response sent by the in-vehicle terminal, transmit a request for any first management-regulation type file, from the second management control type Obtaining the file data corresponding to the file identifier in the first management control class file transfer request, and transmitting the obtained data to the service server indicated by the identifier of the service server in the first management control class file transfer request .
  • FIG. 20 is a schematic structural diagram of a vehicle road interaction service management center according to an embodiment of the present invention, including:
  • the receiving module 2001 is configured to receive an identifier of the receiving vehicle terminal, driving information of the vehicle terminal, and an identifier of the service of interest.
  • a matching module 2002 configured to match the driving information and the identifier of the service of interest with the stored coverage area of each roadside device and the identifier of the service that can be provided, to obtain service demand matching information of the vehicle terminal,
  • the service requirement matching information includes: an identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, and an in-vehicle terminal that can be provided by each roadside device. The identity of the business.
  • the sending module 2003 is configured to send the identifier of the in-vehicle terminal and the service demand matching information of the in-vehicle terminal to the roadside device indicated by the identifier of each roadside device, so that each roadside device determines and After the in-vehicle terminal indicated by the identifier of the in-vehicle terminal establishes a connection, the service data is transmitted to the in-vehicle terminal according to the service demand matching information of the in-vehicle terminal.
  • the matching module 2002 is specifically configured to determine, according to the driving information, each driving route that is possible for the vehicle-mounted terminal. For each determined driving route, perform the following operations: determining a roadside device in which the coverage area includes the driving route And the identifier of the service that can be provided by each roadside device; for each roadside device on the driving route, determining whether the identifier of part or all of the services of interest to the in-vehicle terminal includes the identifier of the service that the roadside device can provide If it is included in the identifier of the service that the roadside device can provide, determine the identifier of part or all of the service that the roadside device can provide for the in-vehicle terminal; the determined in-vehicle terminal that the roadside device can provide The identification of some or all of the services of interest and the identification of the roadside device as the business requirement matching information.
  • the service requirement matching information further includes: an identifier of each service that is interested in the in-vehicle terminal that can be provided by the roadside device Corresponding business interaction priority.
  • the matching module 2002 is specifically configured to determine, according to the following manner, a service interaction priority corresponding to an identifier of each service that the in-vehicle terminal can provide by each roadside device: a sense of providing an in-vehicle terminal for each A roadside device having a number of services of interest greater than one performs the following operations: for each roadside device capable of providing each service of interest to the in-vehicle terminal, determining a route on the driving route where the roadside device is located to provide the service The number of the side devices is set according to the principle that the number of the roadside devices that can provide the service is lower, and the corresponding service interaction priority is set for the identity of the service of the roadside device.
  • the embodiment of the present invention further provides another vehicle road information interaction system, comprising: any of the vehicle-mounted terminals shown in FIG. 18, the road-way interactive service management center and any at least one of the diagrams shown in FIG. The roadside equipment shown in 19.
  • the vehicle-mounted terminal can obtain the information of the roadside device that can provide the service of its own interest on the driving route in advance from the vehicle-side interactive service management center, and does not depend on the service announcement, thereby reducing the complexity of the business interaction.
  • the interaction of the initialization phase is reduced or not, which saves the spectrum resources; further, the vehicle terminal can also know the priority of the service interaction with the roadside device for business interaction, and avoid the occurrence of the driving route.
  • a roadside device provides a certain service, but it is missed due to improper arrangement of business interactions; in the case where the roadside device knows the service demand matching information of the vehicle terminal in advance from the vehicle road business interaction management center, the roadside device
  • the services of the in-vehicle terminal can be transmitted in a multicast manner to save the spectrum resources.
  • the service server pushes the service data to the roadside device in advance, the service interaction delay can be further reduced.
  • the vehicles can be combined and managed to reduce the number of times the vehicle occupies spectrum resources. It applies to frequent the establishment of a small amount of data connection services.
  • FIG. 21 is a schematic structural diagram of hardware of an in-vehicle terminal according to an embodiment of the present invention, including:
  • the processor 2100 is configured to read a program in the memory 2120, and after the vehicle-mounted terminal establishes a connection with the roadside device, perform the following process:
  • the service demand matching information includes: a part of the possible driving route of the in-vehicle terminal that can provide some or all of the services of interest to the in-vehicle terminal.
  • the transceiver 2110 is configured to receive and transmit data under the control of the processor 2100.
  • the processor 2100 is specifically configured to read a program in the memory 2120 and perform the following process:
  • the identifier of the part or all of the services of the in-vehicle terminal that can be provided by the roadside device by using the service data request to be sent to the roadside device through the transceiver 2110; receiving the roadside through the transceiver 2110 The service data sent by the device, where the service data is determined by the roadside device according to the service data request.
  • the service requirement matching information further includes: an identifier of each service that is interested in the in-vehicle terminal that can be provided by the roadside device Corresponding service interaction priority; the processor 2100 is specifically configured to read the program in the memory 2120, and perform the following process:
  • the transceiver 2110 Transmitting, by the transceiver 2110, the service interaction priority corresponding to the part or all of the service and the identifier of the service that is interested in the in-vehicle terminal that can be provided by the roadside device to the roadside device, so that the roadside
  • the device sequentially provides corresponding service data to the in-vehicle terminal according to the priority of the service interaction corresponding to the identifier from high to low.
  • the processor 2100 is specifically configured to read a program in the memory 2120 and perform the following process:
  • the transceiver 2110 And transmitting, by the transceiver 2110, the service sent by the roadside device, by using the transceiver 2110, the identifier of all or part of the service that is interested in the in-vehicle terminal that can be provided by the roadside device in the service demand matching information is sent to the roadside device; Data, the service data is determined by the roadside device according to the identifier of the service that the in-vehicle terminal is interested in.
  • the service requirement matching information further includes: an identifier of each service that is interested in the in-vehicle terminal that can be provided by the roadside device Corresponding service interaction priority; the processor 2100 is specifically configured to read the program in the memory 2120, and perform the following process:
  • the service interaction priority corresponding to the identifier and the identifier of the part or all the services of the in-vehicle terminal that can be provided by the roadside device to the roadside device, so that the roadside device corresponds to the identifier according to the identifier.
  • the service interaction priorities are sequentially supplied to the in-vehicle terminal to provide corresponding service data in descending order.
  • the service data sent by the roadside device is received by the roadside device.
  • the processor 2100 is further configured to read a program in the memory 2120 and perform the following process:
  • a service data request is sent to the roadside device through the transceiver 2110.
  • the service demand matching information further includes: a service interaction priority corresponding to the identifier of each service that is interested in the in-vehicle terminal;
  • the processor 2100 is specifically configured to read a program in the memory 2120 and perform the following processes:
  • the service data request carrying the identifier of the service of the in-vehicle terminal that can be provided by the roadside device is sent to the roadside device in the order of the service interaction priority corresponding to the service identifier, and the roadside device is received.
  • the transmitted service data, the service data is determined by the roadside device according to the identifier of the service that the in-vehicle terminal is interested in.
  • the processor 2100 is specifically configured to read a program in the memory 2120 and perform the following process:
  • the driving information and the identifier of the service of interest are sent to the road interaction service management center through the transceiver 2110; the service demand matching information sent by the road interaction service management center is received, and the service demand matching information is the vehicle road interaction service management center. Matching the driving information and the identifier of the service of interest with the stored coverage area of each roadside device and the identifier of the service that can be provided Or;
  • the driving information and the identifier of the service are matched with the coverage area of the locally stored roadside device and the identifier of the service that can be provided, and the service demand matching information is obtained.
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 2100 and various circuits of memory represented by memory 2120.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 2110 can be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the user interface 2130 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 2100 is responsible for managing the bus architecture and general processing, and the memory 2120 can store data used by the processor 2100 in performing operations.
  • FIG. 22 is a schematic diagram of another hardware structure of an in-vehicle terminal according to an embodiment of the present invention, including:
  • the processor 2200 is configured to read a program in the memory 2220 and perform the following process:
  • the road interaction service management center determines the vehicle according to the driving information and the identification of the service of interest.
  • the service requirement matching information of the terminal where the service demand matching information includes: an identifier of each roadside device that can provide part or all of the services of interest to the in-vehicle terminal, and each roadside device that may be provided on the possible driving route of the in-vehicle terminal.
  • the identifier of the service that is interested in the in-vehicle terminal that can be provided after establishing a connection with the roadside device indicated by the identifier of the roadside device that can provide some or all of the services of interest to the in-vehicle terminal on the driving route,
  • the device 2210 receives the service data sent by the roadside device, and the service data is determined by the roadside device according to the identifier of the vehicle terminal and the service requirement matching information delivered by the roadway interaction service management center.
  • the transceiver 2210 is configured to receive and transmit data under the control of the processor 2200.
  • the bus architecture can include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 2200 and various circuits of memory represented by memory 2220.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 2210 may be a plurality of components, including a transmitter and a receiver, providing means for communicating with various other devices on a transmission medium.
  • the user interface 2230 may also be an interface capable of externally connecting the required devices, including but not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.
  • the processor 2200 is responsible for managing the bus architecture and general processing, and the memory 2220 can store data used by the processor 2200 in performing operations.
  • FIG. 23 it is a schematic diagram of a hardware structure of a roadside device according to an embodiment of the present invention, including:
  • the processor 2300 is configured to read the program in the memory 2320 and perform the following process:
  • the service demand matching information includes: the available driving route on the in-vehicle terminal The identification of each roadside device of the part or all of the services of interest to the in-vehicle terminal, and the identification of the service of interest to the in-vehicle terminal that each roadside device can provide.
  • the transceiver 2310 After establishing a connection with the in-vehicle terminal indicated by the identifier of the in-vehicle terminal, according to the service demand matching information, the transceiver 2310 transmits, to the in-vehicle terminal, a service corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the in-vehicle terminal. data.
  • the transceiver 2310 is configured to receive and transmit data under the control of the processor 2300.
  • the service demand matching information further includes: corresponding services of the in-vehicle terminal that the roadside device can provide Business interaction priority.
  • the processor 2300 is configured to read a program in the memory 2320, and specifically perform the following processes:
  • the service data corresponding to the identifier of the service of the in-vehicle terminal that can be provided by the in-vehicle terminal is transmitted to the in-vehicle terminal in the order of the highest priority of the service interaction priority corresponding to each service.
  • the service that is of interest to the in-vehicle terminal includes a management-type service and the service data of interest to the in-vehicle terminal is a management-regulated file transfer request.
  • the processor 2300 is further configured to read the program in the memory 2320 and perform the following process:
  • the transceiver 2310 Receiving, by the transceiver 2310, a first management control type file transmission request sent by each service server according to the identifier of the management control type service of the in-vehicle terminal issued by the vehicle road interaction service management center, the first management control type file
  • the transmission request carries the identifier of the service server and the file identifier of the file requested for transmission.
  • the processor 2300 is specifically configured to read a program in the memory 2320 and perform the following process:
  • the processor 2300 is further configured to read the program in the memory 2320 after receiving the second management-regulation file transmission response sent by the in-vehicle terminal, and perform the following process:
  • the bus architecture may include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 2300 and various circuits of memory represented by memory 2320.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • the transceiver 2310 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 2300 is responsible for managing the bus architecture and general processing, and the memory 2320 can store data used by the processor 2300 in performing operations.
  • FIG. 24 the hardware structure of the vehicle road interactive service management center according to the embodiment of the present invention is shown.
  • Schematic diagram including:
  • the processor 2400 is configured to read a program in the memory 2420 and perform the following process:
  • Matching obtaining the service demand matching information of the in-vehicle terminal, where the service demand matching information includes: an identifier of each roadside device on the possible driving route of the in-vehicle terminal that can provide part or all of the services of interest to the in-vehicle terminal, And the identification of the service of interest to the in-vehicle terminal that each roadside device can provide.
  • the service data is transmitted to the in-vehicle terminal through the transceiver 2410 according to the in-vehicle terminal service demand matching information.
  • the transceiver 2410 is configured to receive and transmit data under the control of the processor 2400.
  • the processor 2400 is specifically configured to read a program in the memory 2420 and perform the following processes:
  • the service requirement matching information further includes: an identifier of each service that is interested in the in-vehicle terminal that can be provided by the roadside device Corresponding business interaction priority.
  • the processor 2400 is further configured to read a program in the memory 2420 and perform the following process:
  • the vehicle terminal that can be provided by each roadside device is determined by the following manner
  • the service interaction priority corresponding to the identifiers of the services of interest for each roadside device capable of providing the number of services of interest of the in-vehicle terminal greater than 1, the following operations are performed: the sense of the in-vehicle terminal can be provided for the roadside device
  • For each service of interest determine the number of roadside devices on the driving route where the roadside device is located to provide the service; and the less the number of roadside devices that can provide the service, the higher the priority of the corresponding service interaction.
  • the principle is to set a corresponding service interaction priority for the identity of the service of the roadside device.
  • the bus architecture can include any number of interconnected buses and bridges, specifically linked by one or more processors represented by processor 2400 and various circuits of memory represented by memory 2420.
  • the bus architecture can also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be further described herein.
  • the bus interface provides an interface.
  • Transceiver 2410 can be a plurality of components, including a transmitter and a transceiver, providing means for communicating with various other devices on a transmission medium.
  • the processor 2400 is responsible for managing the bus architecture and general processing, and the memory 2420 can store data used by the processor 2400 in performing operations.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the apparatus implements the functions specified in one or more blocks of a flow or a flow and/or block diagram of the flowchart.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Traffic Control Systems (AREA)
  • Navigation (AREA)

Abstract

本发明实施例提供了一种车路信息交互方法、设备及系统,用以解决现有技术中存在初始化流程耗时较长而延误业务数据交互的问题。该方法包括:车载终端与路侧设备建立连接之后,根据确定的业务需求匹配信息,判断该路侧设备的标识是否包含在能提供车载终端感兴趣的部分或全部业务的路侧设备的标识中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;若确定该路侧设备的标识包含在能提供车载终端感兴趣的业务的路侧设备的标识中,则从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据。

Description

一种车路信息交互方法、设备及系统
本申请要求在2015年2月10日提交中国专利局、申请号为201510070028.7、发明名称为“一种车路信息交互方法、设备及系统”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本发明涉及通信技术领域,尤其涉及一种车路信息交互方法、设备及系统。
背景技术
在智能交通系统中,车路通信是其中重要的组成部分。通信的主体是服务提供者(Service Provider)和服务使用者(Service User)。若服务提供者为路侧设备,服务使用者为车载终端,则通信的主体即为路侧设备与车载终端。车载终端和路侧设备的主要通信场景包括路侧设备向车载终端提供交通生活类业务和管理类业务。
针对路侧设备向车载终端提供交通生活类业务:此类场景中路侧设备向车载终端提供的具体业务可以包括交通提示类业务以及娱乐生活类业务,其中,交通提示类业务可以为道路拥堵情况、湿滑情况、涉水情况、道路施工情况、事故处理情况、限速情况等,娱乐生活类业务可以为天气、音频视频点播、餐饮住宿、票务信息等。
针对路侧设备向车载终端提供管理类业务:此类场景中路侧设备通过技术手段对车辆进行管理,可以包括车辆稽查、电子收费、信息统计等。
上述通信场景中的车路信息交互流程包括初始化流程和业务交互流程,初始化流程由路侧设备发送公告消息,根据车载终端是否进行反馈又分为如图1和图2所示的两种情况。
图1中车载终端有反馈的初始化流程结束之后,业务数据交互流程是路 侧设备主动发起的;图2中车载终端没有反馈的初始化流程结束之后,业务数据交互流程是车载终端主动发起的。具体的交互方式有广播和单播。
下面通过具体的例子分别对图1和图2中所示的信息交互流程进行说明:
假设车载终端A当前处于路侧设备1的覆盖范围之内,针对图1,具体的信息交互流程如下:
第一步:路侧设备1向车载终端A发送包含有业务列表的SAM(Service Advertisement Message,业务公告消息),所述业务列表中包含有业务的标识;
上述SAM的作用是让车载终端A获知路侧设备1所能提供的业务;
第二步:车载终端A接收路侧设备1发送的SAM,将业务列表中的业务的标识与车载终端A感兴趣的业务的标识相匹配,获得匹配结果;
上述匹配结果即为路侧设备1提供的业务与车载终端A感兴趣的业务的交集。
第三步:车载终端A将获得的匹配结果携带在CTX(Service Context Messages,业务上下文消息)发送给路侧设备1;
第四步:路侧设备1根据所述匹配结果向车载终端A发送业务数据。
后续路侧设备与车载终端之间进行业务交互,其中,在车载终端接收到REQW(Request message,response message expected,需要响应的请求消息)时,向路侧设备反馈RES(Response message,acknowledging a REQW,响应REQW的应答消息);在车载终端接收到REQN(Request message,no response message expected,不需要响应的请求消息)时,不向路侧设备反馈。
针对图2,具体的信息交互流程如下:
第一步:路侧设备1向车载终端A发送包含有业务列表的公告消息;
第二步:车载终端A接收路侧设备1发送的公告消息,将业务列表中的业务的标识与车载终端A感兴趣的业务的标识相匹配,获得匹配结果;
第三步:车载终端A根据所述匹配结果向路侧设备1发送业务数据请求;
第四步:路侧设备1向车载终端A发送业务数据响应。
后续路侧设备与车载终端之间进行业务交互,其中,在路侧设备接收到 REQW时,向车载终端反馈RES;在路侧设备接收到REQN时,不向车载终端反馈。
上述两种信息交互方式一定程度上能为覆盖范围内的车载终端提供车辆感兴趣的业务,然而,考虑到一个路侧设备可能与多个服务器相连而提供大量的业务,而每个车载终端感兴趣的业务相对较少,两种信息交互方式在初始化流程中,车载终端每经过一个路侧设备均需要接收路侧设备发送的业务公告,以及进行大量的匹配工作,这将会占用较长的时长,在车载终端所在的车辆运行速度较快和/或路侧设备的覆盖范围较小的情况下,很可能会出现车辆已经驶出了覆盖区域时仍未将匹配结果发送给路侧设备,或者仍未收到路侧设备的业务数据;此外,对时效性要求较高的业务来说,即使在历经较长时长后收到了路侧设备根据匹配结果发送的业务数据,该业务数据很可能已经失去使用价值。
综上所述,现有的车路信息交互方式均存在初始化流程耗时较长而延误业务数据交互的问题。
发明内容
本发明实施例提供一种车路信息交互方法、设备及系统,用以解决现有技术中存在初始化流程耗时较长而延误业务数据交互的问题。
第一方面,一种车路信息交互方法,包括:
车载终端与路侧设备建立连接之后,根据确定的业务需求匹配信息,判断该路侧设备的标识是否包含在能提供车载终端感兴趣的部分或全部业务的路侧设备的标识中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
若确定该路侧设备的标识包含在能提供车载终端感兴趣的业务的路侧设备的标识中,则从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据。
较佳的,从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据,包括:
将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识通过业务数据请求发送给该路侧设备;
接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述业务数据请求确定的。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级;
将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的部分或全部标识通过业务数据请求发送给该路侧设备,包括:
将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的部分或全部标识和标识对应的业务交互优先级通过业务数据请求发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
较佳的,从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据,包括:
将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的全部或部分业务的标识发送给该路侧设备;
接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述车载终端感兴趣的业务的标识确定的。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级;
将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识发送给该路侧设备,包括:
将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部 分或全部业务的标识和标识对应的业务交互优先级发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
较佳的,在将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的标识发送给该路侧设备之后,接收该路侧设备发送的业务数据之前,所述方法还包括:
向该路侧设备发送业务数据请求。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的数量大于1时,所述业务需求匹配信息还包括:车载终端感兴趣的各业务的标识对应的业务交互优先级;
从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据,包括:
按照业务的标识对应的业务交互优先级由高到低的顺序,依次向该路侧设备发送携带该路侧设备能提供的车载终端感兴趣的业务的标识的业务数据请求,并接收路侧设备发送的业务数据,所述业务数据是路侧设备根据该车载终端感兴趣的业务的标识确定的。
较佳的,车载终端通过以下方式中的任一种确定业务需求匹配信息:
方式一:
将行驶信息和感兴趣的业务的标识发送给车路交互业务管理中心;
接收车路交互业务管理中心发送的业务需求匹配信息,所述业务需求匹配信息是车路交互业务管理中心将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配得到的;
方式二:
将行驶信息和感兴趣的业务的标识,与本地存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,得到业务需求匹配信息。
第二方面,一种车路信息交互方法,包括:
车载终端向车路交互业务管理中心发送车载终端的标识、行驶信息和感 兴趣的业务的标识,以使车路交互业务管理中心根据所述行驶信息和感兴趣的业务的标识确定该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
与行车路线上经过的能提供车载终端感兴趣的部分或全部业务的所述路侧设备的标识所表示的路侧设备建立连接之后,接收该路侧设备发送的业务数据,所述业务数据是该路侧设备根据车路交互业务管理中心下发的该车载终端的标识和业务需求匹配信息确定的。
第三方面,一种车路信息交互方法,包括:
路侧设备接收车路交互业务管理中心下发的车载终端的标识和该车载终端的业务需求匹配信息,其中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
在与所述车载终端的标识所表示的车载终端建立连接后,根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务对应的业务交互优先级;
根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据,包括:
按照各业务对应的业务交互优先级由高到低的顺序,向该车载终端发送自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
较佳的,所述车载终端感兴趣的业务包括管理管制类业务且车载终端感兴趣的业务数据为管理管制类文件传输请求,所述方法还包括:
接收各业务服务器根据车路交互业务管理中心下发所述车载终端的感兴 趣的管理管制类业务的标识发送的第一管理管制类文件传输请求,所述第一管理管制类文件传输请求中携带有该业务服务器的标识和请求传输的文件的文件标识;
根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据,包括:
向车载终端发送第二管理管制类文件传输请求,所述第二管理管制类文件传输请求中携带有接收的各第一管理管制类文件传输请求中携带的文件标识;
接收车载终端发送的第二管理管制类文件传输响应,所述第二管理管制类文件传输响应中携带有各所述文件标识对应的文件数据;
在接收车载终端发送的第二管理管制类文件传输响应之后,所述方法还包括:
针对任一第一管理管制类文件传输请求,从第二管理管制类文件传输响应中的获得该第一管理管制类文件传输请求中的文件标识对应的文件数据,将获得的数据发送给该第一管理管制类文件传输请求中的业务服务器的标识所表示的业务服务器。
第四方面,一种车路信息交互方法,包括:
车路交互业务管理中心接收车载终端的标识、该车载终端的行驶信息和感兴趣的业务的标识;
将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,获得该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
将所述车载终端的标识和所述车载终端的业务需求匹配信息下发给各路侧设备的标识所表示的路侧设备,以使各路侧设备在确定与所述车载终端的标识所表示的车载终端建立连接后,根据所述车载终端的业务需求匹配信息 向该车载终端发送业务数据。
较佳的,将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,获得该车载终端的业务需求匹配信息,包括:
根据所述行驶信息确定车载终端可能的各行车路线;
针对确定的每一行车路线,执行以下操作:
确定覆盖区域包含该行车路线的路侧设备的标识以及各路侧设备能够提供的业务的标识;
针对每一路侧设备,判断车载终端感兴趣的部分或全部业务的标识是否包含在该路侧设备能够提供的业务的标识中;
若包含在该路侧设备能够提供的业务的标识中,则确定该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识;
将确定的该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识记和该路侧设备的标识作为业务需求匹配信息。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级。
较佳的,在将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配的过程中,通过以下方式确定各路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级:
针对每一能提供车载终端的感兴趣的业务的数量大于1的路侧设备,执行以下操作:
针对该路侧设备能提供车载终端的感兴趣的每一业务,确定该路侧设备所在的行车路线上的能提供该业务的路侧设备的数量;并
按照能提供该业务的路侧设备的数量越少对应的业务交互优先级越高的原则,为该路侧设备的该业务的标识设置对应的业务交互优先级。
第五方面,一种车载终端,包括:
判断模块,用于在所述车载终端与路侧设备建立连接之后,根据确定的业务需求匹配信息,判断该路侧设备的标识是否包含在能提供车载终端感兴趣的部分或全部业务的路侧设备的标识中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
获取模块,用于在判断模块确定该路侧设备的标识包含在能提供车载终端感兴趣的业务的路侧设备的标识中时,从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据。
较佳的,所述获取模块包括:第一发送子模块和第一接收子模块;
所述第一发送子模块,用于将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识通过业务数据请求发送给该路侧设备;
所述第一接收子模块,接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述业务数据请求确定的。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级;
所述第一发送子模块,具体用于将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的部分或全部标识和标识对应的业务交互优先级通过业务数据请求发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
较佳的,所述获取模块包括:第二发送子模块和第二接收子模块;
所述第二发送子模块,用于将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的全部或部分业务的标识发送给该路侧设备;
所述第二接收子模块,用于接收该路侧设备发送的业务数据,所述业务 数据是路侧设备根据所述车载终端感兴趣的业务的标识确定的。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级;
所述第二发送子模块,具体用于将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识和标识对应的业务交互优先级发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
较佳的,所述第二发送子模块,还用于在将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的标识发送给该路侧设备之后,接收该路侧设备发送的业务数据之前,向该路侧设备发送业务数据请求。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的数量大于1时,所述业务需求匹配信息还包括:车载终端感兴趣的各业务的标识对应的业务交互优先级;所述获取模块包括:第三发送子模块和第三接收子模块;
所述第三发送子模块,用于按照业务的标识对应的业务交互优先级由高到低的顺序,依次向该路侧设备发送携带该路侧设备能提供的车载终端感兴趣的业务的标识的业务数据请求;
所述第三接收子模块,用于接收路侧设备发送的业务数据,所述业务数据是路侧设备根据该车载终端感兴趣的业务的标识确定的。
较佳的,所述车载终端还包括:
确定模块,用于将行驶信息和感兴趣的业务的标识发送给车路交互业务管理中心;接收车路交互业务管理中心发送的业务需求匹配信息,所述业务需求匹配信息是车路交互业务管理中心将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配得到的;或者将行驶信息和感兴趣的业务的标识,与本地存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,得到业务需求匹配信息。
第六方面,一种车载终端,包括:
发送模块,用于向车路交互业务管理中心发送行驶信息和感兴趣的业务的标识,以使车路交互业务管理中心根据所述行驶信息和感兴趣的业务的标识确定该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
接收模块,用于在所述车载终端与行车路线上经过的能提供车载终端感兴趣的部分或全部业务的所述路侧设备的标识所表示的路侧设备建立连接之后,接收该路侧设备发送的业务数据,所述业务数据是该路侧设备根据车路交互业务管理中心下发的该车载终端的业务需求匹配信息确定的。
第七方面,一种路侧设备,包括:
接收模块,用于接收车路交互业务管理中心下发的车载终端的标识和该车载终端的业务需求匹配信息,其中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
传输模块,用于在所述路侧设备与所述车载终端的标识所表示的车载终端建立连接后,根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务对应的业务交互优先级;
所述传输模块,具体用于按照各业务对应的业务交互优先级由高到低的顺序,向该车载终端发送自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
较佳的,所述车载终端感兴趣的业务包括管理管制类业务且车载终端感兴趣的业务数据为管理管制类文件传输请求;
所述接收模块,还用于接收各业务服务器根据车路交互业务管理中心下发所述车载终端的感兴趣的管理管制类业务的标识发送的第一管理管制类文件传输请求,所述第一管理管制类文件传输请求中携带有该业务服务器的标识和请求传输的文件的文件标识;
所述传输模块,具体用于向车载终端发送第二管理管制类文件传输请求,所述第二管理管制类文件传输请求中携带有接收的各第一管理管制类文件传输请求中携带的文件标识;接收车载终端发送的第二管理管制类文件传输响应,所述第二管理管制类文件传输响应中携带有各所述文件标识对应的文件数据;
所述传输模块,还用于在接收车载终端发送的第二管理管制类文件传输响应之后针对任一第一管理管制类文件传输请求,从第二管理管制类文件传输响应中的获得该第一管理管制类文件传输请求中的文件标识对应的文件数据,将获得的数据发送给该第一管理管制类文件传输请求中的业务服务器的标识所表示的业务服务器。
第八方面,一种车路交互业务管理中心,包括:
接收模块,用于接收车载终端的标识、该车载终端的行驶信息和感兴趣的业务的标识;
匹配模块,用于将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,获得该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
发送模块,用于将所述车载终端的标识和所述车载终端的业务需求匹配信息下发给各路侧设备的标识所表示的路侧设备,以使各路侧设备在确定与所述车载终端的标识所表示的车载终端建立连接后,根据所述车载终端的业务需求匹配信息向该车载终端发送业务数据。
较佳的,所述匹配模块,具体用于根据所述行驶信息确定车载终端可能 的各行车路线;针对确定的每一行车路线,执行以下操作:确定覆盖区域包含该行车路线的路侧设备的标识以及各路侧设备能够提供的业务的标识;针对该行车路线上的每一路侧设备,判断车载终端感兴趣的部分或全部业务的标识是否包含在该路侧设备能够提供的业务的标识中;若包含在该路侧设备能够提供的业务的标识中,则确定该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识;将确定的该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识记和该路侧设备的标识作为业务需求匹配信息。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级。
较佳的,所述匹配模块,具体用于通过以下方式确定各路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级:针对每一能提供车载终端的感兴趣的业务的数量大于1的路侧设备,执行以下操作:针对该路侧设备能提供车载终端的感兴趣的每一业务,确定该路侧设备所在的行车路线上的能提供该业务的路侧设备的数量;并按照能提供该业务的路侧设备的数量越少对应的业务交互优先级越高的原则,为该路侧设备的该业务的标识设置对应的业务交互优先级。
第九方面,一种车路信息交互系统,第五方面所述车载终端和至少一个路侧设备。
第十方面,一种车路信息交互系统,包括:第六方面所述的车载终端、第八方面所述的车路交互业务管理中心和至少一个第七方面任一所述的路侧设备。
第十一方面,一种车载终端,包括:处理器,收发机和存储器;
所述收发机用于在处理器的控制下接收和发送数据;
所述处理器,用于读取所述存储器中的程序,执行下列过程:
在所述车载终端与路侧设备建立连接之后,根据确定的业务需求匹配信息,判断该路侧设备的标识是否包含在能提供车载终端感兴趣的部分或全部 业务的路侧设备的标识中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;若确定该路侧设备的标识包含在能提供车载终端感兴趣的业务的路侧设备的标识中,则通过收发机从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据。
第十二方面,一种车载终端,包括:处理器,收发机和存储器;
所述收发机用于在处理器的控制下接收和发送数据;
所述处理器,用于读取所述存储器中的程序,执行下列过程:
通过收发机向车路交互业务管理中心发送车载终端的标识、行驶信息和感兴趣的业务的标识,以使车路交互业务管理中心根据所述行驶信息和感兴趣的业务的标识确定该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
与行车路线上经过的能提供车载终端感兴趣的部分或全部业务的所述路侧设备的标识所表示的路侧设备建立连接之后,通过收发机接收该路侧设备发送的业务数据,所述业务数据是该路侧设备根据车路交互业务管理中心下发的该车载终端的标识和业务需求匹配信息确定的。
第十三方面,一种路侧设备,包括:处理器,收发机和存储器;
所述收发机用于在处理器的控制下接收和发送数据;
所述处理器,用于读取所述存储器中的程序,执行下列过程:
通过收发机接收车路交互业务管理中心下发的车载终端的标识和该车载终端的业务需求匹配信息,其中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;在与所述车载终端的标识所表示的车载终端建立连接后,根据所述业务需求 匹配信息,通过收发机向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
第十四方面,一种车路交互业务管理中心,包括:处理器,收发机和存储器;
所述收发机用于在处理器的控制下接收和发送数据;
所述处理器,用于读取所述存储器中的程序,执行下列过程:
通过收发机接收车载终端的标识、行驶信息和感兴趣的业务的标识;
将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,获得该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
将所述车载终端的标识和所述车载终端的业务需求匹配信息下发给各路侧设备的标识所表示的路侧设备,以使各路侧设备在确定与所述车载终端的标识所表示的车载终端建立连接后,根据所述车载终端业务需求匹配信息,通过收发机向该车载终端发送业务数据。
本发明实施例的方案中,由于已提前确定业务需求匹配信息,因此,在进行业务数据交互流程之前,不依赖于路侧设备的业务公告消息,无需进行耗时较长的匹配工作,降低了业务交互复杂度以及以及时延,确保了后续业务数据交互流程能够及时高效地进行。
附图说明
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简要介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域的普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1为本发明背景技术提供的车路信息交互流程示意图之一;
图2为本发明背景技术提供的车路信息交互流程示意图之二;
图3为本发明实施例提供的车路信息交互方法的之一的流程图;
图4为本发明实施例提供用于说明业务需求匹配信息的确定的示意图;
图5(a)为本发明实施例提供的车路信息交互方法之二的流程图;
图5(b)为本发明实施例提供的车路信息交互方法之二的流程图;
图6为本发明实施例提供的路侧设备与车载终端进行交互的示意图之一;
图7为本发明实施例提供的路侧设备与车载终端进行交互的示意图之二;
图8为本发明实施例提供的路侧设备与车载终端进行交互的示意图之三;
图9为本发明实施例提供的信息交互系统的结构示意图;
图10本发明实施例提供的车路信息交互方法之三的流程图;
图11本发明实施例提供的车路信息交互方法之四的流程图;
图12本发明实施例提供的车路信息交互方法之五的流程图;
图13为本发明实施例提供的路侧设备与车载终端进行交互的示意图之四;
图14为本发明实施例提供的一种车载终端的结构示意图;
图15为本发明实施例提供的车载终端的具体实现结构示意图之一;
图16为本发明实施例提供的车载终端的具体实现结构示意图之二;
图17为本发明实施例提供的车载终端的具体实现结构示意图之三;
图18为本发明实施例提供的另一种车载终端的结构示意图;
图19为本发明实施例提供的另一种路侧设备的结构示意图;
图20为本发明实施例提供的一种车路交互业务管理中心的结构示意图;
图21为本发明实施例提供的车载终端的硬件结构示意图;
图22为本发明实施例提供的车载终端的另一硬件结构示意图;
图23为本发明实施例提供的路侧设备的硬件结构示意图;
图24为本发明实施例提供的车路交互业务管理中心的硬件结构示意图。
具体实施方式
本发明实施例中车载终端或路侧设备提前确定车载终端的业务需求匹配信息,该业务需求匹配信息包括:车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;若车载终端提前确定了业务需求匹配信息,则在车载终端与路侧设备建立连接之后,车载终端判断该路侧设备的标识是否包含在能提供车载终端感兴趣的部分或全部业务的路侧设备的标识中,若确定该路侧设备的标识包含在能提供车载终端感兴趣的业务的路侧设备的标识中,则从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据,由于路侧设备与车载终端建立连接之后,无需再实时进行耗时较长的匹配操作,直接根据业务需求匹配信息从路侧设备获取业务数据,因此,降低了业务交互复杂度以及时延,确保了后续业务数据交互流程能够及时高效地进行;若路侧设备提前确定车载终端的业务需求匹配信息,则在与所述车载终端的标识所表示的车载终端建立连接后,路侧设备直接根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据,也无需再实时进行耗时较长的匹配工作,主动的向该车载终端传输业务数据,也降低了业务交互复杂度以及时延,确保了后续业务数据交互流程能够及时高效地进行。
以下结合说明书附图对本发明的优选实施例进行说明,应当理解,此处所描述的优选实施例仅用于说明和解释本发明,并不用于限定本发明。并且在不冲突的情况下,本申请中的实施例及实施例中的特征可以相互组合。
下面结合附图,用具体实施例对本发明提供的方法、设备及系统进行详细描述。
本发明实施例的方案也适用于一般化的Service User与Service Provider之间的交互,为了更为直观的描述,我们将交互的双方称为车载终端与路侧设备,读者和工程技术人员可将其分别理解为更一般的Service User与Service Provider。
本发明实施例中提供了两类车路信息交互方法,针对第一类车路信息交 互方法,先以车载终端为执行主体对方案进行描述,然后以路侧设备为执行主体对方案进行描述,最后描述车载终端和路侧设备两者交互过程;针对第二类车路信息交互方法,先描述实施该方法的系统,然后分别以车载终端、路侧设备、车路交互业务管理中心为执行主体对方案进行描述,最后描述车载终端和路侧设备两者的交互过程。
第一类车路信息交互方法:
如图3所示,为本发明实施例提供的车路信息交互方法之一,以车载终端为执行主体进行描述,具体包括以下步骤:
步骤301、车载终端与路侧设备建立连接之后,根据确定的业务需求匹配信息,判断该路侧设备的标识是否包含在能提供车载终端感兴趣的部分或全部业务的路侧设备的标识中,若判断结果为是,则执行步骤302;若判断结果为否,则执行步骤303。
所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识。
具体实施中,车载终端可以利用以下方式一或方式二中的任一种方式来确定业务需求匹配信息:
方式一:
将行驶信息和感兴趣的业务的标识发送给车路交互业务管理中心,所述行驶信息包括行车路线,或者出发地和目的地信息。
接收车路交互业务管理中心发送的业务需求匹配信息,所述业务需求匹配信息是车路交互业务管理中心将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配得到的。
方式二:
将行驶信息和感兴趣的业务的标识,与本地存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,得到业务需求匹配信息。
上述方式一的本质即为在线匹配,方式二的本质即为在本地进行匹配, 具体匹配过程可以相同。
在方式一中和方式二中,车路交互业务管理中心以及车载终端可以具有导航地图的功能,以便于根据出发地和目的地进行行车路线的查询,在确定出行车路线后,具体匹配时,可以先确定出覆盖区域与行车路线所在的区域有重叠的路侧设备,然后针对每一确定出的路侧设备,将该路侧设备所能提供的业务的标识与车载终端感兴趣的业务的标识进行匹配,得到该路侧设备所能提供的车载终端感兴趣的业务的标识。
此外,在确定出行车路线的个数大于1时,可先针对每一条行车路线进行业务匹配信息的确定,然后车载终端可以根据匹配出的与行车路线对应的业务需求匹配信息来选择一条行车路线。具体的选择方法可以根据实际需求来确定,例如,可以选择含有需求的业务最多的业务需求匹配信息对应的行车线路,还可以选择能持续提供需求的某一业务的业务需求匹配信息对应的行车线路,还可以选择能提供需求的某一种或几种的业务的可靠性最高的业务需求匹配信息对应的行车线路等等;下文中将利用图4对业务需求匹配信息的确定进行说明。
步骤302、从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据。
步骤303、结束。
具体的,上述步骤302可通过以下方式1、方式2和方式3三种方式中的任一种方式来实现:
方式1,包括以下步骤A1和步骤B1:
步骤A1:将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识通过业务数据请求发送给该路侧设备。
步骤B1:接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述业务数据请求确定的。
需要说明的是,若车载终端已完成了某一感兴趣的业务的交互,获得了该已完成的业务对应的业务数据,并确定不再需要与其它路侧设备就该已完 成的业务进行交互,则后续在向其它能提供该业务的路侧设备发送业务数据请求时,可以不将该业务的标识携带在业务请求中。
考虑到各路侧设提供的车载终端感兴趣的业务的个数可能大于1个,客户对不同的业务数据有不同的优先级要求,这时并且一路侧设备与其它路侧设备能提供的车载终端感兴趣的业务的有重复,各感兴趣的业务被重复提供的次数不同,为了避免出现行车路线上有路侧设备提供某项业务,但却因为业务交互顺序安排不当而错过的情况,较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级。
上述步骤A1具体包括:
将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的部分或全部标识和标识对应的业务交互优先级发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
当然,上述业务交互优先级也可以是基于车载终端指定的优先级来确定的,以便满足车载终端对感兴趣的业务的需求。
方式2,包括以下步骤A2和步骤B2:
步骤A2:将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的全部或部分业务的标识发送给该路侧设备。
步骤B2:接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述车载终端感兴趣的业务的标识确定的。
需要说明的是,若车载终端已完成了某一感兴趣的业务的交互,获得了该已完成的业务对应的业务数据,并确定不再需要与其它路侧设备就该已完成的业务进行交互,则后续在向其它能提供该业务的路侧设备发送业务的标识时,可以不将该已完成的业务的标识发送给该其它路侧设备。
上述由步骤A2和步骤B2实现的从路侧设备获取业务数据的方案中,车载终端向路侧设备发送业务标识后,直接等待接收路侧设备发送的业务数据。
考虑到各路侧设提供的车载终端感兴趣的业务的个数可能大于1个,客户对不同的业务数据有不同的优先级要求,这时并且一路侧设备与其它路侧设备能提供的车载终端感兴趣的业务的有重复,各感兴趣的业务被重复提供的次数不同,为了避免出现行车路线上有路侧设备提供某项业务,但却因为业务交互顺序安排不当而错过的情况,较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级。
上述步骤A2具体包括:
将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识和标识对应的业务交互优先级发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
具体实施中,在上述步骤A2之后,上述步骤B2之前,所述方法还包括:
步骤C2:向该路侧设备发送业务数据请求。
上述由步骤A2、步骤C2和步骤B2实现的从路侧设备获取业务数据的方案,是考虑到车载终端向路侧设备发送业务标识后,可能并不确定是否需要路侧设备提供业务数据,仅是为了后续确定需要时路侧设备能立即提供,因此,先执行上述步骤A2,以便路侧设备能及时地确定或准备好业务数据,进而在车载终端执行步骤C2时,能立即将确定好的业务数据发送给车载终端,进而车载终端能较快地通过执行步骤B2获取业务数据,提高业务数据交互的效率。
方式3,当路侧设备能提供的车载终端感兴趣的业务的数量大于1,且所述业务需求匹配信息还包括车载终端感兴趣的各业务的标识对应的业务交互优先级时,包括以下步骤A3和步骤B3:
步骤A3:按照业务的标识对应的业务交互优先级由高到低的顺序,依次向该路侧设备发送携带该路侧设备能提供的车载终端感兴趣的业务的标识的业务数据请求。
步骤B3:接收路侧设备发送的业务数据,所述业务数据是路侧设备根据该车载终端感兴趣的业务的标识确定的。
上述步骤A3和步骤B3的一种具体的执行方式可以是车载终端发送一个业务交互先级较高的业务的标识,接收到该业务的标识之后,再发送比上一次发送的标识的业务交互优先级低一级或与上次发送的标识的业务交互优先级相同的业务的标识,具体过程即为:从所述业务需求匹配信息中获取该路侧设备所能提供的车载终端感兴趣的业务的标识;将对应的业务交互优先级最高的业务的标识携带在业务数据请求中发送给该路侧设备;接收该路侧设备根据其本次接收的业务的标识发送的业务数据;将对应的业务交互优先级次高的业务的标识携带在业务数据请求中发送给该路侧设备;接收该路侧设备根据其本次接收的业务的标识发送的业务数据;依次类推,直至接收到对应的业务交互优先级最低的业务对应的业务数据或者车载终端所在的车辆驶出该路侧设备的覆盖范围。
上述步骤A3和步骤B3的另一种具体的执行方式可以是不管是否接收到发送的业务的标识对应的业务数据,均按照业务交互优先级顺序进行业务的标识的发送。
考虑到车载终端感兴趣的业务可能包括管理管制类业务,此时车载终端感兴趣的业务数据即为管理管制类文件传输请求,不同的管理管制可能需要车载终端提供不同的文件。为了提高此类业务的交互效率,一次性将所有的文件提供给路侧设备,较佳的,上述方法还包括:接收路侧设备发送的第二管理管制类文件传输请求,所述第二管理管制类文件传输请求中携带有至少两个文件标识;确定所述至少两个文件标识中各文件标识对应的文件数据;向路侧设备发送第二管理管制类文件传输响应,所述第二管理管制类文件传输响应中携带有各所述文件标识对应的文件数据。
下面通过图4对业务需求匹配信息的确定进行说明:
假设车载终端所在的车辆要从A地到B地,确定出的可能的行车路线为P1、P2和P3,车载终端感兴趣的业务的标识为业务1、业务2和业务3。三 条可能的行车路线上路侧设备的覆盖情况以及提供的业务情况如图4所示:
其中,路侧设备00001能提供的业务为:业务1、业务3、业务5、业务6和业务7;路侧设备00002能提供的业务为:业务2、业务3、业务5、业务7、业务9;路侧设备00003能提供的业务为:业务2、业务7、业务9、业务15;路侧设备00004能提供的业务为:业务1、业务2、业务6、业务9;路侧设备00005能提供的业务为:业务1、业务3、业务8、业务14。
针对路径P1,将车载终端感兴趣的业务的标识分别与路径P1上的路侧设备00001和路侧设备00002能提供的业务的标识进行匹配后,得到与路径P1对应的业务需求匹配信息包括:
路径P1上,路侧设备0001可以提供业务1、业务3,路侧设备0002可以提供业务2、业务3。
针对路径P2,将车载终端感兴趣的业务的标识分别与路径P2上的路侧设备00001和路侧设备0003能提供的业务的标识进行匹配后,得到与路径P2对应的业务需求匹配信息包括:
路径P2上,路侧设备0001可以提供业务1、业务3,路侧设备0003可以提供业务2,路侧设备0005可以提供业务1、业务3。
针对路径P3,将车载终端感兴趣的业务的标识分别与路径P3上的路侧设备00004和路侧设备00005能提供的业务的标识进行匹配后,得到与路径P3对应的业务需求匹配信息包括:
路径P3上,路侧设备0004可以提供业务1、业务2,路侧设备0005可以提供业务1、业务3。
此外,业务需求匹配信息还可以包括:
-路径P1上,与路侧设备0001交互业务的建议顺序是业务1、3,也即业务1对应的业务交互优先级为最高,业务3对应的业务交互优先级为次高。这是因为后续的路侧设备0002可以提供业务3,但不能提供业务1。
-路径P3上,与路侧设备0004交互业务的建议顺序是业务2、1,也即业务2对应的业务交互优先级为最高,业务1对应的业务交互优先级为次高, 这是因为后续的路侧设备0005可以提供业务1,但不能提供业务2。
-路径P2上,考虑到路侧设备0001和路侧设备0005均能提供业务1和业务3,因此,与路侧设备0001和路侧设备0005交互业务的建议顺序对避免出现行车路线上有路侧设备提供某项业务,但却因为业务交互顺序安排不当而错过的情况作用不大,因此,可以不用针对各路侧设备能提供的业务设置对应的业务交互优先级,当然,在考虑到的路侧设备0001的覆盖区域与路径P2所在的区域重叠的部分较少,根据统计结果显示,在路侧设备0001的覆盖范围下,大多数车载终端仅针对业务1进行了交互,而没来得及对业务3进行交互时,则可以针对路侧设备00005交互业务的建议顺序是业务3、1,也即业务3对应的业务交互优先级为最高,业务1对应的业务交互优先级为次高。
业务需求匹配信息并不限于上述内容,还可以包括其它内容,例如路径上路侧设备总共提供的感兴趣的业务数、提供每项感兴趣业务的路侧设备的平均个数、路侧设备覆盖的范围、可以提供某项业务的路侧设备地理位置等。
下面通过举例对上述方式1及方式2进行说明:
若针对上述路径P1、路径P2、路径P3,车载终端选择的是路径P2,则车载终端所在的车辆在行驶过程中与路侧设备0001的建立连接之后,车载终端确定路侧设备0001所能提供的自身感兴趣的业务为业务1和业务3,然后向路侧设备0001发送携带有业务1和业务3的数据业务请求或者将业务1和业务3发送给路侧设备;最后接收路侧设备0001发送的业务数据1,假设还未来得及接收业务数据3,车载终端所在的车辆已经驶出路侧设备0001的覆盖范围,此时,车载终端可以记录其感兴趣的业务中未收到业务3的业务数据,路侧设备0001也可以记录该车载终端未收到业务3的业务数据。
之后车载终端开始驶入路侧设备0003的覆盖范围,与路侧设备0003建立连接,车载终端确定路侧设备0003所能提供的自身感兴趣的业务为业务2,然后向路侧设备0003发送携带有业务2的数据业务请求或者将业务2发送给路侧设备;最后接收路侧设备0003发送的业务数据2。
接下来,车载终端开始驶入路侧设备0005的覆盖范围,与路侧设备0005建立连接,车载终端确定路侧设备0005所能提供的自身感兴趣的业务为业务1和业务3,此时,由于之前已经从路侧设备0001处获取了业务1的业务数据,但未获得业务3的业务数据,因此,仅需要从路侧设备0005处获得业务3的业务数据,此时车载终端可以向路侧设备0005发送仅携带有业务3的数据业务请求或者将业务3发送给路侧设备;最后接收路侧设备0005发送业务3的业务数据。
上述对于已经完成交互的业务不进行业务请求,是基于相同的业务的标识对应的业务数据是相同的情况下,对于业务的标识相同,但地区不同,对应的业务数据可能不相同的情况,车载终端不用记录该业务是否已经获取,直接从业务需求匹配信息中获取路侧设备能提供的全部车载终端感兴趣的业务的标识;向该路侧设备发送携带有获取的业务的标识的业务请求或者向该路侧设备发送所述获取的业务的标识即可。
此外,在本发明实施例的方案中,车载终端感兴趣的业务可能会发生变化,例如:感兴趣的业务增加了一个或几个,和/或减少了一个或几个。路侧设备能提供的业务信息也可能会发生变化,例如提供的业务增加了一个或几个,和/或减少了一个或几个;
在车载终端感兴趣的业务发生变化时,车载终端可以根据具体的情况进行处理,例如可以选择不处理,也可以针对感兴趣的业务的变化情况向路侧设备发送业务请求或者将感兴趣的业务的变化情况上报给路侧设备,路侧设备根据车载终端感兴趣的业务的变化情况和已经获知的车载终端的感兴趣的业务,将变化的感兴趣的业务对应的业务数据发送给车载终端。
在路侧设备能提供的业务发生变化时,路侧设备可以根据具体的情况进行处理,例如可以选择不处理,也可以先确定出受影响的车载终端,然后将提供的业务变更信息通知给受影响的车载终端,或者将业务变更信息通知给覆盖区域内的所有车辆终端,以便后续车载终端可以根据收到的业务变更信息向路侧设备发送业务请求。
如图5(a)和图5(b)所示,为本发明实施例提供的车路信息交互方法之二的流程图,以路侧设备为执行主体,图5(a)包括:
步骤501a:路侧设备接收车载终端发送的携带有车载终端感兴趣的部分或全部业务的标识的业务数据请求;
步骤502a:确定接收的所述业务的标识对应的业务数据;
步骤503a:将确定的业务数据发送给所述车载终端。
如图5(b)所示,包括:
步骤501b:路侧设备接收接收车载终端发送的车载终端感兴趣的部分或全部业务的标识;
步骤502b:确定接收的所述业务的标识对应的业务数据;
步骤503b:将确定的业务数据发送给所述车载终端。
较佳的,在步骤501b之后,步骤503b之前,所述方法还包括:
接收车载终端发送的业务数据请求;由于路侧设备已经获知了车载终端感兴趣的部分或全部业务的业务标识,该业务数据请求中可以不携带车载终端感兴趣的部分或全部业务的标识。
此时,步骤503b具体包括:
在接收到所述业务数据请求时,将确定的业务数据发送给所述车载终端。上述步骤502b具体可以通过从与路侧设备相连的业务服务器中查询业务的标识对应的业务数据,在路侧设备本地存储有业务数据时,也可以从路侧设备本地查询业务的标识对应的业务数据,查询到之后可以将业务数据存入路侧设备的缓存中,以便在接收到所述业务数据请求时高效地向车载终端发送业务数据。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述步骤501a,包括:
接收车载终端通过业务数据请求发送的该路侧设备所能提供的车载终端感兴趣的业务的部分或全部标识和标识对应的业务交互优先级。
此时步骤502a和步骤503a,具体包括:按照标识对应的业务交互优先级 从高到低的顺序依次确定业务数据,并依次向车载终端提供相应的业务数据。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述步骤501b,包括:
接收车载终端发送的该路侧设备所能提供的车载终端感兴趣的业务的部分或全部标识和标识对应的业务交互优先级。
此时步骤502b和步骤503b,具体包括:按照标识对应的业务交互优先级从高到低的顺序依次确定业务数据,并依次向车载终端提供相应的业务数据。
在所述车载终端感兴趣的业务包括管理管制类业务且车载终端感兴趣的业务数据为管理管制类文件传输请求时,为了实现对各车载终端所在的车辆进行合并管理,减少车载终端占用频谱资源的次数,尤其是减少需要频繁建立连接的小数据量的业务占用频谱资源的次数,较佳的,所述方法还包括:
1)接收各业务服务器发送的第一管理管制类文件传输请求,所述第一管理管制类文件传输请求中携带有该业务服务器的标识和请求传输的文件的文件标识。
2)向车载终端发送第二管理管制类文件传输请求,所述第二管理管制类文件传输请求中携带有接收的各第一管理管制类文件传输请求中携带的文件标识。
3)接收车载终端发送的第二管理管制类文件传输响应,所述第二管理管制类文件传输响应中携带有各所述文件标识对应的文件数据。
4)针对任一第一管理管制类文件传输请求,从第二管理管制类文件传输响应中的获得该第一管理管制类文件传输请求中的文件标识对应的文件数据,将获得的数据发送给该第一管理管制类文件传输请求中的业务服务器标识所表示的业务服务器。
例如:业务服务器1和业务服务器2分别要求车载终端给自己传输文件1和文件2,则路侧设备可以在同一个数据传输请求中对车载终端提出传输文件1和文件2的要求,车载终端打包传输文件1和文件2给路侧设备,路侧设备再将文件1和文件2分别传给业务服务器1和业务服务器2。
如图6所示,为本发明实施例提供的路侧设备与车载终端进行交互的示意图之一。
图6中,车载终端提前确定好业务需求匹配信息,车载终端主动向路侧设备发起业务交互,此种情况下没有初始化阶段,图6中空出初始化阶段是为了与背景技术中的进行比较,并不表明要等待背景技术中的初始化阶段占用的时长后再进行业务交互,图6中并不需要进行初始化阶段,不需要等待,直接进行业务交互操作。
如图7所示,为本发明实施例提供的路侧设备与车载终端进行交互的示意图之二。
图7中,与背景技术中的初始化阶段相比较,这里相应的初始化阶段仅需要车载终端向路侧设备发送包含该路侧设备能提供的车载终端感兴趣的业务的标识,具体实施时可采用业务列表的形式,耗时较短,这里仅仅是为了与背景技术中的初始化阶段进行比较,也可将所述发送业务列表不作为初始化阶段,由于路侧设备已获知车载终端需要的业务的标识,因此,业务交互操作阶段由路侧设备发起。
如图8所示,为本发明实施例提供的路侧设备与车载终端进行交互的示意图之三。
图8中,车载终端提取确定好业务需求匹配信息,向路侧设备上报该路侧设备所能提供自身的车载终端感兴趣的业务的标识,这里实施中可以为向路侧设备上报业务交互列表,此种情况下业务交互初始化阶段只包括业务列表的上报,业务交互操作阶段由车载终端发起。
需要说明的是,图6、图7和图8中的REQW表示的是有需要响应的请求消息,重点是表明需要响应,也即需要返回YES,具体该消息是请求消息,还是业务数据,可以根据上文中的描述来确定,这里并不对其进行限定,当然,图6、图7和图8中仅示意出了REQW,并没有示意出REQN,并不表明本发明实施例中车载终端和路侧设备之间不可以使用REQN进行业务交互操作。
第二类车路信息交互方法:
如图9所示,为本发明实施例中的信息交互系统的结构示意图,包括路侧设备91、车载终端92和车路交互业务管理中心93。
路侧设备91,用于向车路交互业务管理中心93注册自己的设备标识、位置以及覆盖区域,以及注册自身能提供的业务的信息;这个属于基础设施注册,可以不用更新;以及与车载终端进行业务数据交互。
车载终端92,用于向车路交互业务管理中心93发送行驶信息和感兴趣的业务的第三参数信息,接收车路交互业务管理中心发送的业务需求匹配信息;以及与路侧设备进行业务数据交互。
车路交互业务管理中心93,用于接受路侧设备注册和注销,接收路侧设备提供的业务的信息,向车载终端提供查询以及进行业务需求信息的匹配。
在路侧设备拆除时,需向车路交互业务管理中心进行注销。
较佳的,上述信息交互系统还可以包括业务服务器94;在上述信息交互系统包括业务服务器94时,路侧设备可以不向车路交互业务管理中心注册自身能提供的业务的信息,该功能可由于路侧设备相连的业务服务器来执行。
所述业务服务器94,用于向车路交互业务管理中心注册自己通过哪些路侧设备分别提供哪些业务,并及时更新;如果路侧设备发生故障,则删除在该路侧设备处提供的业务。当业务服务器不再通过路侧设备为车载终端提供服务时向车路交互业务管理中心进行注销。
路侧设备发生故障,可以由业务服务器在此路侧设备处提供的业务更新如删除或暂不提供来表示。
如图10所示,为本发明实施例提供的车路信息交互方法之三,以车载终端为执行主体进行描述,具体包括以下步骤:
步骤1001:车载终端向车路交互业务管理中心发送车载终端的标识、行驶信息和感兴趣的业务的标识,以使车路交互业务管理中心根据所述行驶信息和感兴趣的业务的标识确定该车载终端的业务需求匹配信息。
步骤1002:与行车路线上经过的能提供车载终端感兴趣的部分或全部业 务的所述路侧设备的标识所表示的路侧设备建立连接之后,接收该路侧设备发送的业务数据,所述业务数据是该路侧设备根据车路交互业务管理中心下发的该车载终端的标识和业务需求匹配信息确定的。
其中,所述行驶信息包括行车路线,或者出发地和目的地信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识。
这里的下发可以是直接下发,也可以是通过各业务服务器下发给相应的路侧设备,此种情况下没有初始化阶段,业务交互操作阶段由路侧设备发起。
在图10所示的方案中,车路交互业务管理中心可将业务需求匹配信息通知车载终端,也可以不通知车载终端;在通知车载终端时,车载终端也可以主动向路侧设备发送业务数据请求或自身感兴趣的业务的标识,路侧设备在接到该数据业务请求或业务的标识时,向车载终端发送上述根据车路交互业务管理中心下发的车载终端感兴趣的业务的标识确定的业务数据。
如图11所示,为本发明实施例提供的车路信息交互方法之四,以路侧设备为执行主体进行描述,具体包括:
步骤1101:路侧设备接收车路交互业务管理中心下发的车载终端的标识和该车载终端的业务需求匹配信息,其中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识。
步骤1102:在与所述车载终端的标识所表示的车载终端建立连接后,根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务对应的业务交互优先级。
此时,根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据,包括:
按照各业务对应的业务交互优先级由高到底的顺序,向该车载终端发送自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
较佳的,所述车载终端感兴趣的业务包括管理管制类业务且车载终端感兴趣的业务数据为管理管制类文件传输请求,所述方法还包括:
接收各业务服务器根据车路交互业务管理中心下发所述车载终端的感兴趣的管理管制类业务的标识发送的第一管理管制类文件传输请求,所述第一管理管制类文件传输请求中携带有该业务服务器的标识和请求传输的文件的文件标识。
此时,根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据,包括:
向车载终端发送第二管理管制类文件传输请求,所述第二管理管制类文件传输请求中携带有接收的各第一管理管制类文件传输请求中携带的文件标识;接收车载终端发送的第二管理管制类文件传输响应,所述第二管理管制类文件传输响应中携带有各所述文件标识对应的文件数据。
同时,在接收车载终端发送的第二管理管制类文件传输响应之后,所述方法还包括:
针对任一第一管理管制类文件传输请求,从第二管理管制类文件传输响应中的获得该第一管理管制类文件传输请求中的文件标识对应的文件数据,将获得的数据发送给该第一管理管制类文件传输请求中的业务服务器的标识所表示的业务服务器。
如图12所示,为本发明实施例提供的车路信息交互方法之五,以车路交互业务管理中心为执行主体进行描述,具体包括:
步骤1200:车路交互业务管理中心接收车载终端的标识、该车载终端的行驶信息和感兴趣的业务的标识。
需要说明的是,这里车路交互业务管理中心接收的车载终端的行驶信息 和感兴趣的业务的标识可以是所述车辆终端发送的,也可以是其它终端发送的,例如,手机终端、电脑终端等等,本发明实施例并不对此进行限定。
步骤1201:将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,获得该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识。
步骤1202:将所述车载终端的标识和所述车载终端的业务需求匹配信息下发给各路侧设备的标识所表示的路侧设备,以使各路侧设备在确定与所述车载终端的标识所表示的车载终端建立连接后,根据所述车载终端的业务需求匹配信息向该车载终端发送业务数据。
较佳的,将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,获得该车载终端的业务需求匹配信息,包括:
根据所述行驶信息确定车载终端可能的各行车路线;针对确定的每一行车路线,执行以下操作:
1)确定覆盖区域包含该行车路线的路侧设备的标识以及各路侧设备能够提供的业务的标识。
2)针对每一路侧设备,判断车载终端感兴趣的部分或全部业务的标识是否包含在该路侧设备能够提供的业务的标识中。
3)若包含在该路侧设备能够提供的业务的标识中,则确定该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识。
4)将确定的该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识记和该路侧设备的标识作为业务需求匹配信息。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级。
较佳的,在将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配的过程中,通过以下方式确定各路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级:
针对每一能提供车载终端的感兴趣的业务的数量大于1的路侧设备,执行以下操作:
针对该路侧设备能提供车载终端的感兴趣的每一业务,确定该路侧设备所在的行车路线上的能提供该业务的路侧设备的数量;并按照能提供该业务的路侧设备的数量越少对应的业务交互优先级越高的原则,为该路侧设备的该业务的标识设置对应的业务交互优先级。
车路交互业务管理中心确定业务需求匹配信息的具体例子,可参见图4以及前述中对图4的说明,这里不再赘述。
如图13所示,为本发明实施例提供的路侧设备与车载终端进行交互的示意图之四。
图13中,车路交互管理中心提前将车载终端的业务需求匹配信息下发给相应的路侧设备,这里的下发可以是直接下发,也可以是通过各业务服务器下发给相应的路侧设备,此种情况下没有初始化阶段,业务交互操作阶段由路侧设备发起。
图13中的REQW表示的是有需要响应的请求消息,重点是表明需要响应,也即需要返回YES,具体该消息是请求消息,还是业务数据,可以根据上文中的描述来确定,这里并不对其进行限定。当然,图13中仅示意出了REQW,并没有示意出REQN,并不表明本发明实施例中车载终端和路侧设备之间不可以使用REQN进行业务交互操作。
进一步的,针对上述两类信息交互方法,当路侧设备提前获知或确定车载终端业务需求匹配信息,对于不区分业务,或者是区分业务中但不区分车载终端时,路侧设备可以根据对业务感兴趣的车载终端的个数决定采取单播或者组播的方式传输,如果车载终端的个数超过某个设定阈值,路侧设备可 建立一个组播组进行组播传输。
基于同一发明构思,本发明实施例还提供了车载终端、路侧设备和车路交互业务管理中心以及车路信息交互系统,由于该车载终端、路侧设备和车路交互业务管理中心以及车路信息交互系统所解决问题的原理与前述信息交互方法相似,因此该车载终端、路侧设备和车路交互业务管理中心的实施可以参见前述方法的实施,重复之处不再赘述。
如图14所示,为本发明实施例提供的一种车载终端的结构示意图,包括:
判断模块1401,用于在所述车载终端与路侧设备建立连接之后,根据确定的业务需求匹配信息,判断该路侧设备的标识是否包含在能提供车载终端感兴趣的部分或全部业务的路侧设备的标识中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识。
获取模块1402,用于在判断模块确定该路侧设备的标识包含在能提供车载终端感兴趣的业务的路侧设备的标识中时,从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据。
在上述包含判断模块1401和获取模块1402的车载终端的基础上,根据获取模块具体实现方式的功能不同,车载终端的具体实现上可分为三种不同的结构,分别如图15、图16和图17所示,下面分别进行介绍:
图15中,所述获取模块1402包括:第一发送子模块和第一接收子模块。
所述第一发送子模块,用于将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识通过业务数据请求发送给该路侧设备。
较佳的,所述第一接收子模块,用于接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述业务数据请求确定的。
在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标 识对应的业务交互优先级。
此时,所述第一发送子模块,具体用于将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的部分或全部标识和标识对应的业务交互优先级通过业务数据请求发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
图16中,所述获取模块1402包括:第二发送子模块和第二接收子模块。
所述第二发送子模块,用于将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的全部或部分业务的标识发送给该路侧设备。
所述第二接收子模块,用于接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述车载终端感兴趣的业务的标识确定的。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级。
此时,所述第二发送子模块,具体用于将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识和标识对应的业务交互优先级发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
较佳的,所述第二发送子模块,还用于在将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的标识发送给该路侧设备之后,接收该路侧设备发送的业务数据之前,向该路侧设备发送业务数据请求。
图17中,所述获取模块1402包括:第三发送子模块和第三接收子模块。图17是在路侧设备能提供的车载终端感兴趣的业务的数量大于1时,所述业务需求匹配信息还包括:车载终端感兴趣的各业务的标识对应的业务交互优先级;下的车载终端的结构示意图。
所述第三发送子模块,用于按照业务的标识对应的业务交互优先级由高到低的顺序,依次向该路侧设备发送携带该路侧设备能提供的车载终端感兴 趣的业务的标识的业务数据请求。
所述第三接收子模块,用于接收路侧设备发送的业务数据,所述业务数据是路侧设备根据该车载终端感兴趣的业务的标识确定的。
较佳的,所述车载终端还包括:确定模块1403,用于将行驶信息和感兴趣的业务的标识发送给车路交互业务管理中心;接收车路交互业务管理中心发送的业务需求匹配信息,所述业务需求匹配信息是车路交互业务管理中心将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配得到的;或者将行驶信息和感兴趣的业务的标识,与本地存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,得到业务需求匹配信息。
相应的,本发明实施例还提供一种车路信息交互系统,该车路信息交互系统包括上述任一所述的车载终端(如图14、图15、图16、图17所示的)和至少一个路侧设备,这里的路侧设备可以是现有技术中的路侧设备。
如图18所示,为本发明实施例提供的另一种车载终端的结构示意图,包括:
发送模块1801,用于向车路交互业务管理中心发送车载终端的标识、行驶信息和感兴趣的业务的标识,以使车路交互业务管理中心根据所述行驶信息和感兴趣的业务的标识确定该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识。
接收模块1802,用于在所述车载终端与行车路线上经过的能提供车载终端感兴趣的部分或全部业务的所述路侧设备的标识所表示的路侧设备建立连接之后,接收该路侧设备发送的业务数据,所述业务数据是该路侧设备根据车路交互业务管理中心下发的该车载终端的标识和业务需求匹配信息确定的。
如图19所示,为本发明实施例提供的一种路侧设备的结构示意图,包括:
接收模块1901,用于接收车路交互业务管理中心下发的车载终端的标识和该车载终端的业务需求匹配信息,其中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识。
传输模块1902,用于在所述路侧设备与所述车载终端的标识所表示的车载终端建立连接后,根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务对应的业务交互优先级。
此时,所述传输模块1902,具体用于按照各业务对应的业务交互优先级由高到底的顺序,向该车载终端发送自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
较佳的,所述车载终端感兴趣的业务包括管理管制类业务且车载终端感兴趣的业务数据为管理管制类文件传输请求。
此时,所述接收模块1901,还用于接收各业务服务器根据车路交互业务管理中心下发所述车载终端的感兴趣的管理管制类业务的标识发送的第一管理管制类文件传输请求,所述第一管理管制类文件传输请求中携带有该业务服务器的标识和请求传输的文件的文件标识。
所述传输模块1902,具体用于向车载终端发送第二管理管制类文件传输请求,所述第二管理管制类文件传输请求中携带有接收的各第一管理管制类文件传输请求中携带的文件标识;接收车载终端发送的第二管理管制类文件传输响应,所述第二管理管制类文件传输响应中携带有各所述文件标识对应的文件数据。
所述传输模块1902,还用于在接收车载终端发送的第二管理管制类文件传输响应之后针对任一第一管理管制类文件传输请求,从第二管理管制类文 件传输响应中的获得该第一管理管制类文件传输请求中的文件标识对应的文件数据,将获得的数据发送给该第一管理管制类文件传输请求中的业务服务器的标识所表示的业务服务器。
如图20所示,为本发明实施例提供的一种车路交互业务管理中心的结构示意图,包括:
接收模块2001,用于接收接收车载终端的标识、该车载终端的行驶信息和感兴趣的业务的标识。
匹配模块2002,用于将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,获得该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识。
发送模块2003,用于将所述车载终端的标识和所述车载终端的业务需求匹配信息下发给各路侧设备的标识所表示的路侧设备,以使各路侧设备在确定与所述车载终端的标识所表示的车载终端建立连接后,根据所述车载终端的业务需求匹配信息向该车载终端发送业务数据。
较佳的,所述匹配模块2002,具体用于根据所述行驶信息确定车载终端可能的各行车路线,针对确定的每一行车路线,执行以下操作:确定覆盖区域包含该行车路线的路侧设备的标识以及各路侧设备能够提供的业务的标识;针对该行车路线上的每一路侧设备,判断车载终端感兴趣的部分或全部业务的标识是否包含在该路侧设备能够提供的业务的标识中;若包含在该路侧设备能够提供的业务的标识中,则确定该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识;将确定的该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识记和该路侧设备的标识作为业务需求匹配信息。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级。
较佳的,所述匹配模块2002,具体用于通过以下方式确定各路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级:针对每一能提供车载终端的感兴趣的业务的数量大于1的路侧设备,执行以下操作:针对该路侧设备能提供车载终端的感兴趣的每一业务,确定该路侧设备所在的行车路线上的能提供该业务的路侧设备的数量;并按照能提供该业务的路侧设备的数量越少对应的业务交互优先级越高的原则,为该路侧设备的该业务的标识设置对应的业务交互优先级。
相应的,本发明实施例还提供另一种车路信息交互系统,包括:图18所示的任一车载终端、图20所示的任一所述的车路交互业务管理中心和至少一个图19所示的路侧设备。
在本发明实施例的方案中,车载终端可以提前从车路交互业务管理中心获取自己行车路线上可提供自己感兴趣业务的路侧设备的信息,不依赖于业务公告,降低业务交互复杂度及时延,相对于现有技术来说,减少或不进行初始化阶段的交互,节约了频谱资源;进一步地,车载终端还可获知与路侧设备进行业务交互的业务交互优先级,避免出现行车路线上有路侧设备提供某项业务,但却因为业务交互顺序安排不当而错过的情况;在路侧设备提前从车路业务交互管理中心处获知车载终端的业务需求匹配信息的情况下,路侧设备可将有较多车载终端感兴趣的业务采用组播的方式传输,节省频谱资源;在业务服务器提前将业务数据推送到路侧设备处时,不但可进一步降低业务交互时延,路侧设备还可以对车辆进行合并管理,减少车辆占用频谱资源的次数,尤其适用于需要频繁建立连接的小数据量的业务。
下面结合优选的硬件结构,对本发明实施例提供的车载终端、路侧设备和车路交互业务管理中心的结构、处理方式进行说明。
如图21所示,为本发明实施例提供的车载终端的硬件结构示意图,包括:
处理器2100,用于读取存储器2120中的程序,在车载终端与路侧设备建立连接之后,执行下列过程:
根据确定的业务需求匹配信息,判断该路侧设备的标识是否包含在能提 供车载终端感兴趣的部分或全部业务的路侧设备的标识中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;若确定该路侧设备的标识包含在能提供车载终端感兴趣的业务的路侧设备的标识中,则通过收发机2110从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据。
收发机2110,用于在处理器2100的控制下接收和发送数据。
较佳的,所述处理器2100,具体用于读取存储器2120中的程序,执行下列过程:
将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识利用业务数据请求通过收发机2110发送给该路侧设备;通过收发机2110接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述业务数据请求确定的。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级;所述处理器2100,具体用于读取存储器2120中的程序,执行下列过程:
将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的部分或全部标识和标识对应的业务交互优先级通过收发机2110发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
较佳的,所述处理器2100,具体用于读取存储器2120中的程序,执行下列过程:
将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的全部或部分业务的标识通过收发机2110发送给该路侧设备;通过收发机2110接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述车载终端感兴趣的业务的标识确定的。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级;所述处理器2100,具体用于读取存储器2120中的程序,执行下列过程:
将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识和标识对应的业务交互优先级发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
较佳的,在将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的标识通过收发机2110发送给该路侧设备之后,接收该路侧设备发送的业务数据之前,所述处理器2100,还用于读取存储器2120中的程序,执行下列过程:
通过收发机2110向该路侧设备发送业务数据请求。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的数量大于1时,所述业务需求匹配信息还包括:车载终端感兴趣的各业务的标识对应的业务交互优先级;所述处理器2100,具体用于读取存储器2120中的程序,执行下列过程:
按照业务的标识对应的业务交互优先级由高到低的顺序,依次向该路侧设备发送携带该路侧设备能提供的车载终端感兴趣的业务的标识的业务数据请求,并接收路侧设备发送的业务数据,所述业务数据是路侧设备根据该车载终端感兴趣的业务的标识确定的。
较佳的,所述处理器2100,具体用于读取存储器2120中的程序,执行下列过程:
将行驶信息和感兴趣的业务的标识通过收发机2110发送给车路交互业务管理中心;接收车路交互业务管理中心发送的业务需求匹配信息,所述业务需求匹配信息是车路交互业务管理中心将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配得到 的;或者,
将行驶信息和感兴趣的业务的标识,与本地存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,得到业务需求匹配信息。
其中,在图21中,总线架构可以包括任意数量的互联的总线和桥,具体由处理器2100代表的一个或多个处理器和存储器2120代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本文不再对其进行进一步描述。总线接口提供接口。收发机2110可以是多个元件,即包括发送机和接收机,提供用于在传输介质上与各种其他装置通信的模块。针对不同的用户设备,用户接口2130还可以是能够外接内接需要设备的接口,连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器2100负责管理总线架构和通常的处理,存储器2120可以存储处理器2100在执行操作时所使用的数据。
如图22所示,为本发明实施例提供的车载终端的另一种硬件结构示意图,包括:
处理器2200,用于读取存储器2220中的程序,执行下列过程:
通过收发机2210向车路交互业务管理中心发送车载终端的标识、行驶信息和感兴趣的业务的标识,以使车路交互业务管理中心根据所述行驶信息和感兴趣的业务的标识确定该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;与行车路线上经过的能提供车载终端感兴趣的部分或全部业务的所述路侧设备的标识所表示的路侧设备建立连接之后,通过收发机2210接收该路侧设备发送的业务数据,所述业务数据是该路侧设备根据车路交互业务管理中心下发的该车载终端的标识和业务需求匹配信息确定的。
收发机2210,用于在处理器2200的控制下接收和发送数据。
其中,在图22中,总线架构可以包括任意数量的互联的总线和桥,具体由处理器2200代表的一个或多个处理器和存储器2220代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本文不再对其进行进一步描述。总线接口提供接口。收发机2210可以是多个元件,即包括发送机和接收机,提供用于在传输介质上与各种其他装置通信的模块。针对不同的用户设备,用户接口2230还可以是能够外接内接需要设备的接口,连接的设备包括但不限于小键盘、显示器、扬声器、麦克风、操纵杆等。
处理器2200负责管理总线架构和通常的处理,存储器2220可以存储处理器2200在执行操作时所使用的数据。
如图23所示,为本发明实施例提供的路侧设备的硬件结构示意图,包括:
处理器2300,用于读取存储器2320中的程序,执行下列过程:
通过收发机2310接收车路交互业务管理中心下发的车载终端的标识和该车载终端的业务需求匹配信息,其中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识。在与所述车载终端的标识所表示的车载终端建立连接后,根据所述业务需求匹配信息,通过收发机2310向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
收发机2310,用于在处理器2300的控制下接收和发送数据。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务对应的业务交互优先级。所述处理器2300,用于读取存储器2320中的程序,具体执行下列过程:
按照各业务对应的业务交互优先级由高到底的顺序,通过收发机2310向该车载终端发送自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
所述车载终端感兴趣的业务包括管理管制类业务且车载终端感兴趣的业务数据为管理管制类文件传输请求,所述处理器2300,还用于读取存储器2320中的程序,执行下列过程:
通过收发机2310接收各业务服务器根据车路交互业务管理中心下发所述车载终端的感兴趣的管理管制类业务的标识发送的第一管理管制类文件传输请求,所述第一管理管制类文件传输请求中携带有该业务服务器的标识和请求传输的文件的文件标识。
所述处理器2300,具体用于读取存储器2320中的程序,执行下列过程:
向车载终端发送第二管理管制类文件传输请求,所述第二管理管制类文件传输请求中携带有接收的各第一管理管制类文件传输请求中携带的文件标识;接收车载终端发送的第二管理管制类文件传输响应,所述第二管理管制类文件传输响应中携带有各所述文件标识对应的文件数据;
在接收车载终端发送的第二管理管制类文件传输响应之后所述处理器2300,还用于读取存储器2320中的程序,执行下列过程:
针对任一第一管理管制类文件传输请求,从第二管理管制类文件传输响应中的获得该第一管理管制类文件传输请求中的文件标识对应的文件数据,将获得的数据发送给该第一管理管制类文件传输请求中的业务服务器的标识所表示的业务服务器。
其中,在图23中,总线架构可以包括任意数量的互联的总线和桥,具体由处理器2300代表的一个或多个处理器和存储器2320代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本文不再对其进行进一步描述。总线接口提供接口。收发机2310可以是多个元件,即包括发送机和收发机,提供用于在传输介质上与各种其他装置通信的模块。处理器2300负责管理总线架构和通常的处理,存储器2320可以存储处理器2300在执行操作时所使用的数据。
如图24所示,为本发明实施例提供的车路交互业务管理中心的硬件结构 示意图,包括:
处理器2400,用于读取存储器2420中的程序,执行下列过程:
通过收发机2410接收车载终端的标识、行驶信息和感兴趣的业务的标识,将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,获得该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识。将所述车载终端的标识和所述车载终端的业务需求匹配信息下发给各路侧设备的标识所表示的路侧设备,以使各路侧设备在确定与所述车载终端的标识所表示的车载终端建立连接后,根据所述车载终端业务需求匹配信息,通过收发机2410向该车载终端发送业务数据。
收发机2410,用于在处理器2400的控制下接收和发送数据。
较佳的,所述处理器2400,具体用于读取存储器2420中的程序,执行下列过程:
根据所述行驶信息确定车载终端可能的各行车路线;针对确定的每一行车路线,执行以下操作:确定覆盖区域包含该行车路线的路侧设备的标识以及各路侧设备能够提供的业务的标识;针对每一路侧设备,判断车载终端感兴趣的部分或全部业务的标识是否包含在该路侧设备能够提供的业务的标识中;若包含在该路侧设备能够提供的业务的标识中,则确定该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识;将确定的该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识记和该路侧设备的标识作为业务需求匹配信息。
较佳的,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级。
较佳的,所述处理器2400,还用于读取存储器2420中的程序,执行下列过程:
在将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配的过程中,通过以下方式确定各路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级:针对每一能提供车载终端的感兴趣的业务的数量大于1的路侧设备,执行以下操作:针对该路侧设备能提供车载终端的感兴趣的每一业务,确定该路侧设备所在的行车路线上的能提供该业务的路侧设备的数量;并按照能提供该业务的路侧设备的数量越少对应的业务交互优先级越高的原则,为该路侧设备的该业务的标识设置对应的业务交互优先级。
其中,在图24中,总线架构可以包括任意数量的互联的总线和桥,具体由处理器2400代表的一个或多个处理器和存储器2420代表的存储器的各种电路链接在一起。总线架构还可以将诸如外围设备、稳压器和功率管理电路等之类的各种其他电路链接在一起,这些都是本领域所公知的,因此,本文不再对其进行进一步描述。总线接口提供接口。收发机2410可以是多个元件,即包括发送机和收发机,提供用于在传输介质上与各种其他装置通信的模块。处理器2400负责管理总线架构和通常的处理,存储器2420可以存储处理器2400在执行操作时所使用的数据。
本领域内的技术人员应明白,本发明的实施例可提供为方法、系统、或计算机程序产品。因此,本发明可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且,本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器,使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流 程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
显然,本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样,倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内,则本发明也意图包含这些改动和变型在内。

Claims (38)

  1. 一种车路信息交互方法,其特征在于,包括:
    车载终端与路侧设备建立连接之后,根据确定的业务需求匹配信息,判断该路侧设备的标识是否包含在能提供车载终端感兴趣的部分或全部业务的路侧设备的标识中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
    若确定该路侧设备的标识包含在能提供车载终端感兴趣的业务的路侧设备的标识中,则从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据。
  2. 如权利要求1所述的方法,其特征在于,从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据,包括:
    将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识通过业务数据请求发送给该路侧设备;
    接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述业务数据请求确定的。
  3. 如权利要求2所述的方法,其特征在于,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级;
    将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的部分或全部标识通过业务数据请求发送给该路侧设备,包括:
    将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的部分或全部标识和标识对应的业务交互优先级通过业务数据请求发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
  4. 如权利要求1所述的方法,其特征在于,从该路侧设备获取其所能提 供的车载终端感兴趣的业务的标识对应的业务数据,包括:
    将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的全部或部分业务的标识发送给该路侧设备;
    接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述车载终端感兴趣的业务的标识确定的。
  5. 如权利要求4所述的方法,其特征在于,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级;
    将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识发送给该路侧设备,包括:
    将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识和标识对应的业务交互优先级发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
  6. 如权利要求4所述的方法,其特征在于,在将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的标识发送给该路侧设备之后,接收该路侧设备发送的业务数据之前,所述方法还包括:
    向该路侧设备发送业务数据请求。
  7. 如权利要求1所述的方法,其特征在于,在路侧设备能提供的车载终端感兴趣的业务的数量大于1时,所述业务需求匹配信息还包括:车载终端感兴趣的各业务的标识对应的业务交互优先级;
    从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据,包括:
    按照业务的标识对应的业务交互优先级由高到低的顺序,依次向该路侧设备发送携带该路侧设备能提供的车载终端感兴趣的业务的标识的业务数据请求,并接收路侧设备发送的业务数据,所述业务数据是路侧设备根据该车载终端感兴趣的业务的标识确定的。
  8. 如权利要求1至7任一所述的方法,其特征在于,车载终端通过以下方式中的任一种确定业务需求匹配信息:
    方式一:
    将行驶信息和感兴趣的业务的标识发送给车路交互业务管理中心;
    接收车路交互业务管理中心发送的业务需求匹配信息,所述业务需求匹配信息是车路交互业务管理中心将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配得到的;
    方式二:
    将行驶信息和感兴趣的业务的标识,与本地存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,得到业务需求匹配信息。
  9. 一种车路信息交互方法,其特征在于,包括:
    车载终端向车路交互业务管理中心发送车载终端的标识、行驶信息和感兴趣的业务的标识,以使车路交互业务管理中心根据所述行驶信息和感兴趣的业务的标识确定该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
    与行车路线上经过的能提供车载终端感兴趣的部分或全部业务的所述路侧设备的标识所表示的路侧设备建立连接之后,接收该路侧设备发送的业务数据,所述业务数据是该路侧设备根据车路交互业务管理中心下发的该车载终端的标识和业务需求匹配信息确定的。
  10. 一种车路信息交互方法,其特征在于,包括:
    路侧设备接收车路交互业务管理中心下发的车载终端的标识和该车载终端的业务需求匹配信息,其中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
    在与所述车载终端的标识所表示的车载终端建立连接后,根据所述业务 需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
  11. 如权利要求10所述的方法,其特征在于,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务对应的业务交互优先级;
    根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据,包括:
    按照各业务对应的业务交互优先级由高到底的顺序,向该车载终端发送自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
  12. 如权利要求10所述的方法,其特征在于,所述车载终端感兴趣的业务包括管理管制类业务且车载终端感兴趣的业务数据为管理管制类文件传输请求,所述方法还包括:
    接收各业务服务器根据车路交互业务管理中心下发所述车载终端的感兴趣的管理管制类业务的标识发送的第一管理管制类文件传输请求,所述第一管理管制类文件传输请求中携带有该业务服务器的标识和请求传输的文件的文件标识;
    根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据,包括:
    向车载终端发送第二管理管制类文件传输请求,所述第二管理管制类文件传输请求中携带有接收的各第一管理管制类文件传输请求中携带的文件标识;
    接收车载终端发送的第二管理管制类文件传输响应,所述第二管理管制类文件传输响应中携带有各所述文件标识对应的文件数据;
    在接收车载终端发送的第二管理管制类文件传输响应之后,所述方法还包括:
    针对任一第一管理管制类文件传输请求,从第二管理管制类文件传输响应中的获得该第一管理管制类文件传输请求中的文件标识对应的文件数据, 将获得的数据发送给该第一管理管制类文件传输请求中的业务服务器的标识所表示的业务服务器。
  13. 一种车路信息交互方法,其特征在于,包括:
    车路交互业务管理中心接收车载终端的标识、该车载终端的行驶信息和感兴趣的业务的标识;
    将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,获得该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
    将所述车载终端的标识和所述车载终端的业务需求匹配信息下发给各路侧设备的标识所表示的路侧设备,以使各路侧设备在确定与所述车载终端的标识所表示的车载终端建立连接后,根据所述车载终端的业务需求匹配信息向该车载终端发送业务数据。
  14. 如权利要求13所述的方法,其特征在于,将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,获得该车载终端的业务需求匹配信息,包括:
    根据所述行驶信息确定车载终端可能的各行车路线;
    针对确定的每一行车路线,执行以下操作:
    确定覆盖区域包含该行车路线的路侧设备的标识以及各路侧设备能够提供的业务的标识;
    针对每一路侧设备,判断车载终端感兴趣的部分或全部业务的标识是否包含在该路侧设备能够提供的业务的标识中;
    若包含在该路侧设备能够提供的业务的标识中,则确定该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识;
    将确定的该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识记和该路侧设备的标识作为业务需求匹配信息。
  15. 如权利要求14所述的方法,其特征在于,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级。
  16. 如权利要求15所述的方法,其特征在于,在将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配的过程中,通过以下方式确定各路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级:
    针对每一能提供车载终端的感兴趣的业务的数量大于1的路侧设备,执行以下操作:
    针对该路侧设备能提供车载终端的感兴趣的每一业务,确定该路侧设备所在的行车路线上的能提供该业务的路侧设备的数量;并
    按照能提供该业务的路侧设备的数量越少对应的业务交互优先级越高的原则,为该路侧设备的该业务的标识设置对应的业务交互优先级。
  17. 一种车载终端,其特征在于,包括:
    判断模块,用于在所述车载终端与路侧设备建立连接之后,根据确定的业务需求匹配信息,判断该路侧设备的标识是否包含在能提供车载终端感兴趣的部分或全部业务的路侧设备的标识中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
    获取模块,用于在判断模块确定该路侧设备的标识包含在能提供车载终端感兴趣的业务的路侧设备的标识中时,从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据。
  18. 如权利要求17所述的车载终端,其特征在于,所述获取模块包括:第一发送子模块和第一接收子模块;
    所述第一发送子模块,用于将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识通过业务数据请求发送给该 路侧设备;
    所述第一接收子模块,接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述业务数据请求确定的。
  19. 如权利要求18所述的车载终端,其特征在于,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级;
    所述第一发送子模块,具体用于将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的部分或全部标识和标识对应的业务交互优先级发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
  20. 如权利要求17所述的车载终端,其特征在于,所述获取模块包括:第二发送子模块和第二接收子模块;
    所述第二发送子模块,用于将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的全部或部分业务的标识通过业务数据请求发送给该路侧设备;
    所述第二接收子模块,用于接收该路侧设备发送的业务数据,所述业务数据是路侧设备根据所述车载终端感兴趣的业务的标识确定的。
  21. 如权利要求20所述的车载终端,其特征在于,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级;
    所述第二发送子模块,具体用于将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的部分或全部业务的标识和标识对应的业务交互优先级发送给该路侧设备,以使路侧设备按照标识对应的业务交互优先级从高到低的顺序依次向车载终端提供相应的业务数据。
  22. 如权利要求20所述的车载终端,其特征在于,所述第二发送子模块, 还用于在将所述业务需求匹配信息中该路侧设备所能提供的车载终端感兴趣的业务的标识发送给该路侧设备之后,接收该路侧设备发送的业务数据之前,向该路侧设备发送业务数据请求。
  23. 如权利要求17所述的车载终端,其特征在于,在路侧设备能提供的车载终端感兴趣的业务的数量大于1时,所述业务需求匹配信息还包括:车载终端感兴趣的各业务的标识对应的业务交互优先级;所述获取模块包括:第三发送子模块和第三接收子模块;
    所述第三发送子模块,用于按照业务的标识对应的业务交互优先级由高到低的顺序,依次向该路侧设备发送携带该路侧设备能提供的车载终端感兴趣的业务的标识的业务数据请求;
    所述第三接收子模块,用于接收路侧设备发送的业务数据,所述业务数据是路侧设备根据该车载终端感兴趣的业务的标识确定的。
  24. 如权利要求17至23任一所述的车载终端,其特征在于,还包括:
    确定模块,用于将行驶信息和感兴趣的业务的标识发送给车路交互业务管理中心;接收车路交互业务管理中心发送的业务需求匹配信息,所述业务需求匹配信息是车路交互业务管理中心将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配得到的;或者将行驶信息和感兴趣的业务的标识,与本地存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,得到业务需求匹配信息。
  25. 一种车载终端,其特征在于,包括:
    发送模块,用于向车路交互业务管理中心发送车载终端的标识、行驶信息和感兴趣的业务的标识,以使车路交互业务管理中心根据所述行驶信息和感兴趣的业务的标识确定该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
    接收模块,用于在所述车载终端与行车路线上经过的能提供车载终端感 兴趣的部分或全部业务的所述路侧设备的标识所表示的路侧设备建立连接之后,接收该路侧设备发送的业务数据,所述业务数据是该路侧设备根据车路交互业务管理中心下发的该车载终端的标识和业务需求匹配信息确定的。
  26. 一种路侧设备,其特征在于,包括:
    接收模块,用于接收车路交互业务管理中心下发的车载终端的标识和该车载终端的业务需求匹配信息,其中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
    传输模块,用于在所述路侧设备与所述车载终端的标识所表示的车载终端建立连接后,根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
  27. 如权利要求26所述的路侧设备,其特征在于,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务对应的业务交互优先级;
    所述传输模块,具体用于按照各业务对应的业务交互优先级由高到底的顺序,向该车载终端发送自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
  28. 如权利要求26所述的路侧设备,其特征在于,所述车载终端感兴趣的业务包括管理管制类业务且车载终端感兴趣的业务数据为管理管制类文件传输请求;
    所述接收模块,还用于接收各业务服务器根据车路交互业务管理中心下发所述车载终端的感兴趣的管理管制类业务的标识发送的第一管理管制类文件传输请求,所述第一管理管制类文件传输请求中携带有该业务服务器的标识和请求传输的文件的文件标识;
    所述传输模块,具体用于向车载终端发送第二管理管制类文件传输请求,所述第二管理管制类文件传输请求中携带有接收的各第一管理管制类文件传 输请求中携带的文件标识;接收车载终端发送的第二管理管制类文件传输响应,所述第二管理管制类文件传输响应中携带有各所述文件标识对应的文件数据;
    所述传输模块,还用于在接收车载终端发送的第二管理管制类文件传输响应之后针对任一第一管理管制类文件传输请求,从第二管理管制类文件传输响应中的获得该第一管理管制类文件传输请求中的文件标识对应的文件数据,将获得的数据发送给该第一管理管制类文件传输请求中的业务服务器的标识所表示的业务服务器。
  29. 一种车路交互业务管理中心,其特征在于,包括:
    接收模块,用于接收车载终端的标识、该车载终端的行驶信息和感兴趣的业务的标识;
    匹配模块,用于将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,获得该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
    发送模块,用于将所述车载终端的标识和所述车载终端的业务需求匹配信息下发给各路侧设备的标识所表示的路侧设备,以使各路侧设备在确定与所述车载终端的标识所表示的车载终端建立连接后,根据所述车载终端的业务需求匹配信息向该车载终端发送业务数据。
  30. 如权利要求29所述的车路交互业务管理中心,其特征在于,所述匹配模块,具体用于根据所述行驶信息确定车载终端可能的各行车路线;针对确定的每一行车路线,执行以下操作:确定覆盖区域包含该行车路线的路侧设备的标识以及各路侧设备能够提供的业务的标识;针对该行车路线上的每一路侧设备,判断车载终端感兴趣的部分或全部业务的标识是否包含在该路侧设备能够提供的业务的标识中;若包含在该路侧设备能够提供的业务的标识中,则确定该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识; 将确定的该路侧设备能提供的车载终端感兴趣的部分或全部业务的标识记和该路侧设备的标识作为业务需求匹配信息。
  31. 如权利要求30所述的车路交互业务管理中心,其特征在于,在路侧设备能提供的车载终端感兴趣的业务的个数大于1时,所述业务需求匹配信息还包括:该路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级。
  32. 如权利要求31所述的车路交互业务管理中心,其特征在于,所述匹配模块,具体用于通过以下方式确定各路侧设备所能提供的车载终端感兴趣的各业务的标识对应的业务交互优先级:针对每一能提供车载终端的感兴趣的业务的数量大于1的路侧设备,执行以下操作:针对该路侧设备能提供车载终端的感兴趣的每一业务,确定该路侧设备所在的行车路线上的能提供该业务的路侧设备的数量;并按照能提供该业务的路侧设备的数量越少对应的业务交互优先级越高的原则,为该路侧设备的该业务的标识设置对应的业务交互优先级。
  33. 一种车路信息交互系统,其特征在于,包括:权利要求17至24任一所述的车载终端和至少一个路侧设备。
  34. 一种车路信息交互系统,其特征在于,包括:权利要求25所述的车载终端、权利要求29至32任一所述的车路交互业务管理中心和至少一个权利要求26至28任一所述的路侧设备。
  35. 一种车载终端,其特征在于,包括:处理器、存储器和收发机;
    所述处理器,用于读取所述存储器中的程序,执行下列过程:
    在所述车载终端与路侧设备建立连接之后,根据确定的业务需求匹配信息,判断该路侧设备的标识是否包含在能提供车载终端感兴趣的部分或全部业务的路侧设备的标识中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
    在判断模块确定该路侧设备的标识包含在能提供车载终端感兴趣的业务 的路侧设备的标识中时,从该路侧设备获取其所能提供的车载终端感兴趣的业务的标识对应的业务数据。
  36. 一种车载终端,其特征在于,包括:处理器、存储器和收发机;
    所述处理器,用于读取所述存储器中的程序,执行下列过程:
    用于向车路交互业务管理中心发送车载终端的标识、行驶信息和感兴趣的业务的标识,以使车路交互业务管理中心根据所述行驶信息和感兴趣的业务的标识确定该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
    在所述车载终端与行车路线上经过的能提供车载终端感兴趣的部分或全部业务的所述路侧设备的标识所表示的路侧设备建立连接之后,接收该路侧设备发送的业务数据,所述业务数据是该路侧设备根据车路交互业务管理中心下发的该车载终端的标识和业务需求匹配信息确定的。
  37. 一种路侧设备,其特征在于,包括:处理器、存储器和收发机;
    所述处理器,用于读取所述存储器中的程序,执行下列过程:
    接收车路交互业务管理中心下发的车载终端的标识和该车载终端的业务需求匹配信息,其中,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
    在所述路侧设备与所述车载终端的标识所表示的车载终端建立连接后,根据所述业务需求匹配信息,向该车载终端传输自身所能提供的车载终端感兴趣的业务的标识对应的业务数据。
  38. 一种车路交互业务管理中心,其特征在于,包括:处理器、存储器和收发机;
    所述处理器,用于读取所述存储器中的程序,执行下列过程:
    接收车载终端的标识、该车载终端的行驶信息和感兴趣的业务的标识;
    将所述行驶信息和感兴趣的业务的标识与存储的各路侧设备的覆盖区域和能够提供的业务的标识进行匹配,获得该车载终端的业务需求匹配信息,所述业务需求匹配信息包括:该车载终端可能的行车路线上经过的能提供该车载终端感兴趣的部分或全部业务的各路侧设备的标识,以及各路侧设备所能提供的车载终端感兴趣的业务的标识;
    将所述车载终端的标识和所述车载终端的业务需求匹配信息下发给各路侧设备的标识所表示的路侧设备,以使各路侧设备在确定与所述车载终端的标识所表示的车载终端建立连接后,根据所述车载终端的业务需求匹配信息向该车载终端发送业务数据。
PCT/CN2016/073362 2015-02-10 2016-02-03 一种车路信息交互方法、设备及系统 WO2016127895A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201510070028.7A CN105991704B (zh) 2015-02-10 2015-02-10 一种车路信息交互方法、设备及系统
CN201510070028.7 2015-02-10

Publications (1)

Publication Number Publication Date
WO2016127895A1 true WO2016127895A1 (zh) 2016-08-18

Family

ID=56614127

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2016/073362 WO2016127895A1 (zh) 2015-02-10 2016-02-03 一种车路信息交互方法、设备及系统

Country Status (2)

Country Link
CN (1) CN105991704B (zh)
WO (1) WO2016127895A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115696263A (zh) * 2022-09-02 2023-02-03 北京交通大学 一种基于节点代价与业务优先级的城轨车载业务传输方法

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106850744B (zh) * 2016-12-21 2020-08-04 大唐高鸿信息通信研究院(义乌)有限公司 一种车载短距离通信网的路侧节点服务发布方法
CN110139340A (zh) * 2018-02-09 2019-08-16 电信科学技术研究院有限公司 一种连接建立方法及终端
CN111982109A (zh) * 2019-05-24 2020-11-24 北京百度网讯科技有限公司 用于路径规划的方法、装置、设备和计算机可读存储介质
CN110827541B (zh) * 2019-11-08 2022-04-26 腾讯科技(深圳)有限公司 一种信息获取方法、装置、设备及存储介质
CN111970663B (zh) * 2020-08-04 2024-02-09 深圳成谷智能科技有限公司 一种车载单元接入标准5g核心网的方法及装置
CN114969502B (zh) * 2021-06-21 2023-10-27 中移互联网有限公司 车用信息交换方法及系统、计算机可读存储介质
CN115195738A (zh) * 2022-07-21 2022-10-18 智道网联科技(北京)有限公司 车辆变道方法、装置及电子设备、存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101409748A (zh) * 2008-07-08 2009-04-15 浙江大学 一种移动终端的信息收集、索引、订阅发布系统和方法
US20120169517A1 (en) * 2010-11-30 2012-07-05 Institute For Information Industry Driving Assistance Method, On-Board Unit (OBU) Applying the Method and Computer Readable Storage Medium Storing the Method
CN102768768A (zh) * 2011-05-06 2012-11-07 深圳市金溢科技有限公司 一种智能交通服务系统
CN103854317A (zh) * 2012-12-04 2014-06-11 天津中兴软件有限责任公司 Etc系统的通信方法

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7389181B2 (en) * 2004-08-31 2008-06-17 Visre, Inc. Apparatus and method for producing video drive-by data corresponding to a geographic location
CN101604982B (zh) * 2008-06-12 2013-02-27 上海寰创通信科技股份有限公司 同频覆盖下感应切换的方法
CN101833868B (zh) * 2010-05-20 2011-12-28 浙江中控研究院有限公司 交通监控系统和监控方法
CN103946829B (zh) * 2011-10-05 2016-09-21 美国亚德诺半导体公司 用于高速数据和电力分配的双线通信系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101409748A (zh) * 2008-07-08 2009-04-15 浙江大学 一种移动终端的信息收集、索引、订阅发布系统和方法
US20120169517A1 (en) * 2010-11-30 2012-07-05 Institute For Information Industry Driving Assistance Method, On-Board Unit (OBU) Applying the Method and Computer Readable Storage Medium Storing the Method
CN102768768A (zh) * 2011-05-06 2012-11-07 深圳市金溢科技有限公司 一种智能交通服务系统
CN103854317A (zh) * 2012-12-04 2014-06-11 天津中兴软件有限责任公司 Etc系统的通信方法

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115696263A (zh) * 2022-09-02 2023-02-03 北京交通大学 一种基于节点代价与业务优先级的城轨车载业务传输方法

Also Published As

Publication number Publication date
CN105991704B (zh) 2019-04-19
CN105991704A (zh) 2016-10-05

Similar Documents

Publication Publication Date Title
WO2016127895A1 (zh) 一种车路信息交互方法、设备及系统
US11030843B2 (en) Implementing a transport service using unique identifiers
CN111459149B (zh) 一种智能车辆编队行驶方法、装置及系统
WO2022095813A1 (zh) 一种业务数据处理方法、设备以及可读存储介质
CN105144262A (zh) 用于传送包括多个经过地点的最优路径的方法和装置
CN106952062A (zh) 一种智能物流的监控方法及系统
CN107852429A (zh) 车辆外联通信方法、装置及终端
US20240292302A1 (en) Track Information Exchange Method and Apparatus
WO2023044721A1 (en) Infrastructure-based collaborative automated parking and location management
CN108419213A (zh) 组变更方法及装置
CN103248691A (zh) 车联网系统及其数据备份方法
WO2018153296A1 (zh) 一种发现车队的方法和设备
CN107454574B (zh) 设备到设备d2d的通信方法、装置和车联网终端
CN114897428A (zh) 一种订单处理方法、装置、电子设备及存储介质
KR102184100B1 (ko) 앱 미터기를 이용한 모빌리티 합승 호출 서비스 제공 방법 및 이에 사용되는 관리 서버
US20230129199A1 (en) Method of coordinating one or more maneuvers among vehicles
CN103227834A (zh) 车联网系统及其数据备份方法
KR20210151771A (ko) 도착지로 운행 중인 차량의 배차 관리 방법, 이에 사용되는 관리 서버 및 도착지로 운행 중인 차량의 배차 관리 방법을 실행시키는 프로그램이 기록된 기록 매체
WO2023016140A1 (zh) 交互方法、交互装置
CN204833725U (zh) 一种实时拥堵报警装置
CN114298539B (zh) 一种车辆调度方法、装置、电子设备及存储介质
Danquah et al. Data partitioning and scheduling schemes for federated platoon-based vehicular cloud
WO2020143207A1 (zh) 一种应用于物联网的终端管理方法、装置及存储介质
CN105992122A (zh) 一种wave通信设备服务通信协同的方法、相关设备及系统
CN111356073A (zh) 任务处理方法、装置及设备

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 16748696

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 16748696

Country of ref document: EP

Kind code of ref document: A1