WO2023020148A1 - 一种单播连接建立异常处理方法及装置 - Google Patents

一种单播连接建立异常处理方法及装置 Download PDF

Info

Publication number
WO2023020148A1
WO2023020148A1 PCT/CN2022/104228 CN2022104228W WO2023020148A1 WO 2023020148 A1 WO2023020148 A1 WO 2023020148A1 CN 2022104228 W CN2022104228 W CN 2022104228W WO 2023020148 A1 WO2023020148 A1 WO 2023020148A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
identifier
address
mac address
unicast connection
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2022/104228
Other languages
English (en)
French (fr)
Inventor
杨淼
李明超
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to EP22857461.2A priority Critical patent/EP4366342B1/en
Publication of WO2023020148A1 publication Critical patent/WO2023020148A1/zh
Priority to US18/426,254 priority patent/US12615692B2/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/40—Connection management for selective distribution or broadcast
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/30—Services specially adapted for particular environments, situations or purposes
    • H04W4/40—Services specially adapted for particular environments, situations or purposes for vehicles, e.g. vehicle-to-pedestrians [V2P]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/40—Network security protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/12—Detection or prevention of fraud
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/12—Detection or prevention of fraud
    • H04W12/121—Wireless intrusion detection systems [WIDS]; Wireless intrusion prevention systems [WIPS]
    • H04W12/122—Counter-measures against attacks; Protection against rogue devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/08—Testing, supervising or monitoring using real traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/11—Allocation or use of connection identifiers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/18—Management of setup rejection or failure
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/60—Types of network addresses
    • H04L2101/618—Details of network addresses
    • H04L2101/622—Layer-2 addresses, e.g. medium access control [MAC] addresses

Definitions

  • the present application relates to the field of Internet of Vehicles communication, in particular to a method and device for handling exceptions in unicast connection establishment.
  • the Internet of Vehicle (IOV) technology can realize the exchange and sharing of intelligent information (such as road condition information, service information, etc.) between vehicles and X (people, vehicles, roads, clouds, etc.), which greatly facilitates the Communication with X.
  • intelligent information such as road condition information, service information, etc.
  • the application discloses a method and device for handling abnormalities in unicast connection establishment, which can effectively solve the problem of abnormal unicast connection establishments, improve the efficiency of establishing unicast connections, and ensure the smooth execution of unicast services between communication parties.
  • the present application provides a method for handling exceptions in unicast connection establishment, which is applied to a first device, and the method includes: receiving a first message sent by a second device, and the first message is used to request the first device to communicate with the second The device establishes a unicast connection, and the first message carries the first media access control MAC address, address identifier and security mechanism of the second device; according to the first message, it is determined that the establishment of the unicast connection between the second device and the first device is abnormal; Sending a second message to the second device, where the second message carries the first MAC address, an address identifier and an error identifier, where the error identifier is used to indicate the cause of the abnormal establishment of the unicast connection.
  • the first device may be a Road Side Unit (Road Side Unit, RSU), Multi-Access Edge Computing (Multi-Access Edge Computing, MEC), an On Board Unit (OBU), an intelligent gas station, an intelligent signal light, Portable mobile devices (such as mobile phones, tablets, etc.), or other sensors or devices with communication functions such as components and chips in portable mobile devices.
  • RSU Road Side Unit
  • MEC Multi-Access Edge Computing
  • OBU On Board Unit
  • the first device may also be a system consisting of an RSU and an MEC, or a system consisting of an RSU and a sensor, or a system consisting of an RSU, an MEC, and a sensor.
  • the second device may be a vehicle-mounted unit, a smart gas station, a smart signal light, a portable mobile device (such as a mobile phone, a tablet, etc.), or other sensors or devices with communication functions such as components and chips in a portable mobile device. Not specifically limited.
  • the security mechanism refers to the security mode or security protection method adopted by the device during communication.
  • the security mechanism may be a security mechanism based on a symmetric key, a security mechanism based on a certificate, etc., and is not specifically limited in this embodiment of the application.
  • the address identification may identify the second device.
  • the address identifier may be a device identifier of the second device, a random number, or a character string generated according to the MAC address of the second device and the device identifier, etc., which are not specifically limited in this embodiment of the present application.
  • the first device can effectively distinguish different devices with the same MAC address based on the address identification, and can accurately indicate the cause of the abnormal establishment of the unicast connection between the second device and the first device based on the error identification.
  • Messages such as identifiers and error identifiers can effectively solve the problem of abnormal establishment of unicast connections, help to improve the efficiency of establishing unicast connections, and ensure the normal execution of unicast services between communication parties.
  • determining that the unicast connection between the second device and the first device is abnormal includes: determining that the first MAC address is the same as the second MAC address of the third device based on a judgment result that the first MAC address The address is the same as the second MAC address of the third device, where the third device is a device requesting to establish a unicast connection with the first device; based on the judgment result that the security mechanism of the second device does not match the security mechanism supported by the first device , determining that the security mechanism of the second device does not match the security mechanism supported by the first device; or determining that the message structure of the first message is wrong based on a judgment result that the message structure of the first message is wrong.
  • the fact that the first MAC address is the same as the second MAC address of the third device means that there is a conflict between the first MAC address of the second device, which will cause abnormal unicast connection establishment; the security mechanism of the second device is different from that supported by the first device If the security mechanism does not match, it means that the first device and the second device encrypt and decrypt information in different ways during the interaction process, which will lead to abnormal unicast connection establishment; the wrong message structure of the first message means that the first device cannot parse or accurately Parse the first message, which will cause an exception in the establishment of a unicast connection.
  • the first MAC address is a MAC address
  • the second message carries the first MAC address, including: the first MAC address is determined by the destination MAC address field of the second message bearer.
  • 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.
  • the second message carries the address identifier and the error identifier, including: the address identifier and the 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 second The address identifier and error identifier of the device are carried in the Application Extension field in the DSA message frame of the second message.
  • the second message carries the address identifier and error identifier of the second device, so that the receiving end of the second message can quickly determine whether the unicast connection with the first device is abnormal according to the address identifier, and indicate according to the error identifier
  • the cause of the abnormal establishment of the unicast connection is processed accordingly, which is beneficial to solve the problem of the abnormal establishment of the unicast connection between the communication parties.
  • the first MAC address is multiple MAC addresses
  • the second message also includes a dedicated application identifier, which is used to indicate that the unicast connection is abnormally established, and the dedicated application identifier
  • the application identification AID field carried in 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 identification.
  • the second device when the second device is multiple devices, when the destination MAC address field of the second message is used to carry the conversion value of the dedicated application identifier, it can be known that the second message carries the MAC addresses of multiple devices , so that the number of transmission times of the second message can be reduced, effectively reducing the consumption of network resources.
  • the second message carries the first MAC address, address identifier and error identifier, including: the first MAC address, address identifier and error identifier are carried in the header extension field Header in the dedicated service announcement DSA message frame of the second message Extension field; or the first MAC address, address identifier and error identifier are carried in the Application Extension field of the DSA message frame of the second message.
  • the second message in the case of the second device is a plurality of devices, the second message carries a plurality of MAC addresses, a plurality of address identifiers and at least one error identifier, through a second message can inform the communication with the first device
  • Multiple devices with abnormal unicast connection establishment can help improve the efficiency of unicast connection establishment and effectively reduce the consumption of network resources.
  • the address identifier of the second device is carried by at least one of the DSA identifier DSA Identifier field and the Content Count field in the dedicated service announcement DSA message frame of the first message.
  • the first message carries the address identifier of the second device, and the address identifier enables the receiving end of the first message (that is, the first device) to effectively distinguish different devices with the same MAC address.
  • 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.
  • the first message carries the address identifier of the second device, and the address identifier enables the receiving end of the first message (that is, the first device) to effectively distinguish different devices with the same MAC address.
  • the second message is sent by the network layer or the application layer of the first device.
  • the network layer is the network layer in the wireless communication technology of the Internet of Vehicles based on Long Term Evolution (LTE).
  • LTE Long Term Evolution
  • the management sublayer in the network layer can be used to complete functions such as system configuration and maintenance.
  • the data sublayer in the network layer It can be used to transmit data streams between application layers and data streams between management entities of different devices or between management entities and applications;
  • the application layer is the application layer in the LTE-based Internet of Vehicles wireless communication technology, and the application layer is mainly used to process application services application layer business logic, for example, generating instant messages, unicast service announcements, etc.
  • the interaction between the network layer and the application layer can be realized through cross-layer primitives.
  • the network layer of the first device can send the second message, and the network layer of the first device can also determine that the unicast connection between the second device and the first device is abnormal according to the first message, which can be found faster The unicast link establishes an abnormal situation and responds quickly, while saving the consumption of upper-layer resources in the first device.
  • the application layer of the first device can determine the abnormality of the establishment of the unicast connection between the second device and the first device according to the first message and send the second message, which is beneficial to reduce the data processing of other layers in the first device Pressure, the handling method is relatively flexible.
  • the present application provides a method for handling exceptions in unicast connection establishment, which is applied to a second device.
  • the method includes: sending a first message to the first device, and the first message is used to request that the first device communicate with the second device Establishing a unicast connection, the first message carrying the first MAC address of the second device, the first address identifier, and the security mechanism; receiving the 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, where the error identifier is used to indicate the cause of the abnormal establishment of the unicast connection; according to the second message, it is determined that the establishment of the unicast connection between the second device and the first device is abnormal; and an exception handling operation is performed according to the error identifier.
  • an address identifier is added to the content carried in the first message, and the address identifier can identify the second device; according to the error identifier in the second message, the second device, It can accurately know the cause of abnormal unicast connection establishment between itself and the first device, thereby effectively solving the problem of abnormal unicast connection establishment, which is conducive to improving the efficiency of unicast connection establishment and ensuring unicast services between communication parties normal execution.
  • performing the exception handling operation according to the error identifier may be: reselecting the first MAC address when the error identifier indicates that the first MAC address has a conflict.
  • performing the exception handling operation according to the error identifier may be: reselecting the security mechanism of the second device when the error identifier indicates that the security mechanism of the second device does not match the security mechanism supported by the first device.
  • performing the exception handling operation according to the error identifier may be: re-checking the message structure of the first message when the error identifier indicates that the message structure of the first message is wrong.
  • determining, according to the second message, that the establishment of the unicast connection between the second device and the first device is abnormal includes: when the at least one MAC address is the first MAC address and the at least one address identifier is the first address identifier, It is determined that the establishment of the unicast connection between the second device and the first device is abnormal.
  • 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 establishment of the unicast connection between itself and the first device is abnormal.
  • 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 is carried by the destination MAC address field of the second message; the at least one address identifier and the error identifier are carried in The Header Extension field in the dedicated service announcement DSA message frame of the second message, or the above-mentioned at least one address identifier and error identifier are carried in the Application Extension field in the DSA message frame of the second message.
  • the address identifier and error identifier carried in the second message enable the receiving end of the second message to quickly determine whether the unicast connection establishment with the first device is abnormal and whether the unicast connection is established according to the error identifier according to the address identifier. Corresponding processing is performed on the cause of the abnormality, which is beneficial to solving the problem of abnormal establishment of the unicast connection between the communication parties.
  • the second message also includes a dedicated application identifier, which is used to indicate that the unicast connection is abnormally established, and the dedicated application identifier is carried in the application identifier AID field in the dedicated short message DSM message frame of the second message, according to the second
  • the message determines that the establishment of the unicast connection between the second device and the first device is abnormal, which may be: when the content carried in the destination MAC address field of the second message includes the conversion value of the dedicated application identifier, and the at least one MAC address includes the first MAC address address and the at least one address identifier includes the first address identifier, it is determined that the establishment of the unicast connection between the second device and the first device is abnormal.
  • the second message when the destination MAC address field of the second message is used to carry the conversion value of the dedicated application identifier, it can be known that the second message carries multiple MAC addresses and multiple address identifiers, and when the second message carries the second In the case of the MAC address and address identifier of the device, the second device can quickly determine that the establishment of the unicast connection between itself and the first device is abnormal.
  • the second message carries at least one MAC address, at least one address identifier, and error identifier, including: the above-mentioned at least one MAC address, at least one address identifier, and error identifier are carried in a dedicated service announcement DSA message frame of the second message The Header Extension field of the header extension field; or the above-mentioned at least one MAC address, at least one address identifier and error identifier are carried in the Application Extension field of the DSA message frame of the second message.
  • the second message can carry multiple MAC addresses and multiple address identifiers. Through such a second message, multiple devices that have abnormal unicast connection establishment with the first device can be notified at the same time, which is beneficial to improve the establishment of a single The efficiency of the broadcast connection can effectively reduce the consumption of network resources.
  • the first address identifier is carried by at least one of the DSA identifier DSA Identifier field and the Content Count field in the dedicated service announcement DSA message frame of the first message.
  • the first message carries the first address identifier, which enables the receiving end of the first message (that is, the first device) to effectively distinguish different devices with the same MAC address.
  • the first address identifier is carried in the Header Extension field of the dedicated service announcement DSA message frame of the first message.
  • the first message carries the first address identifier, which enables the receiving end of the first message (that is, the first device) to effectively distinguish different devices with the same MAC address.
  • the present application provides a device for processing an abnormal establishment of a unicast connection, the device comprising: a receiving unit, configured to receive a first message sent by the second device, and the first message is used to request the first device to communicate with the The second device establishes a unicast connection, and the first message carries the first media access control MAC address, address identifier and security mechanism of the second device; the processing unit is configured to determine the relationship between the second device and the first device according to the first message The inter-unicast connection establishment is abnormal; the sending unit is configured to send a second message to the second device, the second message carries the first MAC address, address identifier and error identifier, and the error identifier is used to indicate the cause of the abnormal unicast connection establishment.
  • the processing unit is specifically configured to: determine that the first MAC address is the same as the second MAC address of the third device based on a judgment result that the first MAC address is the same as the second MAC address of the third device, wherein the third The device is a device requesting to establish a unicast connection with the first device; based on the judgment result that the security mechanism of the second device does not match the security mechanism supported by the first device, determine that the security mechanism of the second device is different from the security mechanism supported by the first device do not match; or based on the judgment result that the message structure of the first message is wrong, it is determined that the message structure of the first message is wrong.
  • the first MAC address is a MAC address
  • the second message carries the first MAC address, including: the first MAC address is determined by the destination MAC address field of the second message bearer.
  • the second message carries the address identifier and the error identifier, including: the address identifier and the 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 the error identifier are carried in the Application Extension field of the DSA message frame of the second message.
  • the first MAC address is multiple MAC addresses
  • the second message also includes a dedicated application identifier, which is used to indicate that the unicast connection is abnormally established, and the dedicated application identifier
  • the application identification AID field carried in 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 identification.
  • the second message carries the first MAC address, address identifier and error identifier, including: the first MAC address, address identifier and error identifier are carried in the header extension field Header in the dedicated service announcement DSA message frame of the second message Extension field; or the first MAC address, address identifier and error identifier are carried in the Application Extension field of the DSA message frame of the second message.
  • the address identifier of the second device is carried by at least one of the DSA identifier DSA Identifier field and the Content Count field in the dedicated service announcement DSA message frame of 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.
  • the second message is sent by the network layer or the application layer of the first device.
  • the present application provides a device for processing an abnormality in establishing a unicast connection, the device comprising: a sending unit, configured to send a first message to the first device, and the first message is used to request the first device to communicate with the first device
  • the two devices establish a unicast connection, and the first message carries the first media access control MAC address, first address identifier and security mechanism of the second device
  • the receiving unit is configured to receive the second message sent by the first device, and the second message carrying at least one MAC address, at least one address identifier and an error identifier, where the error identifier is used to indicate the cause of the abnormal establishment of the unicast connection
  • the processing unit is configured to determine the unicast connection between the second device and the first device according to the second message Create an exception; the processing unit is also used to perform exception handling operations according to the error identifier.
  • the processing unit is specifically configured to: reselect the first MAC address when the error flag indicates that the first MAC address conflicts.
  • the processing unit is specifically configured to: reselect the security mechanism of the second device 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 processing unit is specifically configured to: recheck the message structure of the first message when the error identifier indicates that the message structure of the first message is wrong.
  • the processing unit is specifically configured to: determine that the establishment of the unicast connection 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.
  • the second message carries at least one MAC address, at least one address identifier and 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 error identifier are carried by the second The Header Extension field in the DSA message frame of the dedicated service announcement of the message, or at least one address identifier and error identifier carried in the Application Extension field in the DSA message frame of the second message.
  • the second message also includes a dedicated application identifier, which is used to indicate that the unicast connection is abnormally established, and the dedicated application identifier is carried in the application identifier AID field in the dedicated short message DSM message frame of the second message; the processing unit specifically Used for: when the content carried in the destination MAC address field of the second message includes the conversion 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, determine the second The unicast connection between the device and the first device is abnormal.
  • the second message carries at least one MAC address, at least one address identifier and error identifier, including: at least one MAC address, at least one address identifier and error identifier carried in the dedicated service announcement DSA message frame of the second message Header Extension field; or at least one MAC address, at least one address identifier and error identifier carried in the Application Extension field of the DSA message frame of the second message.
  • the first address identifier is carried by at least one of the DSA identifier DSA Identifier field and the Content Count field in the dedicated service announcement DSA message frame of 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.
  • the present application provides a device, which includes a processor and a memory, wherein the memory is used to store program instructions; the processor invokes the program instructions in the memory, so that the device executes the first aspect or the first aspect.
  • a device which includes a processor and a memory, wherein the memory is used to store program instructions; the processor invokes the program instructions in the memory, so that the device executes the first aspect or the first aspect.
  • the present application provides a device, which includes a processor and a memory, wherein the memory is used to store program instructions; the processor invokes the program instructions in the memory, so that the device executes the second aspect or the first A method in any possible implementation of the two aspects.
  • the present application provides a computer-readable storage medium, including computer instructions.
  • the computer instructions are executed by a processor, the above-mentioned first aspect or any possible implementation of the first aspect can be realized. method.
  • the present application provides a computer-readable storage medium, including computer instructions.
  • the computer instructions are executed by a processor, the above-mentioned second aspect or any possible implementation of the second aspect can be realized. method.
  • the present application provides a computer program product.
  • the computer program product When the computer program product is executed by a processor, the method in the above-mentioned first aspect or any possible embodiment of the first aspect is implemented.
  • the computer program product can be, for example, a software installation package. If the method provided by any possible design of the first aspect above needs to be used, the computer program product can be downloaded and executed on the processor. , so as to implement the first aspect or the method in any possible embodiment of the first aspect.
  • the present application provides a computer program product.
  • the computer program product When the computer program product is executed by a processor, the method in the above-mentioned second aspect or any possible embodiment of the second aspect is implemented.
  • the computer program product may be, for example, a software installation package. If the method provided by any possible design of the second aspect above needs to be used, the computer program product may be downloaded and executed on the processor. , so as to implement the second aspect or the method in any possible embodiment of the second aspect.
  • the present application provides a vehicle, including the device according to the third or fifth aspect above, or the device according to any possible implementation of the third or fifth aspect above, or including the device according to the fourth or fifth aspect above.
  • the present application provides a unicast connection establishment exception processing system, including a first device and a second device, wherein the first device is the device in the third or fifth aspect above, or the third or fifth device in the above
  • the first device is the device in the third or fifth aspect above, or the third or fifth device in the above
  • the second device is the apparatus of the fourth or sixth aspect above, or the device of any possible implementation manner of the fourth or sixth aspect above.
  • Fig. 1 is a structure diagram of a communication system
  • Fig. 2 is a schematic diagram of a protocol stack of an LTE-based Internet of Vehicles wireless communication technology
  • FIG. 3 is a schematic diagram of a scenario of establishing a unicast connection
  • FIG. 4 is a flow chart of a method for handling exceptions in unicast connection establishment provided by an embodiment of the present application
  • FIG. 5 is a flow chart of another method for handling exceptions in unicast connection establishment provided by an embodiment of the present application.
  • FIG. 6A is a schematic diagram of carrying an address identifier in a first message according to an embodiment of the present application.
  • FIG. 6B is a schematic diagram of carrying an address identifier in a first message according to an embodiment of the present application.
  • Fig. 7A is a schematic diagram of a second message provided by the embodiment of the present application.
  • Fig. 7B is a schematic diagram of a second message provided by the embodiment of the present application.
  • FIG. 8 is a flow chart of another method for handling exceptions in unicast connection establishment provided by an embodiment of the present application.
  • Fig. 9A is a schematic diagram of a second message provided by the embodiment of the present application.
  • Fig. 9B is a schematic diagram of a second message provided by the embodiment of the present application.
  • FIG. 10 is a schematic diagram of a high-speed charging scenario provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a vehicle-to-vehicle communication scenario provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of a functional structure of a communication device provided in this embodiment of the present application.
  • FIG. 13 is a schematic structural diagram of a communication device provided in this embodiment of the present application.
  • FIG. 1 is a schematic diagram of a communication system architecture, wherein the communication system includes a roadside device and at least one terminal, wherein the roadside device and the terminal, and the terminal and the terminal can communicate in a wireless manner.
  • the roadside device can be a roadside unit (Road Side Unit, RSU), or a multi-access edge computing (Multi-Access Edge Computing, MEC) with wireless communication functions, smart gas stations, smart signal lights, etc.
  • the terminal can be a vehicle-mounted Unit (On Board Unit, OBU), portable mobile device (such as mobile phone, tablet, etc.), or other sensors or devices such as components and chips in the portable mobile device that can communicate with roadside devices and other terminals, the embodiment of this application Not specifically limited.
  • At least one terminal may include terminal 1 and terminal 2, the roadside device may respectively establish a unicast connection with terminal 1 and terminal 2, and terminal 1 and terminal 2 may also establish a unicast connection.
  • the communication between the roadside device and the terminal, or between terminals can use cellular communication technology, such as 2G cellular communication, such as global system for mobile communication (GSM) , general packet radio service (GPRS); or 3G cellular communication, such as wideband code division multiple access (WCDMA), time division-synchronous code division multiple access (time division-synchronous code division multiple access, TS-SCDMA), code division multiple access (code division multiple access, CDMA), or 4G cellular communication, such as long term evolution (long term evolution, LTE), LTE-vehicle networking wireless communication technology (Vehicle to Everything , V2X) PC5 communication, or 5G cellular communication, such as New Radio (NR)-V2X PC5 communication, or other evolved cellular communication technologies.
  • 2G cellular communication such as global system for mobile communication (GSM) , general packet radio service (GPRS); or 3G cellular communication, such as wideband code division multiple access (WCDMA), time division-synchronous code division multiple access (time division-synchronous code division multiple access,
  • the wireless communication system may also utilize non-cellular communication technologies, such as Wi-Fi and wireless local area network (wireless local area network, WLAN) communication.
  • the communication between the above devices can also use infrared link, bluetooth or ZigBee for direct communication.
  • other wireless protocols may be used for communication between the above devices, such as various vehicle communication systems, for example, the system may include one or more dedicated short range communications (DSRC) devices, these devices It may include public and/or private data communication between vehicles and/or roadside stations, which is not specifically limited in this application.
  • DSRC dedicated short range communications
  • FIG. 1 is only an exemplary architecture diagram, but does not limit the number of network elements included in the communication system shown in FIG. 1 .
  • FIG. 1 may also include other functional entities.
  • the method provided in the embodiment of the present application can be applied to the communication system shown in FIG. 1 , and of course the method provided in the embodiment of the present application can also be applied to other communication systems, which is not limited in the embodiment of the present application.
  • FIG. 2 provides a schematic diagram of a protocol stack of an LTE-based Internet of Vehicles wireless communication technology.
  • the protocol stack includes application layer, network layer and access layer.
  • the application layer is mainly used for processing application layer business logic of application services, for example, generating instant messages, unicast service announcements, and the like.
  • the application layer includes user applications and a message layer.
  • the message layer is located inside the application layer.
  • the message layer connects to the data sublayer downwards and supports specific user applications upwards.
  • the message layer can support the transmission of various data defined by the network layer of the LTE-based Internet of Vehicles wireless communication technology.
  • the interaction between the message layer and the data sublayer inside the network layer is realized through cross-layer primitives (also called operation primitives or service primitives).
  • the network layer includes a management sublayer and a data sublayer.
  • the management sublayer is used to complete functions such as system configuration and maintenance, such as the selection of MAC addresses and the selection of security mechanisms.
  • the management sublayer can be a dedicated management entity (Dedicated Management Entity) , DME), DME provides a management interface for all data sublayer entities.
  • DME Dedicated Management Entity
  • the data sublayer not only transmits the data flow between application layers, but also transmits the data flow between management entities of different devices or between management entities and applications.
  • the data sublayer includes Adaptation Layer, Dedicated Short Message Protocol (DSMP) layer, etc. Among them, the DSMP layer is used for data interaction with different applications, and the adaptation layer is used to provide access to the underlying layer.
  • DSMP Dedicated Short Message Protocol
  • the transmission adaptation function between the layer and the upper layer protocol stack distinguishes the underlying interface used by the data packet to be sent (for example, DSMP data packet, IP (Internet Protocol) data packet, etc.) and passes the corresponding data packet to the interface
  • the function of the adaptation layer also includes the generation/change/maintenance of the source layer 2 identifier, the mapping between the unicast/multicast address and the layer 2 identifier, etc.
  • the access layer supports a cellular communication interface (for example, a Uu port) and/or a direct connection communication interface (for example, a PC5 port), wherein the PC5 port and the Uu port can support different radio access technologies (Radio Access Technology, RAT),
  • a RAT may include LTE technology or NR technology.
  • the roadside device takes RSU as an example, and the terminal takes OBU as an example.
  • At least one terminal includes OBU1, OBU2 and OBU3.
  • the RSU can communicate with OBU1, OBU2 and OBU3 respectively, wherein the MAC addresses of OBU1, OBU2 and OBU3 are all It is used for random selection within the same address field.
  • the RSU periodically broadcasts unicast service announcements carrying specified application services. Since OBU1, OBU2, and OBU3 are all within the broadcast range of the RSU, OBU1, OBU2, and OBU3 can all receive the unicast service announcements from the RSU.
  • OBU1 After OBU1, OBU2, and OBU3 analyze their own business requirements, only OBU1 responds to the unicast service announcement sent by RSU, that is, OBU1 sends a response message to RSU, and the response message carries the MAC address of OBU1 (for example, MAC1), and RSU receives After receiving the response message sent by OBU1, it is found that the MAC address of OBU1 is the same as that of OBU3 or that it does not support the security mechanism provided by OBU1, etc., resulting in abnormalities in the establishment of unicast connections, which may cause confusion in the communication process and affect the normal execution of services. .
  • OBU1 After receiving the response message sent by OBU1, it is found that the MAC address of OBU1 is the same as that of OBU3 or that it does not support the security mechanism provided by OBU1, etc., resulting in abnormalities in the establishment of unicast connections, which may cause confusion in the communication process and affect the normal execution of services. .
  • the embodiment of the present application proposes a method for handling abnormality of unicast connection establishment to solve the problem of abnormal unicast establishment caused by MAC address conflicts during the unicast establishment process and mismatching security mechanisms of both communication parties. . Therefore, the efficiency of establishing a unicast connection is improved, and the normal execution of the unicast service between the communication parties is ensured.
  • FIG. 4 is a method for handling exceptions in unicast connection establishment provided by an embodiment of the present application, which is applied to a system for handling exceptions in unicast connection establishments.
  • the system includes a first device and a second device, wherein the first device is is the sender of the above-mentioned unicast service announcement, and the second device is the above-mentioned responder.
  • the method includes but is not limited to the following steps:
  • S101 The second device sends a first message to the first device.
  • the first device first sends a broadcast message to the second device, and the broadcast message may be a unicast service announcement for indicating a preset application service.
  • the second device after receiving the broadcast message, determines that it needs to establish a unicast connection based on the preset application service with the first device based on its own business needs, and then the second device sends a message to the first device.
  • the device sends a first message. It can be understood that the first message is a response message to the broadcast message.
  • the second device may be one or more devices.
  • m is a positive integer greater than or equal to 1.
  • the second device is one device, that is, device 1.
  • the distance between the first device and the second device please refer to the description of the embodiment in Figure 5 below;
  • the second device is a plurality of devices, specifically including device 1, device 2, ..., device m, in this case, the first device
  • the interaction process with each device refer to the description of the embodiment in FIG. 8 below, and details are not repeated here.
  • 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 of the second device, the address identifier of the second device, and the security mechanism of the second device are determined by the second device.
  • the MAC address of the second device is an address used by the second device to communicate with other devices in the network.
  • the MAC address of the second device may be 24 bits, which is selected by the second device in an autonomous address selection manner.
  • the security mechanism of the second device is a 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, a security mechanism based on a symmetric key, a security mechanism based on a certificate, and the like.
  • a security mechanism based on a symmetric key means that both communicating parties must use the same key to encrypt and decrypt messages or data. It should be noted that the above-mentioned security mechanism has been widely applied in the field of communication, and will not be repeated here.
  • the address identifier of the second device is used to identify the second device.
  • the address identifier of the second device may be a randomly generated random number, or a device identifier of the second device, or a character string calculated based on the MAC address of the second device and the device identifier of the second device, etc., here Not specifically limited.
  • the first device determines, according to the first message, that the establishment of the unicast connection between the second device and the first device is abnormal.
  • the first device receives the first message sent by the second device, and according to the first message, determines that the establishment of the unicast connection between the second device and the first device is abnormal, specifically including:
  • the MAC address of the second device is the same as the MAC address of the third device, which means that the second device has a MAC address conflict; the security mechanism of the second device does not match the security mechanism supported by the first device, which means that the second device and the first device Communication will be impossible due to different information encryption and decryption methods; the message structure error of the first message sent by the second device indicates that the first device cannot parse the first message sent by the second device. It should be noted that the embodiment of the present application does not limit the conditions for determining that the unicast establishment between the second device and the first device is abnormal to only the conditions listed above, and may also be other conditions that cause the establishment of the unicast connection to fail.
  • the second device when the second device is one device, if it is determined that the establishment of the unicast connection between the second device and the first device is abnormal, the second device may be called an abnormal device.
  • the second device is multiple devices, whether the unicast connection between each device and the first device is abnormal can be judged according to the above method, so that it can be determined that each device in the multiple devices is connected to the first device by unicast An exception is established, each of the plurality of devices may be referred to as an exception device.
  • S103 The first device sends a second message to the second device.
  • the second message carries the MAC address of the abnormal device, the address identifier, and the error identifier, where the error identifier is used to indicate the cause of the abnormal establishment of the unicast connection corresponding to the abnormal device.
  • the error identifier may also be referred to as an error code.
  • the value of the error flag when the value of the error flag is the first value, it indicates that the abnormal device has a MAC address conflict; when the value of the error flag is the second value, it indicates that the security mechanism of the abnormal device is different from the security mechanism supported by the first device. match; when the value of the error flag is the third value, it indicates that the message format of the first message sent by the abnormal device is wrong.
  • the value of the error flag when the value of the error flag is the fourth value, it indicates that the abnormal device has a MAC address conflict and the security mechanism of the abnormal device does not match the security mechanism supported by the first device.
  • the error identification can also be represented by bits, for example, use 001 to indicate that the MAC address conflict of the abnormal device occurs, use 010 to indicate that the security mechanism of the abnormal device does not match the security mechanism supported by the first device, and use 100 Indicates that the message format of the first message sent by the abnormal device is wrong, and 011 indicates that the abnormal device has a MAC address conflict and the security mechanism of the abnormal device does not match the security mechanism supported by the first device, which is not specifically limited here.
  • the MAC address carried in the second message is one.
  • S102 and S103 can be performed by the network layer or application layer of the first device.
  • the network layer is the network layer in the LTE-based Internet of Vehicles wireless communication technology.
  • the application layer is the application layer in the LTE-based Internet of Vehicles wireless communication technology.
  • the relevant description of the application layer in FIG. 2 which will not be repeated here.
  • S102 and S103 may be performed by the network layer of the first device, for example, may be performed by a 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 establishment of the unicast connection between the second device and the first device is abnormal according to the first message, and The sending of the second message is triggered by the DME of the first device.
  • S102 and S103 may also be performed by the application layer of the first device.
  • the network layer of the first device receives the first message sent by the second device
  • the network layer of the first device sends data such as the MAC address, address identifier, and security mechanism in the first message to the
  • the application layer of the first device determines that the establishment of the unicast connection between the second device and the first device is abnormal according to the received data, and the application layer of the first device triggers the sending of the second message.
  • the second device determines, according to the second message, that the establishment of the unicast connection between itself and the first device is abnormal, and performs an exception handling operation.
  • the number of abnormal devices when the number of abnormal devices is one, it means that the MAC address of the abnormal device carried in the second message is one.
  • the MAC address of the abnormal device is the MAC address of the second device and the abnormal The address identifier of the device is the address identifier of the second device, indicating that the second device is the abnormal device, so it is determined that the establishment of the unicast connection between the second device and the first device is abnormal, and the second device performs an exception handling operation.
  • the second device determines that the second message is a unicast establishment In the case of an abnormal message, if it is further judged that the multiple MAC addresses carried in the second message include the MAC address of the second device and the multiple address identifiers carried in the second message include the address identifier of the second device, then it is determined that the second device If the establishment of the unicast connection with the first device is abnormal, the second device performs an exception handling operation.
  • the second device performs an exception handling operation.
  • the execution of the exception handling operation may be performed by the network layer or the application layer of the second device, which is not specifically limited in the embodiment of the present application.
  • the sender can effectively distinguish different responders with the same MAC address based on the address identifier.
  • the sender can carry The responder's address identification, error identification and other content messages are used to inform the responder of the cause of the abnormal establishment of the unicast connection, so that the responder can handle it accordingly, which can effectively solve the problem of abnormal establishment of the unicast connection between the sender and the responder.
  • the efficiency of establishing the unicast connection is improved, and the normal execution of the business between the communication parties is ensured.
  • FIG. 5 is a method for handling exceptions in unicast connection establishment provided by an embodiment of the present application.
  • the second device in FIG. 5 is one device.
  • the embodiment in FIG. 5 may be independent from the embodiment in FIG. 4 above, or may be a supplement to the embodiment in FIG. 4 above.
  • the method includes but is not limited to the following steps:
  • S201 The second device sends a first message to the first device.
  • the second device may send the first message to the first device in response to the unicast service announcement sent by 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 MAC address, address identifier and security mechanism of the second device.
  • the bearing position of the MAC address, address identifier and security mechanism of the second device in the first message will be specifically introduced below.
  • the address identifier of the second device mainly has the following two bearing modes in the first message:
  • the first type carried by at least one of the dedicated service announcement identification field and the content count field in the first message
  • the address identifier of the second device can be determined by the DSA identifier (DSA Identifier) field and the content count (Content Count) field in the dedicated service announcement (Dedicated Services Advertisement, DSA) message frame of the first message.
  • DSA DSA identifier
  • Content count Content count
  • DSA dedicated Services Advertisement
  • FIG. 6A is a schematic diagram of carrying an address identifier in a first message according to an embodiment of the present application.
  • the DSA message frame format of the first message is shown, and the DSA message frame includes a DSA header field and an application information field.
  • the DSA header field specifically includes a dedicated service announcement version number (DSA Version) field, a DSA header extension field indication (DSA Header Extension Indicator) field, a reserved (Reserved) field, a DSA identifier (DSA Identifier) field, a content Count (Content Count) field and header extension domain (Header Extension) field.
  • DSA Version a dedicated service announcement version number
  • DSA Header Extension Indicator DSA header extension field indication
  • reserved Reserve
  • DSA identifier DSA identifier
  • Content Count Content Count
  • Header Extension header extension domain
  • the value of the DSA Header Extension Indicator field is 1, which means that the Header Extension field appears, and the value is 0, which means that the Header Extension field does not appear;
  • the Reserved field can be used for function extension;
  • the DSA Identifier field is used to indicate the uniqueness of DSA;
  • Content Count The field can be used to identify whether it is a duplicate of the previous DSA when the DSA ID is the same; the Header Extension field can be reserved for other information.
  • the application information field specifically includes an application information count field (Application Info Count) field, an application identification (AID, Application Identifier) field and an application extension field (Application Extension) field.
  • Application Info Count field is used to indicate the number of application information following this field
  • AID field is used to indicate the type of application service
  • Application Extension field is used to indicate relevant information of the application service.
  • the address identifier of the second device may be carried in the DSA Identifier field or the Content Count field in FIG. 6A.
  • the address identifier of the second device is a 4-bit device identifier, it may be filled into the DSA Identifier field or the Content Count field in the DSA message frame of the first message.
  • the address identifier of the second device may be jointly carried by both the DSA Identifier field and the Content Count field in FIG. 6A.
  • the address identifier of the second device is an 8-bit random number, which can be filled into the DSA Identifier field and the Content Count field in the DSA message frame of the first message.
  • the second type carried by the header extension field in the first message
  • the address identifier of the second device may be carried by the Header Extension field in the DSA message frame of the first message.
  • FIG. 6B is a schematic diagram of carrying an address identifier in a first message according to an embodiment of the present application.
  • the Header Extension field further includes the information element count (Information Element Count) field and at least one information element (Information Elements), and an information element can pass an Element ID field, a length length field and a content content field representation.
  • the address identifier of the second device may be carried by the Header Extension field.
  • the address identifier of the second device can be carried in the Header Extension field through the newly defined Element ID.
  • an Element ID field is defined to indicate the function identifier for detecting address conflicts
  • the content field is used to indicate the address of the second device.
  • the identifier and length fields are used to indicate the length of the address identifier of the second device.
  • 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 (Source Layer 2 ID) of the first message;
  • the security mechanism may also be carried in the header extension field (Header Extension) field in the DSA message frame of the first message, which will not be repeated here.
  • the second device may further store a mapping relationship between the MAC address of the second device and the address identifier of the second device.
  • the first device determines, according to the first message, that the establishment of the unicast connection between the second device and the first device is abnormal.
  • the process for the first device to determine that the unicast connection establishment between the second device and the first device is abnormal according to the first message may be: judging whether the first message sent by the second device can be correctly parsed, and comparing the Whether the security mechanism of the first device matches the security mechanism supported by the first device and whether the MAC address of the third device is the same as the MAC address of the second device, etc., where the third device is a request to establish a unicast connection with the first device device, the third device is different from the second device. If the first message cannot be parsed, it means that the message structure of the first message is wrong, and it is determined that the establishment of the unicast connection between the second device and the first device is abnormal.
  • the security mechanism of the second device does not match the security mechanism supported by the first device, it is determined that the establishment of the unicast connection between the second device and the first device is abnormal. If it is detected that the MAC address of the third device is the same as the MAC address of the second device, it means that the MAC address of the second device conflicts, and it is determined that the establishment of the unicast connection between the second device and the first device is abnormal. In some possible embodiments, various combinations of the failure of the first message to be parsed, the MAC address conflict of the second device, and the mismatch between the security mechanism of the second device and the security mechanism supported by the first device may also occur. It can be determined that the establishment of the unicast connection between the second device and the first device is abnormal.
  • 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 does not conflict, and the security mechanism of the second device is the same as that of the first device. If the supported security mechanisms match, the first device and the second device successfully establish a unicast connection.
  • S203 The first device sends a second message to the second device.
  • the first device when it is determined that the unicast connection between the second device and the first device is abnormally established, the first device sends a second message to the second device, and the second message carries the second device's MAC address, An address identifier and an error identifier, wherein the error identifier is used to indicate the cause of the abnormal establishment of the unicast connection.
  • 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 target layer 2 identification (Destination Layer2 ID) of the second message.
  • FIG. 7A is a schematic diagram of a second message provided by an embodiment of the present application.
  • the source MAC address field of the second message is used to carry 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, and the destination MAC address field of the second message is used for
  • the MAC address of the second device is carried, that is, the target layer 2 identifier of the second message is the MAC address of the second device, and the MAC payload field of the second message can be used to carry a dedicated short message (Dedicated Short Message, DSM) message frame.
  • DSM dedicated Short Message
  • the DSM message frame includes a dedicated short message protocol version number (DSMP Version) field, a DSMP extension domain indication (DSMP Extension Indicator) field, a reserved (Reserved) field, an extension domain (Extension) field, an application identification (AID) field, and a length ( Length) field and data (Data) field.
  • DSMP Version a dedicated short message protocol version number
  • DSMP Extension Indicator a DSMP Extension Indicator
  • Reserve reserved
  • Extension Extension
  • Extension extension domain
  • AID application identification
  • Data data
  • the value of the DSMP Extension Indicator field is 1, which means that the following Extension field appears, and the value of 0 means that the Extension field does not appear;
  • the Reserved field can be used for function extension;
  • the AID field is used to fill in the application identifier to distinguish different applications;
  • the Length field is used to indicate the byte length of the application layer data entity;
  • the Data field can be used to carry the data entity of the application layer or the management sublayer.
  • the Data field in the DSM message frame is used to carry the DSA message frame. For details of each field in the DSA message frame, refer to the description of the DSA message frame in FIG. 6A .
  • the address identifier of the second device and the error identifier of the second device are carried by the Application Extension field in the DSA message frame of the second message.
  • a Data field may be newly defined in the Application Extension field to carry the address identifier and error identifier of the second device.
  • FIG. 7B is a schematic diagram of a second message provided by an embodiment of the present application.
  • the source MAC address field of the second message is used to carry the MAC address of the first device
  • the destination MAC address field of the second message is used to carry the MAC address of the second device
  • the MAC payload field is used to carry the DSM message Frame
  • the Data field in the DSM message frame is used to carry the DSA message frame, wherein, for each field in the DSM message frame, please refer to the relevant description in Figure 7A, for each field in the DSA message frame, please refer to the relevant description in Figure 6A , which will not be repeated here.
  • the address identifier of the second device and the error identifier of the second device are carried by the Header Extension field in the DSA message frame of the second message.
  • a new information element is defined in the Header Extension field, and the information element is represented by the Element ID field, the length field, and the content field, where the Element ID field is used to indicate the abnormality of unicast establishment, and the length field is used to indicate the content field
  • the Element ID field is used to indicate the abnormality of unicast establishment
  • the length field is used to indicate the content field
  • the length of the carried content, the content field is used to carry the address identifier and error identifier of the second device.
  • the second device determines that the establishment of the unicast connection between itself and the first device is abnormal according to the second message, and performs an exception handling operation according to the error identifier carried in the second message.
  • the second device receives the second message, 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, and 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, so the second device determines that The establishment of the unicast connection between the first device is abnormal.
  • the second device after determining that the establishment of the unicast connection between itself and the first device is abnormal, the second device performs an exception handling operation according to the error identifier carried in the second message.
  • the second device performs an exception handling operation according to the error identifier carried in the second message, specifically: when the error identifier indicates that the MAC address of the second device conflicts, the second device reselects its own MAC address.
  • the address identifier of the second device is obtained based on the MAC address of the second device, since the MAC address of the second device changes, the address identifier of the second device also needs to be changed. After re-selecting the own MAC address, the own address identification can also be re-determined.
  • the second device performs an exception handling operation according to the error identifier carried in 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 restarts Choose your own security mechanism.
  • the second device performs an exception handling operation according to the error identifier carried in the second message. It may also be: 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 first message sent by the second device. A message structure for a message. In some possible embodiments, when the error flag 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. The embodiment of the present application does not specifically limit the exception handling operation performed by the second device.
  • the second device may re-request the first device to establish a unicast connection with the second device.
  • the responding party can be identified based on the MAC address and address identifier of the responding party, based on the information carried in the message, and based on the error identification carried in the message, the responding party can be guided to effectively resolve MAC address conflicts and security mechanisms.
  • the problem of abnormal establishment of the unicast connection between the sender and the responder caused by the mismatch and other problems is conducive to improving the efficiency of establishing the unicast connection and ensuring the normal execution of the unicast service between the communication parties.
  • FIG. 8 is another method for handling exceptions in establishing a unicast connection provided by an embodiment of the present application.
  • the embodiment in FIG. 8 may be independent from the above-mentioned embodiments in FIG. 4 and FIG. 5 , and may also be a supplement to the above-mentioned embodiment in FIG. 4 .
  • the method includes but is not limited to the following steps:
  • S301 Multiple devices send a first message to a first device.
  • the multiple devices sending the first message to the first device may be: each of the multiple devices sends a first message to the first device, that is, the number of first messages is equal to the number of The number of devices is the same.
  • the first message is used to request the first device to establish a unicast connection with the device.
  • the multiple devices may be device 1, device 2, ..., device m in FIG. 8 , where m is a positive integer greater than 1.
  • the first message sent by device 1 to the first device is used to request the first device to establish a unicast connection with device 1, and the first message sent by device 1 carries The MAC address, address identifier and security mechanism of device 1 are shown.
  • the MAC address, address identifier, and security mechanism of the device 1 are carried in the first message, reference may be made to the related description of the above-mentioned embodiment S201 in FIG. 5 , which will not be repeated here.
  • the first device determines, according to the first message sent by the multiple devices, that the establishment of the unicast connection between the multiple devices and the first device is abnormal.
  • the first device determines, according to the first message sent by each of the multiple devices, that each of the multiple devices has an abnormal establishment of a unicast connection with the first device.
  • the first device determines that the unicast connection between device 1 and the first device is abnormal according to the first message sent by device 1.
  • the specific process For details, reference may be made to relevant descriptions of S102 in the embodiment of FIG. 4 or S202 in the embodiment of FIG. 5 , and details are not repeated here.
  • S303 The first device sends a second message to multiple devices.
  • the second message carries the MAC addresses, address identifiers, and error identifiers of the above-mentioned multiple devices (that is, m devices), and the error identifier is used to indicate the reason why the unicast connection establishment of the corresponding device is abnormal.
  • the second message may be a broadcast message.
  • the second message further includes a dedicated application identifier, which is used to indicate that the unicast connection is abnormally established, and the dedicated application identifier is carried by the AID field in the 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.
  • the bearing positions of the MAC addresses, address identifiers and error identifiers of multiple devices in the second message mainly have the following two modes:
  • FIG. 9A is a schematic diagram of a second message provided by an embodiment of the present application.
  • the source MAC address field of the second message is used to carry the MAC address of the first device
  • the destination MAC address field of the second message is used to carry the converted value of the dedicated application identifier
  • the MAC payload field is used to carry the DSM message frame
  • the AID field in the DSM message frame is used to carry the dedicated application identifier
  • the Data field in the DSM message frame is used to carry the DSA message frame.
  • FIG. 6A which will not be repeated here.
  • 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.
  • a Data field can be newly defined in the Application Extension field to carry the MAC addresses, address identifiers, and error identifiers of multiple devices.
  • it can also carry the statistical value m of the device.
  • a plurality of devices include device 1, ..., device m.
  • FIG. 9B is a schematic diagram of a second message provided by an embodiment of the present application.
  • the source MAC address field of the second message is used to carry the MAC address of the first device
  • the MAC payload field of the second message is used to carry the DSM message frame
  • the destination MAC address field of the second message is used to carry the dedicated application
  • the conversion value of the identifier, the AID field in the DSM message frame of the second message is used to carry the dedicated application identifier
  • the Data field in the DSM message frame is used to carry the DSA message frame, where each field in the DSM message frame can refer to the figure
  • FIG. 6A for details.
  • 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.
  • a new information element is defined in the Header Extension field, and the information element is represented by the Element ID field, the length field, and the content field.
  • the Element ID field can be used to indicate the abnormality of unicast establishment, and the length field is used to indicate the content The length of the content carried by the field.
  • the content field is used to carry the MAC addresses, address identifiers, and error identifiers of multiple devices. In addition, it can also carry the statistical value m of the device.
  • the plurality of devices include device 1, ..., device m.
  • the first message may also send a corresponding second message to each of the multiple devices, and each The second message corresponding to the device only carries the MAC address, address identifier, and error identifier of the device.
  • the second message may be in the form shown in FIG. 7A or FIG. 7B.
  • Each of the multiple devices determines that the establishment of the unicast connection between itself and the first device is abnormal according to the second message, and performs an exception handling operation according to the corresponding error identifier.
  • device 1 After device 1 receives the second message from the first device, it first determines that the content carried in the destination MAC address field of the second message includes the conversion value of the 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 judges whether the MAC address of device 1 is included in the multiple MAC addresses carried in the second message and whether the address identifier of device 1 is included in the multiple address identifiers carried in the second message. When the MAC addresses include the MAC address of the device 1 and the multiple address identifiers carried in the second message include the address identifiers of the device 1, the device 1 determines that the establishment of the unicast connection between itself and the first device is abnormal.
  • mapping relationship among 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 The mapping relationship between the address identifier and the error identifier obtains the error identifier corresponding to the device 1 from the second message, and the device 1 executes an exception handling operation according to its corresponding error identifier. It should be noted that, for details about the process of the device 1 executing the exception handling operation, reference may be made to the related description of the second device executing the exception handling operation in S204 in the embodiment of FIG. 5 , which will not be repeated here.
  • an address identifier and an error identifier for the processing procedure of the device 1, refer to the related description of S204 in the embodiment of FIG. 5 for details.
  • the sender can effectively distinguish different responders with the same MAC address based on the address identifier.
  • Fig. 10 is a schematic diagram of a high-speed charging scenario.
  • RSU is equivalent to the first device in FIG. 5 above
  • OBU1 is equivalent to the second device in FIG. 5 above
  • OBU2 is equivalent to the third device in FIG. 5 above.
  • the MAC address of OBU2 is the same as the MAC address of OBU1, both are MAC1
  • the address identifier of OBU1 is address identifier 1
  • the security mechanism of OBU1 is security mechanism 1.
  • OBU2 enters the broadcast range of the RSU before OBU1.
  • OBU2 establishes a unicast connection with the RSU to complete a near-field payment.
  • the RSU stores the MAC address of OBU2 (That is, MAC1).
  • OBU1 enters the broadcast range of the RSU, responds to the received unicast service announcement, and sends the first message to the RSU to request the RSU to establish a unicast connection with OBU1.
  • the first message carries the information of OBU1 MAC1, address identification 1 and security mechanism 1.
  • the RSU detects that MAC1 is identical to the MAC address of OBU1 in the stored MAC address list, that is, the MAC address of OBU1 conflicts, so it is determined that the error identifier of OBU1 is error identifier 1, which is used to indicate that the MAC address has conflict, and trigger the RSU to send a second message, the second message carries the MAC1 of the OBU1, the address ID 1 and the error ID 1.
  • 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, that is, it determines that the establishment of the unicast connection between OBU1 and the RSU is abnormal.
  • the cause of the abnormal establishment of the unicast connection is that the MAC address conflicts. Therefore, OBU1 reselects its own MAC address, or reselects its own MAC address and address identification, and then Re-response to unicast service announcements from the RSU, thereby improving the efficiency of unicast connection establishment.
  • FIG. 11 is a schematic diagram of a vehicle-to-vehicle communication scenario.
  • OBU1 may be the device 1 in FIG. 8 above, and OBU2 is equivalent to the first device in FIG. 8 above.
  • the MAC address of OBU1 is MAC1
  • the address identifier of OBU1 is address identifier 1
  • the security mechanism of OBU1 is security mechanism 1.
  • the security mechanism supported by OBU2 is security mechanism 2, and security mechanism 1 is different from security mechanism 2.
  • OBU2 broadcasts a unicast service announcement for traffic service applications.
  • OBU1 is within the broadcast range of OBU2.
  • OBU1 sends a first message to OBU2 in response to the unicast service announcement to request OBU2 to establish a unicast connection with OBU1.
  • the first message carries MAC1, address identifier 1 and security mechanism 1 of OBU1.
  • OBU2 detects that the security mechanism 1 of OBU1 does not match the security mechanism supported by itself (that is, security mechanism 2), and determines that the error identifier of OBU1 is error identifier 2, and the error identifier 2 is used to indicate the security mechanism of OBU1 It does not match the security mechanism supported by OBU2, and triggers OBU2 to send a second message.
  • the second message is a broadcast message, and the second message carries multiple MAC addresses, multiple address identifiers and at least one error identifier.
  • OBU1 detects that the content carried in the destination MAC address field of the second message is the conversion value of the dedicated application identifier, which is used to indicate that the unicast connection is abnormally established.
  • the multiple MAC addresses include MAC1 of OBU1 and the multiple address identifiers include address identifier 1 of OBU1.
  • OBU1 determines that the unicast connection between itself and OBU2 is abnormal. Further, the error ID corresponding to itself is obtained from the second message as error ID 2, and the reason for obtaining the unicast connection establishment exception according to error ID 2 is that the security mechanism does not match. Therefore, OBU1 reselects its own security mechanism, and then restarts Responding to the unicast service announcement from OBU2 improves the efficiency of unicast connection establishment and ensures the normal execution of services between the communication parties.
  • FIG. 12 is a schematic functional structure diagram of a communication device provided by an embodiment of the present application.
  • the communication device 30 includes a sending unit 310 , a processing unit 312 and a receiving unit 314 .
  • the communication device 30 may be implemented by hardware, software, or a combination of software and hardware.
  • the communication device 30 may be the first device in the foregoing FIG. 4 , FIG. 5 or FIG. 8 .
  • the receiving unit 314 is configured 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 first media access control of the second device MAC address, address identification and security mechanism;
  • the processing unit 312 is used to determine that the unicast connection between the second device and the first device is abnormal according to the first message;
  • the sending unit 310 is used to send the second message to the second device, the first The second message carries the first MAC address, an address identifier and an error identifier, and the error identifier is used to indicate the reason for the abnormal establishment of the unicast connection.
  • the communication device 30 may be used to implement the method on the first device side described in the embodiment of FIG. 4 .
  • the receiving unit 314 and the processing unit 312 may be used to perform S102
  • the sending unit 310 may be used to perform S103.
  • Each functional module of the communication device 30 may also be used to implement the method on the first device side described in the embodiment of FIG. 5 or FIG. 8 , and for the sake of brevity of the description, details are not repeated here.
  • the communication device 30 may be the second device in FIG. 4 or FIG. 5 above, or any one of the multiple devices shown in FIG. 8 above.
  • the sending unit 310 is configured 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 first medium access control MAC of the second device address, a first address identifier and a security mechanism;
  • the receiving unit 314 is configured 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, and the error identifier is used to indicate a unicast connection The cause of the establishment exception;
  • the processing unit 312 is configured to determine, according to the second message, that the establishment of the unicast connection between the second device and the first device is abnormal, and perform an exception handling operation according to the error identifier.
  • the communication device 30 may be used to implement the method on the second device side described in the embodiment of FIG. 4 .
  • the sending unit 310 may be used to execute S101
  • the receiving unit 314 and the processing unit 312 may be used to execute S104.
  • the functional modules of the communication device 30 can also be used to implement the method on the second device side described in the embodiment of FIG. 5 or the methods on the multiple device sides described in the embodiment of FIG. 8 . .
  • each unit in the above embodiment shown in FIG. 12 can be realized by software, hardware, firmware or a combination thereof.
  • the software or firmware includes but is not limited to computer program instructions or codes, and can be executed by a hardware processor.
  • the hardware includes but is not limited to various integrated circuits, such as a central processing unit (CPU, Central Processing Unit), a digital signal processor (DSP, Digital Signal Processor), a field programmable gate array (FPGA, Field Programmable Gate Array) or Application Specific Integrated Circuit (ASIC).
  • CPU central processing unit
  • DSP Digital Signal Processor
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • FIG. 13 is a schematic structural diagram of a communication device provided by an embodiment of the present application.
  • the communication device 32 includes: a processor 321 , a transceiver 322 , a memory 323 and a bus 324 .
  • the processor 321 , the memory 323 and the transceiver 322 communicate through the bus 324 . It should be understood that the present application does not limit the number of processors and memories in the communication device 32 .
  • the communication device 32 may be the first device in the embodiment of FIG. 4, FIG. 5 or FIG. 8, and the first device may be a roadside device, such as a roadside unit (Road Side Unit, RSU) , Multi-Access Edge Computing (MEC), smart gas stations, smart signal lights, etc.
  • RSU roadside unit
  • MEC Multi-Access Edge Computing
  • smart gas stations smart signal lights
  • RSU and MEC a roadside unit
  • RSU Roadside unit
  • MEC Multi-Access Edge Computing
  • the first device can also be a terminal, for example, an on-board unit (On Board Unit, OBU), a portable mobile device (such as a mobile phone, a tablet, etc.), or other sensors or devices with communication functions such as components and chips in the portable mobile device , which is not specifically limited in this embodiment of the present application.
  • OBU On Board Unit
  • portable mobile device such as a mobile phone, a tablet, etc.
  • sensors or devices with communication functions such as components and chips in the portable mobile device , which is not specifically limited in this embodiment of the present application.
  • the communication device 32 may be the second device in FIG. 4 or FIG. 5 or any one of the multiple devices shown in FIG. Any one of these devices can be an on-board unit (On Board Unit, OBU), a smart gas station, a smart signal light, a portable mobile device (such as a mobile phone, a tablet, etc.), or a component, chip, etc.
  • OBU On Board Unit
  • a smart gas station such as a gas pump
  • a smart signal light such as a mobile phone, a tablet, etc.
  • portable mobile device such as a mobile phone, a tablet, etc.
  • component, chip etc.
  • Other sensors or devices with functions are not specifically limited in this embodiment of the present application.
  • the bus 324 may be a peripheral component interconnect standard (peripheral component interconnect, PCI) bus or an extended industry standard architecture (extended industry standard architecture, EISA) bus or the like.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of representation, only one line is used in FIG. 13 , but it does not mean that there is only one bus or one type of bus.
  • Bus 324 may include pathways for communicating information between various components of communication device 32 (eg, memory 323 , processor 321 , transceiver 322 ).
  • the processor 321 may include any one or more of processors such as a central processing unit (central processing unit, CPU), a microprocessor (micro processor, MP), or a digital signal processor (digital signal processor, DSP).
  • processors such as a central processing unit (central processing unit, CPU), a microprocessor (micro processor, MP), or a digital signal processor (digital signal processor, DSP).
  • the memory 323 is used to provide a storage space, in which data such as operating systems and computer programs can be stored.
  • Memory 323 can be random access memory (random access memory, RAM), erasable programmable read only memory (erasable programmable read only memory, EPROM), read-only memory (read-only memory, ROM), or portable read-only memory One or more combinations of memory (compact disc read memory, CD-ROM), etc.
  • the memory 323 can exist independently, or can be integrated inside the processor 321 .
  • Transceiver 322 may be used to provide information input or output to processor 321 .
  • the transceiver 322 can be used to receive data sent from the outside and/or send data to the outside, and can be a wired link interface such as an Ethernet cable, or a wireless link (such as Wi-Fi, Bluetooth, general wireless transmission, vehicle short-distance communication technology, etc.) interface.
  • the transceiver 322 may also include a transmitter (such as a radio frequency transmitter, an antenna, etc.) or a receiver coupled with the interface.
  • the processor 321 in the communication device 32 is used to read the computer program stored in the memory 323, and is used to execute the aforementioned FIG. 4, FIG. 5 or The method on the first device side described in the embodiment of FIG. 8 .
  • the communication device 32 can be one or more modules in the first device that executes the method shown in FIG. 4 , and the processor 321 can be used to read one or more computer Programs that do the following:
  • 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 first media access control MAC address and address of the second device Identification and security mechanism; according to the first message, determine that the unicast connection between the second device and the first device is abnormal; send a second message to the second device through the sending unit 310, and the second message carries the first MAC address, address ID and error ID, the error ID is used to indicate the cause of the abnormal establishment of the unicast connection.
  • the processor 321 in the communication device 32 is used to read the computer program stored in the memory 323, and is used to execute the aforementioned FIG. 4 or FIG. 5 The method on the second device side described in the embodiment or the methods on multiple device sides described in the embodiment in FIG. 8 .
  • the communication device 32 can be one or more modules in the second device that executes the method shown in FIG. 4 , and the processor 321 can be used to read one or more computer Programs that do the following:
  • the sending unit 310 is configured 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 a first media access control MAC address of the second device, First address identification and security mechanism; receiving the second message sent by the first device through the receiving unit 314, the second message carries at least one MAC address, at least one address identification and error identification, and the error identification is used to indicate that the unicast connection is abnormally established Reason: determining, according to the second message, that the establishment of the unicast connection between the second device and the first device is abnormal, and performing an exception handling operation according to the error identification.
  • An embodiment of the present application further provides a vehicle, and the vehicle includes the above-mentioned first device or second device.
  • the vehicle can be used to execute the method on the first device side described in the embodiment in FIG. 4 , FIG. 5 or FIG. 8 .
  • the vehicle can be used to execute the method on the second device side described in the embodiment in FIG. 4 or FIG. 5 , or the methods on multiple device sides described in the embodiment in FIG. 8 .
  • An embodiment of the present application also provides a system for handling exceptions in establishing a unicast connection, and the system includes the above-mentioned first device and second device.
  • the system is used to implement the methods described in the above embodiments of the present application.
  • the first device may be a Road Side Unit (Road Side Unit, RSU), Multi-Access Edge Computing (Multi-Access Edge Computing, MEC), an On Board Unit (OBU), an intelligent gas station, an intelligent signal light, Portable mobile devices (such as mobile phones, tablets, etc.), or other sensors or devices with communication functions such as components and chips in portable mobile devices.
  • RSU Road Side Unit
  • MEC Multi-Access Edge Computing
  • OBU On Board Unit
  • the first device may also be a system consisting of an RSU and an MEC, or a system consisting of an RSU and a sensor, or a system consisting of an RSU, an MEC, and a sensor.
  • the second device may be a vehicle-mounted unit, a smart gas station, a smart signal light, a portable mobile device (such as a mobile phone, a tablet, etc.), or other sensors or devices with communication functions such as components and chips in a portable mobile device. Examples are not specifically limited.
  • storage medium includes read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), programmable read-only memory (Programmable Read-only Memory, PROM), erasable programmable read-only memory ( 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 disk storage, magnetic disk storage, tape storage, or any other computer-readable medium that can be used to carry or store data.
  • Read-Only Memory Read-Only Memory
  • RAM Random Access Memory
  • PROM Programmable Read-only Memory
  • PROM Programmable Read-only Memory
  • EPROM Erasable Programmable Read Only Memory
  • OTPROM One-time Programmable Read-Only Memory
  • EEPROM Electrically-Erasable Programmable Read-Only Memory
  • CD-ROM Compact Disc Read-Only Memory
  • the essence of the technical solution of the present application or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of software products.
  • the computer program product is stored in a storage medium, including several instructions. So that a device (which may be a personal computer, a server, or a network device, a robot, a single-chip microcomputer, a chip, a robot, etc.) executes all or part of the steps of the methods described in the various embodiments of the present application.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Small-Scale Networks (AREA)

Abstract

本申请公开了一种单播连接建立异常处理方法及装置，该方法包括：第二设备向第一设备发送第一消息以请求第一设备与第二设备建立单播连接，第一消息携带第二设备的媒介接入控制MAC地址、地址标识和安全机制，第一设备根据第一消息确定自身与第二设备之间单播连接建立异常并向第二设备发送第二消息，第二消息携带第二设备的MAC地址、地址标识和错误标识，以使第二设备根据错误标识指示的单播连接建立异常的原因执行相应地处理。实施本申请，基于消息中的设备的MAC地址和地址标识可以快速识别第二设备，消息中的错误标识可指导第二设备有效解决单播连接建立异常的问题，提高建立单播连接的效率，确保通信双方之间的单播业务的顺利执行。

Description

一种单播连接建立异常处理方法及装置
本申请要求于2021年08月19日提交中国知识产权局、申请号为202110955602.2、申请名称为“一种单播连接建立异常处理方法及装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及车联网通信领域，尤其涉及一种单播连接建立异常处理方法及装置。
背景技术
车联网(Internet of Vehicle，IOV)技术，可实现车与X(人、车、路、云端等)之间的智能信息(例如，路况信息、服务信息等)的交换、共享，大大方便了车与X的通信。
针对车与X通信之间的单播业务，单播业务公告的发送方在与单播业务公告的响应方建立单播连接的过程中，会出现多个响应方的媒介接入控制MAC(Medium Access Control)地址发生冲突、通信双方的安全机制不匹配等情况，从而影响发送方与响应方之间的单播连接的建立，还会造成基于单播业务的交互混乱、业务无法正常执行。
发明内容
本申请公开了一种单播连接建立异常处理方法和装置，能够有效解决单播连接建立异常的问题，提高建立单播连接的效率，可确保通信双方之间的单播业务的顺利执行。
第一方面，本申请提供了一种单播连接建立异常处理方法，应用于第一设备，该方法包括：接收第二设备发送的第一消息，第一消息用于请求第一设备与第二设备建立单播连接，第一消息携带第二设备的第一媒介接入控制MAC地址、地址标识和安全机制；根据第一消息，确定第二设备与第一设备之间单播连接建立异常；向第二设备发送第二消息，第二消息中携带第一MAC地址、地址标识和错误标识，错误标识用于指示单播连接建立异常的原因。
其中，第一设备可以是路侧单元(Road Side Unit，RSU)、多接入边缘计算(Multi-Access Edge Computing，MEC)、车载单元(On Board Unit，OBU)、智能加油站、智能信号灯、便携移动设备(例如，手机、平板等)，或者便携移动设备内的部件、芯片等具有通信功能的其他传感器或设备。又例如，第一设备也可以是RSU和MEC组成的系统，或者是由RSU和传感器组成的系统，还可以是由RSU、MEC和传感器组成的系统。第二设备可以是车载单元、智能加油站、智能信号灯、便携移动设备(例如，手机、平板等)，或者便携移动设备内的部件、芯片等具有通信功能的其他传感器或设备，本申请实施例不做具体限定。
安全机制为设备在通信中采取的安全模式或安全保护方法，安全机制可以是基于对称密钥的安全机制、基于证书的安全机制等，本申请实施例不做具体限定。
地址标识可以标识第二设备。地址标识可以是第二设备的设备标识、随机数或者根据第二设备的MAC地址和设备标识生成的字符串等，本申请实施例不做具体限定。
上述方法中，第一设备基于地址标识可以有效区分具有相同MAC地址的不同设备，基于错误标识可以准确指示第二设备与第一设备之间单播连接建立异常的原因，如此，通过携带了地址标识、错误标识等内容的消息可以有效解决单播连接建立异常的问题，有利于提高 建立单播连接的效率，确保了通信双方之间的单播业务的正常执行。
可选地，根据第一消息，确定第二设备与第一设备之间单播连接建立异常，包括：基于第一MAC地址与第三设备的第二MAC地址相同的判断结果，确定第一MAC地址与第三设备的第二MAC地址相同，其中，第三设备为请求与第一设备建立单播连接的设备；基于第二设备的安全机制与第一设备支持的安全机制不匹配的判断结果，确定第二设备的安全机制与第一设备支持的安全机制不匹配；或基于第一消息的消息结构错误的判断结果，确定第一消息的消息结构错误。
其中，第一MAC地址与第三设备的第二MAC地址相同即说明第二设备的第一MAC地址有冲突，其会导致单播连接建立异常；第二设备的安全机制与第一设备支持的安全机制不匹配即说明第一设备和第二设备在交互过程中对信息的加密解密方式不同，其会导致单播连接建立异常；第一消息的消息结构错误即说明第一设备无法解析或准确解析第一消息，其会导致单播连接建立异常。
实施上述实现方式，在单播连接建立过程中，可以快速识别第二设备与第一设备之间单播连接建立异常以及单播连接建立异常的原因。
可选地，在第二设备为一个设备的情况下，第一MAC地址为一个MAC地址，且第二消息中携带第一MAC地址，包括：第一MAC地址由第二消息的目的MAC地址字段承载。
实施上述实现方式，在第二消息中，第一MAC地址由第二消息的目的MAC地址字段承载，即第一MAC地址为第二消息的目标层二标识Destination Layer2 ID。
可选地，第二消息中携带地址标识和错误标识，包括：第二设备的地址标识和错误标识承载于第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段；或者第二设备的地址标识和错误标识承载于第二消息的DSA消息帧中的应用扩展域Application Extension字段。
实施上述实现方式，第二消息中携带第二设备的地址标识和错误标识，使得第二消息的接收端可以根据地址标识快速确定自身是否与第一设备单播连接建立异常，以及根据错误标识指示的单播连接建立异常的原因执行相应处理，有利于解决通信双方之间的单播连接建立异常的问题。
可选地，在第二设备为多个设备的情况下，第一MAC地址为多个MAC地址，第二消息还包括专用应用标识，专用应用标识用于指示单播连接建立异常，专用应用标识承载于第二消息的专用短消息DSM消息帧中的应用标识AID字段；第二消息的目的MAC地址字段用于承载专用应用标识的转化值。
实施上述实现方式，在第二设备为多个设备的情况下，当第二消息的目的MAC地址字段用于承载专用应用标识的转化值时，可以知晓第二消息携带了多个设备的MAC地址，如此可以减少第二消息的传输次数，有效减小了网络资源的消耗。
可选地，第二消息中携带第一MAC地址、地址标识和错误标识，包括：第一MAC地址、地址标识和错误标识承载于第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段；或者第一MAC地址、地址标识和错误标识承载于第二消息的DSA消息帧中的应用扩展域Application Extension字段。
实施上述实现方式，在第二设备为多个设备的情况下，第二消息携带了多个MAC地址、多个地址标识和至少一个错误标识，通过一条第二消息可以告知与第一设备之间单播连接建 立异常的多个设备，有利于提高建立单播连接的效率，有效减小了网络资源的消耗。
可选地，在第一消息中，第二设备的地址标识由第一消息的专用业务公告DSA消息帧中的DSA标识DSA Identifier字段和内容计数Content Count字段中的至少一者承载。
实施上述实现方式，第一消息中携带第二设备的地址标识，该地址标识可使得第一消息的接收端(即第一设备)能有效区分具有相同MAC地址的不同设备。
可选地，在第一消息中，第二设备的地址标识承载于第一消息的专用业务公告DSA消息帧的头扩展域Header Extension字段中。
实施上述实现方式，第一消息中携带第二设备的地址标识，该地址标识可使得第一消息的接收端(即第一设备)能有效区分具有相同MAC地址的不同设备。
可选地，第二消息由第一设备的网络层或应用层发送。
其中，网络层为基于长期演进(Long Term Evolution，LTE)的车联网无线通信技术中的网络层，网络层中的管理子层可用于完成系统配置及维护等功能，网络层中的数据子层可用于传输应用层间的数据流以及不同设备管理层实体或管理层实体与应用间的数据流；应用层为基于LTE的车联网无线通信技术中的应用层，应用层主要用于处理应用服务的应用层业务逻辑，例如，生成即时消息、单播业务公告等。网络层和应用层之间可通过跨层原语实现交互。
一具体实施中，可由第一设备的网络层发送第二消息，还可以由第一设备的网络层根据第一消息确定第二设备与第一设备之间单播连接建立异常，可更快发现单播链路建立异常情况并快速做出响应，同时节省第一设备内上层资源的消耗。
另一具体实施中，可由第一设备的应用层根据第一消息确定第二设备与第一设备之间单播连接建立异常以及发送第二消息，有利于减轻第一设备内其他层的数据处理压力，处理方法相对灵活。
第二方面，本申请提供了一种单播连接建立异常处理方法，应用于第二设备，该方法包括：向第一设备发送第一消息，第一消息用于请求第一设备与第二设备建立单播连接，第一消息携带第二设备的第一媒介接入控制MAC地址、第一地址标识和安全机制；接收第一设备发送的第二消息，第二消息中携带至少一个MAC地址、至少一个地址标识和错误标识，错误标识用于指示单播连接建立异常的原因；根据第二消息确定第二设备与第一设备之间单播连接建立异常；根据错误标识执行异常处理操作。
其中，第一设备、第二设备具体可参考上述第一方面中有关第一设备、第二设备的描述，在此不再赘述。
实施上述方法，针对无法区分具有相同MAC的不同设备这一问题，在第一消息携带的内容中增加了地址标识，地址标识可以标识第二设备；第二设备根据第二消息中的错误标识，可以准确知晓自身与第一设备之间单播连接建立异常的原因，从而可以有效解决单播连接建立异常的问题，有利于提高建立单播连接的效率，确保了通信双方之间的单播业务的正常执行。
可选地，根据错误标识执行异常处理操作可以是：在错误标识指示第一MAC地址有冲突时，重新选择第一MAC地址。
实施上述实现方式，可以有效解决MAC冲突导致的单播连接建立异常的问题，有利于提高建立单播连接的效率。
可选地，根据错误标识执行异常处理操作可以是：在错误标识指示第二设备的安全机制与第一设备支持的安全机制不匹配时，重新选择第二设备的安全机制。
实施上述实现方式，可以有效解决安全机制不匹配导致的单播连接建立异常的问题，有利于提高建立单播连接的效率。
可选地，根据错误标识执行异常处理操作可以是：在错误标识指示第一消息的消息结构错误时，重新校验第一消息的消息结构。
实施上述实现方式，可以有效解决第一消息无法解析导致的单播连接建立异常的问题，有利于提高建立单播连接的效率。
可选地，根据第二消息确定第二设备与第一设备之间单播连接建立异常，包括：当上述至少一个MAC地址为第一MAC地址且上述至少一个地址标识为第一地址标识时，确定第二设备与第一设备之间单播连接建立异常。
实施上述实现方式，第二消息携带的MAC地址和地址标识，可使得第二消息的接收端唯一确定自身与第一设备之间单播连接建立异常。
可选地，第二消息中携带至少一个MAC地址、至少一个地址标识和错误标识，包括：上述至少一个MAC地址由第二消息的目的MAC地址字段承载；上述至少一个地址标识和错误标识承载于第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段，或者，上述至少一个地址标识和错误标识承载于第二消息的DSA消息帧中的应用扩展域Application Extension字段。
实施上述实现方式，第二消息携带的地址标识和错误标识，使得第二消息的接收端可以根据地址标识快速确定自身是否与第一设备单播连接建立异常以及根据错误标识指示的单播连接建立异常的原因执行相应处理，有利于解决通信双方之间的单播连接建立异常的问题。
可选地，第二消息还包括专用应用标识，专用应用标识用于指示单播连接建立异常，专用应用标识承载于第二消息的专用短消息DSM消息帧中的应用标识AID字段，根据第二消息确定第二设备与第一设备之间单播连接建立异常，可以是：当第二消息的目的MAC地址字段承载的内容包括专用应用标识的转化值，以及上述至少一个MAC地址包括第一MAC地址且上述至少一个地址标识包括第一地址标识时，确定第二设备与第一设备之间单播连接建立异常。
实施上述实现方式，在第二消息的目的MAC地址字段用于承载专用应用标识的转化值时，可知晓第二消息携带了多个MAC地址和多个地址标识，在第二消息携带了第二设备的MAC地址和地址标识的情况下，第二设备可快速确定自身与第一设备之间单播连接建立异常。
可选地，第二消息中携带至少一个MAC地址、至少一个地址标识和错误标识，包括：上述至少一个MAC地址、至少一个地址标识和错误标识承载于第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段；或者上述至少一个MAC地址、至少一个地址标识和错误标识承载于第二消息的DSA消息帧中的应用扩展域Application Extension字段。
实施上述实现方式，第二消息可携带多个MAC地址和多个地址标识，通过这样一条第二消息可同时通知与第一设备之间单播连接建立异常的多个设备，有利于提高建立单播连接的效率，有效减小了网络资源的消耗。
可选地，在第一消息中，第一地址标识由第一消息的专用业务公告DSA消息帧中的DSA标识DSA Identifier字段和内容计数Content Count字段中的至少一者承载。
实施上述实现方式，第一消息中携带第一地址标识，该地址标识可使得第一消息的接收端(即第一设备)能有效区分具有相同MAC地址的不同设备。
可选地，在第一消息中，第一地址标识承载于第一消息的专用业务公告DSA消息帧的头扩展域Header Extension字段中。
实施上述实现方式，第一消息中携带第一地址标识，该地址标识可使得第一消息的接收端(即第一设备)能有效区分具有相同MAC地址的不同设备。
第三方面，本申请提供了一种用于处理单播连接建立异常的装置，该装置包括:接收单元，用于接收第二设备发送的第一消息，第一消息用于请求第一设备与第二设备建立单播连接，第一消息携带第二设备的第一媒介接入控制MAC地址、地址标识和安全机制；处理单元，用于根据第一消息，确定第二设备与第一设备之间单播连接建立异常；发送单元，用于向第二设备发送第二消息，第二消息中携带第一MAC地址、地址标识和错误标识，错误标识用于指示单播连接建立异常的原因。
可选地，处理单元，具体用于：基于第一MAC地址与第三设备的第二MAC地址相同的判断结果，确定第一MAC地址与第三设备的第二MAC地址相同，其中，第三设备为请求与第一设备建立单播连接的设备；基于第二设备的安全机制与第一设备支持的安全机制不匹配的判断结果，确定第二设备的安全机制与第一设备支持的安全机制不匹配；或基于第一消息的消息结构错误的判断结果，确定第一消息的消息结构错误。
可选地，在第二设备为一个设备的情况下，第一MAC地址为一个MAC地址，且第二消息中携带第一MAC地址，包括：第一MAC地址由第二消息的目的MAC地址字段承载。
可选地，第二消息中携带地址标识和错误标识，包括：第二设备的地址标识和错误标识承载于第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段；或者地址标识和错误标识承载于第二消息的DSA消息帧中的应用扩展域Application Extension字段。
可选地，在第二设备为多个设备的情况下，第一MAC地址为多个MAC地址，第二消息还包括专用应用标识，专用应用标识用于指示单播连接建立异常，专用应用标识承载于第二消息的专用短消息DSM消息帧中的应用标识AID字段；第二消息的目的MAC地址字段用于承载专用应用标识的转化值。
可选地，第二消息中携带第一MAC地址、地址标识和错误标识，包括：第一MAC地址、地址标识和错误标识承载于第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段；或者第一MAC地址、地址标识和错误标识承载于第二消息的DSA消息帧中的应用扩展域Application Extension字段。
可选地，在第一消息中，第二设备的地址标识由第一消息的专用业务公告DSA消息帧中的DSA标识DSA Identifier字段和内容计数Content Count字段中的至少一者承载。
可选地，在第一消息中，第二设备的地址标识承载于第一消息的专用业务公告DSA消息帧的头扩展域Header Extension字段中。
可选地，第二消息由第一设备的网络层或应用层发送。
第四方面，本申请提供了一种用于处理单播连接建立异常的装置，该装置包括:发送单元，用于向第一设备发送第一消息，第一消息用于请求第一设备与第二设备建立单播连接，第一消息携带第二设备的第一媒介接入控制MAC地址、第一地址标识和安全机制；接收单元，用于接收第一设备发送的第二消息，第二消息中携带至少一个MAC地址、至少一个地址标 识和错误标识，错误标识用于指示单播连接建立异常的原因；处理单元，用于根据第二消息确定第二设备与第一设备之间单播连接建立异常；处理单元，还用于根据错误标识执行异常处理操作。
可选地，处理单元具体用于：在错误标识指示第一MAC地址有冲突时，重新选择第一MAC地址。
可选地，处理单元具体用于：在错误标识指示第二设备的安全机制与第一设备支持的安全机制不匹配时，重新选择第二设备的安全机制。
可选地，处理单元具体用于：在错误标识指示第一消息的消息结构错误时，重新校验第一消息的消息结构。
可选地，处理单元具体用于：当上述至少一个MAC地址为第一MAC地址且上述至少一个地址标识为第一地址标识时，确定第二设备与第一设备之间单播连接建立异常。
可选地，第二消息中携带至少一个MAC地址、至少一个地址标识和错误标识，包括：至少一个MAC地址由第二消息的目的MAC地址字段承载；至少一个地址标识和错误标识承载于第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段，或者，至少一个地址标识和错误标识承载于第二消息的DSA消息帧中的应用扩展域Application Extension字段。
可选地，第二消息还包括专用应用标识，专用应用标识用于指示单播连接建立异常，专用应用标识承载于第二消息的专用短消息DSM消息帧中的应用标识AID字段；处理单元具体用于：当第二消息的目的MAC地址字段承载的内容包括专用应用标识的转化值，以及上述至少一个MAC地址包括第一MAC地址且上述至少一个地址标识包括第一地址标识时，确定第二设备与第一设备之间单播连接建立异常。
可选地，第二消息中携带至少一个MAC地址、至少一个地址标识和错误标识，包括：至少一个MAC地址、至少一个地址标识和错误标识承载于第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段；或者至少一个MAC地址、至少一个地址标识和错误标识承载于第二消息的DSA消息帧中的应用扩展域Application Extension字段。
可选地，在第一消息中，第一地址标识由第一消息的专用业务公告DSA消息帧中的DSA标识DSA Identifier字段和内容计数Content Count字段中的至少一者承载。
可选地，在第一消息中，第一地址标识承载于第一消息的专用业务公告DSA消息帧的头扩展域Header Extension字段中。
第五方面，本申请提供了一种装置，该装置包括处理器和存储器，其中，存储器用于存储程序指令；所述处理器调用所述存储器中的程序指令，使得装置执行第一方面或者第一方面的任一可能的实现方式中的方法。
第六方面，本申请提供了一种装置，该装置包括处理器和存储器，其中，存储器用于存储程序指令；所述处理器调用所述存储器中的程序指令，使得装置执行第二方面或者第二方面的任一可能的实现方式中的方法。
第七方面，本申请提供了一种计算机可读存储介质，包括计算机指令，当所述计算机指令在被处理器运行时，实现上述第一方面或者第一方面的任一可能的实现方式中的方法。
第八方面，本申请提供了一种计算机可读存储介质，包括计算机指令，当所述计算机指令在被处理器运行时，实现上述第二方面或者第二方面的任一可能的实现方式中的方法。
第九方面，本申请提供了一种计算机程序产品，当该计算机程序产品被处理器执行时，实现上述第一方面或者第一方面的任一可能的实施例中的所述方法。该计算机程序产品，例如可以为一个软件安装包，在需要使用上述第一方面的任一种可能的设计提供的方法的情况下，可以下载该计算机程序产品并在处理器上执行该计算机程序产品，以实现第一方面或者第一方面的任一可能的实施例中的所述方法。
第十方面，本申请提供了一种计算机程序产品，当该计算机程序产品被处理器执行时，实现上述第二方面或者第二方面的任一可能的实施例中的所述方法。该计算机程序产品，例如可以为一个软件安装包，在需要使用上述第二方面的任一种可能的设计提供的方法的情况下，可以下载该计算机程序产品并在处理器上执行该计算机程序产品，以实现第二方面或者第二方面的任一可能的实施例中的所述方法。
第十一方面，本申请提供了一种车辆，包括如上述第三或五方面的装置，或者包括如上述第三或五方面的任一可能的实现方式的装置，或者包括如上述第四或六方面的装置，或者包括如上述第四或六的任一可能的实现方式的装置。
第十二方面，本申请提供了一种单播连接建立异常处理系统，包括第一设备和第二设备，其中，第一设备为上述第三或五方面的装置，或者为上述第三或五方面的任一可能的实现方式的装置；第二设备为上述第四或六方面的装置，或者为上述第四或六的任一可能的实现方式的装置。
附图说明
图1是一种通信系统的架构图；
图2是一种基于LTE的车联网无线通信技术的协议栈的示意图；
图3是一种建立单播连接的场景示意图；
图4是本申请实施例提供的一种单播连接建立异常处理方法的流程图；
图5是本申请实施例提供的又一种单播连接建立异常处理方法的流程图；
图6A是本申请实施例提供的一种地址标识在第一消息中的承载示意图；
图6B是本申请实施例提供的一种地址标识在第一消息中的承载示意图；
图7A是本申请实施例提供的一种第二消息的示意图；
图7B是本申请实施例提供的一种第二消息的示意图；
图8是本申请实施例提供的又一种单播连接建立异常处理方法的流程图；
图9A是本申请实施例提供的一种第二消息的示意图；
图9B是本申请实施例提供的一种第二消息的示意图；
图10是本申请实施例提供的一种高速收费场景示意图；
图11是本申请实施例提供的一种车-车通信场景示意图；
图12是本申请本实施例提供的一种通信装置的功能结构示意图；
图13是本申请本实施例提供的一种通信装置的结构示意图。
具体实施方式
在本申请实施例中使用的术语是仅仅出于描述特定实施例的目的，而非旨在限制本申请。本申请实施例中的说明书和权利要求书中的术语“第一”、“第二”等是用于区别不同对象，而 不是用于描述特定顺序。
下面将结合附图，对本申请中的技术方案进行描述。
参见图1，图1是一种通信系统的架构示意图，其中，该通信系统包括道路侧装置和至少一个终端，其中，道路侧装置与终端、终端与终端之间可以通过无线的方式进行通信。
道路侧装置可以是路侧单元(Road Side Unit，RSU)、或是具备无线通信功能的多接入边缘计算(Multi-Access Edge Computing，MEC)、智能加油站、智能信号灯等，终端可以是车载单元(On Board Unit，OBU)、便携移动设备(例如，手机、平板等)，或者便携移动设备内的部件、芯片等可以与道路侧装置、其他终端通信的其他传感器或设备，本申请实施例不做具体限定。
在图1所示系统架构中，至少一个终端可以包括终端1和终端2，道路侧装置可以分别与终端1、终端2建立单播连接，终端1与终端2也可以建立单播连接。
需要说明的是，在图1所示系统中，道路侧装置与终端，或终端之间的通信可使用蜂窝通信技术，例如2G蜂窝通信，例如全球移动通信系统(global system for mobile communication，GSM)、通用分组无线业务(general packet radio service，GPRS)；或者3G蜂窝通信，例如宽带码分多址(wideband code division multiple access，WCDMA)、时分同步码分多址接入(time division-synchronous code division multiple access，TS-SCDMA)、码分多址接入(code division multiple access，CDMA)，或者4G蜂窝通信，例如长期演进(long term evolution，LTE)、LTE-车联网无线通信技术(Vehicle to Everything，V2X)PC5通信，或者5G蜂窝通信，例如新空口(New Radio，NR)-V2X PC5通信，或者其他演进的蜂窝通信技术。无线通信系统也可利用非蜂窝通信技术，如Wi-Fi与无线局域网(wireless local area network，WLAN)通信。在一些实施例中，上述设备之间通信还可利用红外链路、蓝牙或ZigBee进行直接通信。在一些实施例中，上述设备之间通信还可以采用其他无线协议，例如各种车辆通信系统，例如，系统中可包括一个或多个专用短程通信(dedicated short range communications，DSRC)设备，这些设备可包括车辆和/或路边台站之间的公共和/或私有数据通信，本申请不做具体限定。
需要说明的是，图1仅为示例性架构图，但不限定图1所示通信系统包括的网元的数量。虽然图1未示出，但除图1所示的功能实体外，图1还可以包括其他功能实体。另外，本申请实施例提供的方法可以应用于图1所示的通信系统，当然本申请实施例提供的方法也可以适用其他通信系统，本申请实施例对此不予限制。
具体地，上述终端或道路侧装置可以建立如图2所示的协议栈，终端之间，或者终端与道路侧装置之间可以基于图2所示的协议栈进行交互。参见图2，图2提供了一种基于LTE的车联网无线通信技术的协议栈的示意图。
该协议栈包括应用层、网络层和接入层。其中，应用层主要用于处理应用服务的应用层业务逻辑，例如，生成即时消息、单播业务公告等。应用层包括用户应用和消息层，消息层位于应用层内部，消息层向下对接数据子层，向上支持具体的用户应用。消息层可支持基于LTE的车联网无线通信技术的网络层定义的各类数据的传输。消息层与网络层内部的数据子层之间的交互通过跨层原语(也可称为操作原语或服务原语)实现。
网络层包括管理子层和数据子层，其中，管理子层用于完成系统配置及维护等功能，例如MAC地址的选择、安全机制的选择等，管理子层可以是专用管理实体(Dedicated  Management Entity，DME)，DME为所有的数据子层的实体提供管理接口。数据子层既传输应用层间的数据流，也传输不同设备管理层实体间或管理层实体与应用间的数据流。数据子层包括适配层(Adaptation Layer)、专用短消息协议(Dedicated Short Message Protocol，DSMP)层等，其中，DSMP层用于与不同应用进行数据交互，适配层用于提供底层的接入层与上层协议栈之间的传输适配功能，例如，区分待发送的数据包(例如，DSMP数据包、IP(Internet Protocol)数据包等)所使用的底层接口并将相应数据包传递至接入层的对应接口进行传输等，适配层的功能还包括源层二标识的产生/改变/维持、单播/组播地址与层二标识之间的映射等。
接入层支持蜂窝通信接口(例如，Uu口)和/或直连通信接口(例如，PC5口)，其中，PC5口、Uu口可以支持不同的无线接入技术(Radio Access Technology，RAT)，例如，RAT可以包括LTE技术或者NR技术。
参见图3，道路侧装置以RSU为例，终端以OBU为例，至少一个终端包括OBU1、OBU2和OBU3，RSU可分别与OBU1、OBU2和OBU3通信，其中，OBU1、OBU2和OBU3的MAC地址都是在相同的地址域内进行随机选择使用的。假设RSU向外周期性地广播携带指定应用服务的单播业务公告，由于OBU1、OBU2和OBU3均在RSU的广播范围内，故OBU1、OBU2和OBU3均可接收到RSU的单播业务公告，在OBU1、OBU2和OBU3分别结合自身的业务需求分析后，仅有OBU1响应RSU发送的单播业务公告，即OBU1向RSU发送响应消息，响应消息携带OBU1的MAC地址(例如，MAC1)，RSU在接收到OBU1发送的响应消息后，发现OBU1的MAC地址与OBU3的MAC地址相同或自身不支持OBU1提供的安全机制等，导致单播连接建立发生异常，易造成通信过程的混乱，影响业务的正常执行。
针对上述问题，本申请实施例提出了一种单播连接建立异常处理方法，以解决单播建立过程中出现的MAC地址冲突、通信双方的安全机制不匹配等情况导致的单播建立异常的问题。由此，提高了建立单播连接的效率，确保通信双方之间的单播业务的正常执行。
参见图4，图4是本申请实施例提供的一种单播连接建立异常处理方法，应用于单播连接建立异常处理系统，该系统包括第一设备和第二设备，其中，第一设备即为上述中的单播业务公告的发送方，第二设备即为上述中的响应方。该方法包括但不限于以下步骤：
S101：第二设备向第一设备发送第一消息。
在本申请实施例中，第一设备先向第二设备发送广播消息，该广播消息可以是用于指示预设应用服务的单播业务公告。
在本申请实施例中，第二设备接收到广播消息后，结合自身业务需求，第二设备确定自身需要与第一设备建立基于该预设应用服务的单播连接，则第二设备向第一设备发送第一消息。可以理解，第一消息为该广播消息的响应消息。
其中，第二设备可以是一个或多个设备。例如，在图4中，m为大于等于1的正整数，当m等于1时，则第二设备为一个设备，即设备1，在此情况下，第一设备与该第二设备之间的交互过程具体可参考下述图5实施例的叙述；当m大于1时，则第二设备为多个设备，具体包括设备1、设备2、…、设备m，在此情况下，第一设备与各个设备之间的交互过程具体可参考下述图8实施例的叙述，在此不在赘述。
在本申请实施例中，第一消息用于请求第一设备与第二设备建立单播连接。第一消息携 带第二设备的MAC地址、第二设备的地址标识和第二设备的安全机制。其中，第二设备的MAC地址、第二设备的地址标识和第二设备的安全机制由该第二设备确定。
在本申请实施例中，第二设备的MAC地址为第二设备与网络中与其他设备通信的地址。例如，第二设备的MAC地址可以是24比特(bit)，由第二设备采用自主式的地址选择方式选取。
在本申请实施例中，第二设备的安全机制为第二设备在与其他设备交互中采取的安全模式。第二设备的安全机制包括但不限于基于对称密钥的安全机制、基于证书的安全机制等。
可以理解，通信双方需采用同一种安全机制才可保证通信双方的正常交互。例如，基于对称密钥的安全机制是指通信双方必须相同的密钥对消息或数据进行加密以及解密运算。需要说明的是，上述安全机制在通信领域已有广泛的应用领域，在此不再赘述。
在本申请实施例中，第二设备的地址标识用于标识该第二设备。第二设备的地址标识可以是随机生成的随机数，也可以是第二设备的设备标识，还可以是根据第二设备的MAC地址和第二设备的设备标识等计算获得的字符串，在此不做具体限定。
在本申请实施例中，第二设备的MAC地址、地址标识和安全机制在第一消息中的承载位置具体可参考下述图5实施例的相关叙述，在此不再赘述。
S102：第一设备根据第一消息，确定第二设备与第一设备之间单播连接建立异常。
在本申请实施例中，第一设备接收第二设备发送的第一消息，根据第一消息，确定第二设备与第一设备之间单播连接建立异常，具体包括：
(1)基于第二设备的MAC地址与第三设备的MAC地址相同的判断结果，确定第二设备与第一设备之间单播连接建立异常，其中，第三设备为请求与第一设备建立单播连接的设备；
(2)基于第二设备的安全机制与第一设备支持的安全机制不匹配的判断结果，确定第二设备与第一设备之间单播连接建立异常；或者
(3)基于第二设备发送的第一消息的消息结构错误的判断结果，确定第二设备与第一设备之间单播连接建立异常。
其中，第二设备的MAC地址与第三设备的MAC地址相同说明第二设备发生MAC地址冲突；第二设备的安全机制与第一设备支持的安全机制不匹配说明该第二设备与第一设备会因为信息加密解密方式不同导致无法通信；第二设备发送的第一消息的消息结构错误说明第一设备无法解析第二设备发送的第一消息。需要说明的是，本申请实施例并不限定确定第二设备与第一设备之间单播建立异常的条件仅为以上罗列的条件，还可以是导致单播连接建立失败的其他条件。
可以理解，在第二设备为一个设备时，若确定第二设备与第一设备之间单播连接建立异常，则第二设备可称作异常设备。在第二设备为多个设备时，每个设备与第一设备之间是否单播连接建立异常可按照上述方法进行判断，从而可以确定多个设备中的每个设备与第一设备单播连接建立异常，多个设备中的每个设备可称作异常设备。
S103：第一设备向第二设备发送第二消息。
在本申请实施例中，第二消息携带异常设备的MAC地址、地址标识和错误标识，其中，错误标识用于指示该异常设备对应的单播连接建立异常的原因。需要说明的是，错误标识也可以称作错误代码。
一具体实施中，错误标识取值为第一值时，指示该异常设备发生MAC地址冲突；错误标识取值为第二值时，指示该异常设备的安全机制与第一设备支持的安全机制不匹配；错误标识取值为第三值时，指示该异常设备发送的第一消息的消息格式错误。在一些可能的实施例中，错误标识取值为第四值时，指示该异常设备发生MAC地址冲突且该异常设备的安全机制与第一设备支持的安全机制不匹配等。另一具体实施中，错误标识也可以通过比特位表示，例如，用001表示该异常设备发生MAC地址冲突，用010表示该异常设备的安全机制与第一设备支持的安全机制不匹配，用100表示该异常设备发送的第一消息的消息格式错误，用011表示该异常设备发生MAC地址冲突且该异常设备的安全机制与第一设备支持的安全机制不匹配，在此不做具体限定。
在本申请实施例中，在异常设备的数量为一个的情况下，第二消息携带的MAC地址为一个。此实施例具体可参考下述图5实施例中的相关叙述。
在本申请实施例中，在异常设备的数量为多个的情况下，第二消息携带的MAC地址为多个。此实施例具体可参考下述图8实施例中的相关叙述。
在本申请实施例中，S102和S103可由第一设备的网络层或应用层执行，需要说明的是，网络层为基于LTE的车联网无线通信技术中的网络层，具体可参考图2中网络层的相关叙述，应用层为基于LTE的车联网无线通信技术中的应用层，具体可参考图2中应用层的相关叙述，在此不再赘述。
一具体实施中，S102和S103可由第一设备的网络层执行，例如，可以是第一设备的网络层中的DME执行。具体地，第一设备的网络层中的DME接收到第二设备发送的第一消息后，第一设备的DME根据第一消息确定第二设备与第一设备之间单播连接建立异常，并由第一设备的DME触发发送第二消息。
一具体实施中，S102和S103也可由第一设备的应用层执行。具体地，第一设备的网络层接收到第二设备发送的第一消息后，第一设备的网络层通过跨层原语将第一消息中的MAC地址、地址标识和安全机制等数据发送给第一设备的应用层，第一设备的应用层根据接收到的数据确定第二设备与第一设备之间单播连接建立异常，并由第一设备的应用层触发发送第二消息。
S104：第二设备根据第二消息确定自身与第一设备之间单播连接建立异常以及执行异常处理操作。
以第二设备为一个设备为例进行方案的示例性阐述：
在本申请实施例中，在异常设备的数量为一个时，说明第二消息携带的异常设备的MAC地址为一个，在此情况下，若异常设备的MAC地址为第二设备的MAC地址且异常设备的地址标识为第二设备的地址标识，说明第二设备为该异常设备，故确定第二设备与第一设备之间单播连接建立异常，第二设备执行异常处理操作。此实施例具体可参考下述图5实施例中的相关叙述，在此不再赘述。
在本申请实施例中，在异常设备的数量为多个时，说明第二消息携带了多个MAC地址和多个地址标识，在此情况下，第二设备在确定第二消息为单播建立异常消息的情况下，再进一步判断得出第二消息携带的多个MAC地址包括第二设备的MAC地址且第二消息携带的多个地址标识包括第二设备的地址标识，则确定第二设备与第一设备之间单播连接建立异常，第二设备执行异常处理操作。此实施例具体可参考下述图8实施例中的相关叙述，在此不再 赘述。
在本申请实施例中，异常处理操作的执行可由第二设备的网络层或应用层执行，本申请实施例不做具体限定。
可以看到，实施本申请实施例，发送方基于地址标识可以有效区分具相同MAC地址的不同响应方，在确定有响应方对应的单播连接建立异常的情况下，发送方可通过发送携带了响应方的地址标识、错误标识等内容的消息以告知响应方单播连接建立异常的原因，使得响应方可以进行相应处理，能有效解决发送方与响应方之间单播连接建立异常的问题，提高了单播连接建立的效率，确保了通信双方之间的业务的正常执行。
参见图5，图5是本申请实施例提供的一种单播连接建立异常处理方法。相较于图4实施例，图5中的第二设备为一个设备。图5实施例可以独立于上述图4实施例，也可以是对上述图4实施例的补充。该方法包括但不限于以下步骤：
S201：第二设备向第一设备发送第一消息。
在本申请实施例中，第二设备可以是响应于第一设备发送的单播业务公告，向第一设备发送第一消息。其中，第一消息用于请求第一设备与第二设备建立单播连接，第一消息携带第二设备的MAC地址、地址标识和安全机制。
下面具体介绍第二设备的MAC地址、地址标识和安全机制在第一消息中的承载位置。
其中，在第一消息中，第二设备的地址标识在第一消息中主要有以下两种承载方式：
第一种：由第一消息中的专用业务公告标识字段和内容计数字段中的至少一者承载
在本申请实施例中，第二设备的地址标识可以由第一消息的专用业务公告(Dedicated Services Advertisement，DSA)消息帧中的DSA标识(DSA Identifier)字段和内容计数(Content Count)字段中的一个或多个承载。
参见图6A，图6A是本申请实施例提供的一种地址标识在第一消息中的承载示意图。在图6A中，示出了第一消息的DSA消息帧格式，DSA消息帧包括DSA头域和应用信息域。
在图6A中，DSA头域具体包括专用业务公告版本号(DSA Version)字段、DSA头扩展域指示(DSA Header Extension Indicator)字段、预留(Reserved)字段、DSA标识(DSA Identifier)字段、内容计数(Content Count)字段和头扩展域(Header Extension)字段。其中，DSA Header Extension Indicator字段取值为1表示出现Header Extension字段，取值为0则表示不出现Header Extension字段；Reserved字段可用于功能的扩展；DSA Identifier字段用于表示DSA的唯一性；Content Count字段可以用于在DSA ID相同时，识别是否是上一个DSA的重复；Header Extension字段可作为预留用于其他信息。
在图6A中，应用信息域具体包括应用信息计数字段(Application Info Count)字段、应用标识(AID，Application Identifier)字段和应用扩展域(Application Extension)字段。其中，Application Info Count字段用于指示该字段后应用信息的数量，AID字段用于指示应用服务的类型，Application Extension字段用于指示该应用服务的相关信息。
一具体实施中，第二设备的地址标识可承载在图6A中的DSA Identifier字段或者Content Count字段。例如，第二设备的地址标识为4bit的设备标识，则可以将其填充至第一消息的DSA消息帧中的DSA Identifier字段或者Content Count字段。
另一具体实施中，第二设备的地址标识可以由图6A中的DSA Identifier字段和Content  Count字段两者共同承载。例如，第二设备的地址标识为8bit的随机数，则可以将其填充至第一消息的DSA消息帧中的DSA Identifier字段和Content Count字段。
第二种：由第一消息中的头扩展字段承载
在本申请实施例中，第二设备的地址标识可由第一消息的DSA消息帧中的头扩展域Header Extension字段承载。
参见图6B，图6B是本申请实施例提供的一种地址标识在第一消息中的承载示意图。在图6B中，DSA消息帧具体可参考图6A中的相关叙述，在此不再赘述。在DSA消息帧中，Header Extension字段进一步包括信息元素个数(Information Element Count)字段和至少一个信息元素(Information Elements)，且一个信息元素可通过一个Element ID字段、一个长度length字段和一个内容content字段表示。在图6B中，第二设备的地址标识可由Header Extension字段承载。具体地，第二设备的地址标识可通过新定义的Element ID承载于Header Extension字段中，例如，定义一个Element ID字段用于指示检测地址冲突的功能标识，content字段用于指示第二设备的地址标识以及length字段用于指示第二设备的地址标识的长度。
在本申请实施例中，第二设备的MAC地址由第一消息的源MAC地址字段承载，即第二设备的MAC地址为第一消息的源层二标识(Source Layer2 ID)；第二设备的安全机制也可以承载于第一消息的DSA消息帧中的头扩展域(Header Extension)字段中，在此不再赘述。
需要说明的是，第二设备在确定自身的MAC地址和地址标识后，还可以存储第二设备的MAC地址与第二设备的地址标识之间的映射关系。
S202：第一设备根据第一消息确定第二设备与第一设备之间单播连接建立异常。
具体地，第一设备根据第一消息确定第二设备与第一设备之间单播连接建立异常的过程可以是：可以执行判断第二设备发送的第一消息是否可以正确解析、比较第二设备的安全机制是否与第一设备支持的安全机制匹配以及检测是否存在第三设备的MAC地址与第二设备的MAC地址相同等操作，其中，第三设备为请求与第一设备建立单播连接的设备，第三设备与第二设备不同。若出现第一消息无法解析即说明第一消息的消息结构错误，则确定第二设备与第一设备之间单播连接建立异常。若第二设备的安全机制与第一设备支持的安全机制不匹配，则确定第二设备与第一设备之间单播连接建立异常。若检测到存在第三设备的MAC地址与第二设备的MAC地址相同即说明第二设备的MAC地址有冲突，则确定第二设备与第一设备之间单播连接建立异常。在一些可能的实施例中，也可以出现第一消息无法解析、第二设备发生MAC地址冲突和第二设备的安全机制与第一设备支持的安全机制不匹配这三者的各种组合情况，均可确定第二设备与第一设备之间单播连接建立异常。
在一些可能的实施例中，若第二设备均满足下述条件：第二设备发送的第一消息的消息结构正确、第二设备的MAC地址无冲突且第二设备的安全机制与第一设备支持的安全机制匹配，则第一设备与第二设备成功建立单播连接。
S203：第一设备向第二设备发送第二消息。
在本申请实施例中，在确定第二设备与第一设备之间单播连接建立异常的情况下，第一设备向第二设备发送第二消息，第二消息携带第二设备的MAC地址、地址标识和错误标识，其中，错误标识用于指示单播连接建立异常的原因。
在第二消息中，第二设备的MAC地址由第二消息的目的MAC地址字段承载，即第二设备的MAC地址为第二消息的目标层二标识(Destination Layer2 ID)。
在第二消息中，第二设备的地址标识和错误标识在第二消息中的承载位置主要有以下两种方式：
方式一：承载于第二消息的DSA消息帧中的Application Extension字段
参见图7A，图7A是本申请实施例提供的一种第二消息的示意图。在图7A中，第二消息的源MAC地址字段用于承载第一设备的MAC地址，即第二消息的源层二标识为第一设备的MAC地址，第二消息的目的MAC地址字段用于承载该第二设备的MAC地址，即第二消息的目标层二标识为第二设备的MAC地址，第二消息的MAC载荷字段可用于承载专用短消息(Dedicated Short Message，DSM)消息帧。DSM消息帧包括专用短消息协议版本号(DSMP Version)字段、DSMP扩展域指示(DSMP Extension Indicator)字段、预留(Reserved)字段、扩展域(Extension)字段,应用标识(AID)字段，长度(Length)字段和数据(Data)字段。其中，DSMP Extension Indicator字段取值为1表示后面的Extension字段出现，取值为0则表示不出现Extension字段；Reserved字段可用于功能的扩展；AID字段用于填充应用标识，以区分不同的应用；Length字段用于表示应用层数据实体的字节长度；Data字段可用于承载应用层或管理子层的数据实体。在图7A中，DSM消息帧中的Data字段用于承载DSA消息帧，DSA消息帧中的各个字段具体可参考图6A中DSA消息帧的叙述。
在图7A所示的第二消息中，第二设备的地址标识和第二设备的错误标识由第二消息的DSA消息帧中的Application Extension字段承载。例如，可以在Application Extension字段中新定义一个数据Data字段用于承载该第二设备的地址标识和错误标识。
方式二：承载于第二消息的DSA消息帧的Header Extension字段
参见图7B，图7B是本申请实施例提供的一种第二消息的示意图。在图7B中，第二消息的源MAC地址字段用于承载第一设备的MAC地址，第二消息的目的MAC地址字段用于承载该第二设备的MAC地址，MAC载荷字段用于承载DSM消息帧，DSM消息帧中的Data字段用于承载DSA消息帧，其中，DSM消息帧中的各字段具体可参考图7A的相关叙述，DSA消息帧中的各字段具体可参考图6A中的相关叙述，在此不再赘述。
在图7B所示的第二消息中，第二设备的地址标识和第二设备的错误标识由第二消息的DSA消息帧中的Header Extension字段承载。例如，在Header Extension字段中新定义一个信息元素，该信息元素通过Element ID字段、length字段和content字段表示，其中，Element ID字段用于指示单播建立异常的标识，length字段用于指示content字段承载的内容的长度，content字段用于承载该第二设备的地址标识和错误标识。
S204：第二设备根据第二消息确定自身与第一设备之间单播连接建立异常，并根据第二消息携带的错误标识执行异常处理操作。
在本申请实施例中，第二设备接收第二消息，知晓第二消息携带的MAC地址的数量为一个且第二消息携带的地址标识的数量为一个，检测到第二消息携带的MAC地址为第二设备的MAC地址且第二消息携带的地址标识为第二设备的地址标识，即说明第二消息携带了第二设备的MAC地址和第二设备的地址标识，故第二设备确定自身与第一设备之间单播连接建立异常。
在本申请实施例中，第二设备在确定自身与第一设备之间单播连接建立异常后，根据第二消息携带的错误标识执行异常处理操作。
一具体实施中，第二设备根据第二消息携带的错误标识执行异常处理操作，具体为：在 错误标识指示第二设备的MAC地址有冲突时，第二设备重新选择自身的MAC地址。在一些可能的实施例中，若第二设备的地址标识是根据第二设备的MAC地址获得，由于第二设备的MAC地址发生改变，故第二设备的地址标识也需要改变，第二设备在重新选择自身的MAC地址后，还可以重新确定自身的地址标识。
一具体实施中，第二设备根据第二消息携带的错误标识执行异常处理操作，具体为：在错误标识指示第二设备的安全机制与第一设备支持的安全机制不匹配时，第二设备重新选择自身的安全机制。
在一些可能的实施例，第二设备根据第二消息携带的错误标识执行异常处理操作，还可以是：在错误标识指示第二设备发送的第一消息的消息结构错误时，第二设备检查第一消息的消息结构。在一些可能的实施例中，在错误标识指示第二设备的MAC地址有冲突且第二设备的安全机制与第一设备支持的安全机制不匹配时，第二设备重新选择自身的MAC地址和自身的安全机制。本申请实施例对第二设备执行的异常处理操作不做具体限定。
在本申请实施例中，第二设备根据第二消息携带的错误标识执行异常处理操作后，第二设备可以重新请求第一设备与第二设备建立单播连接。
可以看到，实施本申请实施例，基于响应方的MAC地址和地址标识可以识别响应方，基于消息中携带的基于，基于消息中携带的错误标识可指导响应方有效解决MAC地址冲突、安全机制不匹配等问题导致的发送方与响应方之间的单播连接建立异常的问题，有利于提高建立单播连接的效率，确保了通信双方之间的单播业务的正常执行。
参见图8，图8是本申请实施例提供的又一种单播连接建立异常处理方法。相较于图5实施例，图8中有多个设备与第一设备交互，也相当于图4实施例中的第二设备包括多个设备。图8实施例可以独立于上述图4和图5实施例，也可以是对上述图4实施例的补充。该方法包括但不限于以下步骤：
S301：多个设备向第一设备发送第一消息。
在本申请实施例中，多个设备向第一设备发送第一消息可以是：多个设备中的每个设备向第一设备发送一条第一消息，也就是说，第一消息的数量与多个设备的数量相同。其中，第一消息用于请求第一设备与该设备建立单播连接。需要说明的是，多个设备可以是图8中的设备1，设备2,…,设备m，其中，m为大于1的正整数。
以多个设备中的设备1为例进行方案的示例性阐述，设备1向第一设备发送的第一消息用于请求第一设备与设备1建立单播连接，设备1发送的第一消息携带了设备1的MAC地址、地址标识和安全机制。其中，设备1的MAC地址、地址标识和安全机制在第一消息中的承载方式具体可参考上述图5实施例S201的相关叙述，在此不再赘述。
需要说明的是，多个设备中每个设备发送的第一消息可参考上述设备1发送的第一消息的相关说明，在此不再赘述。
S302：第一设备根据多个设备发送的第一消息确定这多个设备与第一设备之间单播连接建立异常。
在本申请实施例中，第一设备根据多个设备中每个设备发送的第一消息确定多个设备中的每个设备均与第一设备之间单播连接建立异常。
对于多个设备中的每个设备，以多个设备中的设备1为例，即第一设备根据设备1发送 的第一消息确定设备1与第一设备之间单播连接建立异常，具体过程具体可参考图4实施例中S102或者图5实施例中S202的相关叙述，在此不再赘述。
S303：第一设备向多个设备发送第二消息。
在本申请实施例中，第二消息携带了上述多个设备(即m个设备)的MAC地址、地址标识和错误标识，错误标识用于指示对应设备的单播连接建立异常的原因。示例性地，第二消息可以是一条广播消息。
在本申请实施例中，第二消息还包括专用应用标识，专用应用标识用于指示单播连接建立异常，专用应用标识由第二消息的DSM消息帧中的AID字段承载。
在第二消息中，第二消息的目的MAC地址字段用于承载专用应用标识的转化值。
在第二消息中，多个设备的MAC地址、地址标识和错误标识在第二消息中的承载位置主要有以下两种方式：
方式一：承载于第二消息的DSA消息帧中的Application Extension字段
参见图9A，图9A是本申请实施例提供的一种第二消息的示意图。在图9A中，第二消息的源MAC地址字段用于承载第一设备的MAC地址，第二消息的目的MAC地址字段用于承载专用应用标识的转化值，MAC载荷字段用于承载DSM消息帧，DSM消息帧具体可参考图7A中的相关叙述。DSM消息帧中的AID字段用于承载专用应用标识，DSM消息帧中的Data字段用于承载DSA消息帧，DSA消息帧具体可参考图6A中的相关叙述，在此不再赘述。
在图9A所示的第二消息中，多个设备的MAC地址、地址标识和错误标识由第二消息的DSA消息帧中的Application Extension字段承载。例如，可以在Application Extension字段中新定义一个数据Data字段用于承载多个设备的MAC地址、地址标识和错误标识,除此之外，还可以承载设备的统计值m。在图9A中，多个设备包括设备1，…，设备m。
方式二：承载于第二消息的DSA消息帧中的Header Extension字段
参见图9B，图9B是本申请实施例提供的一种第二消息的示意图。在图9B中，第二消息的源MAC地址字段用于承载第一设备的MAC地址，第二消息的MAC载荷字段用于承载DSM消息帧，第二消息的目的MAC地址字段用于承载专用应用标识的转化值，第二消息的DSM消息帧中的AID字段用于承载专用应用标识，DSM消息帧中的Data字段用于承载DSA消息帧，其中，DSM消息帧中的各个字段具体可参考图7A中的相关叙述，DSA消息帧中的各个字段具体可参考图6A中的相关叙述。
在图9B所示的第二消息中，多个设备的MAC地址、地址标识和错误标识由第二消息的DSA消息帧中的Header Extension字段承载。例如，在Header Extension字段中新定义一个信息元素，该信息元素通过Element ID字段、length字段和content字段表示，其中，Element ID字段可以用于指示单播建立异常的标识，length字段用于指示content字段承载的内容的长度，content字段用于承载多个设备的MAC地址、地址标识和错误标识,除此之外，还可以承载设备的统计值m。在图9B中，多个设备包括设备1，…，设备m。
在一些可能的实施例中，在多个设备与第一设备之间单播连接建立异常的情况下，第一消息也可以向多个设备中的每个设备发送对应的第二消息，每个设备对应的第二消息仅携带该设备的MAC地址、地址标识和错误标识，在此情况下，第二消息可以是上述图7A或图7B所示形式。
S304：多个设备中的每个设备根据第二消息确定自身与第一设备之间单播连接建立异常， 并根据对应的错误标识执行异常处理操作。
以多个设备中的设备1为例进行该步骤的示例性阐述：
设备1接收到来自第一设备的第二消息后，先确定第二消息的目的MAC地址字段承载的内容包括专用应用标识的转化值，相当于知晓第二消息中携带了多个MAC地址、多个地址标识和至少一个错误标识。进一步地，设备1分别判断第二消息携带的多个MAC地址中是否包括设备1的MAC地址以及第二消息携带的多个地址标识中是否包括设备1的地址标识，当第二消息携带的多个MAC地址包括设备1的MAC地址且第二消息携带的多个地址标识包括设备1的地址标识时，设备1确定自身与第一设备之间单播连接建立异常。
由于第二消息中携带的MAC地址、地址标识和错误标识这三者之间存在映射关系，在设备1确定自身与第一设备之间单播连接建立异常的情况下，设备1基于MAC地址、地址标识和错误标识之间的映射关系从第二消息中获取设备1对应的错误标识，设备1根据自身对应的错误标识执行异常处理操作。需要说明的是，设备1执行异常处理操作的过程具体可参考图5实施例中S204中第二设备执行异常处理操作的相关叙述，在此不再赘述。
在一些可能的实施例中，在第二消息仅携带了一个MAC地址、一个地址标识和一个错误标识的情况下，设备1的处理过程具体可参考图5实施例中S204的相关叙述。
可以看到，实施本申请实施例，发送方基于地址标识可以有效区分具有相同MAC地址的不同响应方，在确定有多个响应方对应的单播连接建立异常的情况下，发送方可通过发送一条携带了多个响应方的地址标识的消息以告知各个响应方单播连接建立异常的原因，使得响应方可以进行相应处理，能有效解决发送方与响应方之间单播连接建立异常的问题，减少了网络资源的消耗，提高了单播连接建立的效率，确保了通信双方之间的业务的正常执行。
下面以具体的应用场景说明上述方法的应用。
参见图10，图10是一种高速收费场景示意图。在图10中，RSU相当于上述图5中的第一设备，OBU1相当于上述图5中的第二设备，OBU2相当于上述中的第三设备。OBU2的MAC地址与OBU1的MAC地址相同，均为MAC1，OBU1的地址标识为地址标识1，OBU1的安全机制为安全机制1。
假设RSU向外广播用于近场服务应用的单播业务公告，OBU2先于OBU1进入RSU的广播范围内，OBU2与RSU建立了单播连接完成了一次近场支付，RSU存储OBU2的MAC地址(即MAC1)。在OBU2正驶离RSU的过程中，OBU1进入RSU的广播范围内，响应接收到的单播业务公告，向RSU发送第一消息用于请求RSU与OBU1建立单播连接，第一消息携带OBU1的MAC1、地址标识1和安全机制1。RSU根据第一消息检测到存储的MAC地址列表中存在MAC1与OBU1的MAC地址相同，即OBU1的MAC地址发生冲突，故确定OBU1的错误标识为错误标识1，错误标识1用于指示MAC地址有冲突，并触发RSU发送第二消息，第二消息携带OBU1的MAC1、地址标识1和错误标识1。OBU1接收到第二消息后，检测到第二消息携带的MAC地址为MAC1且第二消息携带的地址标识为地址标识1，即确定OBU1与RSU之间单播连接建立异常。进一步地，根据第二消息中携带的错误标识获得单播连接建立异常的原因是MAC地址有冲突，因此，OBU1重新选择自身的MAC地址，或者，重新选择自身的MAC地址和地址标识，然后再重新响应来自RSU的单播业务公告，由此提高了单播连接建立的效率。
参见图11，图11是一种车-车通信场景示意图。在图11中，OBU1可以是上述图8中的设备1，OBU2相当于上述图8中的第一设备。OBU1的MAC地址为MAC1，OBU1的地址标识为地址标识1以及OBU1的安全机制为安全机制1。OBU2支持的安全机制为安全机制2，安全机制1与安全机制2不相同。
假设OBU2向外广播用于交通服务应用的单播业务公告。OBU1在OBU2的广播范围内，OBU1响应于该单播业务公告，向OBU2发送第一消息用于请求OBU2与OBU1建立单播连接，第一消息携带OBU1的MAC1、地址标识1和安全机制1。OBU2根据接收到的第一消息检测到OBU1的安全机制1与自身支持的安全机制(即安全机制2)不匹配，确定OBU1的错误标识为错误标识2，错误标识2用于指示OBU1的安全机制与OBU2支持的安全机制不匹配，并触发OBU2发送第二消息，示例性地，第二消息是一条广播消息，第二消息携带了多个MAC地址、多个地址标识和至少一个错误标识。OBU1接收到第二消息后，检测到第二消息的目的MAC地址字段承载的内容为专用应用标识的转化值，专用应用标识用于指示单播连接建立异常，进一步地，检测到第二消息携带的多个MAC地址包括OBU1的MAC1且多个地址标识包括OBU1的地址标识1，OBU1确定自身与OBU2之间单播连接建立异常。进一步地，从第二消息中获取自身对应的错误标识为错误标识2，根据错误标识2获得单播连接建立异常的原因是安全机制不匹配，因此，OBU1重新选择自身的安全机制，然后再重新响应来自OBU2的单播业务公告，由此提高了单播连接建立的效率，确保了通信双方之间的业务的正常执行。
上述详细阐述了本申请实施例的方法，下面提供了本申请实施例的装置。
参见图12，图12是本申请实施例提供的一种通信装置的功能结构示意图，通信装置30包括发送单元310、处理单元312和接收单元314。该通信装置30可以通过硬件、软件或者软硬件结合的方式来实现。
在一种可能的设计中，通信装置30可以是上述图4、图5或图8中的第一设备。具体地：接收单元314用于接收第二设备发送的第一消息，第一消息用于请求第一设备与第二设备建立单播连接，第一消息携带第二设备的第一媒介接入控制MAC地址、地址标识和安全机制；处理单元312用于根据第一消息，确定第二设备与第一设备之间单播连接建立异常；发送单元310用于向第二设备发送第二消息，第二消息中携带第一MAC地址、地址标识和错误标识，错误标识用于指示单播连接建立异常的原因。
在此情况下，该通信装置30可用于实现图4实施例所描述的第一设备侧的方法。在图4实施例中，接收单元314和处理单元312可用于执行S102，发送单元310可用于执行S103。该通信装置30的各功能模块还可用于实现图5或图8实施例所描述的第一设备侧的方法，为了说明书的简洁，在此不再赘述。
在另一种可能的设计中，通信装置30可以是上述图4或图5中的第二设备或者上述图8所示的多个设备中的任意一个设备。具体地：发送单元310用于向第一设备发送第一消息，第一消息用于请求第一设备与第二设备建立单播连接，第一消息携带第二设备的第一媒介接入控制MAC地址、第一地址标识和安全机制；接收单元314用于接收第一设备发送的第二消息，第二消息携带至少一个MAC地址、至少一个地址标识和错误标识，错误标识用于指示单播连接建立异常的原因；处理单元312用于根据第二消息确定第二设备与第一设备之间 单播连接建立异常，以及根据错误标识执行异常处理操作。
在此情况下，该通信装置30可用于实现图4实施例所描述的第二设备侧的方法。在图4实施例中，发送单元310可用于执行S101，接收单元314和处理单元312可用于执行S104。该通信装置30的各功能模块还可用于实现图5实施例所描述的第二设备侧的方法或图8实施例所描述的多个设备侧的方法，为了说明书的简洁，在此不再赘述。
以上图12所示实施例中的各个单元的只一个或多个可以软件、硬件、固件或其结合实现。所述软件或固件包括但不限于计算机程序指令或代码，并可以被硬件处理器所执行。所述硬件包括但不限于各类集成电路，如中央处理单元(CPU，Central Processing Unit)、数字信号处理器(DSP，Digital Signal Processor)、现场可编程门阵列(FPGA，Field Programmable Gate Array)或专用集成电路(ASIC，Application Specific Integrated Circuit)。
参见图13，图13是本申请实施例提供的一种通信装置的结构示意图。如图13所示，通信装置32包括：处理器321、收发器322、存储器323和总线324。一具体实施中，处理器321、存储器323和收发器322之间通过总线324通信。应理解，本申请不限定通信装置32中的处理器、存储器的个数。
在一种可能的设计中，通信装置32可以是上述图4、图5或图8实施例中的第一设备，第一设备可以是道路侧装置，例如路侧单元(Road Side Unit，RSU)、多接入边缘计算(Multi-Access Edge Computing，MEC)、智能加油站、智能信号灯等。又例如，也可以是RSU和MEC组成的系统，或者是由RSU和传感器组成的系统，还可以是由RSU、MEC和传感器组成的系统。第一设备还可以是终端，例如，车载单元(On Board Unit，OBU)、便携移动设备(例如，手机、平板等)，或者便携移动设备内的部件、芯片等具有通信功能的其他传感器或设备，本申请实施例不做具体限定。
在另一种可能的设计中，通信装置32可以是上述图4或图5中的第二设备或者图8所示的多个设备中的任意一个设备，第二设备或图8所示的多个设备中的任意一个设备可以是车载单元(On Board Unit，OBU)、智能加油站、智能信号灯、便携移动设备(例如，手机、平板等)，或者便携移动设备内的部件、芯片等具有通信功能的其他传感器或设备，本申请实施例不做具体限定。
总线324可以是外设部件互连标准(peripheral component interconnect，PCI)总线或扩展工业标准结构(extended industry standard architecture，EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示，图13中仅用一条线表示，但并不表示仅有一根总线或一种类型的总线。总线324可包括在通信装置32各个部件(例如，存储器323、处理器321、收发器322)之间传送信息的通路。
处理器321可以包括中央处理器(central processing unit，CPU)、微处理器(micro processor，MP)或者数字信号处理器(digital signal processor，DSP)等处理器中的任意一种或多种。
存储器323用于提供存储空间，存储空间中可以存储操作系统和计算机程序等数据。存储器323可以是随机存取存储器(random access memory，RAM)、可擦除可编程只读存储器(erasable programmable read only memory，EPROM)、只读存储器(read-only memory，ROM)，或便携式只读存储器(compact disc read memory，CD-ROM)等中的一种或者多种的组合。存储器323可以单独存在，也可以集成于处理器321内部。
收发器322可用于为处理器321提供信息输入或输出。或者可替换的，该收发器322可用于接收外部发送的数据和/或向外部发送数据，可以为包括诸如以太网电缆等的有线链路接口，也可以是无线链路(如Wi-Fi、蓝牙、通用无线传输、车载短距通信技术等)接口。或者可替换的，收发器322还可以包括与接口耦合的发射器(如射频发射器、天线等)，或者接收器等。
一具体实施中，在该通信装置32为上述中的第一设备时，该通信装置32中的处理器321用于读取存储器323中存储的计算机程序，用于执行前述图4、图5或图8实施例描述的第一设备侧的方法。
在一种可能的设计方式中，通信装置32可为执行图4所示方法的第一设备中的一个或多个模块，该处理器321可用于读取存储器323中存储的一个或多个计算机程序，用于执行以下操作：
通过接收单元314接收第二设备发送的第一消息，第一消息用于请求第一设备与第二设备建立单播连接，第一消息携带第二设备的第一媒介接入控制MAC地址、地址标识和安全机制；根据第一消息，确定第二设备与第一设备之间单播连接建立异常；通过发送单元310向第二设备发送第二消息，第二消息中携带第一MAC地址、地址标识和错误标识，错误标识用于指示单播连接建立异常的原因。
另一具体实施中，在该通信装置32为上述中的第二设备时，该通信装置32中的处理器321用于读取存储器323中存储的计算机程序，用于执行前述图4或图5实施例描述的第二设备侧的方法或图8实施例描述的多个设备侧的方法。
在一种可能的设计方式中，通信装置32可为执行图4所示方法的第二设备中的一个或多个模块，该处理器321可用于读取存储器323中存储的一个或多个计算机程序，用于执行以下操作：
通过发送单元310用于向第一设备发送第一消息，第一消息用于请求第一设备与第二设备建立单播连接，第一消息携带第二设备的第一媒介接入控制MAC地址、第一地址标识和安全机制；通过接收单元314接收第一设备发送的第二消息，第二消息携带至少一个MAC地址、至少一个地址标识和错误标识，错误标识用于指示单播连接建立异常的原因；根据第二消息确定第二设备与第一设备之间单播连接建立异常，以及根据错误标识执行异常处理操作。
本申请实施例还提供了一种车辆，车辆包括上述第一设备或第二设备。一具体实施中，该车辆可用于执行上述图4、图5或图8实施例所描述的第一设备侧的方法。另一具体实施中，该车辆可用于执行上述图4或图5实施例所描述的第二设备侧的方法、或者图8实施例所描述的多个设备侧的方法。
本申请实施例还提供了一种单播连接建立异常处理系统，该系统包括上述中的第一设备和第二设备。该系统用于执行本申请上文各实施例所描述的方法。
其中，第一设备可以是路侧单元(Road Side Unit，RSU)、多接入边缘计算(Multi-Access Edge Computing，MEC)、车载单元(On Board Unit，OBU)、智能加油站、智能信号灯、便携移动设备(例如，手机、平板等)，或者便携移动设备内的部件、芯片等具有通信功能的其他传感器或设备。又例如，第一设备也可以是RSU和MEC组成的系统，或者是由RSU和 传感器组成的系统，还可以是由RSU、MEC和传感器组成的系统。
其中，第二设备可以是车载单元、智能加油站、智能信号灯、便携移动设备(例如，手机、平板等)，或者便携移动设备内的部件、芯片等具有通信功能的其他传感器或设备，本申请实施例不做具体限定。
在本文上述的实施例中，对各个实施例的描述都各有侧重，某个实施例中没有详细描述的部分，可以参见其他实施例的相关描述。
需要说明的是，本领域普通技术人员可以看到上述实施例的各种方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成，该程序可以存储于一计算机可读存储介质中，存储介质包括只读存储器(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)或其他光盘存储器、磁盘存储器、磁带存储器、或者能够用于携带或存储数据的计算机可读的任何其他介质。
本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的全部或部分可以以软件产品的形式体现出来，该计算机程序产品存储在一个存储介质中，包括若干指令用以使得一个设备(可以是个人计算机，服务器，或者网络设备、机器人、单片机、芯片、机器人等)执行本申请各个实施例所述方法的全部或部分步骤。

Claims (41)

  1. 一种单播连接建立异常处理方法，应用于第一设备，其特征在于，所述方法包括：
    接收第二设备发送的第一消息，所述第一消息用于请求所述第一设备与所述第二设备建立单播连接，所述第一消息携带所述第二设备的第一媒介接入控制MAC地址、地址标识和安全机制；
    根据所述第一消息，确定所述第二设备与所述第一设备之间单播连接建立异常；
    向所述第二设备发送第二消息，所述第二消息中携带所述第一MAC地址、所述地址标识和错误标识，所述错误标识用于指示所述单播连接建立异常的原因。
  2. 根据权利要求1所述的方法，其特征在于，所述根据所述第一消息，确定所述第二设备与所述第一设备之间单播连接建立异常包括：
    基于所述第一MAC地址与第三设备的第二MAC地址相同的判断结果，确定所述第二设备与所述第一设备之间单播连接建立异常，其中，所述第三设备为请求与所述第一设备建立单播连接的设备；
    基于所述安全机制与所述第一设备支持的安全机制不匹配的判断结果，确定所述第二设备与所述第一设备之间单播连接建立异常；或
    基于所述第一消息的消息结构错误的判断结果，确定所述第二设备与所述第一设备之间单播连接建立异常。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第二设备为一个设备，所述第一MAC地址为一个MAC地址，且所述第二消息中携带所述第一MAC地址包括：
    所述第一MAC地址由所述第二消息的目的MAC地址字段承载。
  4. 根据权利要求3所述的方法，其特征在于，所述第二消息中携带所述地址标识和错误标识，包括：
    所述地址标识和所述错误标识承载于所述第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段；或者
    所述地址标识和所述错误标识承载于所述第二消息的所述DSA消息帧中的应用扩展域Application Extension字段。
  5. 根据权利要求1或2所述的方法，其特征在于，所述第二设备为多个设备，所述第一MAC地址为多个MAC地址，所述第二消息还包括专用应用标识，所述专用应用标识用于指示所述单播连接建立异常，所述专用应用标识承载于所述第二消息的专用短消息DSM消息帧中的应用标识AID字段；所述第二消息的目的MAC地址字段用于承载所述专用应用标识的转化值。
  6. 根据权利要求5所述的方法，其特征在于，所述第二消息中携带所述第一MAC地址、所述地址标识和错误标识，包括：
    所述第一MAC地址、所述地址标识和所述错误标识承载于所述第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段；或者
    所述第一MAC地址、所述地址标识和所述错误标识承载于所述第二消息的所述DSA消息帧中的应用扩展域Application Extension字段。
  7. 根据权利要求1-6任一项所述的方法，其特征在于，在所述第一消息中，所述第二设备的地址标识由所述第一消息的专用业务公告DSA消息帧中的DSA标识DSA Identifier字段和 内容计数Content Count字段中的至少一者承载。
  8. 根据权利要求1-6任一项所述的方法，其特征在于，在所述第一消息中，所述第二设备的地址标识承载于所述第一消息的专用业务公告DSA消息帧的头扩展域Header Extension字段中。
  9. 一种单播连接建立异常处理方法，应用于第二设备，其特征在于，所述方法包括：
    向第一设备发送第一消息，所述第一消息用于请求所述第一设备与所述第二设备建立单播连接，所述第一消息携带所述第二设备的第一媒介接入控制MAC地址、第一地址标识和安全机制；
    接收所述第一设备发送的第二消息，所述第二消息中携带至少一个MAC地址、至少一个地址标识和错误标识，所述错误标识用于指示所述单播连接建立异常的原因；
    根据所述第二消息确定所述第二设备与所述第一设备之间单播连接建立异常；
    根据所述错误标识执行异常处理操作。
  10. 根据权利要求9所述的方法，其特征在于，所述根据所述错误标识执行异常处理操作，包括：
    在所述错误标识指示所述第一MAC地址有冲突时，重新选择所述第一MAC地址。
  11. 根据权利要求9或10所述的方法，其特征在于，所述根据所述错误标识执行异常处理操作，包括：
    在所述错误标识指示所述安全机制与所述第一设备支持的安全机制不匹配时，重新选择所述安全机制。
  12. 根据权利要求9-11任一项所述的方法，其特征在于，所述根据所述第二消息确定所述第二设备与所述第一设备之间单播连接建立异常，包括：
    当所述至少一个MAC地址为所述第一MAC地址且所述至少一个地址标识为所述第一地址标识时，确定所述第二设备与所述第一设备之间单播连接建立异常。
  13. 根据权利要求12所述的方法，其特征在于，所述第二消息中携带至少一个MAC地址、至少一个地址标识和错误标识，包括：
    所述至少一个MAC地址由所述第二消息的目的MAC地址字段承载；
    所述至少一个地址标识和错误标识承载于所述第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段，或者，所述至少一个地址标识和错误标识承载于所述第二消息的所述DSA消息帧中的应用扩展域Application Extension字段。
  14. 根据权利要求9-11任一项所述的方法，其特征在于，所述第二消息还包括专用应用标识，所述专用应用标识用于指示所述单播连接建立异常，所述专用应用标识承载于所述第二消息的专用短消息DSM消息帧中的应用标识AID字段，所述根据所述第二消息确定所述第二设备与所述第一设备之间单播连接建立异常，包括：
    当所述第二消息的目的MAC地址字段承载的内容包括所述专用应用标识的转化值，以及所述至少一个MAC地址包括所述第一MAC地址且所述至少一个地址标识包括所述第一地址标识时，确定所述第二设备与所述第一设备之间单播连接建立异常。
  15. 根据权利要求14所述的方法，其特征在于，所述第二消息中携带至少一个MAC地址、至少一个地址标识和错误标识，包括：
    所述至少一个MAC地址、所述至少一个地址标识和错误标识承载于所述第二消息的专 用业务公告DSA消息帧中的头扩展域Header Extension字段；或者
    所述至少一个MAC地址、所述至少一个地址标识和错误标识承载于所述第二消息的所述DSA消息帧中的应用扩展域Application Extension字段。
  16. 根据权利要求9-15任一项所述的方法，其特征在于，在所述第一消息中，所述第一地址标识由所述第一消息的专用业务公告DSA消息帧中的DSA标识DSA Identifier字段和内容计数Content Count字段中的至少一者承载。
  17. 根据权利要求9-15任一项所述的方法，其特征在于，在所述第一消息中，所述第一地址标识承载于所述第一消息的专用业务公告DSA消息帧的头扩展域Header Extension字段中。
  18. 一种用于处理单播连接建立异常的装置，其特征在于，所述装置包括：
    接收单元，用于接收第二设备发送的第一消息，所述第一消息用于请求所述第一设备与所述第二设备建立单播连接，所述第一消息携带所述第二设备的第一媒介接入控制MAC地址、地址标识和安全机制；
    处理单元，用于根据所述第一消息，确定所述第二设备与所述第一设备之间单播连接建立异常；
    发送单元，用于向所述第二设备发送第二消息，所述第二消息中携带所述第一MAC地址、所述地址标识和错误标识，所述错误标识用于指示所述单播连接建立异常的原因。
  19. 根据权利要求18所述的装置，其特征在于，所述处理单元，具体用于：
    基于所述第一MAC地址与第三设备的第二MAC地址相同的判断结果，确定所述第二设备与所述第一设备之间单播连接建立异常，其中，所述第三设备为请求与所述第一设备建立单播连接的设备；
    基于所述安全机制与所述第一设备支持的安全机制不匹配的判断结果，确定所述第二设备与所述第一设备之间单播连接建立异常；或
    基于所述第一消息的消息结构错误的判断结果，确定所述第二设备与所述第一设备之间单播连接建立异常。
  20. 根据权利要求18或19所述的装置，其特征在于，所述第二设备为一个设备，所述第一MAC地址为一个MAC地址，且所述第二消息中携带所述第一MAC地址包括：
    所述第一MAC地址由所述第二消息的目的MAC地址字段承载。
  21. 根据权利要求20所述的装置，其特征在于，所述第二消息中携带所述地址标识和错误标识，包括：
    所述地址标识和所述错误标识承载于所述第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段；或者
    所述地址标识和所述错误标识承载于所述第二消息的所述DSA消息帧中的应用扩展域Application Extension字段。
  22. 根据权利要求18或19所述的装置，其特征在于，所述第二设备为多个设备，所述第一MAC地址为多个MAC地址，所述第二消息还包括专用应用标识，所述专用应用标识用于指示所述单播连接建立异常，所述专用应用标识承载于所述第二消息的专用短消息DSM消息帧中的应用标识AID字段；所述第二消息的目的MAC地址字段用于承载所述专用应用标识的转化值。
  23. 根据权利要求22所述的装置，其特征在于，所述第二消息中携带所述第一MAC地址、 所述地址标识和错误标识，包括：
    所述第一MAC地址、所述地址标识和所述错误标识承载于所述第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段；或者
    所述第一MAC地址、所述地址标识和所述错误标识承载于所述第二消息的所述DSA消息帧中的应用扩展域Application Extension字段。
  24. 根据权利要求18-23任一项所述的装置，其特征在于，在所述第一消息中，所述第二设备的地址标识由所述第一消息的专用业务公告DSA消息帧中的DSA标识DSA Identifier字段和内容计数Content Count字段中的至少一者承载。
  25. 根据权利要求18-23任一项所述的装置，其特征在于，在所述第一消息中，所述第二设备的地址标识承载于所述第一消息的专用业务公告DSA消息帧的头扩展域Header Extension字段中。
  26. 一种用于处理单播连接建立异常的装置，其特征在于，所述装置包括：
    发送单元，用于向第一设备发送第一消息，所述第一消息用于请求所述第一设备与所述第二设备建立单播连接，所述第一消息携带所述第二设备的第一媒介接入控制MAC地址、第一地址标识和安全机制；
    接收单元，用于接收所述第一设备发送的第二消息，所述第二消息中携带至少一个MAC地址、至少一个地址标识和错误标识，所述错误标识用于指示所述单播连接建立异常的原因；
    处理单元，用于根据所述第二消息确定所述第二设备与所述第一设备之间单播连接建立异常；
    所述处理单元，还用于根据所述错误标识执行异常处理操作。
  27. 根据权利要求26所述的装置，其特征在于，所述处理单元，具体用于：
    在所述错误标识指示所述第一MAC地址有冲突时，重新选择所述第一MAC地址。
  28. 根据权利要求26或27所述的装置，其特征在于，所述处理单元，具体用于：
    在所述错误标识指示所述安全机制与所述第一设备支持的安全机制不匹配时，重新选择所述安全机制。
  29. 根据权利要求26-28任一项所述的装置，其特征在于，所述处理单元，具体用于：
    当所述至少一个MAC地址为所述第一MAC地址且所述至少一个地址标识为所述第一地址标识时，确定所述第二设备与所述第一设备之间单播连接建立异常。
  30. 根据权利要求29所述的装置，其特征在于，所述第二消息中携带至少一个MAC地址、至少一个地址标识和错误标识，包括：
    所述至少一个MAC地址由所述第二消息的目的MAC地址字段承载；
    所述至少一个地址标识和错误标识承载于所述第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段，或者，所述至少一个地址标识和错误标识承载于所述第二消息的所述DSA消息帧中的应用扩展域Application Extension字段。
  31. 根据权利要求26-28任一项所述的装置，其特征在于，所述第二消息还包括专用应用标识，所述专用应用标识用于指示所述单播连接建立异常，所述专用应用标识承载于所述第二消息的专用短消息DSM消息帧中的应用标识AID字段，所述处理单元，具体用于：
    当所述第二消息的目的MAC地址字段承载的内容包括所述专用应用标识的转化值，以及所述至少一个MAC地址包括所述第一MAC地址且所述至少一个地址标识包括所述第一地 址标识时，确定所述第二设备与所述第一设备之间单播连接建立异常。
  32. 根据权利要求31所述的装置，其特征在于，所述第二消息中携带至少一个MAC地址、至少一个地址标识和错误标识，包括：
    所述至少一个MAC地址、所述至少一个地址标识和错误标识承载于所述第二消息的专用业务公告DSA消息帧中的头扩展域Header Extension字段；或者
    所述至少一个MAC地址、所述至少一个地址标识和错误标识承载于所述第二消息的所述DSA消息帧中的应用扩展域Application Extension字段。
  33. 根据权利要求26-31任一项所述的装置，其特征在于，在所述第一消息中，所述第一地址标识由所述第一消息的专用业务公告DSA消息帧中的DSA标识DSA Identifier字段和内容计数Content Count字段中的至少一者承载。
  34. 根据权利要求26-31任一项所述的装置，其特征在于，在所述第一消息中，所述第一地址标识承载于所述第一消息的专用业务公告DSA消息帧的头扩展域Header Extension字段中。
  35. 一种用于处理单播连接建立异常的装置，其特征在于，所述装置包括存储器和处理器，所述存储器存储计算机程序指令，所述处理器运行所述计算机程序指令以使所述装置执行如权利要求1-8任一项所述的方法。
  36. 一种用于处理单播连接建立异常的装置，其特征在于，所述装置包括存储器和处理器，所述存储器存储计算机程序指令，所述处理器运行所述计算机程序指令以使所述装置执行如权利要求9-17任一项所述的方法。
  37. 一种计算机可读存储介质，其特征在于，包括计算机指令，当所述计算机指令在被处理器运行时，实现如权利要求1-8任一项所述的方法。
  38. 一种计算机可读存储介质，其特征在于，包括计算机指令，当所述计算机指令在被处理器运行时，实现如权利要求9-17任一项所述的方法。
  39. 一种车辆，其特征在于，所述车辆包括如权利要求18-25或35所述的装置，或者，所述车辆包括如权利要求26-34或36所述的装置。
  40. 一种单播连接建立异常处理系统，其特征在于，所述系统包括第一设备和第二设备，其中，所述第一设备用于执行如权利要求1-8所述的方法，所述第二设备用于执行如权利要求9-17所述的方法。
  41. 一种计算机程序产品，其特征在于，包括计算机指令，当所述计算机指令在处理器上运行时，实现如权利要求1-8或者9-17任一项所述的方法。
PCT/CN2022/104228 2021-08-19 2022-07-06 一种单播连接建立异常处理方法及装置 Ceased WO2023020148A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP22857461.2A EP4366342B1 (en) 2021-08-19 2022-07-06 Method and apparatus for processing exception in unicast connection establishment
US18/426,254 US12615692B2 (en) 2021-08-19 2024-01-29 Method and apparatus for handling unicast connection establishment abnormality

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110955602.2A CN115708370B (zh) 2021-08-19 2021-08-19 一种单播连接建立异常处理方法及装置
CN202110955602.2 2021-08-19

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/426,254 Continuation US12615692B2 (en) 2021-08-19 2024-01-29 Method and apparatus for handling unicast connection establishment abnormality

Publications (1)

Publication Number Publication Date
WO2023020148A1 true WO2023020148A1 (zh) 2023-02-23

Family

ID=85212609

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/104228 Ceased WO2023020148A1 (zh) 2021-08-19 2022-07-06 一种单播连接建立异常处理方法及装置

Country Status (4)

Country Link
US (1) US12615692B2 (zh)
EP (1) EP4366342B1 (zh)
CN (1) CN115708370B (zh)
WO (1) WO2023020148A1 (zh)

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US12273782B2 (en) 2020-04-02 2025-04-08 Interdigital Patent Holdings, Inc. Methods, apparatus and systems for command and control (C2) communications setup and update
JP7792181B2 (ja) * 2023-07-18 2025-12-25 インターデイジタル パテント ホールディングス インコーポレイテッド 無線送信／受信ユニット（ｗｔｒｕ）リレー媒体アクセス制御（ｍａｃ）アクセス競合サポートのためのｗｔｒｕ
US12335229B2 (en) 2023-07-18 2025-06-17 Interdigital Patent Holdings, Inc. Wireless transmit/receive unit (WTRU) to WTRU relay media access control (MAC) access conflict support
WO2025019402A1 (en) * 2023-07-18 2025-01-23 Interdigital Patent Holdings, Inc. Wireless transmit/receive unit (wtru) to wtru relay media access control (mac) access conflict support
KR20250054831A (ko) 2023-07-18 2025-04-23 인터디지탈 패튼 홀딩스, 인크 무선 송수신 유닛(wtru) 대 wtru 릴레이 미디어 액세스 제어(mac) 액세스 충돌 지원

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106603740A (zh) * 2016-12-07 2017-04-26 广东欧珀移动通信有限公司 网络连接异常的处理方法与终端设备
CN111278165A (zh) * 2019-01-11 2020-06-12 维沃移动通信有限公司 连接建立方法、终端设备及网络设备
CN111866796A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 用于获取无线承载配置的方法和装置
CN112118326A (zh) * 2019-06-20 2020-12-22 上海诺基亚贝尔股份有限公司 Mac地址冲突检测方法、设备、装置和计算机可读存储介质

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070104109A1 (en) * 2005-11-04 2007-05-10 Innovative Sonic Limited Method and apparatus for RLC protocol error handling in a wireless communications system
EP3151599A1 (en) * 2015-09-30 2017-04-05 Apple Inc. Authentication failure handling for cellular network access through wlan
CN114727328B (zh) * 2018-12-14 2024-11-29 华为技术有限公司 一种故障确定方法及装置
EP4593471A3 (en) * 2019-01-10 2025-10-01 Samsung Electronics Co., Ltd. Method and apparatus for performing communication in wireless communication system
WO2020150495A1 (en) * 2019-01-16 2020-07-23 Apple Inc. Sideline connection establishment design to support unicast and groupcast communication for nr v2x
CN109982450B (zh) * 2019-02-19 2020-09-29 生迪智慧科技有限公司 通信链路修复方法、装置、协调器及系统
CN110248347B (zh) * 2019-06-28 2022-03-15 Oppo广东移动通信有限公司 通话异常检测方法、装置、设备及存储介质
US20210227620A1 (en) * 2020-01-21 2021-07-22 Asustek Computer Inc. Method and apparatus for configuring sidelink discontinuous reception in a wireless communication system

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106603740A (zh) * 2016-12-07 2017-04-26 广东欧珀移动通信有限公司 网络连接异常的处理方法与终端设备
CN111278165A (zh) * 2019-01-11 2020-06-12 维沃移动通信有限公司 连接建立方法、终端设备及网络设备
CN111866796A (zh) * 2019-04-30 2020-10-30 华为技术有限公司 用于获取无线承载配置的方法和装置
CN112118326A (zh) * 2019-06-20 2020-12-22 上海诺基亚贝尔股份有限公司 Mac地址冲突检测方法、设备、装置和计算机可读存储介质

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4366342A4

Also Published As

Publication number Publication date
US12615692B2 (en) 2026-04-28
CN115708370A (zh) 2023-02-21
CN115708370B (zh) 2026-03-17
EP4366342B1 (en) 2025-10-01
EP4366342A1 (en) 2024-05-08
US20240172330A1 (en) 2024-05-23
EP4366342A4 (en) 2024-11-06

Similar Documents

Publication Publication Date Title
WO2023020148A1 (zh) 一种单播连接建立异常处理方法及装置
CN104871637B (zh) 代理连接方法和装置
EP3893530B1 (en) Communication method and communication device
US9736876B1 (en) Method and apparatus for establishing links and maintaining consistent link information between stations
WO2023001307A1 (zh) 旁链路通信方法及设备
US20240244408A1 (en) Communication method and apparatus, and related device
CN116158187A (zh) 多链路设备的aid分配方法及相关装置
CN121464708A (zh) 感测数据交换
US10812545B2 (en) Beacon sensor advertisement frame
WO2021114043A1 (zh) 设备到设备的通信方法和通信装置
WO2023065999A1 (zh) 一种数据传输方法及相关装置
WO2018137209A1 (zh) 一种业务数据传输方法、第一通信节点及基站
US20220030400A1 (en) Data Sending Method and Apparatus, and Computer-Readable Storage Medium
CN110224803B (zh) 一种实现beacon自主发现的LoRa通信方法
WO2019226098A1 (en) Methods, transmitting node and receiving user equipment for handling a pdu based on 3gpp release, version or feature
CN112640495B (zh) 针对组播业务的配置管理方法及相关产品
EP4639997A1 (en) Communication apparatus and communication method for enhanced tunnelled direct link setup
KR20060059326A (ko) 인터넷 접속 서비스를 위한 ｄｓｒｃ 단말기 및 기지국의브릿지 방법 및 장치
EP4566347A1 (en) Systems and methods for facilitating ue route selection policy rule enforcement

Legal Events

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

Ref document number: 22857461

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2022857461

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2022857461

Country of ref document: EP

Effective date: 20240130

NENP Non-entry into the national phase

Ref country code: DE

WWG Wipo information: grant in national office

Ref document number: 2022857461

Country of ref document: EP