Vehicle internet communication methods and devices

Abstract

A vehicle internet communication method, apparatus, and storage medium are provided. The vehicle internet communication method includes the steps of: a first roadside unit receiving transfer information of a target mounted unit transmitted by a second roadside unit, wherein the target mounted unit is a mounted unit that communicates with the second roadside unit, and the transfer information of the target mounted unit includes an identifier of the target mounted unit; and storing the transfer information of the target mounted unit in a transfer table.

Description

Technical Field

[0001] (Cross - reference to related applications) This application claims priority based on a Chinese patent application with application number 202310248793.8 filed on March 3, 2023 as the basic application, and all of its disclosure content is incorporated herein by reference.

[0002] This disclosure relates to the field of vehicle Internet technology, and particularly to vehicle Internet communication methods, devices, and storage media.

Background Art

[0003] With the continuous development of information technology, Vehicle - to - Everything (V2X) has become a research hot - spot with great potential as a next - generation information and communication technology spanning fields such as communication, vehicles, and transportation. Currently, as a major candidate technology for the global vehicle Internet, Cellular Vehicle - to - everything (C - V2X) technology has also attracted increasing attention. Currently, many vehicle Internet application demonstrations based on C - V2X technology have been launched across the country.

Summary of the Invention

Means for Solving the Problems

[0004] In one aspect, an embodiment of this disclosure provides a vehicle Internet communication method applied to a first roadside unit. This vehicle Internet communication method includes receiving transfer information of a target on - vehicle unit transmitted by a second roadside unit, where the target on - vehicle unit is an on - vehicle unit that communicates with the second roadside unit, and the transfer information of the target on - vehicle unit includes an identifier of the target on - vehicle unit, and storing the transfer information of the target on - vehicle unit in a transfer table.

[0005] In other embodiments, embodiments of the present disclosure provide a vehicle internet communication method applicable to a second roadside unit. This vehicle internet communication method is A step of obtaining transfer information of a target mounting unit, wherein the target mounting unit is a mounting unit that communicates with a second roadside unit, and the transfer information includes an identifier of the target mounting unit. The process includes the step of transmitting transfer information to a first roadside unit.

[0006] In other embodiments, embodiments of the present disclosure provide a communication device comprising a memory and a processor, the memory and the processor being coupled, the memory being used to store instructions that can be executed by the processor, and when the processor executes the instructions, the communication device implements the method described in any one of the above descriptions.

[0007] In another embodiment, embodiments of the present disclosure provide a computer-readable storage medium in which computer program instructions are stored, and when the computer program instructions are executed by a computer, the method described in any one of the above paragraphs is realized.

[0008] In another embodiment, embodiments of the present disclosure provide a computer program product which includes computer program instructions, and when such computer program instructions are executed by a computer, the computer implements the method described in any one of the above descriptions.

[0009] To more clearly illustrate the technical solutions of this disclosure, the drawings used in some embodiments of this disclosure are briefly described below. Obviously, the drawings in the following description are only those of some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these. [Brief explanation of the drawing]

[0010] [Figure 1]This figure shows the architecture of a communication system according to several embodiments. [Figure 2] This is a flowchart of a vehicle internet communication method according to several embodiments. [Figure 3] This is a flowchart of another vehicle internet communication method relating to several embodiments. [Figure 4] This is a flowchart of yet another vehicle internet communication method relating to several embodiments. [Figure 5] This is a flowchart of yet another vehicle internet communication method relating to several embodiments. [Figure 6] This is a scenario diagram of a vehicle internet communication method according to several embodiments. [Figure 7] This is a scenario diagram of another vehicle internet communication method according to several embodiments. [Figure 8] This is a scenario diagram of yet another vehicle internet communication method relating to several embodiments. [Figure 9] This is a scenario diagram of yet another vehicle internet communication method relating to several embodiments. [Figure 10] This is a scenario diagram of yet another vehicle internet communication method relating to several embodiments. [Figure 11] This is a scenario diagram of yet another vehicle internet communication method relating to several embodiments. [Figure 12] This is a scenario diagram of yet another vehicle internet communication method relating to several embodiments. [Figure 13] This figure shows the configuration of a communication device according to several embodiments. [Figure 14] This figure shows the configuration of another communication device according to several embodiments. [Modes for carrying out the invention]

[0011] The following clearly and completely describes the technical solutions in the present disclosure with reference to the drawings of the present disclosure. Obviously, the described embodiments are only a part of the embodiments of the present disclosure, rather than all embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by those skilled in the art without creative labor shall fall within the protection scope of the present disclosure.

[0012] In addition, in the present disclosure, expressions such as "exemplarily" or "for example" are used for the purpose of giving examples, illustrations or explanations. Any embodiment or design solution described as "exemplarily" or "for example" in the present disclosure In this disclosure should not be construed as being more preferred or having an advantage over other embodiments or design solutions. Exactly, by using expressions such as "exemplarily" or "for example", the purpose is to show the related concepts in detail.

[0013] In the following, terms such as "first" and "second" are used only for the purpose of explanation and should not be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, features limited by "first", "second", etc. may explicitly or implicitly include one or more of such features.

[0014] In the description of the present disclosure, unless otherwise specified, " / " represents the meaning of "or". For example, A / B can represent A or B. "And / or" in the text only describes the relevant relationship of the relevant object and indicates that three types of relationships may exist. For example, A and / or B can represent three cases: only A exists, only B exists, and both A and B exist. Also, "at least one" refers to one or more, and "a plurality" refers to two or more.

[0015] With the continuous development of information technology, vehicle-to-everything (V2X) has become a research hot spot with great potential as a next-generation information and communication technology that spans fields such as communication, vehicles, and transportation. Currently, as a major candidate technology for vehicle-to-everything in the world, cellular vehicle-to-everything (C-V2X) technology has also attracted increasing attention.

[0016] To facilitate understanding, V2X and C-V2X technologies are briefly described below first.

[0017] V2X is an abbreviation of Vehicle-to-Everything, and is used to achieve all-round communication between the on-board unit, the surrounding environment, and the network. For example, V2X can achieve communication interconnection between vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), and vehicle-to-network (V2N).

[0018] C-V2X is an abbreviation of Cellular Vehicle-to-Everything, and is a Vehicle-to-Everything that integrates cellular communication and direct communication.

[0019] In C-V2X that integrates direct communication, data transmission can be performed between terminals (such as on-board units, roadside units, etc.) via the direct link PC5 interface, thereby realizing communication connections such as V2V, V2I, and V2P without passing through the base station, and supporting two types of scenarios inside and outside the cellular coverage.

[0020] In C-V2X technology that integrates cellular communication, V2N communication can be realized between the terminal (such as on-board unit, roadside unit, etc.) and the base station via the Uu interface, and communication such as V2V, V2I, and V2P can be realized based on data transfer by the base station. As the cellular mobile communication system evolves from 4G to 5G, C-V2X further includes LTE-V2X and NR-V2X. It is understood that as the communication system evolves, C-V2X may further include other Vehicle-to-Everything technologies that are compatible with future communication technologies.

[0021] However, C-V2X in some technologies still faces some problems.

[0022] On the other hand, in C-V2X technology that integrates direct communication, deploying an entirely new PC5 V2X network faces challenges such as excessive deployment for full coverage, low user adoption rates of onboard units (OBUs) that use the PC5 interface, and limited operational capabilities, making large-scale deployment difficult.

[0023] On the other hand, in C-V2X technology that integrates cellular communication, terminals (e.g., onboard units) communicate via a Uu interface. Therefore, when a terminal moves between different integrated cellular units (e.g., roadside units) or between base stations equipped with different integrated cellular units, situations may arise where the service of the onboard unit is interrupted or service continuity is reduced.

[0024] In contrast, embodiments of the present disclosure provide a vehicle internet communication method that can be used to ensure service continuity when an onboard unit spans different integrated ventilation units. The method includes the steps of: a first roadside unit receiving a target onboard unit transfer information transmitted by a second roadside unit, the target onboard unit being an onboard unit communicating with the second roadside unit, the transfer information of the target onboard unit including an identifier for the target onboard unit; and storing the transfer information of the target onboard unit in a transfer table.

[0025] Furthermore, the vehicle internet communication method provided by the embodiments of this disclosure can be applied to systems of multiple communication standards. For example, the method provided by the embodiments of this disclosure can be applied to next-generation communication systems such as Long Term Evolution (LTE) systems, systems based on various evolutionary versions of LTE, 5G systems, and New Radio (NR). In addition, the method provided by the embodiments of this disclosure can be applied to future communication technologies, etc.

[0026] The network architecture of the communication network in the embodiments of this disclosure may include integrated communication units (e.g., roadside units, base stations, roadside sensing devices, etc.) and terminals (e.g., onboard units, etc.). In some embodiments, the network architecture may further include service terminals (e.g., servers or core networks, etc.).

[0027] As an example, Figure 1 shows a schematic diagram of the communication system architecture, with the integrated ventilation unit as a roadside unit (RSU) and the terminal as an onboard unit. Referring to Figure 1, the communication system 100 includes, but is not limited to, roadside units (e.g., first roadside unit 101, second roadside unit 102) and onboard units (e.g., target onboard unit 103 in Figure 1). In some embodiments, as shown in Figure 1, the communication system 100 further includes a service terminal (e.g., vehicle internet server 104 in Figure 1).

[0028] A roadside unit (RSU) is a device installed on the roadside to enable V2X communication. For example, a roadside unit may be the base station itself. Alternatively, a roadside unit may include at least one of the following components that make up a base station: an active antenna unit (AAU), a building base band unit (BBU), or a radio remote unit (RRU). Alternatively, a roadside unit may be a roadside sensing system. Alternatively, a roadside unit may be another device having service functions (e.g., data transmission and reception) and / or management functions. Alternatively, a roadside unit may be a virtual roadside unit (vRSU). Alternatively, a roadside unit may be a device such as a camera, LiDAR, millimeter-wave radar, or industrial computer. In some embodiments, a roadside unit may further be a collection of one or more of the above-mentioned devices. In one example, a roadside unit may be one or more combinations of a BBU, AAU, and a roadside sensing system. The forms and functions of the roadside units described above are illustrative and are not limited to those described herein. Roadside units may be located together with traffic lights, solar-powered streetlights, trees, buildings, devices, base stations, utility poles, etc., in a scenario, or they may be located alone in a scenario, and are not limited to these arrangements. In some examples, a roadside unit includes at least a communication unit, and the communication unit supports a Uu interface for V2N communication. In other examples, the communication unit further supports a PC5 interface for V2I communication. It is understood that data transmission can occur with a roadside unit when the mounted unit is within the service area of ​​that roadside unit.

[0029] An Onboard Unit (OBU) is a device mounted in a vehicle to enable V2X communication. For example, an Onboard Unit may be a car navigation system, or it may be another type of onboard hardware or software device. The embodiments of this disclosure do not limit the content and form of the Onboard Unit. The Onboard Unit may integrate a communication network, for example, a 4G / 5G Uu communication chip and module, or an LTE-V2X / 5G NR-V2X communication chip and module. The Onboard Unit may use a Uu interface and / or a PC5 interface. In some examples, the basic functions of the Onboard Unit include service functions (for example, the basic functions of the Onboard Unit include at least one of service functions such as data transmission and reception, protocol conversion, reading CAN (Controller Area Network) bus data, positioning, and clock synchronization). The embodiments of this disclosure also do not limit the functions of the Onboard Unit.

[0030] The service terminal is used to provide services to the onboard unit, and for example, the service terminal can provide vehicle internet-related services. The service terminal may be a server (e.g., a vehicle internet server), a core network, or a node within the core network, and this disclosure is not limited to the form of the service terminal. In some embodiments, the service terminal and the onboard unit are roadside Communication is achieved through the unit. For example, a service terminal may transmit service information to the onboard unit via a roadside unit. Alternatively, for example, a service terminal may receive registration information from the onboard unit via a roadside unit and register the onboard unit based on that registration information.

[0031] Although Figure 1 shows only one mounted unit and two roadside units, there may actually be many more mounted units or roadside units. For example, one mounted unit may sequentially span the service ranges of three or more different roadside units. Also, for example, multiple mounted units may move simultaneously or sequentially from the service range of one roadside unit to the service range of another roadside unit. This disclosure is not limited thereto.

[0032] When an onboard unit is moved, it should be considered that the onboard unit's IP (Internet Protocol) address may change. If the onboard unit and the roadside unit use Uu interface communication, and the transmission control protocol (TCP) is used, a TCP connection exists between the onboard unit and the service end. This TCP connection includes a quadruple containing the onboard unit's IP address. Therefore, if the onboard unit's IP address changes, the TCP connection between the onboard unit and the service end will be interrupted. If it is necessary to re-establish the TCP connection between the onboard unit and the service end, a three-way handshake is required, causing a significant delay and affecting the continuity of the service.

[0033] Therefore, in the embodiments of this disclosure, the connection between the mounted unit and the service end is established based on the User Datagram Protocol (UDP), and communication between the mounted unit and the roadside unit is performed using the UDP protocol.

[0034] Unlike TCP, with UDP connections, the sender does not need to establish a connection before sending data; they can send data packets if they know the receiver's IP address and port number. The receiver can receive data from any IP address on the specified port without needing to give any acknowledgment to the sender. Furthermore, after receiving a UDP message, the receiver can obtain the IP address and port number of the sender of that UDP message.

[0035] In Quick UDP Internet Connection (QUIC), a protocol derived from UDP, QUIC connections can only identify a random number generated by the service end as their ID. As a result, as long as the ID remains unchanged, the connection between the service end and the installed unit will still be maintained even if the IP address or port number of the installed unit changes. Therefore, there is no need to re-establish the connection, and to a certain extent, the continuity of the installed unit's services can be guaranteed.

[0036] It is understood that the above-described communication system may have other names (for example, it may be called a communication network, network system, network architecture, communication architecture, etc.), and that the above-described communication system may further include other possible network configurations (for example, core network network elements, etc.), and that the embodiments of this disclosure are not limited thereto.

[0037] Furthermore, the aforementioned communication system is merely intended to provide a clearer explanation of the technical solutions of this disclosure and does not limit the disclosure. Those skilled in the art will understand that, as network architectures evolve and new service scenarios emerge, the technical solutions provided in this disclosure are similarly applicable to similar technical challenges.

[0038] To more clearly explain the technical solutions provided by the embodiments of this disclosure, the vehicle internet communication method provided by the embodiments of this disclosure will be described in detail below.

[0039] Figure 2 shows an example of a vehicle internet communication method according to an embodiment of the present disclosure. Referring to Figure 2, this method includes steps S101 to S103.

[0040] S101, the second roadside unit acquires the transfer information of the target-mounted unit.

[0041] The target onboard unit is the onboard unit that communicates with the second path-side unit.

[0042] In some embodiments, the transfer information includes an identifier for the target-mounted unit.

[0043] In some embodiments, the transfer information is Service requirements for the target onboard unit, The port number of the target-mounted unit, The IP address of the target-mounted unit, It further includes at least one of the service statuses of the target onboard unit.

[0044] In some embodiments, a correspondence exists between the service request of a target-equipped unit and the port number of the target-equipped unit. For example, a service request of a target-equipped unit corresponds to a single port number of the target-equipped unit. Alternatively, for example, a service request of a target-equipped unit may be bound to the port number of the target-equipped unit, and if the forwarding information includes a service request of the target-equipped unit, the second forward unit may determine the port number of the target-equipped unit based on the service request and the correspondence.

[0045] In some embodiments, the service status of the target-bearing unit is used to indicate whether the target-bearing unit is active or inactive.

[0046] To facilitate understanding of the service status of the target-carrying unit, the active and inactive states of the target-carrying unit are explained below with illustrative examples.

[0047] (1) Active State If the service status of a target-carrying unit stored in a roadside unit is active, the relationship between that roadside unit and the target-carrying unit may satisfy any of the following situations 1-1 to 1-4.

[0048] Situation 1-1: The target unit has already moved to the service area of ​​the roadside unit in question.

[0049] Situation 1-2: The target-mounted unit can communicate with the roadside unit.

[0050] For example, the target-mounted unit can transmit service data to the roadside unit. Alternatively, for example, the target-mounted unit may have established a communication connection with the roadside unit.

[0051] Situation 1-3: The roadside unit received information transmitted by the target-mounted unit.

[0052] Situation 1-4: The roadside unit is providing service to the target unit.

[0053] (2) Inactive / Standby State If the service status of a target-carrying unit stored in a roadside unit is inactive, the relationship between that roadside unit and the target-carrying unit may satisfy any of the following situations 2-1 to 2-6.

[0054] Situation 2-1: The target-carrying unit has not yet moved to the service area of ​​the roadside unit.

[0055] Situation 2-2: The target-mounted unit is not communicating with the roadside unit.

[0056] For example, the target-carrying unit has not transmitted information to the roadside unit, or has not established a communication connection with the roadside unit.

[0057] Situation 2-3: The target-mounted unit did not communicate with the roadside unit within the first predetermined time.

[0058] The first predetermined time may have other names, such as activation waiting time or active-time, and this disclosure is not limited to these.

[0059] Situation 2-4: The target-mounted unit is communicating with another roadside unit adjacent to the roadside unit in question.

[0060] Scenario 2-5: The target-mounted unit may communicate with the roadside unit or pass through the service area of ​​the roadside unit within the following period (e.g., one predetermined time period).

[0061] Situation 2-6: A roadside unit that has a related relationship with the roadside unit in question is providing service to the target mounting unit.

[0062] For example, a roadside unit adjacent to the roadside unit in question is providing service to the target-equipped unit. Alternatively, for example, a roadside unit belonging to the same predetermined roadside unit group as the roadside unit in question is providing service to the target-equipped unit.

[0063] The possible active and inactive states described above are merely examples, and this disclosure is not limited to these.

[0064] In some embodiments, the forwarding information of the target-carrying unit is obtained based on information transmitted by the target-carrying unit. Furthermore, after obtaining the forwarding information of the target-carrying unit, the second path-side unit may set the service status of the target-carrying unit to the active state in the forwarding table.

[0065] In some embodiments, if the service status in the forwarding information is active, and the second path unit does not receive information transmitted by the target-mounted unit within a first predetermined time, the second path unit sets the service status in the forwarding information to inactive.

[0066] For example, if the service status in the forwarding information is active, the second roadside unit sends a V2X message to the IP address of the target unit. If the message sent by the target unit is not received within a first predetermined time, the service status of the target unit is set to inactive. In some examples, the message sent by the target unit may include at least one of the following: service access request information, basic safety message (BSM), road side information (RSI) / road safety message (RSM), signal phase timing message (SPAT), and map message, and may also be any message that the target unit sends to the second roadside unit.

[0067] In some embodiments, S101 may be implemented such that, for example, the second roadside unit receives service access request information from the target-mounting unit and generates transfer information based on the service access request information.

[0068] The service access request information includes at least the identifier of the target-mounted unit. In some examples, the service access request information is: Service requirements for the target onboard unit, The port number of the target-mounted unit, It may include at least one of the IP addresses of the target-mounted unit.

[0069] For example, the second forward unit receives service access request information from the target unit, which includes the target unit's identifier, the target unit's service request, and the target unit's IP address. Based on this, the second forward unit can generate forwarding information that includes at least the target unit's identifier, the target unit's service request, the target unit's IP address, and the target unit's service status. The target unit's service status is set to active.

[0070] In some embodiments, it is understood that service access request information includes the IP address of the target unit if the service access request information is carried in an uplink message sent by the target unit and the IP address of the target unit is present in the uplink message, or if the IP address of the target unit is not present in the uplink message but can be determined by the second roadside unit based on analysis of the uplink message.

[0071] In some embodiments, service access request information is transmitted by the target-mounted unit to the second roadside unit based on the Uu interface.

[0072] In some embodiments, the service access request is sent by the target-carrying unit to the second-side unit using UDP or QUIC.

[0073] In some embodiments, the second path unit acquires the transfer information of the target mounted unit and then adds or stores this transfer information in its own transfer table. The transfer table of the second path unit contains the transfer information of multiple mounted units.

[0074] In some embodiments, the second forwarding unit may further update the forwarding information of the target-carrying unit stored in its forwarding table based on information transmitted by the target-carrying unit. For example, if the IP address of the target-carrying unit changes as the target-carrying unit moves, the second forwarding unit may further update the IP address of the target-carrying unit in the forwarding information based on information transmitted by the target-carrying unit.

[0075] In some embodiments, the second path unit may further transmit data with the target-mounting unit based on the transfer information of the target-mounting unit.

[0076] For example, if the forwarding information includes the identifier and IP address of the target unit, the second roadside unit can obtain service data for the target unit from the service end (e.g., a vehicle internet server) based on the identifier and send that service data to the target unit's IP address.

[0077] In some embodiments, the second path-side unit and the target-carrying unit transmit data using UDP or QUIC.

[0078] When transmitting data using UDP or QUIC connections, it is important to understand that the UDP or QUIC connection established between the target roadside unit and the service end is indexed by the identifier of the target unit. Therefore, as long as the identifier of the target unit does not change, the connection between the service end and the target unit will still be maintained even if the IP address or port number of the target unit changes, and there is no need to re-establish the connection or re-register the target unit with the service end. This ensures service continuity when the target unit spans different roadside units.

[0079] In some embodiments, when the second roadside unit and the target-carrying unit transmit data using QUIC, the identifier of the target-carrying unit may be associated with an ID generated by the service end, or the identifier of the target-carrying unit may be bound to an ID generated by the service end, or the identifier of the target-carrying unit may be associated with an ID generated by the service end.

[0080] It is understood that QUIC connections can identify target-carrying units using only random numbers generated by the service end as their ID. Since the identifier of a target-carrying unit is unique and immutable, as long as the identifier of the target-carrying unit does not change, the ID generated by the service end corresponding to / bound to / associated with that identifier will still be retained, even if the IP address or port number of the target-carrying unit changes. Therefore, the connection between the service end and the target-carrying unit will still be maintained, and there is no need to re-establish the connection or re-register the target-carrying unit with the service end. This ensures service continuity when a target-carrying unit crosses different roadside units.

[0081] S102, the second roadside unit transmits the transfer information of the target-mounted unit to the first roadside unit, and in response, the first roadside unit receives the transfer information of the target-mounted unit transmitted by the second roadside unit.

[0082] In some embodiments, a relationship exists between the first roadside unit and the second roadside unit. For example, the first roadside unit may be a unit adjacent to the second roadside unit. Alternatively, for example, the second roadside unit may be associated with a group of roadside units, the group of roadside units including at least the first roadside unit. This disclosure is not limited to the detailed relationships between the first roadside unit and the second roadside unit.

[0083] In some embodiments, if at least one of the following conditions 1-1 to 1-3 is met, the second path-side unit transmits the transfer information of the target-mounted unit to the first path-side unit.

[0084] Condition 1-1: The predetermined cycle start point has been reached.

[0085] For example, when a predetermined cycle start point is reached, the second path-side unit transmits the transfer information of the target-mounted unit to the first path-side unit. This allows the transfer table in the first path-side unit to be updated periodically.

[0086] Condition 1-2: The transfer information for the target mounted unit in the transfer table of the second roadside unit has changed.

[0087] For example, if the second path unit adds or stores the forwarding information of the target-carrying unit, or updates the forwarding information of the target-carrying unit, the second path unit transmits the forwarding information of the target-carrying unit to the first path unit. This avoids redundant transmission of forwarding information between the first and second path units, thereby saving overhead.

[0088] Condition 1-3: The service status in the transfer information of the target-carrying unit stored in the second roadside unit is active.

[0089] Conditions 1-3 can be understood by referring to the description of the inactive state above. For example, if a target-carrying unit has not yet moved into the service range of a roadside unit, and that roadside unit has transfer information for a target-carrying unit in an inactive service state stored in it, that roadside unit will not continue to transfer or transmit that transfer information to other roadside units.

[0090] This prevents the transmission of target-mounted unit information indefinitely, and ensures that the transmission information is stored only in the second roadside unit that communicates with the target-mounted unit, and in roadside units that have a related relationship with the second roadside unit (e.g., the first roadside unit). The explanation of this related relationship can be found above, but will not be repeated here.

[0091] In some embodiments, the second roadside unit transmits forwarding information of the target-carrying unit to the first roadside unit via the base station connection interface. In some examples, the base station connection interface includes at least one of the following: an Xn interface, an N2 interface, or a tunnel connection.

[0092] In some embodiments, the first roadside unit may, after receiving the transfer information of the target-carrying unit, further transmit response information to the second roadside unit. In some examples, this response information is used to indicate whether the reception was successful or unsuccessful.

[0093] S103, the first roadside unit stores the transfer information of the target-mounted unit in the transfer table.

[0094] In some embodiments, the transfer table contains transfer information for multiple mounted units. The transfer information for each mounted unit corresponds to the identifier of that mounted unit. In some examples, the first roadside unit may determine the transfer information for the mounted unit corresponding to that identifier from the transfer table based on the identifier of the mounted unit.

[0095] In some embodiments, the first roadside unit stores the transfer information of the target-equipped unit in the transfer table and sets the service status of the target-equipped unit to an inactive state.

[0096] In some embodiments, if the service status in the forwarding information is inactive, and the first roadside unit does not receive information transmitted by the target-mounting unit within a second predetermined time, the first roadside unit deletes the forwarding information of the target-mounting unit. The second predetermined time may have other names, for example, it may also be called standby waiting time, deactivation waiting time, or standby time, but this disclosure is not limited to these.

[0097] In an inactive state, if the first road-side unit does not receive information transmitted by the target-carrying unit within a second predetermined time, it means that the target-carrying unit may not pass through the service range of the first road-side unit or may not communicate with the first road-side unit. Therefore, it is understood that the transfer information is deleted from the transfer table of the first road-side unit to save memory space.

[0098] In another embodiment, when the service status in the forwarding information is inactive, if the first roadside unit receives information transmitted by the target-mounted unit within a second predetermined time, it switches the service status in the forwarding information of the target-mounted unit from inactive to active.

[0099] If, while in an inactive state, the first roadside unit receives information transmitted by the target-equipped unit within a second predetermined time, it means that the target-equipped unit may have already moved into the service range of the first roadside unit, or that the target-equipped unit can communicate with the first roadside unit, or that the target-equipped unit is about to establish a communication connection with the first roadside unit. Therefore, it is understood that the service state will be switched to an active state for subsequent data transmission between the target-equipped unit and the first roadside unit.

[0100] The vehicle internet communication method provided in the embodiments of this disclosure enables the first roadside unit to obtain in advance the identifier of the target-mounted unit that communicates with the second roadside unit. As a result, when the target-mounted unit moves from the second roadside unit to the service area of ​​the first roadside unit, the identifier of the target-mounted unit already exists in the first roadside unit, so the first roadside unit does not need to re-register the target-mounted unit with the service end or re-assist in establishing a connection between the target-mounted unit and the service end, thus guaranteeing service continuity when the mounted unit crosses different roadside units.

[0101] In some embodiments, as shown in Figure 3, the method further includes S104 after S103.

[0102] S104. After detecting that the target-equipped unit has moved within the service range of the first road-side unit, the first road-side unit transmits data to the target-equipped unit based on the transfer information of the target-equipped unit.

[0103] In some embodiments, the first roadside unit may detect whether the target-mounted unit has entered its service range using a variety of methods.

[0104] In some examples, the first roadside unit may detect whether the target-carrying unit has entered its service range by whether it has received information transmitted by the target-carrying unit. For example, if it receives information carrying the identifier of the target-carrying unit, the first roadside unit determines that the target-carrying unit has moved into the service range of the first roadside unit.

[0105] In other examples, the first roadside unit may further use a combination of methods, such as camera imaging and radar ranging, to detect whether the target-carrying unit has moved within the service range of the first roadside unit.

[0106] This disclosure is not limited to the detection method of the first roadside unit.

[0107] In some embodiments, after detecting that the target-carrying unit has moved within the service range of the first roadside unit, the first roadside unit sets the service status of the target-carrying unit to an active state. For example, after receiving information carrying the identifier of the target-carrying unit, the first roadside unit sets the service status of the target-carrying unit to an active state.

[0108] In some embodiments, if the service status of the target-equipped unit stored in the first road-side unit is active, the first road-side unit performs data transmission with the target-equipped unit based on the target-equipped unit's transfer information.

[0109] 1 If the service status of the target-carrying unit stored in the roadside unit is inactive, the target-carrying unit may not yet be within the service range of the first roadside unit. Therefore, data transmission can only be performed when the service status is active. This avoids data loss or unnecessary communication overhead.

[0110] In some embodiments, the forwarding table of the first roadside unit contains forwarding information for Num mounted units, and the first roadside unit may determine the forwarding information for K mounted units from the Num forwarding information, with the service status of the K mounted units being active. Based on the forwarding information for the K mounted units, the first roadside unit performs data transmission with the K mounted units. Num is a positive integer, and K is a positive integer less than or equal to Num. This enables data transmission between a single roadside unit and multiple mounted units.

[0111] In some embodiments, the uplink data transmitted by the target-carrying unit to the first roadside unit includes at least the identifier of the target-carrying unit. In some examples, the uplink data further includes at least one of the target-carrying unit's service request, the target-carrying unit's IP address, and the target-carrying unit's port number.

[0112] In some embodiments, the downlink data transmitted by the first roadside unit to the target-carrying unit is: The service IP address of the first roadside unit, The service port number of the first roadside unit, The service IP address of at least one roadside unit (e.g., the second roadside unit) that has a related relationship with the first roadside unit, The service port number of at least one roadside unit (e.g., a second roadside unit) that has a related relationship with the first roadside unit, Service data of the target onboard unit, This includes, but is not limited to, at least one of the response pieces of information for responding to uplink data from the target-carrying unit.

[0113] In some embodiments, S104 may be implemented such that, after detecting that the target-equipped unit has moved within the service range of the first road-side unit, the first road-side unit obtains service data of the target-equipped unit from the service end based on the identifier of the target-equipped unit, and transmits the service data to the target-equipped unit based on the IP address of the target-equipped unit in the forwarding information.

[0114] In some embodiments, the first roadside unit and the target-carrying unit transmit data using UDP or QUIC.

[0115] When transmitting data using UDP or QUIC connections, it is important to understand that the UDP or QUIC connection established between the target road-side unit and the service end is an indexed connection using the identifier of the target unit. Therefore, as long as the identifier of the target unit does not change, the connection between the service end and the target unit will still be maintained, even if the IP address or port number of the target unit changes.

[0116] Furthermore, during the process of the target-carrying unit moving from the second main-side unit to the service range of the first main-side unit, the first main-side unit already knows the identifier of the target-carrying unit in advance, so the first main-side unit does not need to re-establish the connection or re-register the target-carrying unit with the service end. For example, after the target-carrying unit moves to the service range of the first main-side unit, the first main-side unit does not need to re-register the target-carrying unit with the service end, and may instead retrieve the service data of the target-carrying unit from the service end based on the identifier of the target-carrying unit and send the service data to the target-carrying unit based on the IP address of the target-carrying unit in its own forwarding table.

[0117] Based on this, service continuity can be guaranteed when target-mounted units span different roadside units.

[0118] In some embodiments, when the second roadside unit and the target-carrying unit transmit data using QUIC, the identifier of the target-carrying unit may be associated with an ID generated by the service end, or the identifier of the target-carrying unit may be bound to an ID generated by the service end, or the identifier of the target-carrying unit may be associated with an ID generated by the service end.

[0119] It is understood that QUIC connections can identify target-carrying units using only random numbers generated by the service end as their ID. Since the identifier of a target-carrying unit is unique and immutable, as long as the identifier of the target-carrying unit does not change, the ID generated by the service end corresponding to / bound to / associated with that identifier will still be retained, even if the IP address or port number of the target-carrying unit changes. Therefore, the connection between the service end and the target-carrying unit will still be maintained. In the process of a target-carrying unit moving from a second roadside unit to the service range of a first roadside unit, the first roadside unit does not need to re-establish the connection or re-register the target-carrying unit with the service end because it already knows the identifier of the target-carrying unit in advance. This ensures the continuity of service when a target-carrying unit crosses different roadside units.

[0120] In some embodiments, the first roadside unit may further update the transfer information stored within itself and perform data transmission based on the updated transfer information. Exemplarily, as shown in Figure 4, after S103, the above method further includes the following S105 to S107.

[0121] S105, the first roadside unit receives service access request information transmitted by the target-onboard unit.

[0122] In some embodiments, the service access request information carries target parameters, which include at least an identifier for the target-carrying unit. In some examples, the target parameters are: Service requirements for the target onboard unit, The port number of the target-mounted unit, It further includes at least one of the IP addresses of the target-mounted unit.

[0123] In some embodiments, after receiving service access request information, the first roadside unit sets the service status of the target-mounted unit to the active state.

[0124] S106. If the target parameters carried by the service access request information differ from the target parameters in the forwarding information, the first roadside unit updates the forwarding information based on the service access request information and obtains the updated forwarding information.

[0125] S107, the first roadside unit transmits data to the target onboard unit based on the updated transfer information.

[0126] Furthermore, the first roadside unit transmits the updated transfer information to the second roadside unit, enabling the second roadside unit to update the transfer information of the target-carrying unit stored in its transfer table.

[0127] This enables the updating of transfer information of the target-mounted unit at the roadside unit, ensuring accurate data transmission and improving communication reliability.

[0128] To explain the solution more clearly, the following provides an illustrative example of how to store or update the transfer information of the target-mounted unit in the transfer table of a roadside unit (e.g., a first roadside unit and / or a second roadside unit).

[0129] In some embodiments, the roadside unit's transfer table includes transfer information for multiple mounted units, and the transfer information for each mounted unit corresponds to the identifier of one mounted unit.

[0130] For example, when a roadside unit receives transfer information for a target-mounted unit, if the identifier for the target-mounted unit exists in the transfer table, the roadside unit will use the transfer information for the target-mounted unit to correspond to the identifier for the target-mounted unit in the transfer table. Target-carrying unit Update the forwarding information.

[0131] As another example, if a roadside unit receives transfer information for a target-equipped unit, and the identifier for that unit does not exist in the transfer table, the roadside unit will add / store the transfer information for that target-equipped unit in the transfer table.

[0132] Furthermore, if the transfer information of the target-equipped unit was transmitted by another roadside unit with which the roadside unit has an association, the roadside unit sets the service status of the target-equipped unit to inactive. Alternatively, if the transfer information of the target-equipped unit was obtained by the roadside unit based on information transmitted from the target-equipped unit, the roadside unit sets the service status of the target-equipped unit to active.

[0133] Furthermore, the service status of the target-carrying unit may change in accordance with changes in communication conditions. For example, see the explanation above, which will not be repeated here. In addition, other possible update or storage methods for the transfer table may exist, but this disclosure is not limited to these.

[0134] In some embodiments, the first and second path units are configured with the same access IP address and access port number. The access IP address and access port number are used for service access to the target unit.

[0135] In some embodiments, the first and second roadside units are configured with the same service IP address and service port number. The service IP address and service port number are used for data transmission and service access with the target-equipped unit.

[0136] In some embodiments, the first and second roadside units are configured with different service IP addresses and service port numbers.

[0137] In order to maintain continuity of service even after the target onboard unit crosses roadside units (for example, after crossing from the service range of the second roadside unit to the service range of the first roadside unit) when the first roadside unit and the second roadside unit have different service IP addresses and service port numbers, the disclosure further provides another vehicle internet communication method. As shown in Figure 5, this method includes S201 to S203.

[0138] S201, the second-side unit transmits the service IP address and service port number of the second-side unit to the target unit.

[0139] In some embodiments, upon receiving an access request from the target-equipped unit, the second-side unit sends its own service IP address and service port number to the target-equipped unit.

[0140] In another embodiment, once the second route unit receives an access request from the target-equipped unit and the identity authentication and authorization of the target-equipped unit are completed, the second route unit sends its own service IP address and service port number to the target-equipped unit.

[0141] In some embodiments, this access request is sent by the target-carrying unit based on the access IP address and access port number. Alternatively, this access request is obtained by the second-side unit through monitoring based on the access IP address and access port number.

[0142] In some embodiments, the second roadside unit authenticates and authorizes the target-carrying unit based on the access request transmitted by the target-carrying unit.

[0143] S202, the first main-side unit sends its service IP address and service port number to the second main-side unit. In response, the second main-side unit obtains the service IP address and service port number from the first main-side unit.

[0144] In some embodiments, if at least one of the following conditions 2-1 to 2-3 is met, the first leading unit transmits its service IP address and service port number to the second leading unit.

[0145] Condition 2-1: The first roadside unit received the transfer information of the target-carrying unit transmitted by the second roadside unit.

[0146] Condition 2-2: The predetermined cycle start point has been reached.

[0147] Condition 2-3: The first roadside unit received a request from the second roadside unit to obtain the service IP address and service port number.

[0148] The above conditions are merely examples, and this disclosure is not limited to them.

[0149] S202 may be performed before or after any of the steps S101 to S103. In some embodiments, it is also possible to omit S202. For example, when the service IP address and service port number of the first unit are set to the second roadside unit by default. This disclosure is not limited to these.

[0150] S203, the second roadside unit transmits the service IP address and service port number of the first roadside unit to the target unit.

[0151] It is understood that S201 may be executed before S202 or after S202. This disclosure is not limited to these cases.

[0152] Based on this, even when the first roadside unit and the second roadside unit have different service IP addresses and service port numbers, the continuity of service when the installed unit crosses roadside units can be guaranteed.

[0153] To explain the solution more clearly, the following example illustrates a scenario where the second road-side unit is vRSU A and the first road-side unit is vRSU B, and the target-mounted unit communicates bidirectionally with vRSU A and vRSU B, respectively, using the UDP protocol.

[0154] Example 1 If vRSU A and vRSU B have the same service IP address and service port number, as shown in Figure 6, the target-embedded unit sends service access request information to vRSU A via the Uu interface. This service access request information includes the target-embedded unit identifier VID_a and the service request u.

[0155] vRSU A analyzes the service access request information transmitted by the target-embedded unit (for example, the message carrying this service access request information) and obtains the IP address x of the target-embedded unit.

[0156] vRSU A adds the forwarding information for this target-equipped unit to its forwarding table. This forwarding information includes the target-equipped unit's identifier, the target-equipped unit's service request, the target-equipped unit's IP address, and the target-equipped unit's service status, which is set to active.

[0157] vRSU A transmits V2X information to the target-mounted unit based on the target-mounted unit's forwarding information. If vRSU A does not receive any messages transmitted by the target-mounted unit within a first predetermined time, it sets the service status of the target-mounted unit to an inactive state (not shown).

[0158] As shown in Figure 7, vRSU A transmits forwarding information of the target-carrying unit to vRSU B via the base station connection interface (such as the Xn interface, X2 interface, or tunnel connection). vRSU B updates its forwarding table based on the forwarding information of the target-carrying unit and sets the service status of the target-carrying unit to the inactive state (standby).

[0159] As shown in Figure 8, after detecting that the target-mounted unit has moved within the service range of vRSU B, service access request information is sent to vRSU B. This service access request information includes the target-mounted unit identifier VID_a and service request u or updated service request v. If vRSU B does not receive the information sent by the target-mounted unit within a second predetermined time, it removes the target-mounted unit's transfer information from its transfer table.

[0160] vRSU B analyzes the service access request information transmitted by the target-embedded unit (for example, the message carrying this service access request information) and obtains the identifier of the target-embedded unit and the IP address x or updated IP address y of the target-embedded unit.

[0161] If the identifier of the target-equipped unit exists in vRSU B's own forwarding table, vRSU B updates the forwarding information for that target-equipped unit in its own forwarding table. Figure 8 shows only the situation where vRSU B has received the updated IP address y and the updated service request v. vRSU B sets the service status of the target-equipped unit to active.

[0162] As shown in Figure 9, vRSU B transmits forwarding information of the target-carrying unit to vRSU A via the base station connection interface (such as the Xn interface, X2 interface, or tunnel connection). Based on the forwarding information of the target-carrying unit transmitted by vRSU B, vRSU A updates its forwarding table and sets the service status of the target-carrying unit to the inactive state (standby).

[0163] vRSU B communicates with the target-carrying unit based on the target-carrying unit's transfer information in its own transfer table.

[0164] Example 2 If vRSU A and vRSU B have different service IP addresses and service port numbers, as shown in Figure 10, the target-equipped unit sends an access request to vRSU A via the Uu interface. The destination address is the pre-configured access IP address and access port number. Upon receiving this access request, vRSU A completes identity authentication and authorization, and then sends vRSU A's service IP address m and vRSU A's service port number p_a to the target-equipped unit.

[0165] As still shown in Figure 6, the target-embedded unit sends service access request information to vRSU A via the Uu interface. This service access request information includes the target-embedded unit identifier VID_a and the service request u. The destination address of this service access request information is the service IP address m and the service port number p_a of vRSU A.

[0166] vRSU A analyzes the service access request information transmitted by the target-embedded unit (for example, the message carrying this service access request information) and obtains the IP address x of the target-embedded unit.

[0167] vRSU A adds the forwarding information for this target-equipped unit to its forwarding table. This forwarding information includes the target-equipped unit's identifier, the target-equipped unit's service request, the target-equipped unit's IP address, and the target-equipped unit's service status, which is set to active.

[0168] vRSU A transmits V2X information to the target-mounted unit based on the target-mounted unit's forwarding information. If vRSU A does not receive any messages transmitted by the target-mounted unit within a first predetermined time, it sets the service status of the target-mounted unit to an inactive state (not shown).

[0169] As shown in Figure 11, vRSU A transmits forwarding information of the target-carrying unit to vRSU B via the base station connection interface (such as the Xn interface, X2 interface, or tunnel connection). vRSU B updates its forwarding table based on the forwarding information of the target-carrying unit and sets the service status of the target-carrying unit to the inactive state (standby). vRSU B further transmits its service IP address n and service port number p_b to vRSU A.

[0170] As shown in Figure 12, vRSU A transmits the service IP address n and service port number p_b of vRSU B to the target unit via the Uu interface.

[0171] As still shown in Figure 8, after detecting that the target-equipped unit has moved within the service range of vRSU B, service access request information is sent to vRSU B using vRSU B's service IP address n and vRSU B's service port number p_b. This service access request information includes the target-equipped unit's identifier VID_a and the service request u or updated service request v. If vRSU B does not receive the information sent by the target-equipped unit within the second predetermined time, the forwarding information for the target-equipped unit is removed from its forwarding table.

[0172] vRSU B analyzes the service access request information transmitted by the target-embedded unit (for example, the message carrying this service access request information) and obtains the identifier of the target-embedded unit and the IP address x or updated IP address y of the target-embedded unit.

[0173] If the identifier of the target-equipped unit exists in vRSU B's own forwarding table, vRSU B updates the forwarding information for that target-equipped unit in its own forwarding table. Figure 8 shows only the situation where vRSU B has received the updated IP address y and the updated service request v. vRSU B sets the service status of the target-equipped unit to active.

[0174] As still shown in Figure 9, vRSU B transmits the forwarding information of the target-carrying unit to vRSU A via the base station connection interface (such as the Xn interface, X2 interface, or tunnel connection). Based on the forwarding information of the target-carrying unit transmitted by vRSU B, vRSU A updates its forwarding table and sets the service status of the target-carrying unit to the inactive state, standby.

[0175] vRSU B communicates with the target-carrying unit based on the target-carrying unit's transfer information in its own transfer table.

[0176] The inventions relating to embodiments of this disclosure have been described above primarily from a methodological standpoint. Below, communication devices for performing the vehicle internet communication method in any of the above embodiments and their possible implementations are also described. It will be understood that in order for the communication device to perform the above functions, it will include hardware configurations and / or software modules corresponding to each function. Those skilled in the art will readily recognize, in combination with the algorithmic steps of each example described in the embodiments of this disclosure, that this disclosure can be implemented in hardware form or in a combination of hardware and computer software. Whether a function is performed by hardware or by computer software driving the hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art may implement the described functions using different methods for each specific application, but such implementations will not be considered beyond the scope of this disclosure.

[0177] Embodiments of this disclosure allow for the division of a communication device into functional modules based on the method embodiments described above. For example, each functional module may be divided according to each function, or two or more functions may be integrated into one functional module. The integrated module described above may be implemented in hardware form or in the form of a software functional module. It should be noted that the module division in the embodiments of this disclosure is merely schematic and represents the division of a single logical function, and other division methods may exist in actual implementation. It is understood that the above modules may also be called "units". Below, an example of dividing each functional unit according to each function will be given and explained.

[0178] Figure 13 shows the configuration of a communication device according to several embodiments. Referring to Figure 13, the communication device 200 includes a communication module 201 and a processing module 202.

[0179] The communication module 201 is used to receive transfer information of the target-mounted unit transmitted by the second road-side unit, the target-mounted unit being a mounted unit that communicates with the second road-side unit, and the transfer information of the target-mounted unit includes the identifier of the target-mounted unit.

[0180] The processing module 202 is used to store the transfer information of the target-mounted unit in the transfer table.

[0181] In some embodiments, the forwarding information further includes a service request from the target unit, the IP address of the target unit, and the service status of the target unit.

[0182] In some embodiments, the processing module 202 is further used to delete the transfer information of the target mounting unit if the service status in the transfer information is inactive and the information transmitted by the target mounting unit is not received within a second predetermined time.

[0183] In some embodiments, the processing module 202 is further used to switch the service status in the transfer information of the target mounting unit from inactive to active when it receives information transmitted by the target mounting unit within a second predetermined time if the service status in the transfer information is inactive.

[0184] In some embodiments, the communication module 201 is further used to transmit data with the target-mounted unit based on the target-mounted unit's forwarding information after detecting that the target-mounted unit has moved within the service range of the first road-side unit.

[0185] In some embodiments, the communication module 201 is further used to receive service access request information transmitted by the target-carrying unit. The processing module 202 is used to update the transfer information based on the service access request information and obtain the updated transfer information if the target parameters carried by the service access request information differ from the target parameters in the transfer information, the target parameters include the service request of the target-carrying unit and / or the IP address of the target-carrying unit. The processing module 202 is further used to perform data transmission with the target-carrying unit based on the updated transfer information.

[0186] In some embodiments, the communication device 200 and the second roadside unit are configured with the same service IP address and service port number. The service IP address and service port number are used for data transmission and service access with the target onboard unit.

[0187] In some embodiments, the communication device 200 and the second roadside unit are configured with different service IP addresses and service port numbers, while the communication device 200 and the second roadside unit are configured with the same access IP address and access port number. The service IP address and service port number are used for data transmission and service access with the target-equipped unit, while the access IP address and access port number are used for service access with the target-equipped unit.

[0188] In some embodiments, the communication module 201 is further used to transmit the service IP address and service port number of the first road-side unit to the second road-side unit.

[0189] As still shown in Figure 13, the disclosure further provides another communication device. Referring to Figure 13, the communication device 200 includes a communication module 201 and a processing module 202.

[0190] The communication module 201 is used to obtain transfer information of the target-mounted unit, which is a mounted unit that communicates with the second path-side unit, and the transfer information includes the identifier of the target-mounted unit.

[0191] The communication module 201 is further used to transmit transfer information to the first roadside unit.

[0192] In some embodiments, the forwarding information further includes a service request from the target unit, the IP address of the target unit, and the service status of the target unit.

[0193] In some embodiments, the communication module 201 is used to receive service access request information from a target-mounted unit, the service access request information includes the identifier of the target-mounted unit, the service request of the target-mounted unit, and the IP address of the target-mounted unit.

[0194] In some embodiments, the processing module 202 is used to generate transfer information based on service access request information.

[0195] In some embodiments, the processing module 202 is further used to set the service status in the transfer information to an inactive state if, when the service status in the transfer information is active, information on the target mounting unit is not received within a first predetermined time.

[0196] In some embodiments, the processing module 202 is further used to delete the transfer information if the service status in the transfer information is inactive, or if information on the target mounting unit is not received within a second predetermined time.

[0197] In some embodiments, the communication device 200 and the second roadside unit are configured with the same service IP address and service port number. The service IP address and service port number are used for data transmission and service access with the target onboard unit.

[0198] In some embodiments, the communication device 200 and the second roadside unit are configured with different service IP addresses and service port numbers, while the communication device 200 and the second roadside unit are configured with the same access IP address and access port number. The service IP address and service port number are used for data transmission and service access with the target-equipped unit, while the access IP address and access port number are used for service access with the target-equipped unit.

[0199] In some embodiments, the communication module 201 is further used to transmit the service IP address and service port number of the communication device 200 to the target onboard unit.

[0200] In some embodiments, the communication module 201 is further used to obtain the service IP address and service port number of the first road-side unit. The communication module 201 is also further used to transmit the service IP address and service port number of the first road-side unit to the target-mounted unit.

[0201] When the functions of the integrated module described above are implemented in hardware form, embodiments of this disclosure further provide possible configurations of a communication device. This communication device is used to perform the vehicle internet communication method provided by embodiments of this disclosure. As shown in Figure 14, the communication device 300 includes a processor 302. In some examples, the communication device may further include at least one of a communication interface 303, a bus 304, and a memory 301.

[0202] The processor 302 may implement or execute various exemplary logic blocks, modules, and circuits described in relation to embodiments of the present disclosure. The processor 302 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in relation to embodiments of the present disclosure. The processor 302 may include combinations that implement arithmetic functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and so on.

[0203] The communication interface 303 is used to connect to other devices via a communication network. This communication network may be Ethernet®, a wireless access network, a wireless local area network (WLAN), or the like.

[0204] The memory 301 may be a read-only memory (ROM) or another type of static storage device capable of storing static information and instructions, a random access memory (RAM) or another type of dynamic storage device capable of storing information and instructions, and the memory 301 may be an electrically erasable programmable read-only memory (EEPROM), a disk storage medium or other magnetic storage device, or any other medium accessible by a computer that can be used to transport or store desired program code having instruction or data structure form.

[0205] In one implementation, the memory 301 may be integrated with the processor 302.

[0206] In other implementations, the memory 301 exists independently of the processor 302 and is connected to the processor 302 via the bus 304, and stores instructions that the processor 302 can execute, such as computer program instructions or program code. When the processor 302 calls and executes the instructions or program code stored in the memory 301, the vehicle internet communication method provided by the embodiment of this disclosure can be realized.

[0207] Bus 304 may be an extended industry standard architecture (EISA) bus, etc. Bus 404 can be divided into an address bus, a data bus, a control bus, etc. For simplicity of representation, Figure 13 shows only one thick line, but this does not mean that there is only one bus or only one type of bus.

[0208] Some embodiments of this disclosure provide a computer-readable storage medium (e.g., a non-temporary computer-readable storage medium) on which computer program instructions are stored, and when these computer program instructions are executed on a computer (e.g., the aforementioned communication device, communication device, base station, first terminal, second terminal and its processor, etc.), the computer is caused to execute the vehicle internet communication method described in any of the embodiments described above. It is understood that this disclosure does not limit the form of the computer.

[0209] In some examples, the computer-readable storage media described above may include, but are not limited to, magnetic storage devices (e.g., hard disks, floppy disks, magnetic tapes, etc.), optical discs (e.g., Compact Disks (CDs), Digital Versatile Disks (DVDs), etc.), smart cards, and flash memory devices (e.g., Erasable Programmable Read-Only Memory (EPROMs), cards, sticks, or key drives, etc.). The various computer-readable storage media described in this disclosure may represent one or more devices and / or other machine-readable storage media for storing information. The term “machine-readable storage media” includes, but is not limited to, a variety of other media capable of storing, containing, and / or carrying wireless channels, instructions, and / or data.

[0210] Embodiments of this disclosure provide a computer program product including instructions. When the computer program product is executed on a computer, it causes the computer to execute the vehicle internet communication method described in any of the embodiments described above.

[0211] The foregoing describes only specific embodiments of the Disclosure, and the scope of protection of the Disclosure is not limited thereto. Any modifications or substitutions within the technical scope disclosed herein shall be included within the scope of protection of the Disclosure. Accordingly, the scope of protection of the Disclosure shall be governed by the scope of protection of the claims.

Claims

1. A vehicle internet communication method applicable to a first roadside unit, A step of receiving transfer information of a target mounting unit transmitted by a second roadside unit, wherein the target mounting unit is a mounting unit that communicates with the second roadside unit, and the transfer information of the target mounting unit includes an identifier of the target mounting unit. The further step includes storing the transfer information of the target mounting unit in a transfer table, method.

2. The transfer information further includes the service request of the target-equipped unit, the IP address of the target-equipped unit, and the service status of the target-equipped unit. The method according to claim 1.

3. If the service status in the aforementioned transfer information is inactive, and the information transmitted by the target mounting unit is not received within the second predetermined time, the transfer information of the target mounting unit is deleted. The method according to claim 2.

4. When the service status in the transfer information is inactive, if information transmitted by the target mounting unit is received within a second predetermined time, the service status in the transfer information of the target mounting unit is switched from inactive to active. The method according to claim 2.

5. The further step includes detecting that the target-mounted unit has moved within the service range of the first roadside unit, and then performing data transmission with the target-mounted unit based on the transfer information of the target-mounted unit. The method according to claim 2.

6. The steps include receiving service access request information transmitted by the target-mounted unit, If the target parameters carried by the service access request information differ from the target parameters in the transfer information, the step of updating the transfer information based on the service access request information and obtaining the updated transfer information, wherein the target parameters include the service request of the target-equipped unit and / or the IP address of the target-equipped unit. The further step includes transmitting data to the target mounting unit based on the updated transfer information, The method according to claim 2.

7. The first and second road units are configured with the same service IP address and service port number, and these service IP address and service port number are used for data transmission and service access with the target unit. The method according to claim 1.

8. The first and second road-side units are configured with different service IP addresses and service port numbers, while the first and second road-side units are configured with the same access IP address and access port number. The service IP address and service port number are used for data transmission with the target-equipped unit, and the access IP address and access port number are used for service access with the target-equipped unit. The method according to claim 1.

9. The further step includes transmitting the service IP address and service port number of the first roadside unit to the second roadside unit. The method according to claim 8.

10. A vehicle internet communication method applicable to a second roadside unit, A step of acquiring transfer information of the target mounting unit, wherein the target mounting unit is a mounting unit that communicates with the second roadside unit, and the transfer information includes an identifier for the target mounting unit. The step of transmitting the transfer information to the first roadside unit includes, method.

11. The transfer information further includes the service request of the target-equipped unit, the IP address of the target-equipped unit, and the service status of the target-equipped unit. The method according to claim 10.

12. The step of obtaining the transfer information of the target-mounted unit is: A step of receiving service access request information of the target-equipped unit, wherein the service access request information includes an identifier of the target-equipped unit, a service request of the target-equipped unit, and the IP address of the target-equipped unit. The step of generating the transfer information based on the service access request information includes, The method according to claim 11.

13. If the service status in the transfer information is active, and the information transmitted by the target mounting unit is not received within a first predetermined time, the further step includes setting the service status in the transfer information to inactive. The method according to claim 10.

14. If the service status in the transfer information is inactive, and the information transmitted by the target mounting unit is not received within a second predetermined time, the further step includes deleting the transfer information. The method according to claim 13.

15. The first and second road units are configured with the same service IP address and service port number, and these service IP address and service port number are used for data transmission and service access with the target unit. The method according to claim 10.

16. The first and second road-side units are configured with different service IP addresses and service port numbers, while the first and second road-side units are configured with the same access IP address and access port number. The service IP address and service port number are used for data transmission with the target-equipped unit, and the access IP address and access port number are used for service access with the target-equipped unit. The method according to claim 10.

17. The further step includes transmitting the service IP address and service port number of the second road-side unit to the target-equipped unit. The method according to claim 16.

18. The steps include obtaining the service IP address and service port number of the first road-side unit, The further step includes transmitting the service IP address and service port number of the first road-side unit to the target-equipped unit, The method according to claim 16.

19. A communication device including memory and a processor, The memory and the processor are coupled, and the memory is used to store instructions that can be executed by the processor. If the processor is configured to execute the instructions, the communication device performs the method according to any one of claims 1 to 18. Communication device.

20. A computer-readable storage medium, The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by the computer, the computer is made to execute the method according to any one of claims 1 to 18. Computer-readable storage medium.

Images