A unicast connection establishment exception handling method and device

Abstract

The application discloses a unicast connection establishment exception processing method and device, the method comprises the following steps: a second device sends a first message to a first device to request the first device to establish a unicast connection with the second device, the first message carries a media access control (MAC) address, an address identifier and a security mechanism of the second device, the first device determines that the unicast connection between the first device and the second device is abnormal according to the first message and sends a second message to the second device, the second message carries the MAC address, the address identifier and an error identifier of the second device, so that the second device performs corresponding processing according to the reason of the unicast connection establishment exception indicated by the error identifier. The application can quickly identify the second device based on the MAC address and the address identifier of the device in the message, the error identifier in the message can guide the second device to effectively solve the problem of the unicast connection establishment exception, improve the efficiency of establishing the unicast connection, and ensure the smooth execution of the unicast service between the two communication parties.

Description

Technical Field

[0001] This application relates to the field of vehicle-to-everything (V2X) communication, and in particular to a method and apparatus for handling unicast connection establishment anomalies. Background Technology

[0002] The Internet of Vehicles (IOV) technology enables the exchange and sharing of intelligent information (such as traffic information and service information) between vehicles and X (people, vehicles, roads, cloud, etc.), greatly facilitating communication between vehicles and X.

[0003] For unicast services between vehicles and X communication, during the process of establishing a unicast connection between the sender of the unicast service announcement and the responder of the unicast service announcement, situations may occur such as conflicts in the Medium Access Control (MAC) addresses of multiple responders and incompatibility in the security mechanisms of the two communicating parties. This will affect the establishment of the unicast connection between the sender and the responder, and may also cause interactive chaos based on unicast services and prevent the services from being executed normally. Summary of the Invention

[0004] This application discloses a method and apparatus for handling unicast connection establishment anomalies, which can effectively solve the problem of unicast connection establishment anomalies, improve the efficiency of establishing unicast connections, and ensure the smooth execution of unicast services between communicating parties.

[0005] In a first aspect, this application provides a method for handling unicast connection establishment exceptions, applied to a first device. The method includes: receiving a first message sent by a second device, the first message being used to request the first device to establish a unicast connection with the second device, the first message carrying a first Media Access Control (MAC) address, address identifier, and security mechanism of the second device; determining, based on the first message, that a unicast connection establishment exception has occurred between the second device and the first device; and sending a second message to the second device, the second message carrying a first MAC address, address identifier, and error identifier, the error identifier being used to indicate the reason for the unicast connection establishment exception.

[0006] The first device can be a roadside unit (RSU), a multi-access edge computing (MEC), an on-board unit (OBU), a smart gas station, a smart traffic light, a portable mobile device (e.g., a mobile phone, tablet, etc.), or other sensors or devices with communication functions, such as components or chips within a portable mobile device. For example, the first device can also be a system composed of an RSU and an MEC, a system composed of an RSU and sensors, or a system composed of an RSU, an MEC, and sensors. The second device can be an on-board unit, a smart gas station, a smart traffic light, a portable mobile device (e.g., a mobile phone, tablet, etc.), or other sensors or devices with communication functions, such as components or chips within a portable mobile device; this application does not specifically limit the specific devices described.

[0007] A security mechanism is a security mode or security protection method adopted by a device in communication. The security mechanism can be a symmetric key-based security mechanism, a certificate-based security mechanism, etc., and the embodiments of this application do not make specific limitations.

[0008] The address identifier can identify the second device. The address identifier can be the device identifier of the second device, a random number, or a string generated based on the MAC address and device identifier of the second device, etc., and this application embodiment does not specifically limit it.

[0009] In the above method, the first device can effectively distinguish different devices with the same MAC address based on the address identifier, and can accurately indicate the reason for the unicast connection establishment failure between the second device and the first device based on the error identifier. In this way, the problem of unicast connection establishment failure can be effectively solved by carrying messages with address identifiers, error identifiers and other content, which is conducive to improving the efficiency of establishing unicast connections and ensuring the normal execution of unicast services between the two communicating parties.

[0010] Optionally, determining an anomaly in the establishment of a unicast connection between the second device and the first device based on the first message includes: determining that the first MAC address and the second MAC address of the third device are the same based on a judgment result that the first MAC address and the second MAC address of the third device are the same, wherein the third device is the device requesting to establish a unicast connection with the first device; determining that the security mechanism of the second device is incompatible with the security mechanism supported by the first device based on a judgment result that the security mechanism of the second device is incompatible with the security mechanism supported by the first device; or determining that the message structure of the first message is incorrect based on a judgment result that the message structure of the first message is incorrect.

[0011] Specifically, if the first MAC address is the same as the second MAC address of the third device, it means that the first MAC address of the second device conflicts, which will cause the unicast connection to be established abnormally; if the security mechanism of the second device does not match the security mechanism supported by the first device, it means that the encryption and decryption methods of the first device and the second device are different during the interaction, which will cause the unicast connection to be established abnormally; if the message structure of the first message is incorrect, it means that the first device cannot parse or accurately parse the first message, which will cause the unicast connection to be established abnormally.

[0012] By implementing the above method, during the unicast connection establishment process, abnormal unicast connection establishment between the second device and the first device, as well as the reasons for the abnormal unicast connection establishment, can be quickly identified.

[0013] Optionally, if the second device is a single device, the first MAC address is a single MAC address, and the second message carries the first MAC address, including: the first MAC address is carried by the destination MAC address field of the second message.

[0014] Implementing the above method, in the second message, the first MAC address is carried by the destination MAC address field of the second message, that is, the first MAC address is the Destination Layer 2 ID of the second message.

[0015] Optionally, the second message carries an address identifier and an error identifier, including: the address identifier and error identifier of the second device are carried in the Header Extension field of the Dedicated Service Announcement (DSA) message frame of the second message; or the address identifier and error identifier of the second device are carried in the Application Extension field of the DSA message frame of the second message.

[0016] By implementing the above method, the second message carries the address identifier and error identifier of the second device, which enables the receiving end of the second message to quickly determine whether there is an error in the establishment of the unicast connection with the first device based on the address identifier, and to perform corresponding processing based on the reason for the unicast connection establishment error indicated by the error identifier. This is beneficial for solving the problem of unicast connection establishment error between the two communicating parties.

[0017] Optionally, if there are multiple devices as the second device, the first MAC address is multiple MAC addresses, and the second message also includes a dedicated application identifier, which is used to indicate a unicast connection establishment failure. The dedicated application identifier is carried in the application identifier AID field of the dedicated short message DSM message frame of the second message; the destination MAC address field of the second message is used to carry the conversion value of the dedicated application identifier.

[0018] By implementing the above method, when there are multiple devices as the second device, when the destination MAC address field of the second message is used to carry the converted value of the dedicated application identifier, it can be known that the second message carries the MAC addresses of multiple devices. This can reduce the number of transmissions of the second message and effectively reduce the consumption of network resources.

[0019] Optionally, the second message carries the first MAC address, address identifier, and error identifier, including: the first MAC address, address identifier, and error identifier being carried in the HeaderExtension field of the Dedicated Service Announcement (DSA) message frame of the second message; or the first MAC address, address identifier, and error identifier being carried in the Application Extension field of the DSA message frame of the second message.

[0020] When implementing the above method, if there are multiple devices as the second device, the second message carries multiple MAC addresses, multiple address identifiers, and at least one error identifier. A single second message can inform multiple devices that have encountered unicast connection establishment failures with the first device, which helps improve the efficiency of establishing unicast connections and effectively reduces the consumption of network resources.

[0021] Optionally, in the first message, the address identifier of the second device is carried by at least one of the DSA Identifier field and the Content Count field in the DSA message frame of the first message.

[0022] By implementing the above method, the first message carries the address identifier of the second device, which enables the receiving end of the first message (i.e. the first device) to effectively distinguish different devices with the same MAC address.

[0023] Optionally, in the first message, the address identifier of the second device is carried in the Header Extension field of the Dedicated Service Announcement (DSA) message frame of the first message.

[0024] By implementing the above method, the first message carries the address identifier of the second device, which enables the receiving end of the first message (i.e. the first device) to effectively distinguish different devices with the same MAC address.

[0025] Optionally, the second message is sent by the network layer or application layer of the first device.

[0026] The network layer, based on Long Term Evolution (LTE) vehicular wireless communication technology, includes a management sublayer for system configuration and maintenance, and a data sublayer for transmitting data streams between application layers and between different device management layers or between management layers and applications. The application layer, also based on LTE, primarily handles application-level business logic, such as generating instant messages and unicast service announcements. Interaction between the network and application layers is achieved through cross-layer primitives.

[0027] In a specific implementation, the network layer of the first device can send the second message, and the network layer of the first device can also determine the unicast connection establishment anomaly between the second device and the first device based on the first message. This can detect the unicast link establishment anomaly more quickly and respond rapidly, while saving the consumption of upper-layer resources in the first device.

[0028] In another specific implementation, the application layer of the first device can determine the unicast connection establishment failure between the second device and the first device based on the first message and send the second message, which helps to reduce the data processing pressure of other layers in the first device and the processing method is relatively flexible.

[0029] Secondly, this application provides a method for handling unicast connection establishment exceptions, applied to a second device. The method includes: sending a first message to a first device, the first message requesting the first device to establish a unicast connection with the second device, the first message carrying a first Media Access Control (MAC) address, a first address identifier, and a security mechanism of the second device; receiving a second message sent by the first device, the second message carrying at least one MAC address, at least one address identifier, and an error identifier, the error identifier indicating the reason for the unicast connection establishment exception; determining, based on the second message, that a unicast connection establishment exception has occurred between the second device and the first device; and performing exception handling operations based on the error identifier.

[0030] The specific details of the first device and the second device can be found in the description of the first device and the second device in the first aspect above, and will not be repeated here.

[0031] By implementing the above method, an address identifier is added to the content carried in the first message to address the problem of not being able to distinguish between different devices with the same MAC address. The address identifier can identify the second device. Based on the error identifier in the second message, the second device can accurately know the reason for the unicast connection establishment failure between itself and the first device, thereby effectively solving the problem of unicast connection establishment failure, improving the efficiency of establishing unicast connections, and ensuring the normal execution of unicast services between the two communicating parties.

[0032] Optionally, performing exception handling based on the error flag could be: when the error flag indicates that the first MAC address is conflicted, reselecting the first MAC address.

[0033] Implementing the above method can effectively solve the problem of abnormal unicast connection establishment caused by MAC conflicts, and is conducive to improving the efficiency of establishing unicast connections.

[0034] Optionally, performing exception handling based on the error flag can be: when the error flag indicates that the security mechanism of the second device does not match the security mechanism supported by the first device, reselect the security mechanism of the second device.

[0035] Implementing the above method can effectively solve the problem of abnormal unicast connection establishment caused by security mechanism mismatch, and is conducive to improving the efficiency of establishing unicast connections.

[0036] Optionally, performing exception handling based on the error identifier can be: when the error identifier indicates that the message structure of the first message is incorrect, re-validate the message structure of the first message.

[0037] Implementing the above method can effectively solve the problem of unicast connection establishment anomalies caused by the inability to parse the first message, and is conducive to improving the efficiency of establishing unicast connections.

[0038] Optionally, determining an anomaly in the establishment of a unicast connection between the second device and the first device based on the second message includes: determining an anomaly in the establishment of a unicast connection between the second device and the first device when at least one MAC address is a first MAC address and at least one address identifier is a first address identifier.

[0039] By implementing the above method, the MAC address and address identifier carried in the second message can enable the receiving end of the second message to uniquely determine that the unicast connection between itself and the first device has failed to be established.

[0040] Optionally, the second message carries at least one MAC address, at least one address identifier, and an error identifier, including: the at least one MAC address being carried by the destination MAC address field of the second message; the at least one address identifier and the error identifier being carried by the Header Extension field in the Dedicated Service Announcement (DSA) message frame of the second message, or the at least one address identifier and the error identifier being carried by the Application Extension field in the DSA message frame of the second message.

[0041] By implementing the above method, the address identifier and error identifier carried in the second message enable the receiving end of the second message to quickly determine whether there is an error in the establishment of the unicast connection with the first device based on the address identifier, and to perform corresponding processing based on the reason for the unicast connection establishment error indicated by the error identifier. This is beneficial for solving the problem of unicast connection establishment errors between the two communicating parties.

[0042] Optionally, the second message also includes a dedicated application identifier, which is used to indicate a unicast connection establishment failure. The dedicated application identifier is carried in the application identifier AID field of the dedicated short message DSM message frame of the second message. Determining a unicast connection establishment failure between the second device and the first device based on the second message can be as follows: when the content carried by the destination MAC address field of the second message includes the converted value of the dedicated application identifier, and the at least one MAC address includes the first MAC address and the at least one address identifier includes the first address identifier, it can be determined that a unicast connection establishment failure between the second device and the first device is determined.

[0043] By implementing the above method, when the destination MAC address field of the second message is used to carry the converted value of the dedicated application identifier, it can be known that the second message carries multiple MAC addresses and multiple address identifiers. When the second message carries the MAC address and address identifier of the second device, the second device can quickly determine that the unicast connection between itself and the first device is abnormal.

[0044] Optionally, the second message carries at least one MAC address, at least one address identifier, and an error identifier, including: the at least one MAC address, at least one address identifier, and error identifier being carried in the Header Extension field of the Dedicated Service Announcement (DSA) message frame of the second message; or the at least one MAC address, at least one address identifier, and error identifier being carried in the Application Extension field of the DSA message frame of the second message.

[0045] By implementing the above method, the second message can carry multiple MAC addresses and multiple address identifiers. Through such a second message, multiple devices that have failed to establish a unicast connection with the first device can be notified simultaneously, which helps to improve the efficiency of establishing a unicast connection and effectively reduces the consumption of network resources.

[0046] Optionally, in the first message, the first address identifier is carried by at least one of the DSA Identifier field and the Content Count field in the DSA message frame of the first message.

[0047] By implementing the above method, the first message carries a first address identifier, which enables the receiving end of the first message (i.e., the first device) to effectively distinguish different devices with the same MAC address.

[0048] Optionally, in the first message, the first address identifier is carried in the Header Extension field of the Dedicated Service Announcement (DSA) message frame of the first message.

[0049] By implementing the above method, the first message carries a first address identifier, which enables the receiving end of the first message (i.e., the first device) to effectively distinguish different devices with the same MAC address.

[0050] Thirdly, this application provides an apparatus for handling unicast connection establishment anomalies. The apparatus includes: a receiving unit for receiving a first message sent by a second device, the first message requesting the first device to establish a unicast connection with the second device, the first message carrying a first Media Access Control (MAC) address, an address identifier, and a security mechanism of the second device; a processing unit for determining, based on the first message, that a unicast connection establishment anomaly has occurred between the second device and the first device; and a sending unit for sending a second message to the second device, the second message carrying a first MAC address, an address identifier, and an error identifier, the error identifier indicating the reason for the unicast connection establishment anomaly.

[0051] Optionally, the processing unit is specifically configured to: determine that the first MAC address and the second MAC address of the third device are the same based on the judgment result that the first MAC address is the same as the second MAC address of the third device, wherein the third device is the device that requests to establish a unicast connection with the first device; determine that the security mechanism of the second device is incompatible with the security mechanism supported by the first device based on the judgment result that the security mechanism of the second device is incompatible with the security mechanism supported by the first device; or determine that the message structure of the first message is incorrect based on the judgment result that the message structure of the first message is incorrect.

[0052] Optionally, if the second device is a single device, the first MAC address is a single MAC address, and the second message carries the first MAC address, including: the first MAC address is carried by the destination MAC address field of the second message.

[0053] Optionally, the second message carries an address identifier and an error identifier, including: the address identifier and error identifier of the second device are carried in the Header Extension field of the Dedicated Service Announcement (DSA) message frame of the second message; or the address identifier and error identifier are carried in the ApplicationExtension field of the DSA message frame of the second message.

[0054] Optionally, if there are multiple devices as the second device, the first MAC address is multiple MAC addresses, and the second message also includes a dedicated application identifier, which is used to indicate a unicast connection establishment failure. The dedicated application identifier is carried in the application identifier AID field of the dedicated short message DSM message frame of the second message; the destination MAC address field of the second message is used to carry the conversion value of the dedicated application identifier.

[0055] Optionally, the second message carries the first MAC address, address identifier, and error identifier, including: the first MAC address, address identifier, and error identifier being carried in the HeaderExtension field of the Dedicated Service Announcement (DSA) message frame of the second message; or the first MAC address, address identifier, and error identifier being carried in the Application Extension field of the DSA message frame of the second message.

[0056] Optionally, in the first message, the address identifier of the second device is carried by at least one of the DSA Identifier field and the Content Count field in the DSA message frame of the first message.

[0057] Optionally, in the first message, the address identifier of the second device is carried in the Header Extension field of the Dedicated Service Announcement (DSA) message frame of the first message.

[0058] Optionally, the second message is sent by the network layer or application layer of the first device.

[0059] Fourthly, this application provides an apparatus for handling unicast connection establishment anomalies. The apparatus includes: a sending unit for sending a first message to a first device, the first message requesting the first device to establish a unicast connection with a second device, the first message carrying a first Media Access Control (MAC) address, a first address identifier, and a security mechanism of the second device; a receiving unit for receiving a second message sent by the first device, the second message carrying at least one MAC address, at least one address identifier, and an error identifier, the error identifier indicating the reason for the unicast connection establishment anomaly; a processing unit for determining, based on the second message, that a unicast connection establishment anomaly exists between the second device and the first device; and the processing unit is further configured to perform an anomaly handling operation based on the error identifier.

[0060] Optionally, the processing unit is specifically configured to: reselect the first MAC address when the error indicator indicates that the first MAC address is conflicted.

[0061] Optionally, the processing unit is specifically configured to: when an error flag indicates that the security mechanism of the second device does not match the security mechanism supported by the first device, reselect the security mechanism of the second device.

[0062] Optionally, the processing unit is specifically configured to: re-verify the message structure of the first message when the error flag indicates that the message structure of the first message is incorrect.

[0063] Optionally, the processing unit is specifically configured to: determine that the unicast connection establishment between the second device and the first device is abnormal when at least one of the above MAC addresses is a first MAC address and at least one of the above address identifiers is a first address identifier.

[0064] Optionally, the second message carries at least one MAC address, at least one address identifier, and an error identifier, including: at least one MAC address is carried by the destination MAC address field of the second message; at least one address identifier and an error identifier are carried in the Header Extension field of the DSA message frame of the second message, or at least one address identifier and an error identifier are carried in the ApplicationExtension field of the DSA message frame of the second message.

[0065] Optionally, the second message also includes a dedicated application identifier, which is used to indicate a unicast connection establishment failure. The dedicated application identifier is carried in the application identifier AID field of the dedicated short message DSM message frame of the second message. The processing unit is specifically used to: determine that a unicast connection establishment failure between the second device and the first device is occurring when the content carried by the destination MAC address field of the second message includes the converted value of the dedicated application identifier, and when the at least one MAC address includes a first MAC address and the at least one address identifier includes a first address identifier.

[0066] Optionally, the second message carries at least one MAC address, at least one address identifier, and an error identifier, including: at least one MAC address, at least one address identifier, and an error identifier carried in the Header Extension field of the Dedicated Service Announcement (DSA) message frame of the second message; or at least one MAC address, at least one address identifier, and an error identifier carried in the Application Extension field of the DSA message frame of the second message.

[0067] Optionally, in the first message, the first address identifier is carried by at least one of the DSA Identifier field and the Content Count field in the DSA message frame of the first message.

[0068] Optionally, in the first message, the first address identifier is carried in the Header Extension field of the Dedicated Service Announcement (DSA) message frame of the first message.

[0069] Fifthly, this application provides an apparatus comprising a processor and a memory, wherein the memory is used to store program instructions; the processor invokes the program instructions in the memory to cause the apparatus to perform the method of the first aspect or any possible implementation thereof.

[0070] In a sixth aspect, this application provides an apparatus comprising a processor and a memory, wherein the memory is used to store program instructions; the processor invokes the program instructions in the memory to cause the apparatus to perform the method of the second aspect or any possible implementation thereof.

[0071] In a seventh aspect, this application provides a computer-readable storage medium including computer instructions that, when executed by a processor, implement the method in the first aspect or any possible implementation thereof.

[0072] Eighthly, this application provides a computer-readable storage medium including computer instructions that, when executed by a processor, implement the method in the second aspect or any possible implementation thereof.

[0073] Ninthly, this application provides a computer program product that, when executed by a processor, implements the methods described in the first aspect or any possible embodiment of the first aspect. The computer program product may, for example, be a software installation package. When the methods provided by any possible design of the first aspect are required, the computer program product can be downloaded and executed on a processor to implement the methods described in the first aspect or any possible embodiment of the first aspect.

[0074] In a tenth aspect, this application provides a computer program product that, when executed by a processor, implements the methods described in the second aspect or any possible embodiment of the second aspect. The computer program product may, for example, be a software installation package. When the methods provided by any possible design of the second aspect are required, the computer program product can be downloaded and executed on a processor to implement the methods described in the second aspect or any possible embodiment of the second aspect.

[0075] In the eleventh aspect, this application provides a vehicle that includes the device as described in the third or fifth aspect above, or the device as described in any possible implementation of the third or fifth aspect above, or the device as described in the fourth or sixth aspect above, or the device as described in any possible implementation of the fourth or sixth aspect above.

[0076] In a twelfth aspect, this application provides a unicast connection establishment exception handling system, including a first device and a second device, wherein the first device is the apparatus of the third or fifth aspect described above, or an apparatus of any possible implementation of the third or fifth aspect described above; and the second device is the apparatus of the fourth or sixth aspect described above, or an apparatus of any possible implementation of the fourth or sixth aspect described above. Attached Figure Description

[0077] Figure 1 It is an architecture diagram of a communication system;

[0078] Figure 2 This is a schematic diagram of a protocol stack for LTE-based vehicle-to-everything (V2X) wireless communication technology.

[0079] Figure 3 This is a schematic diagram illustrating a scenario for establishing a unicast connection.

[0080] Figure 4 This is a flowchart of a unicast connection establishment exception handling method provided in an embodiment of this application;

[0081] Figure 5 This is a flowchart of another unicast connection establishment exception handling method provided in the embodiments of this application;

[0082] Figure 6A This is a schematic diagram illustrating the carrying of an address identifier in a first message, as provided in an embodiment of this application.

[0083] Figure 6B This is a schematic diagram illustrating the carrying of an address identifier in a first message, as provided in an embodiment of this application.

[0084] Figure 7A This is a schematic diagram of a second message provided in an embodiment of this application;

[0085] Figure 7B This is a schematic diagram of a second message provided in an embodiment of this application;

[0086] Figure 8 This is a flowchart of another unicast connection establishment exception handling method provided in the embodiments of this application;

[0087] Figure 9A This is a schematic diagram of a second message provided in an embodiment of this application;

[0088] Figure 9B This is a schematic diagram of a second message provided in an embodiment of this application;

[0089] Figure 10 This is a schematic diagram of a highway toll collection scenario provided in an embodiment of this application;

[0090] Figure 11 This is a schematic diagram of a vehicle-to-vehicle communication scenario provided in an embodiment of this application;

[0091] Figure 12 This is a functional structure diagram of a communication device provided in this application and this embodiment;

[0092] Figure 13 This is a schematic diagram of the structure of a communication device provided in this embodiment of the application. Detailed Implementation

[0093] The terminology used in the embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the application. Terms such as "first," "second," etc., in the specification and claims of this application are used to distinguish different objects, not to describe a particular order.

[0094] The technical solutions in this application will now be described with reference to the accompanying drawings.

[0095] See Figure 1 , Figure 1 This is a schematic diagram of the architecture of a communication system, which includes a roadside device and at least one terminal, wherein the roadside device and the terminal, and the terminals and the terminal can communicate wirelessly.

[0096] The roadside device can be a roadside unit (RSU), or a multi-access edge computing (MEC) device with wireless communication capabilities, a smart gas station, a smart traffic light, etc. The terminal can be an on-board unit (OBU), a portable mobile device (e.g., a mobile phone, a tablet, etc.), or other sensors or devices such as components or chips in a portable mobile device that can communicate with the roadside device or other terminals. The embodiments of this application do not impose specific limitations.

[0097] exist Figure 1 In the system architecture shown, at least one terminal may include terminal 1 and terminal 2. The roadside device may establish unicast connections with terminal 1 and terminal 2 respectively, and terminal 1 may also establish a unicast connection with terminal 2.

[0098] It should be noted that, in Figure 1In the system shown, communication between roadside devices and terminals, or between terminals, can utilize cellular communication technologies, such as 2G cellular communication, such as Global System for Mobile Communication (GSM) and General Packet Radio Service (GPRS); or 3G cellular communication, such as Wideband Code Division Multiple Access (WCDMA), Time Division-Synchronous Code Division Multiple Access (TS-SCDMA), and Code Division Multiple Access (CDMA); or 4G cellular communication, such as Long Term Evolution (LTE), LTE-Vehicle to Everything (V2X) PC5 communication; or 5G cellular communication, such as New Radio (NR)-V2X PC5 communication; or other evolved cellular communication technologies. The wireless communication system can also utilize non-cellular communication technologies, such as Wi-Fi and Wireless Local Area Network (WLAN) communication. In some embodiments, communication between the aforementioned devices can also utilize infrared links, Bluetooth, or ZigBee for direct communication. In some embodiments, communication between the above-mentioned devices may also employ other wireless protocols, such as various vehicle communication systems. For example, the system may include one or more dedicated short range communications (DSRC) devices, which may include public and / or private data communication between vehicles and / or roadside stations. This application does not specifically limit this.

[0099] It should be noted that, Figure 1 This is merely an illustrative architecture diagram and is not intended to limit the scope of the invention. Figure 1 The number of network elements included in the communication system shown. Although Figure 1 Not shown, but except Figure 1 In addition to the functional entities shown, Figure 1 It may also include other functional entities. Furthermore, the method provided in the embodiments of this application can be applied to… Figure 1 The communication system shown is applicable to other communication systems as well, and this application does not limit this application.

[0100] Specifically, the aforementioned terminal or roadside device can establish, for example... Figure 2 The protocol stack shown allows for communication between terminals, or between a terminal and a roadside device, based on... Figure 2 The protocol stack shown interacts with the interface. See also... Figure 2 , Figure 2 A schematic diagram of a protocol stack for LTE-based vehicle-to-everything (V2X) wireless communication technology is provided.

[0101] This protocol stack comprises an application layer, a network layer, and an access layer. The application layer primarily handles the application-level business logic of application services, such as generating instant messages and unicast service announcements. The application layer includes user applications and a messaging layer, which resides within the application layer. The messaging layer interfaces downwards with the data sublayer and supports specific user applications upwards. The messaging layer supports the transmission of various data types defined by the network layer based on LTE-based vehicular wireless communication technology. Interaction between the messaging layer and the data sublayer within the network layer is achieved through cross-layer primitives (also known as operation primitives or service primitives).

[0102] The network layer comprises a management sublayer and a data sublayer. The management sublayer handles system configuration and maintenance functions, such as MAC address selection and security mechanism selection. This sublayer can be a Dedicated Management Entity (DME), which provides management interfaces for all data sublayer entities. The data sublayer transmits data streams between application layers, as well as between different device management layer entities or between management layer entities and applications. The data sublayer includes an adaptation layer and a Dedicated Short Message Protocol (DSMP) layer. The DSMP layer interacts with different applications, while the adaptation layer provides transmission adaptation functions between the lower access layer and the upper protocol stack. For example, it distinguishes the underlying interface used by the data packets to be sent (e.g., DSMP packets, IP (Internet Protocol) packets) and passes the corresponding packets to the corresponding interface in the access layer for transmission. The adaptation layer also includes functions such as generating / changing / maintaining the source layer 2 identifier and mapping unicast / multicast addresses to layer 2 identifiers.

[0103] The access layer supports cellular communication interfaces (e.g., Uu port) and / or direct communication interfaces (e.g., PC5 port). The PC5 port and Uu port can support different Radio Access Technologies (RATs). For example, RATs can include LTE or NR technologies.

[0104] See Figure 3Taking the Roadside Unit (RSU) as an example and the OBU as an example, at least one terminal includes OBU1, OBU2 and OBU3. The RSU can communicate with OBU1, OBU2 and OBU3 respectively. The MAC addresses of OBU1, OBU2 and OBU3 are randomly selected from the same address domain. Suppose that the RSU periodically broadcasts unicast service announcements carrying specified application services. Since OBU1, OBU2, and OBU3 are all within the RSU's broadcast range, they can all receive the unicast service announcements from the RSU. After analyzing their own service needs, only OBU1 responds to the unicast service announcements sent by the RSU. That is, OBU1 sends a response message to the RSU, carrying OBU1's MAC address (e.g., MAC1). After receiving the response message from OBU1, the RSU finds that OBU1's MAC address is the same as OBU3's MAC address or that it does not support the security mechanisms provided by OBU1, causing an anomaly in the establishment of the unicast connection. This can easily lead to communication chaos and affect the normal execution of services.

[0105] To address the aforementioned issues, this application proposes a method for handling unicast connection establishment anomalies. This method resolves unicast establishment anomalies caused by MAC address conflicts, mismatched security mechanisms between communicating parties, and other factors. This improves the efficiency of establishing unicast connections and ensures the normal execution of unicast services between the communicating parties.

[0106] See Figure 4 , Figure 4 This application provides a method for handling unicast connection establishment exceptions, applied to a unicast connection establishment exception handling system. The system includes a first device and a second device, wherein the first device is the sender of the unicast service announcement, and the second device is the responder. The method includes, but is not limited to, the following steps:

[0107] S101: The second device sends the first message to the first device.

[0108] In this embodiment of the application, the first device first sends a broadcast message to the second device. The broadcast message may be a unicast service announcement used to indicate a preset application service.

[0109] In this embodiment, after receiving the broadcast message, the second device, based on its own business needs, determines that it needs to establish a unicast connection with the first device based on the preset application service. Therefore, the second device sends a first message to the first device. It can be understood that the first message is a response message to the broadcast message.

[0110] The second device can be one or more devices. For example, in Figure 4 In this context, m is a positive integer greater than or equal to 1. When m equals 1, the second device is a single device, i.e., device 1. In this case, the interaction process between the first device and the second device can be referred to in the following details. Figure 5 Description of the embodiment; when m is greater than 1, the second device is multiple devices, specifically including device 1, device 2, ..., device m. In this case, the interaction process between the first device and each device can be referred to the following. Figure 8 The description of the embodiments will not be repeated here.

[0111] In this embodiment, the first message is used to request the first device to establish a unicast connection with the second device. The first message carries the MAC address of the second device, the address identifier of the second device, and the security mechanism of the second device. The MAC address, address identifier, and security mechanism of the second device are determined by the second device.

[0112] In this embodiment, the MAC address of the second device is the address used by the second device to communicate with other devices on the network. For example, the MAC address of the second device can be 24 bits, selected by the second device using an autonomous address selection method.

[0113] In this embodiment, the security mechanism of the second device is the security mode adopted by the second device when interacting with other devices. The security mechanism of the second device includes, but is not limited to, symmetric key-based security mechanisms and certificate-based security mechanisms.

[0114] It is understandable that both communicating parties need to use the same security mechanism to ensure normal interaction. For example, a symmetric key-based security mechanism means that both parties must use the same key to encrypt and decrypt messages or data. It should be noted that the above security mechanisms have wide applications in the field of communications, and will not be elaborated upon here.

[0115] In this embodiment, the address identifier of the second device is used to identify the second device. The address identifier of the second device can be a randomly generated random number, the device identifier of the second device, or a string calculated based on the MAC address and device identifier of the second device, etc., and is not specifically limited here.

[0116] In this embodiment, the specific locations of the second device's MAC address, address identifier, and security mechanism within the first message can be referred to as follows. Figure 5 The relevant descriptions of the embodiments will not be repeated here.

[0117] S102: The first device determines, based on the first message, that the unicast connection between the second device and the first device is not established.

[0118] In this embodiment of the application, the first device receives a first message sent by the second device, and determines, based on the first message, that the unicast connection between the second device and the first device is not established, specifically including:

[0119] (1) Based on the judgment result that the MAC address of the second device is the same as the MAC address of the third device, it is determined that the unicast connection between the second device and the first device is abnormal, wherein the third device is the device that requested to establish a unicast connection with the first device;

[0120] (2) Based on the judgment result that the security mechanism of the second device is incompatible with the security mechanism supported by the first device, it is determined that the unicast connection establishment between the second device and the first device is abnormal; or

[0121] (3) Based on the judgment result of the message structure error of the first message sent by the second device, it is determined that the unicast connection between the second device and the first device is abnormal.

[0122] Specifically, if the MAC address of the second device is the same as that of the third device, it indicates a MAC address conflict; if the security mechanism of the second device is incompatible with the security mechanism supported by the first device, it indicates that the second device and the first device cannot communicate due to different encryption and decryption methods; if the message structure of the first message sent by the second device is incorrect, it indicates that the first device cannot parse the first message sent by the second device. It should be noted that the embodiments of this application do not limit the conditions for determining an anomaly in unicast connection establishment between the second device and the first device to the conditions listed above; other conditions that could lead to unicast connection establishment failure may also apply.

[0123] It is understandable that when the second device is a single device, if it is determined that the unicast connection between the second device and the first device is abnormal, then the second device can be called an abnormal device. When the second device is multiple devices, whether the unicast connection between each device and the first device is abnormal can be determined using the above method. Thus, it can be determined that the unicast connection between each of the multiple devices and the first device is abnormal, and each of the multiple devices can be called an abnormal device.

[0124] S103: The first device sends a second message to the second device.

[0125] In this embodiment, the second message carries the MAC address, address identifier, and error identifier of the abnormal device. The error identifier indicates the reason for the unicast connection establishment failure corresponding to the abnormal device. It should be noted that the error identifier can also be called an error code.

[0126] In one specific implementation, when the error identifier takes a first value, it indicates that a MAC address conflict has occurred in the abnormal device; when the error identifier takes a second value, it indicates that the security mechanism of the abnormal device is incompatible with the security mechanism supported by the first device; when the error identifier takes a third value, it indicates that the message format of the first message sent by the abnormal device is incorrect. In some possible embodiments, when the error identifier takes a fourth value, it indicates that a MAC address conflict has occurred in the abnormal device and that the security mechanism of the abnormal device is incompatible with the security mechanism supported by the first device. In another specific implementation, the error identifier can also be represented by bits. For example, 001 indicates that a MAC address conflict has occurred in the abnormal device, 010 indicates that the security mechanism of the abnormal device is incompatible with the security mechanism supported by the first device, 100 indicates that the message format of the first message sent by the abnormal device is incorrect, and 011 indicates that a MAC address conflict has occurred in the abnormal device and that the security mechanism of the abnormal device is incompatible with the security mechanism supported by the first device. No specific limitation is made here.

[0127] In this embodiment, when the number of abnormal devices is one, the second message carries a single MAC address. This embodiment can be further explained below. Figure 5 The relevant descriptions in the embodiments.

[0128] In this embodiment, when there are multiple abnormal devices, the second message carries multiple MAC addresses. This embodiment can be specifically referred to below. Figure 8 The relevant descriptions in the embodiments.

[0129] In this embodiment, S102 and S103 can be executed by the network layer or application layer of the first device. It should be noted that the network layer is the network layer in LTE-based vehicle-to-everything (V2X) wireless communication technology; for details, please refer to... Figure 2 The description of the network layer is provided above. The application layer refers to the application layer in LTE-based vehicle-to-everything (V2X) wireless communication technology. For details, please refer to [link / reference needed]. Figure 2 The relevant descriptions of the application layer will not be repeated here.

[0130] In one specific implementation, S102 and S103 can be executed by the network layer of the first device, for example, by the DME in the network layer of the first device. Specifically, after the DME in the network layer of the first device receives the first message sent by the second device, the DME of the first device determines that the unicast connection between the second device and the first device is not established, and triggers the sending of the second message by the DME of the first device.

[0131] In one specific implementation, S102 and S103 can also be executed by the application layer of the first device. Specifically, after the network layer of the first device receives the first message sent by the second device, the network layer of the first device sends the MAC address, address identifier, security mechanism, and other data in the first message to the application layer of the first device through cross-layer primitives. The application layer of the first device determines that the unicast connection between the second device and the first device is not established based on the received data, and triggers the sending of the second message by the application layer of the first device.

[0132] S104: The second device determines that the unicast connection between itself and the first device is not established according to the second message and performs exception handling operations.

[0133] The following is an illustrative example of the solution, using the second device as an example:

[0134] In this embodiment, when there is only one abnormal device, it means that the MAC address of the abnormal device carried in the second message is only one. In this case, if the MAC address of the abnormal device is the MAC address of the second device and the address identifier of the abnormal device is the address identifier of the second device, it means that the second device is the abnormal device. Therefore, it is determined that the unicast connection between the second device and the first device is abnormal, and the second device performs an exception handling operation. For details of this embodiment, please refer to the following: Figure 5 The relevant descriptions in the embodiments will not be repeated here.

[0135] In this embodiment, when there are multiple abnormal devices, it indicates that the second message carries multiple MAC addresses and multiple address identifiers. In this case, if the second device determines that the second message is a unicast connection establishment failure message, and further determines that the multiple MAC addresses carried by the second message include the MAC address of the second device and the multiple address identifiers carried by the second message include the address identifiers of the second device, then it determines that the unicast connection establishment between the second device and the first device is abnormal, and the second device performs an error handling operation. This embodiment can be specifically referred to below. Figure 8 The relevant descriptions in the embodiments will not be repeated here.

[0136] In the embodiments of this application, the execution of the exception handling operation may be performed by the network layer or the application layer of the second device, and the embodiments of this application do not make specific limitations.

[0137] As can be seen, by implementing the embodiments of this application, the sender can effectively distinguish different responders with the same MAC address based on the address identifier. If it is determined that there is an abnormal unicast connection establishment for a responder, the sender can send a message carrying the responder's address identifier, error identifier, and other information to inform the responder of the reason for the abnormal unicast connection establishment, so that the responder can take appropriate action. This can effectively solve the problem of abnormal unicast connection establishment between the sender and the responder, improve the efficiency of unicast connection establishment, and ensure the normal execution of services between the two communicating parties.

[0138] See Figure 5 , Figure 5 This application provides a method for handling unicast connection establishment exceptions. Compared to... Figure 4 Example, Figure 5 The second device in the text is a device. Figure 5 Implementation examples may be independent of the above. Figure 4 The embodiment can also be based on the above. Figure 4 Supplement to the embodiments. The method includes, but is not limited to, the following steps:

[0139] S201: The second device sends a first message to the first device.

[0140] In this embodiment, the second device may send a first message to the first device in response to a unicast service announcement sent by the first device. The first message requests the first device to establish a unicast connection with the second device, and carries the second device's MAC address, address identifier, and security mechanism.

[0141] The following details the location of the second device's MAC address, address identifier, and security mechanism within the first message.

[0142] In the first message, the address identifier of the second device is mainly carried in the following two ways:

[0143] The first type: It is carried by at least one of the dedicated business announcement identifier field and the content count field in the first message.

[0144] In this embodiment of the application, the address identifier of the second device may be one or more bearers of the DSA Identifier field and the Content Count field in the Dedicated Services Advertisement (DSA) message frame of the first message.

[0145] See Figure 6A , Figure 6A This is a schematic diagram illustrating the carrying of an address identifier in a first message, as provided in an embodiment of this application. Figure 6A The image shows the DSA message frame format of the first message, which includes a DSA header field and an application information field.

[0146] exist Figure 6A The DSA header field specifically includes the DSA Version field, the DSA Header Extension Indicator field, the Reserved field, the DSA Identifier field, the Content Count field, and the Header Extension field. Specifically, the DSA Header Extension Indicator field has a value of 1 indicating the presence of the Header Extension field, and a value of 0 indicating its absence. The Reserved field can be used for functional expansion. The DSA Identifier field indicates the uniqueness of the DSA. The Content Count field can be used to identify whether a DSA is a duplicate of the previous one when DSA IDs are the same. The Header Extension field can be reserved for other information.

[0147] exist Figure 6A The application information field specifically includes the Application Info Count field, the Application Identifier (AID) field, and the Application Extension field. The Application Info Count field indicates the number of application messages following it, the AID field indicates the type of application service, and the Application Extension field indicates relevant information about that application service.

[0148] In a specific implementation, the address identifier of the second device can be carried in Figure 6A The DSA Identifier field or Content Count field in the first message's DSA message frame. For example, if the address identifier of the second device is a 4-bit device identifier, it can be filled into the DSA Identifier field or Content Count field in the first message's DSA message frame.

[0149] In another specific implementation, the address identifier of the second device can be determined by... Figure 6AThe DSA Identifier and Content Count fields are carried together in the DSA message frame of the first message. For example, if the address identifier of the second device is an 8-bit random number, it can be filled into the DSA Identifier and Content Count fields of the DSA message frame of the first message.

[0150] The second method: carried by the header extension field in the first message.

[0151] In this embodiment of the application, the address identifier of the second device may be carried by the Header Extension field in the DSA message frame of the first message.

[0152] See Figure 6B , Figure 6B This is a schematic diagram illustrating the carrying of an address identifier in a first message, as provided in an embodiment of this application. Figure 6B For details on DSA message frames, please refer to [link / reference]. Figure 6A The relevant descriptions in the text will not be repeated here. In the DSA message frame, the Header Extension field further includes an Information Element Count field and at least one Information Element, and an Information Element can be represented by an Element ID field, a length field, and a content field. Figure 6B In this context, the address identifier of the second device can be carried by the Header Extension field. Specifically, the address identifier of the second device can be carried in the Header Extension field through a newly defined Element ID. For example, an Element ID field can be defined to indicate the function identifier for detecting address conflicts, a content field can be defined to indicate the address identifier of the second device, and a length field can be defined to indicate the length of the address identifier of the second device.

[0153] In this embodiment, the MAC address of the second device is carried by the source MAC address field of the first message, that is, the MAC address of the second device is the source layer 2 ID of the first message; the security mechanism of the second device can also be carried in the header extension field of the DSA message frame of the first message, which will not be elaborated here.

[0154] It should be noted that after determining its own MAC address and address identifier, the second device can also store the mapping relationship between the second device's MAC address and the second device's address identifier.

[0155] S202: The first device determines, based on the first message, that the unicast connection between the second device and the first device is not established.

[0156] Specifically, the process by which the first device determines that the unicast connection between the second device and the first device is abnormal based on the first message can include: performing operations such as determining whether the first message sent by the second device can be correctly parsed, comparing whether the security mechanism of the second device matches the security mechanism supported by the first device, and detecting whether there is a third device whose MAC address is the same as the MAC address of the second device. Here, the third device is the device requesting to establish a unicast connection with the first device, and the third device is different from the second device. If the first message cannot be parsed, it indicates an error in the message structure of the first message, and the unicast connection between the second device and the first device is determined to be abnormal. If the security mechanism of the second device does not match the security mechanism supported by the first device, the unicast connection between the second device and the first device is determined to be abnormal. If a third device's MAC address is detected to be the same as the MAC address of the second device, it indicates a MAC address conflict with the second device, and the unicast connection between the second device and the first device is determined to be abnormal. In some possible embodiments, various combinations of the following three conditions can occur: the first message cannot be parsed, the second device experiences a MAC address conflict, and the second device's security mechanism does not match the security mechanism supported by the first device; all of these can determine that the unicast connection between the second device and the first device is abnormal.

[0157] In some possible embodiments, if the second device satisfies the following conditions: the message structure of the first message sent by the second device is correct, the MAC address of the second device is not conflicting, and the security mechanism of the second device matches the security mechanism supported by the first device, then the first device and the second device successfully establish a unicast connection.

[0158] S203: The first device sends a second message to the second device.

[0159] In this embodiment of the application, if it is determined that the unicast connection establishment between the second device and the first device is abnormal, the first device sends a second message to the second device. The second message carries the MAC address, address identifier and error identifier of the second device, wherein the error identifier is used to indicate the reason for the unicast connection establishment abnormality.

[0160] In the second message, the MAC address of the second device is carried by the destination MAC address field of the second message, that is, the MAC address of the second device is the destination Layer 2 ID of the second message.

[0161] In the second message, the address identifier and error identifier of the second device are carried in the following two main ways:

[0162] Method 1: The Application Extension field carried in the DSA message frame of the second message

[0163] See Figure 7A , Figure 7A This is a schematic diagram of a second message provided in an embodiment of this application. Figure 7A In the second message, the source MAC address field carries the MAC address of the first device; that is, the source layer 2 identifier of the second message is the MAC address of the first device. The destination MAC address field carries the MAC address of the second device; that is, the destination layer 2 identifier of the second message is the MAC address of the second device. The MAC payload field of the second message can be used to carry Dedicated Short Message (DSM) message frames. A DSM message frame includes a Dedicated Short Message Protocol Version (DSMPVersion) field, a DSMP Extension Indicator field, a Reserved field, an Extension field, an Application Identifier (AID) field, a Length field, and a Data field. Specifically, a DSMP Extension Indicator field value of 1 indicates the presence of the subsequent Extension field, while a value of 0 indicates its absence. The Reserved field can be used for functional extensions. The AID field is used to fill in the application identifier to distinguish different applications. The Length field indicates the byte length of the application layer data entity. The Data field can be used to carry data entities from the application layer or management sublayer. Figure 7A In DSM message frames, the Data field is used to carry DSA message frames. For details on the various fields in a DSA message frame, please refer to [reference needed]. Figure 6A Description of DSA message frames.

[0164] exist Figure 7A In the second message shown, the address identifier and error identifier of the second device are carried by the Application Extension field in the DSA message frame of the second message. For example, a new Data field can be defined in the ApplicationExtension field to carry the address identifier and error identifier of the second device.

[0165] Method 2: Header Extension field carried in the DSA message frame of the second message

[0166] See Figure 7B , Figure 7B This is a schematic diagram of a second message provided in an embodiment of this application. Figure 7B In the second message, the source MAC address field carries the MAC address of the first device, the destination MAC address field carries the MAC address of the second device, the MAC payload field carries the DSM message frame, and the Data field in the DSM message frame carries the DSA message frame. For details on the fields in the DSM message frame, please refer to [reference needed]. Figure 7A For related descriptions, please refer to the specific fields in the DSA message frame. Figure 6A The relevant descriptions in the text will not be repeated here.

[0167] exist Figure 7B In the second message shown, the address identifier and error identifier of the second device are carried by the Header Extension field in the DSA message frame of the second message. For example, a new information element is defined in the Header Extension field, which is represented by the Element ID field, the length field, and the content field. The Element ID field is used to indicate the identifier of the unicast establishment failure, the length field is used to indicate the length of the content carried by the content field, and the content field is used to carry the address identifier and error identifier of the second device.

[0168] S204: The second device determines that the unicast connection between itself and the first device is not established according to the second message, and performs an exception handling operation according to the error identifier carried in the second message.

[0169] In this embodiment of the application, the second device receives the second message and knows that the number of MAC addresses carried in the second message is one and the number of address identifiers carried in the second message is one. It detects that the MAC address carried in the second message is the MAC address of the second device and the address identifier carried in the second message is the address identifier of the second device, which means that the second message carries the MAC address of the second device and the address identifier of the second device. Therefore, the second device determines that the unicast connection between itself and the first device is abnormal.

[0170] In this embodiment of the application, after the second device determines that the unicast connection between itself and the first device is not established, it performs an error handling operation according to the error identifier carried in the second message.

[0171] In one specific implementation, the second device performs an exception handling operation based on the error identifier carried in the second message. Specifically, when the error identifier indicates a MAC address conflict for the second device, the second device reselects its own MAC address. In some possible embodiments, if the address identifier of the second device is obtained based on the MAC address of the second device, and since the MAC address of the second device changes, the address identifier of the second device also needs to be changed. After reselecting its own MAC address, the second device can also re-determine its own address identifier.

[0172] In one specific implementation, the second device performs an exception handling operation based on the error identifier carried by the second message. Specifically, when the error identifier indicates that the security mechanism of the second device does not match the security mechanism supported by the first device, the second device reselects its own security mechanism.

[0173] In some possible embodiments, the second device performs exception handling operations based on the error identifier carried in the second message. Alternatively, when the error identifier indicates that the message structure of the first message sent by the second device is incorrect, the second device checks the message structure of the first message. In some possible embodiments, when the error identifier indicates that the MAC address of the second device conflicts and the security mechanism of the second device does not match the security mechanism supported by the first device, the second device reselects its own MAC address and its own security mechanism. This application does not specifically limit the exception handling operations performed by the second device.

[0174] In this embodiment of the application, after the second device performs an exception handling operation based on the error identifier carried in the second message, the second device can re-request the first device to establish a unicast connection with the second device.

[0175] As can be seen, by implementing the embodiments of this application, the responder can be identified based on the responder's MAC address and address identifier. Based on the error identifier carried in the message, the responder can be guided to effectively resolve the problem of abnormal unicast connection establishment between the sender and the responder caused by MAC address conflicts, security mechanism mismatches, etc., which is conducive to improving the efficiency of establishing unicast connections and ensuring the normal execution of unicast services between the two communicating parties.

[0176] See Figure 8 , Figure 8 This is yet another method for handling unicast connection establishment exceptions provided in the embodiments of this application. Compared to Figure 5 Example, Figure 8 Multiple devices interact with the first device, which is equivalent to... Figure 4 The second device in the embodiment includes multiple devices. Figure 8 Implementation examples may be independent of the above. Figure 4 and Figure 5 The embodiment can also be based on the above. Figure 4 Supplement to the embodiments. The method includes, but is not limited to, the following steps:

[0177] S301: Multiple devices send the first message to the first device.

[0178] In this embodiment, sending a first message from multiple devices to a first device can be achieved by each of the multiple devices sending one first message to the first device; that is, the number of first messages is the same as the number of devices. The first message is used to request the first device to establish a unicast connection with the first device. It should be noted that the multiple devices can be... Figure 8 Let device 1, device 2, ..., device m be a positive integer greater than 1.

[0179] Taking device 1 out of multiple devices as an example, the solution is illustrated below. The first message sent by device 1 to the first device requests the first device to establish a unicast connection with device 1. This first message carries device 1's MAC address, address identifier, and security mechanism. The specific method by which device 1's MAC address, address identifier, and security mechanism are carried in the first message can be found above. Figure 5 The relevant description of Example S201 will not be repeated here.

[0180] It should be noted that the first message sent by each of the multiple devices can be referred to the relevant description of the first message sent by device 1 above, and will not be repeated here.

[0181] S302: The first device determines that the unicast connection between the first device and the multiple devices is not established based on the first message sent by the multiple devices.

[0182] In this embodiment of the application, the first device determines that the unicast connection between each of the multiple devices and the first device is abnormal based on the first message sent by each of the multiple devices.

[0183] For each of the multiple devices, taking device 1 as an example, the first device determines that the unicast connection between device 1 and the first device is not established based on the first message sent by device 1. For details, please refer to [link / reference needed]. Figure 4 In the embodiment, S102 or Figure 5 The relevant descriptions of S202 in the embodiments will not be repeated here.

[0184] S303: The first device sends a second message to multiple devices.

[0185] In this embodiment, the second message carries the MAC addresses, address identifiers, and error identifiers of the aforementioned multiple devices (i.e., m devices). The error identifiers are used to indicate the reason for the abnormal establishment of the unicast connection of the corresponding device. For example, the second message may be a broadcast message.

[0186] In this embodiment of the application, the second message also includes a dedicated application identifier, which is used to indicate a unicast connection establishment failure. The dedicated application identifier is carried by the AID field in the DSM message frame of the second message.

[0187] In the second message, the destination MAC address field is used to carry the converted value of the dedicated application identifier.

[0188] In the second message, the MAC addresses, address identifiers, and error identifiers of multiple devices are carried in the following two main ways:

[0189] Method 1: The Application Extension field carried in the DSA message frame of the second message

[0190] See Figure 9A , Figure 9A This is a schematic diagram of a second message provided in an embodiment of this application. Figure 9A In the second message, the source MAC address field carries the MAC address of the first device, the destination MAC address field carries the converted value of the dedicated application identifier, and the MAC payload field carries the DSM message frame. For details on the DSM message frame, please refer to [link / reference needed]. Figure 7A The relevant descriptions are provided below. The AID field in a DSM message frame is used to carry a dedicated application identifier, and the Data field in a DSM message frame is used to carry a DSA message frame. For details on DSA message frames, please refer to [link / reference needed]. Figure 6A The relevant descriptions in the text will not be repeated here.

[0191] exist Figure 9A In the second message shown, the MAC addresses, address identifiers, and error identifiers of multiple devices are carried by the Application Extension field in the DSA message frame of the second message. For example, a new Data field can be defined within the Application Extension field to carry the MAC addresses, address identifiers, and error identifiers of multiple devices; additionally, it can also carry the device's statistical value 'm'. Figure 9A In this context, multiple devices include device 1, ..., device m.

[0192] Method 2: The Header Extension field carried in the DSA message frame of the second message

[0193] See Figure 9B , Figure 9B This is a schematic diagram of a second message provided in an embodiment of this application. Figure 9B In the second message, the source MAC address field carries the MAC address of the first device; the MAC payload field carries the DSM message frame; the destination MAC address field carries the converted value of the dedicated application identifier; the AID field in the DSM message frame carries the dedicated application identifier; and the Data field in the DSM message frame carries the DSA message frame. For details on each field in the DSM message frame, please refer to [reference needed]. Figure 7A For details regarding the relevant descriptions and the specific fields within the DSA message frame, please refer to [the relevant documentation / reference]. Figure 6A The relevant descriptions in the text.

[0194] exist Figure 9B In the second message shown, the MAC addresses, address identifiers, and error identifiers of multiple devices are carried by the Header Extension field in the DSA message frame of the second message. For example, a new information element is defined in the Header Extension field, represented by the Element ID field, length field, and content field. The Element ID field can be used to indicate a unicast establishment failure; the length field indicates the length of the content carried by the content field; and the content field carries the MAC addresses, address identifiers, and error identifiers of multiple devices. In addition, it can also carry the device's statistical value 'm'. Figure 9B In this context, multiple devices include device 1, ..., device m.

[0195] In some possible embodiments, in the event of an anomaly in establishing a unicast connection between multiple devices and the first device, the first message may also send a corresponding second message to each of the multiple devices. Each device's corresponding second message carries only its MAC address, address identifier, and error identifier. In this case, the second message may be as described above. Figure 7A or Figure 7B As shown in the figure.

[0196] S304: Each of the multiple devices determines that the unicast connection between itself and the first device has failed based on the second message, and performs exception handling operations according to the corresponding error identifier.

[0197] The following is an illustrative explanation of this step, using device 1 out of a set of multiple devices as an example:

[0198] After receiving the second message from the first device, device 1 first determines that the destination MAC address field of the second message carries a converted value of a dedicated application identifier, which is equivalent to knowing that the second message carries multiple MAC addresses, multiple address identifiers, and at least one error identifier. Further, device 1 determines whether the multiple MAC addresses carried in the second message include device 1's MAC address and whether the multiple address identifiers carried in the second message include device 1's address identifier. If both the multiple MAC addresses carried in the second message include device 1's MAC address and the multiple address identifiers carried in the second message include device 1's address identifier, device 1 determines that the unicast connection between itself and the first device is abnormal.

[0199] Because there is a mapping relationship between the MAC address, address identifier, and error identifier carried in the second message, when device 1 determines that the unicast connection between itself and the first device is abnormal, device 1 obtains its corresponding error identifier from the second message based on the mapping relationship between the MAC address, address identifier, and error identifier. Device 1 then performs exception handling operations based on its own corresponding error identifier. It should be noted that the specific process of device 1 performing exception handling operations can be found in [reference needed]. Figure 5 The description of the second device performing the exception handling operation in S204 of the embodiment will not be repeated here.

[0200] In some possible embodiments, where the second message carries only a MAC address, an address identifier, and an error identifier, the processing procedure of device 1 can be specifically referred to Figure 5 The relevant description of S204 in the embodiments.

[0201] As can be seen, by implementing the embodiments of this application, the sender can effectively distinguish different responders with the same MAC address based on the address identifier. If it is determined that there is an anomaly in the establishment of a unicast connection corresponding to multiple responders, the sender can send a message carrying the address identifiers of multiple responders to inform each responder of the reason for the anomaly in the establishment of the unicast connection, so that the responders can take appropriate action. This can effectively solve the problem of anomalies in the establishment of a unicast connection between the sender and the responders, reduce the consumption of network resources, improve the efficiency of unicast connection establishment, and ensure the normal execution of services between the two communicating parties.

[0202] The application of the above method is illustrated below with specific application scenarios.

[0203] See Figure 10 , Figure 10 This is a schematic diagram of a highway toll collection scenario. Figure 10 In this context, RSU is equivalent to the above. Figure 5 The first device in the list, OBU1, is equivalent to the one mentioned above. Figure 5The second device in this context, OBU2, is equivalent to the third device mentioned above. OBU2's MAC address is the same as OBU1's MAC address, both being MAC1. OBU1's address identifier is Address Identifier 1, and its security mechanism is Security Mechanism 1.

[0204] Assume the RSU broadcasts a unicast service announcement for near-field service applications. OBU2 enters the RSU's broadcast range before OBU1, establishes a unicast connection with the RSU, and completes a near-field payment. The RSU stores OBU2's MAC address (MAC1). While OBU2 is leaving the RSU, OBU1 enters the RSU's broadcast range and responds to the received unicast service announcement by sending a first message to the RSU requesting a unicast connection. This first message carries OBU1's MAC1, address identifier 1, and security mechanism 1. Based on the first message, the RSU detects a MAC address conflict in its stored MAC address list, indicating a MAC address conflict. Therefore, it identifies OBU1's error as error identifier 1, which indicates a MAC address conflict. This triggers the RSU to send a second message, carrying OBU1's MAC1, address identifier 1, and error identifier 1. After receiving the second message, OBU1 detects that the MAC address carried in the second message is MAC1 and the address identifier carried in the second message is address identifier 1, thus determining that the unicast connection establishment between OBU1 and RSU is abnormal. Furthermore, based on the error identifier carried in the second message, the cause of the unicast connection establishment abnormality is determined to be a MAC address conflict. Therefore, OBU1 reselects its own MAC address, or reselects its own MAC address and address identifier, and then responds again to the unicast service announcement from RSU, thereby improving the efficiency of unicast connection establishment.

[0205] See Figure 11 , Figure 11 This is a schematic diagram of a vehicle-to-vehicle communication scenario. Figure 11 In this context, OBU1 can be one of the above. Figure 8 Device 1 and OBU2 are equivalent to the above. Figure 8 The first device in the OBU. The MAC address of OBU1 is MAC1, the address identifier of OBU1 is address identifier 1, and the security mechanism of OBU1 is security mechanism 1. The security mechanism supported by OBU2 is security mechanism 2, and security mechanism 1 and security mechanism 2 are different.

[0206] Suppose OBU2 broadcasts a unicast service announcement for traffic service applications. OBU1 is within the broadcast range of OBU2. In response to this unicast service announcement, OBU1 sends a first message to OBU2 requesting OBU2 to establish a unicast connection with OBU1. The first message carries OBU1's MAC address (MAC1), address identifier (address identifier 1), and security mechanism (security mechanism 1). Based on the received first message, OBU2 detects that OBU1's security mechanism 1 does not match its own supported security mechanism (i.e., security mechanism 2), determines OBU1's error identifier as error identifier 2, and uses error identifier 2 to indicate that OBU1's security mechanism does not match OBU2's supported security mechanism. This triggers OBU2 to send a second message. For example, the second message is a broadcast message carrying multiple MAC addresses, multiple address identifiers, and at least one error identifier. After receiving the second message, OBU1 detects that the destination MAC address field of the second message carries a converted value of a dedicated application identifier, which indicates an anomaly in unicast connection establishment. Furthermore, it detects that the second message carries multiple MAC addresses, including OBU1's MAC1, and multiple address identifiers, including OBU1's address identifier 1. OBU1 determines that the unicast connection establishment between itself and OBU2 is abnormal. Further, it retrieves its corresponding error identifier, error identifier 2, from the second message. Based on error identifier 2, it determines that the unicast connection establishment anomaly is due to a security mechanism mismatch. Therefore, OBU1 reselects its own security mechanism and then responds again to the unicast service announcement from OBU2, thereby improving the efficiency of unicast connection establishment and ensuring the normal execution of services between the two communicating parties.

[0207] The methods of the embodiments of this application have been described in detail above, and the apparatus of the embodiments of this application is provided below.

[0208] See Figure 12 , Figure 12 This is a functional structure diagram of a communication device provided in an embodiment of this application. The communication device 30 includes a transmitting unit 310, a processing unit 312, and a receiving unit 314. The communication device 30 can be implemented by hardware, software, or a combination of hardware and software.

[0209] In one possible design, the communication device 30 can be as described above. Figure 4 , Figure 5 or Figure 8The first device in the process. Specifically: the receiving unit 314 is used to receive a first message sent by the second device, the first message is used to request the first device to establish a unicast connection with the second device, and the first message carries the second device's first medium access control MAC address, address identifier, and security mechanism; the processing unit 312 is used to determine, based on the first message, that the unicast connection establishment between the second device and the first device is abnormal; the sending unit 310 is used to send a second message to the second device, the second message carrying the first MAC address, address identifier, and error identifier, the error identifier being used to indicate the reason for the unicast connection establishment abnormality.

[0210] In this case, the communication device 30 can be used to achieve Figure 4 The method on the first device side described in the embodiments. Figure 4 In this embodiment, the receiving unit 314 and the processing unit 312 can be used to execute S102, and the sending unit 310 can be used to execute S103. The functional modules of the communication device 30 can also be used to implement... Figure 5 or Figure 8 The method on the first device side described in the embodiments will not be repeated here for the sake of brevity.

[0211] In another possible design, the communication device 30 can be as described above. Figure 4 or Figure 5 The second device or the above Figure 8 Any one of the multiple devices shown. Specifically: the sending unit 310 is used to send a first message to the first device, the first message is used to request the first device to establish a unicast connection with the second device, and the first message carries the second device's first medium access control MAC address, first address identifier, and security mechanism; the receiving unit 314 is used to receive a second message sent by the first device, the second message carries at least one MAC address, at least one address identifier, and an error identifier, the error identifier is used to indicate the reason for the unicast connection establishment failure; the processing unit 312 is used to determine the unicast connection establishment failure between the second device and the first device based on the second message, and to perform an exception handling operation based on the error identifier.

[0212] In this case, the communication device 30 can be used to achieve Figure 4 The method on the second device side described in the embodiments. Figure 4 In this embodiment, the transmitting unit 310 can be used to execute S101, and the receiving unit 314 and the processing unit 312 can be used to execute S104. The functional modules of the communication device 30 can also be used to implement... Figure 5 The method on the second device side described in the embodiments or Figure 8 The various device-side methods described in the embodiments will not be repeated here for the sake of brevity.

[0213] above Figure 12 One or more of the units in the illustrated embodiments may be implemented using software, hardware, firmware, or a combination thereof. The software or firmware includes, but is not limited to, computer program instructions or code, and may be executed by a hardware processor. The hardware includes, but is not limited to, various integrated circuits, such as a central processing unit (CPU), a digital signal processor (DSP), a field-programmable gate array (FPGA), or an application-specific integrated circuit (ASIC).

[0214] See Figure 13 , Figure 13 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Figure 13 As shown, the communication device 32 includes a processor 321, a transceiver 322, a memory 323, and a bus 324. In one specific embodiment, the processor 321, the memory 323, and the transceiver 322 communicate via the bus 324. It should be understood that this application does not limit the number of processors and memories in the communication device 32.

[0215] In one possible design, the communication device 32 can be as described above. Figure 4 , Figure 5 or Figure 8 The first device in the embodiments can be a roadside device, such as a roadside unit (RSU), multi-access edge computing (MEC), smart gas station, smart traffic light, etc. Alternatively, it can be a system composed of an RSU and MEC, a system composed of an RSU and sensors, or a system composed of an RSU, MEC, and sensors. The first device can also be a terminal, such as an on-board unit (OBU), a portable mobile device (e.g., a mobile phone, tablet, etc.), or other sensors or devices with communication functions, such as components or chips within a portable mobile device. This application does not specifically limit the specific devices described in the embodiments.

[0216] In another possible design, the communication device 32 can be as described above. Figure 4 or Figure 5 The second device or Figure 8 Any one of the multiple devices shown, the second device or Figure 8Any one of the multiple devices shown can be an On Board Unit (OBU), a smart gas station, a smart traffic light, a portable mobile device (e.g., a mobile phone, a tablet, etc.), or other sensors or devices with communication functions such as components or chips within a portable mobile device. This application does not impose specific limitations on the embodiments.

[0217] The 324 bus can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of representation, Figure 13 The bus 324 may be represented by a single line, but this does not mean that there is only one bus or one type of bus. The bus 324 may include a path for transmitting information between various components of the communication device 32 (e.g., memory 323, processor 321, transceiver 322).

[0218] Processor 321 may include any one or more processors such as a central processing unit (CPU), a microprocessor (MP), or a digital signal processor (DSP).

[0219] Memory 323 provides storage space, which can store data such as the operating system and computer programs. Memory 323 can be one or a combination of several of the following: random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read memory (CD-ROM). Memory 323 can exist independently or be integrated within processor 321.

[0220] Transceiver 322 can be used to provide information input or output to processor 321. Alternatively, transceiver 322 can be used to receive and / or transmit data to externally transmitted data, and can be a wired link interface including an Ethernet cable, or a wireless link interface (such as Wi-Fi, Bluetooth, general wireless transmission, vehicular short-range communication technology, etc.). Alternatively, transceiver 322 may also include a transmitter (such as an RF transmitter, antenna, etc.) or a receiver coupled to the interface.

[0221] In one specific implementation, when the communication device 32 is the first device described above, the processor 321 in the communication device 32 is used to read the computer program stored in the memory 323 and execute the aforementioned... Figure 4 , Figure 5 or Figure 8 The method on the first device side described in the embodiments.

[0222] In one possible design, the communication device 32 can be used for execution Figure 4 One or more modules in the first device of the method shown, the processor 321 being able to read one or more computer programs stored in memory 323, for performing the following operations:

[0223] The receiving unit 314 receives a first message sent by the second device. The first message is used to request the first device to establish a unicast connection with the second device. The first message carries the first medium access control MAC address, address identifier, and security mechanism of the second device. Based on the first message, it is determined that the unicast connection establishment between the second device and the first device is abnormal. The sending unit 310 sends a second message to the second device. The second message carries the first MAC address, address identifier, and error identifier. The error identifier is used to indicate the reason for the unicast connection establishment abnormality.

[0224] In another specific implementation, when the communication device 32 is the second device described above, the processor 321 in the communication device 32 is used to read the computer program stored in the memory 323 and execute the aforementioned... Figure 4 or Figure 5 The method on the second device side described in the embodiments or Figure 8 The embodiments describe multiple device-side methods.

[0225] In one possible design, the communication device 32 can be used for execution Figure 4 One or more modules in the second device of the method shown, the processor 321 being able to read one or more computer programs stored in memory 323, for performing the following operations:

[0226] The sending unit 310 sends a first message to the first device, which requests the first device to establish a unicast connection with the second device. The first message carries the second device's first medium access control MAC address, first address identifier, and security mechanism. The receiving unit 314 receives a second message sent by the first device. The second message carries at least one MAC address, at least one address identifier, and an error identifier. The error identifier indicates the reason for the unicast connection establishment failure. The receiving unit 314 determines that the unicast connection establishment between the second device and the first device is abnormal based on the second message and performs an exception handling operation based on the error identifier.

[0227] This application also provides a vehicle, which includes the first device or the second device described above. In one specific implementation, the vehicle can be used to perform the above-described... Figure 4 , Figure 5 or Figure 8 The method on the first device side described in the embodiments. In another specific embodiment, the vehicle can be used to perform the above. Figure 4 or Figure 5 The method on the second device side described in the embodiments, or Figure 8 The embodiments describe multiple device-side methods.

[0228] This application also provides a unicast connection establishment exception handling system, which includes the first device and the second device described above. This system is used to execute the methods described in the embodiments of this application above.

[0229] The first device can be a roadside unit (RSU), a multi-access edge computing (MEC), an on-board unit (OBU), a smart gas station, a smart traffic light, a portable mobile device (e.g., a mobile phone, tablet, etc.), or other sensors or devices with communication functions, such as components or chips within a portable mobile device. For example, the first device can also be a system composed of an RSU and an MEC, a system composed of an RSU and sensors, or a system composed of an RSU, an MEC, and sensors.

[0230] The second device may be an on-board unit, a smart gas station, a smart traffic light, a portable mobile device (e.g., a mobile phone, a tablet, etc.), or other sensors or devices with communication functions such as components or chips within a portable mobile device. This application does not impose specific limitations on the embodiments.

[0231] In the embodiments described above, each embodiment has its own emphasis. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0232] It should be noted that those skilled in the art will recognize that all or part of the steps in the various methods of the above embodiments can be implemented by a program instructing related hardware. This program can be stored in a computer-readable storage medium, including read-only memory (ROM), random access memory (RAM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), one-time programmable read-only memory (OTPROM), electrically-erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, disk storage, magnetic tape storage, or any other computer-readable medium capable of carrying or storing data.

[0233] The technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. The computer program product is stored in a storage medium and includes several instructions to cause a device (which may be a personal computer, server, network device, robot, microcontroller, chip, robot, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application.

Claims

1. A method for handling unicast connection establishment anomalies in vehicle-to-everything (V2X) communication, applied to a first device, characterized in that, The method comprises: receiving a first message sent by a second device, the first message being used for requesting the first device to establish a unicast connection with the second device, the first message carrying a first media access control (MAC) address of the second device, an address identifier and a security mechanism, the address identifier being used for identifying the second device from different devices with the same MAC address; determining, according to the first message, that the unicast connection establishment between the second device and the first device is abnormal; sending a second message to the second device, the second message carrying the first MAC address, the address identifier and an error identifier, the error identifier being used for indicating the reason of the unicast connection establishment abnormality.

2. The method of claim 1, wherein, The determining, according to the first message, that the unicast connection establishment between the second device and the first device is abnormal comprises: determining, based on a result of judging that the first MAC address is the same as a second MAC address of a third device, that the unicast connection establishment between the second device and the first device is abnormal, wherein the third device is a device requesting to establish a unicast connection with the first device; determining, based on a result of judging that the security mechanism does not match a security mechanism supported by the first device, that the unicast connection establishment between the second device and the first device is abnormal; or determining, based on a result of judging that a message structure of the first message is wrong, that the unicast connection establishment between the second device and the first device is abnormal.

3. The method of claim 1, wherein, The second device is one device, the first MAC address is one MAC address, and the second message carrying the first MAC address comprises: The first MAC address is carried by a destination MAC address field of the second message.

4. The method of claim 3, wherein, The second message carrying the address identifier and the error identifier comprises: The address identifier and the error identifier are carried in a Header Extension field in a dedicated service announcement (DSA) message frame of the second message; or The address identifier and the error identifier are carried in an Application Extension field in the DSA message frame of the second message.

5. The method of claim 1, wherein, The second device is a plurality of devices, the first MAC address is a plurality of MAC addresses, the second message further comprises a dedicated application identifier, the dedicated application identifier being used for indicating the unicast connection establishment abnormality, the dedicated application identifier being carried in an application identifier (AID) field in a dedicated short message (DSM) message frame of the second message; A destination MAC address field of the second message is used for carrying a conversion value of the dedicated application identifier.

6. The method of claim 5, wherein, The second message carrying the first MAC address, the address identifier and the error identifier comprises: The first MAC address, the address identifier and the error identifier are carried in a Header Extension field in a dedicated service announcement (DSA) message frame of the second message; or The first MAC address, the address identifier and the error identifier are carried in an Application Extension field in the DSA message frame of the second message.

7. The method according to any one of claims 1 to 6, characterized in that, In the first message, the address identifier of the second device is carried in at least one of a DSA Identifier field and a Content Count field in a Dedicated Short-Range Communications (DSRC) message frame of the first message.

8. The method according to any one of claims 1 to 6, characterized in that, In the first message, the address identifier of the second device is carried in a Header Extension field of a Dedicated Short-Range Communications (DSRC) message frame of the first message.

9. The method according to any one of claims 1 to 6, characterized in that, The address identifier is a random number.

10. A method for handling unicast connection establishment anomalies in vehicle-to-everything (V2X) communication, applied to a second device, characterized in that, The method comprises: sending a first message to a first device, the first message being used to request the first device to establish a unicast connection with a second device, the first message carrying a first Media Access Control (MAC) address of the second device, a first address identifier and a security mechanism, the first address identifier being used to identify the second device from different devices having the same MAC address; receiving a second message sent by the first device, the second message carrying at least one MAC address, at least one address identifier and an error identifier, the error identifier being used to indicate a reason for an abnormality of the unicast connection establishment; determining, according to the second message, that the unicast connection establishment between the second device and the first device is abnormal; performing an abnormality handling operation according to the error identifier.

11. The method of claim 10, wherein, The performing of the abnormality handling operation according to the error identifier comprises: reselecting the first MAC address when the error identifier indicates that the first MAC address is in conflict.

12. The method of claim 10, wherein, The performing of the abnormality handling operation according to the error identifier comprises: reselecting the security mechanism when the error identifier indicates that the security mechanism does not match a security mechanism supported by the first device.

13. The method of claim 10, wherein, The determining of the unicast connection establishment between the second device and the first device being abnormal according to the second message comprises: determining that the unicast connection establishment between the second device and the first device is abnormal when the at least one MAC address is the first MAC address and the at least one address identifier is the first address identifier.

14. The method of claim 13, wherein, The second message carrying at least one MAC address, at least one address identifier and an error identifier comprises: The at least one MAC address is carried by a Destination MAC Address field of the second message. The at least one address identifier and the error identifier are carried in a Header Extension field in a Dedicated Short-Range Communications (DSRC) message frame of the second message, or the at least one address identifier and the error identifier are carried in an Application Extension field in the DSA message frame of the second message.

15. The method of claim 10, wherein, The second message further comprises a dedicated application identifier, the dedicated application identifier is used to indicate the abnormal unicast connection establishment, the dedicated application identifier is carried in an application identifier (AID) field in a dedicated short message (DSM) message frame of the second message, and the determining the abnormal unicast connection establishment between the second device and the first device according to the second message comprises: when the content carried in a destination MAC address field of the second message comprises a converted value of the dedicated application identifier, and the at least one MAC address comprises the first MAC address and the at least one address identifier comprises the first address identifier, it is determined that the abnormal unicast connection establishment between the second device and the first device.

16. The method of claim 15, wherein, The second message carries at least one MAC address, at least one address identifier and an error identifier, comprising: The at least one MAC address, the at least one address identifier and the error identifier are carried in a header extension field in a dedicated service announcement (DSA) message frame of the second message; or The at least one MAC address, the at least one address identifier and the error identifier are carried in an application extension field in the DSA message frame of the second message.

17. The method according to any one of claims 10-16, characterized in that, In the first message, the first address identifier is carried in at least one of a DSA identifier (DSA Identifier) field and a content count (Content Count) field in a dedicated service announcement (DSA) message frame of the first message.

18. The method according to any one of claims 10-16, characterized in that, In the first message, the first address identifier is carried in a header extension field in a dedicated service announcement (DSA) message frame of the first message.

19. An apparatus for handling unicast connection establishment anomalies in vehicle-to-everything (V2X) communication, characterized in that, The apparatus comprises: a receiving unit configured to receive a first message sent by a second device, the first message being used to request a first device to establish a unicast connection with the second device, and the first message carrying a first media access control (MAC) address of the second device, an address identifier and a security mechanism, the address identifier being used to identify the second device from different devices having the same MAC address; a processing unit configured to determine, according to the first message, that the unicast connection establishment between the second device and the first device is abnormal; a sending unit configured to send a second message to the second device, the second message carrying the first MAC address, the address identifier and an error identifier, the error identifier being used to indicate a reason for the abnormal unicast connection establishment.

20. The apparatus of claim 19, wherein, The processing unit is specifically configured to: determine, based on a result of judging that the first MAC address is the same as a second MAC address of a third device, that the unicast connection establishment between the second device and the first device is abnormal, wherein the third device is a device requesting to establish a unicast connection with the first device; determine, based on a result of judging that the security mechanism does not match a security mechanism supported by the first device, that the unicast connection establishment between the second device and the first device is abnormal; or determine that the unicast connection establishment between the second device and the first device is abnormal based on the result of determining that the first message has a message structure error.

21. The apparatus of claim 19, wherein, The second device is one device, the first MAC address is one MAC address, and the first MAC address is carried in the second message includes: The first MAC address is carried by a destination MAC address field of the second message.

22. The apparatus of claim 21, wherein, The address identifier and the error identifier are carried in a header extension field of a dedicated service announcement (DSA) message frame of the second message; or The address identifier and the error identifier are carried in an application extension field of the DSA message frame of the second message. The second device is a plurality of devices, the first MAC address is a plurality of MAC addresses, the second message further includes a dedicated application identifier, the dedicated application identifier is used to indicate that the unicast connection establishment is abnormal, and the dedicated application identifier is carried in an application identifier (AID) field of a dedicated short message (DSM) message frame of the second message.

23. The apparatus of claim 19, wherein, The destination MAC address field of the second message is used to carry a conversion value of the dedicated application identifier. The first MAC address, the address identifier, and the error identifier are carried in a header extension field of a dedicated service announcement (DSA) message frame of the second message; or 24. The apparatus of claim 23, wherein, The first MAC address, the address identifier, and the error identifier are carried in an application extension field of the DSA message frame of the second message. In the first message, the address identifier of the second device is carried in at least one of a DSA identifier (DSA Identifier) field and a content count (Content Count) field of a dedicated service announcement (DSA) message frame of the first message. In the first message, the address identifier of the second device is carried in a header extension field of a dedicated service announcement (DSA) message frame of the first message.

25. The apparatus of any one of claims 19-24, wherein, The apparatus includes:

26. The apparatus of any one of claims 19-24, wherein, a sending unit configured to send a first message to a first device, the first message being used to request the first device to establish a unicast connection with a second device, the first message carrying a first media access control (MAC) address of the second device, a first address identifier, and a security mechanism, the first address identifier being used to identify the second device from different devices having the same MAC address; 27. An apparatus for handling unicast connection establishment anomalies in vehicle-to-everything (V2X) communication, characterized in that, a receiving unit configured to receive a second message sent by the first device, the second message carrying at least one MAC address, at least one address identifier, and an error identifier, the error identifier being used to indicate a reason for the unicast connection establishment being abnormal; and ​ ​ a processing unit, configured to determine, according to the second message, that a unicast connection establishment between the second device and the first device is abnormal; the processing unit is further configured to perform an abnormality handling operation according to the error identification.

28. The apparatus of claim 27, wherein, the processing unit is specifically configured to: reselect the first MAC address when the error identification indicates that the first MAC address is in conflict.

29. The apparatus of claim 27, wherein, the processing unit is specifically configured to: reselect the security mechanism when the error identification indicates that the security mechanism does not match a security mechanism supported by the first device.

30. The apparatus of claim 27, wherein, the processing unit is specifically configured to: determine that the unicast connection establishment between the second device and the first device is abnormal when the at least one MAC address is the first MAC address and the at least one address identification is the first address identification.

31. The apparatus of claim 30, wherein, the second message carries at least one MAC address, at least one address identification, and an error identification, and includes: the at least one MAC address is carried by a destination MAC address field of the second message; the at least one address identification and the error identification are carried in a header extension field of a dedicated service announcement (DSA) message frame of the second message, or the at least one address identification and the error identification are carried in an application extension field of the DSA message frame of the second message.

32. The apparatus of claim 27, wherein, the second message further includes a dedicated application identification, the dedicated application identification is used to indicate the unicast connection establishment abnormality, the dedicated application identification is carried in an application identification (AID) field of a dedicated short message (DSM) message frame of the second message, and the processing unit is specifically configured to: determine that the unicast connection establishment between the second device and the first device is abnormal when content carried by the destination MAC address field of the second message includes a conversion value of the dedicated application identification, and the at least one MAC address includes the first MAC address and the at least one address identification includes the first address identification.

33. The apparatus of claim 32, wherein, the second message carries at least one MAC address, at least one address identification, and an error identification, and includes: the at least one MAC address, the at least one address identification, and the error identification are carried in a header extension field of a dedicated service announcement (DSA) message frame of the second message; or the at least one MAC address, the at least one address identification, and the error identification are carried in an application extension field of the DSA message frame of the second message.

34. The device of any one of claims 27-32, wherein, in the first message, the first address identification is carried in at least one of a DSA identifier (DSA Identifier) field and a content count (Content Count) field of a DSA message frame of the first message.

35. The device of any one of claims 27-32, wherein, in the first message, the first address identification is carried in a header extension field of a DSA message frame of the first message.

36. An apparatus for handling unicast connection setup exceptions, the apparatus comprising: The apparatus comprises a memory storing computer program instructions and a processor executing the computer program instructions to cause the apparatus to perform the method of any of claims 1-9.

37. An apparatus for handling unicast connection setup exceptions, the apparatus comprising: The apparatus comprises a memory storing computer program instructions and a processor executing the computer program instructions to cause the apparatus to perform the method of any of claims 10-18.

38. A computer-readable storage medium, characterized in that, Computer program instructions comprising a computer program instructions, when executed by a processor, implement the method of any of claims 1-9.

39. A computer-readable storage medium, characterized in that, Computer program instructions comprising a computer program instructions, when executed by a processor, implement the method of any of claims 10-18.

40. A vehicle characterized by The vehicle comprises the apparatus of any of claims 19-26 or 36, or the vehicle comprises the apparatus of any of claims 27-35 or 37.

41. A unicast connection establishment exception handling system, characterized by The system comprises a first device for performing the method of any of claims 1-9 and a second device for performing the method of any of claims 10-18.

Images