Method, apparatus and user equipment for id collision handling in internet of vehicles

Abstract

This application discloses an ID collision handling method, apparatus, and user equipment in the Internet of Vehicles (IoV) field, applied in the field of communications. The method is applied to a first user equipment and includes, after sending a pass-through link establishment request message, receiving pass-through link establishment acceptance messages from at least two second user equipments; if source ID collisions exist between at least two second user equipments, either abandoning link establishment with the at least two second user equipments with source ID collisions, or establishing a link with one of the at least two second user equipments with source ID collisions. This avoids ID collisions during pass-through link establishment and provides standardized avoidance processing for ID collisions that may occur during pass-through link establishment.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to an ID collision processing method, apparatus and user equipment in the Internet of Vehicles. Background Technology

[0002] Currently, User Equipment (UE) A can establish a unicast link with UE B and then establish a unicast link with UE C, and UE C is allowed to use the same source ID as UE B. In this case, UE A can avoid collisions by using UE A's source ID. That is, UE A can uniquely identify a unicast link by using the source ID and the target ID.

[0003] However, when UE B and UE C simultaneously participate in the unicast establishment process based on the service ID of UE A, it is necessary to avoid ID conflicts caused by the same source ID in the Direct Communication Accept message (based on the service) sent by UE B and UE C. Current standards identify source ID collision issues during the direct link establishment process, but there is currently no standardized solution to avoid them. Summary of the Invention

[0004] The purpose of this application is to provide an ID collision handling method, device and user equipment in the Internet of Vehicles, thereby solving the problem that the existing technology does not have a standardized avoidance process for source ID collision during the establishment of a pass-through link.

[0005] In a first aspect, embodiments of this application provide an ID collision processing method applied to a first user equipment, the method comprising:

[0006] After sending a direct link establishment request message, receive at least two direct link establishment acceptance messages sent by second user equipment;

[0007] If at least two second user equipments have source ID collisions, the link establishment with the at least two second user equipments with source ID collisions shall be abandoned, or a link establishment shall be performed with one of the at least two second user equipments with source ID collisions.

[0008] Optionally, the method further includes:

[0009] If the source IDs in at least two received direct link establishment acceptance messages are the same and the difference between the two sequence numbers is greater than a preset threshold, it is determined that the second user equipment that sent the at least two direct link establishment acceptance messages has a source ID collision.

[0010] Optionally, if at least two second user equipments have source ID collisions, the link establishment with at least two second user equipments with source ID collisions is abandoned, including at least one of the following:

[0011] Release the maintained context information of the at least two second user devices with source ID collisions, and stop maintaining the context information of the at least two second user devices with source ID collisions.

[0012] Send a link release request to at least two second user equipments where source ID collision exists.

[0013] Optionally, when establishing a link with one of the at least two second user equipments that have a source ID collision, the method further includes at least one of the following:

[0014] In the at least two second user equipments where source ID collision exists, the relevant context information of the second user equipment that established the link with the first user equipment is passed to the underlying layer of the first user equipment;

[0015] In the at least two second user equipments where source ID collision exists, the relevant context information maintained by the second user equipment that the first user equipment abandoned link establishment is released, and the relevant context information of the second user equipment that the first user equipment abandoned link establishment is no longer maintained;

[0016] Send a link release request to the second user equipment that has given up establishing a link with the first user equipment.

[0017] Optionally, in the case of source ID collision between at least two second user equipments, link establishment is performed with one of the at least two second user equipments with source ID collision, including:

[0018] Send a first direct link establishment response / acknowledgment message, wherein the first direct link establishment response / acknowledgment message includes the sequence number of the second user equipment that established the link with the first user equipment among the at least two second user equipments that have source ID collisions.

[0019] Optionally, the method further includes:

[0020] Send a second direct link response / acknowledgment message, wherein the second direct link establishment response / acknowledgment message includes the serial number of the second user equipment where there is no source ID collision.

[0021] Optionally, in the case of source ID collision between at least two second user equipments, link establishment is performed with one of the at least two second user equipments with source ID collision, including:

[0022] Send a third direct link establishment response / acknowledgment message, wherein the third direct link establishment response / acknowledgment message includes the sequence number of each second user equipment determined by the first user equipment to establish the link, wherein each second user equipment includes one of at least two second user equipments with source ID collision, and a second user equipment without source ID collision.

[0023] Secondly, embodiments of this application also provide an ID collision processing method applied to a second user equipment, the method comprising:

[0024] After receiving a pass-through link establishment request message from a first user equipment, a pass-through link establishment acceptance message is sent to the first user equipment. The pass-through link establishment acceptance message is used to enable the first user equipment to determine whether there is a source ID collision between at least two second user equipments.

[0025] Optionally, the method further includes:

[0026] Receive a link release request sent by the first user equipment for at least two second user equipments where there is a source ID collision.

[0027] Optionally, the method further includes:

[0028] Receive a link release request from the first user equipment, requesting the second user equipment to abandon link establishment.

[0029] Optionally, the method further includes:

[0030] The system receives a first direct link establishment response / acknowledgment message sent by the first user equipment. The first direct link establishment response / acknowledgment message includes a sequence number, which is the sequence number of the second user equipment that establishes a link with the first user equipment among at least two second user equipments that have source ID collisions.

[0031] If the serial number is a serial number in the serial number set maintained by the second user equipment, the relevant context information of the first user equipment is passed to the underlying layer of the second user equipment.

[0032] Optionally, the method further includes:

[0033] The system receives a second direct link establishment response / acknowledgment message sent by the first user equipment, the second direct link establishment response / acknowledgment message including the serial number of the second user equipment in which there is no source ID collision.

[0034] Optionally, the method further includes:

[0035] The system receives a third direct link establishment response / acknowledgment message sent by the first user equipment, wherein the third direct link establishment response / acknowledgment message includes the sequence number of each second user equipment determined by the first user equipment to establish the link, wherein each second user equipment includes one of at least two second user equipments with source ID collisions, and a second user equipment without source ID collisions.

[0036] Thirdly, embodiments of this application also provide a user equipment, including a transceiver, a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that the processor, when executing the computer program, implements the ID collision processing method as described in the first aspect, or the ID collision processing method as described in the second aspect.

[0037] Fourthly, embodiments of this application also provide an ID collision processing apparatus, applied to a first user equipment, comprising:

[0038] The receiving module is used to receive at least two direct link establishment acceptance messages sent by second user equipment after sending a direct link establishment request message;

[0039] The first processing module is configured to either abandon link establishment with at least two second user equipments that have source ID collisions, or establish a link with one of the at least two second user equipments that have source ID collisions, in the event that at least two second user equipments have source ID collisions.

[0040] Fifthly, embodiments of this application also provide an ID collision processing apparatus, applied to a second user equipment, comprising:

[0041] The first sending module is configured to send a direct link establishment acceptance message to the first user equipment after receiving a direct link establishment request message sent by the first user equipment.

[0042] Sixthly, embodiments of this application also provide a computer-readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, implements the ID collision processing method as described in the first aspect, or the ID collision processing method as described in the second aspect.

[0043] The above-mentioned technical solution of this application has at least the following beneficial effects:

[0044] The ID collision handling method in this application embodiment firstly involves a first user equipment receiving direct link establishment acceptance messages from at least two second user equipments after sending a direct link establishment request message. Secondly, if source ID collisions exist between at least two second user equipments, the method either abandons link establishment with the two second user equipments experiencing source ID collisions, or establishes a link with one of the two second user equipments experiencing source ID collisions. This avoids ID collisions during direct link establishment and provides standardized avoidance processing for ID collisions that may occur during direct link establishment. Attached Figure Description

[0045] Figure 1 This is one of the flowcharts illustrating the ID collision handling method according to an embodiment of this application;

[0046] Figure 2 This is a second schematic flowchart of the ID collision handling method according to an embodiment of this application;

[0047] Figure 3 This is one of the structural schematic diagrams of the ID collision processing device according to an embodiment of this application;

[0048] Figure 4 This is a second schematic diagram of the structure of the ID collision processing device according to an embodiment of this application;

[0049] Figure 5 This is a schematic diagram of the structure of a user equipment according to an embodiment of this application. Detailed Implementation

[0050] To make the technical problems, technical solutions, and advantages of this application clearer, a detailed description will be provided below in conjunction with the accompanying drawings and specific embodiments. In the following description, specific details such as particular configurations and components are provided merely to aid in a comprehensive understanding of the embodiments of this application. Therefore, those skilled in the art should understand that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of this application. Furthermore, for clarity and brevity, descriptions of known functions and structures have been omitted.

[0051] It should be understood that the phrase "one embodiment" or "an embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of this application. Therefore, "in one embodiment" or "in an embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0052] In the various embodiments of this application, it should be understood that the sequence number of each process described below does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0053] In the embodiments provided in this application, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined based on A. However, it should also be understood that determining B based on A does not mean determining B solely based on A; B can also be determined based on A and / or other information.

[0054] like Figure 1 The diagram shown is one of the flowcharts illustrating an ID collision handling method according to an embodiment of this application. This method is applied to a first user equipment and includes:

[0055] Step 101: After sending a Direct Link Establishment Request message, receive Direct Link Establishment Acceptance messages from at least two second user equipments;

[0056] It should be noted here that the message received for establishing a direct link is a PC-5 message.

[0057] Step 102: If at least two second user equipments have source ID collisions, abandon link establishment with at least two second user equipments with source ID collisions, or establish a link with one of the at least two second user equipments with source ID collisions.

[0058] The ID collision handling method in this application embodiment firstly involves a first user equipment receiving direct link establishment acceptance messages from at least two second user equipments after sending a direct link establishment request message. Secondly, if source ID collisions exist between at least two second user equipments, the method either abandons link establishment with the two second user equipments experiencing source ID collisions, or establishes a link with one of the two second user equipments experiencing source ID collisions. This avoids ID collisions during direct link establishment and provides standardized avoidance processing for ID collisions that may occur during direct link establishment.

[0059] Furthermore, as an optional implementation, the method also includes:

[0060] If the source IDs in at least two Direct Link Establishment Acceptance messages are the same and the difference between the two sequence numbers is greater than a preset threshold, it is determined that the second user equipment that sent the at least two Direct Link Establishment Acceptance messages has a source ID collision.

[0061] In other words, the first user equipment can determine whether multiple second user equipments are the same user equipment based on the sequence number (SN) in the direct link establishment acceptance (DIRECT LINK ESTABLISHMENT ACCEPT) messages sent by multiple second user equipments, thereby determining whether there is a source ID collision among the multiple second user equipments.

[0062] It should be noted here that, since the SN in the Direct Link Establishment Acceptance (DIRECT LINK ESTABLISHMENT ACCEPT) message sent by the second user equipment is randomly generated, in order to avoid being mistakenly identified as different second user equipments due to different SNs in the same Direct Link Establishment Acceptance (DIRECT LINK ESTABLISHMENT ACCEPT) messages sent repeatedly by the same second user equipment due to link anomalies, this optional implementation method determines whether there is a source ID collision of the second user equipment by comparing the difference of the SNs in different Direct Link Establishment Acceptance (DIRECT LINK ESTABLISHMENT ACCEPT) messages with a preset threshold value (for example, the preset threshold value is 3, or the preset threshold value is 0).

[0063] As an optional implementation, step 102, which involves abandoning link establishment with at least two second user equipments in the event of source ID collision, includes at least one of the following:

[0064] Release the maintained context information of the at least two second user devices with source ID collisions, and stop maintaining the context information of the at least two second user devices with source ID collisions.

[0065] Send a link release request to at least two second user equipments where source ID collision exists.

[0066] In other words, when the first user equipment determines that multiple second user equipments have source ID collisions and determines that it will not establish a direct link with the second user equipments with source ID collisions, the first user equipment will no longer maintain the relevant contexts of the second user equipments with source ID collisions and will release the maintained relevant contexts. In addition, it will send link release requests to at least two second user equipments with source ID collisions to stop the establishment of links between the first user equipment and at least two second user equipments with source ID collisions, thereby avoiding communication abnormalities caused by source ID collisions.

[0067] The ID collision handling method of this optional implementation will be explained below with specific examples, where UE A is the first user equipment, and UE B and UE C are the second user equipment:

[0068] First, in slot n, UE A broadcasts a Direct Link Establishment Request (DRLEF) message;

[0069] Second, in slot (n+x), UE B sends a Direct Link Establishment Acceptance message to UE A. The source ID in this message is 001, the SN is 005, and the Quality of Service (QoS) information matches the service requested by UE A.

[0070] Third, once UE A confirms that the link with UE B has been successfully established, it informs the underlying layer of UE A of the relevant context information of UE B.

[0071] Fourth, in slot (n+x+2), UE C sends a Direct Link Establishment Acceptance message to UE A. The source ID in this message is 001, the SN is 020, and the Quality of Service (QoS) information matches the service requested by UE A.

[0072] Fifth, UE A determines that UE B and UE C are different UEs by the difference in the serial numbers (SNs) in the two direct link acceptance signals (DIRECT LINK ESTABLISHMENT ACEPT). At this point:

[0073] UE A does not maintain context information for UE C, and at the same time releases the previously maintained context information for UE B;

[0074] UE A does not maintain context information for UE C, and simultaneously triggers link release requests for both UE B and UE C.

[0075] It should be noted here that {n, n+x, n+x+2, n+x+5} is just one example:

[0076] After UEA sends a Direct Link Establishment Request (DIRECT LINK ESTABLISHMENT REQUEST) message in slot n, both UE B and UE C will receive this message. Then, UE B and UE C will confirm the Direct Link Establishment Accept (DIRECT LINK ESTABLISHMENT ACCEPT) message. The specific timing of sending the DIRECT LINK ESTABLISHMENT ACCEPT message depends on the scheduling time of UE B and UE C. Here, slots (n+x) and (n+x+2) are merely examples to illustrate that the timing of the two UEs sending the DIRECT LINK ESTABLISHMENT ACCEPT message may differ.

[0077] As an optional implementation, in step 102, if a link is established with one of the at least two second user equipments that have a source ID collision, the method further includes at least one of the following:

[0078] In the at least two second user equipments where source ID collision exists, the relevant context information of the second user equipment that established the link with the first user equipment is passed to the underlying layer of the first user equipment;

[0079] In other words, when the first user equipment determines that at least two second user equipments have source ID collisions, the first user equipment can select one of the at least two second user equipments with source ID collisions to establish a link according to pre-set rules or its own implementation. On this basis, the first user equipment will pass the relevant context information of the second user equipment with which it establishes a link to the underlying layer of the first user equipment.

[0080] In the at least two second user equipments where source ID collision exists, the relevant context information maintained by the second user equipment that the first user equipment abandoned link establishment is released, and the relevant context information of the second user equipment that the first user equipment abandoned link establishment is no longer maintained;

[0081] That is, the first user equipment no longer maintains the relevant context information of the second user equipment with which it does not establish a link, so as to terminate the link establishment.

[0082] Send a link release request to the second user equipment that has given up establishing a link with the first user equipment.

[0083] The ID collision handling method of this optional implementation will be explained below with specific examples:

[0084] First, in slot n, UE A broadcasts a Direct Link Establishment Request (DRLEF) message;

[0085] Second, in slot (n+x), UE B sends a Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) message to UE A. The source ID in this message is 001, the SN is 005, and the QoS information matches the service requested by UE A.

[0086] Third, once UE A confirms that the link with UE B has been successfully established, it informs the underlying layer of UE A of the relevant context information of UE B.

[0087] Fourth, in slot (n+x+2), UE C sends a Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) message to UE A. The source ID in this message is 001, the SN is 020, and the QoS information matches the service requested by UE A.

[0088] Fifth, UE A determines that UE B and UE C are different UEs by the difference in the serial numbers (SNs) in the two direct link acceptance signals (DIRECT LINK ESTABLISHMENT ACEPT). At this point:

[0089] Sixth, UE A confirms the need to establish a unicast link with UE B, and UE A transmits the relevant context information of UE B internally to other UE A devices.

[0090] Seventh, UE A confirms that it will not establish a unicast link with UE C, UE A will not maintain the context information of UE C, and will release the relevant context information of UE C that was previously maintained, and trigger a link release request to UE C.

[0091] It should be noted here that {n, n+x, n+x+2, n+x+5} is just one example:

[0092] After UEA sends a Direct Link Establishment Request (DIRECT LINK ESTABLISHMENT REQUEST) message in slot n, both UE B and UE C will receive this message. Then, UE B and UE C will confirm the Direct Link Establishment Accept (DIRECT LINK ESTABLISHMENT ACCEPT) message. The specific timing of sending the DIRECT LINK ESTABLISHMENT ACCEPT message depends on the scheduling time of UE B and UE C. Here, slots (n+x) and (n+x+2) are merely examples to illustrate that the timing of the two UEs sending the DIRECT LINK ESTABLISHMENT ACCEPT message may differ.

[0093] As an optional implementation, step 102, in the case of source ID collision between at least two second user equipments, establishes a link with one of the at least two second user equipments with source ID collision, including:

[0094] Send a first direct link establishment response / acknowledgment message, wherein the first direct link establishment response / acknowledgment message includes the sequence number of the second user equipment that established the link with the first user equipment among the at least two second user equipments that have source ID collisions.

[0095] In other words, this optional implementation involves adding two handshake processes during the direct link establishment process and including the identifier of the second user equipment in the direct link establishment response / acknowledgment message sent by the first user equipment. This allows the first user equipment to determine the second user equipment to establish a direct link with, thus ensuring that the first user equipment establishes a link with only one of the at least two second user equipments that have source ID collisions. This solves the source ID collision problem and provides a standardized avoidance method for the source ID collision problem.

[0096] The ID collision handling method of this optional implementation will be explained below, taking the establishment of a unicast link as an example:

[0097] First, in slot n, UE A broadcasts a Direct Link Establishment Request (DIRECT LINK ESTABLISHMENT REQUEST) message;

[0098] Second, in slot (n+x), UEB sends a Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) message to UEB. The source ID in this message is 001, the SN is 005, and the QoS information matches the service requested by UEB.

[0099] Third, in slot (n+x+2), UE C sends a Direct Link Establishment Accept (DIRECT LINK ESTABLISHMENT ACCEPT) message. The source ID in this message is 001, the SN is 020, and the QoS information matches the service requested by UE A.

[0100] Fourth, in slot (n+x+2), UE A parses the Direct Link Establishment Accept message sent by UE B; UE A confirms that it needs to establish a unicast link with UE B;

[0101] Fifth, in slot (n+x+5), UE A sends a Direct Link Establishment Acknowledgment (DIRECT LINKESTABLISHMENT ACK) message to UE B. This message contains the SN from the Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) message sent by UE B. UE A then passes on the relevant context information of UE B internally.

[0102] Sixth, in slot (n+x+2+2), UE A parses the Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) message sent by UE C; based on the difference in SN in the Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) messages sent by UE B and UE C, UE A determines that UE B and UE C are different UEs, and UE A abandons the unicast link establishment with UE C;

[0103] Seventh, if UE B receives the first direct link establishment acknowledgment (DIRECT LINKESTABLISHMENT ACK) message sent by UE A, and the SN in the message is one of the SN sets that UE B maintains and sends to UE A, then the unicast link is considered to be successfully established, and the relevant context information of UE A is passed down within UE B.

[0104] Eighth, if UE C receives the first direct link establishment acknowledgment (DIRECT LINKESTABLISHMENT ACK) message sent by UE A, but the SN in the received message is not one of the SN sets it maintains and sends to UE A, then it considers the unicast link establishment to have failed.

[0105] It should be noted here that {n, n+x, n+x+2, n+x+5} is just one example:

[0106] On one hand, typically UE A sends a data packet in slot n. UE B receives it at the end of slot n, processes it, and parses it after several slots. Then, based on the parsed content, UE B determines whether to send a direct link establishment accept message or a direct link establishment reject message (this response is a PC5-S message, not much different from a service packet, and also requires scheduling). Therefore, UE B selects a resource and sends it out in the corresponding slot. Considering processing and scheduling, the actual time is longer. Here, UE C sends in slot (n+x+2), and UE A starts parsing in slot (n+x+2). The specific completion depends on the UE's capabilities; parsing in slot (n+x+2) is just an example.

[0107] On the other hand, in slot (n+x+5), UE A sends a Direct Link Establishment Acknowledgment (DIRECT LINKESTABLISHMENT ACK) message. This message is a scheduling result, and this is just an example. After parsing in slot (n+x+2) and determining which message to send, the packet is assembled and delivered from the higher layer down, triggering the lower layer. The specific timing here is just an example.

[0108] Furthermore, as an optional implementation, after the first user equipment sends the first direct link establishment acknowledgment / acknowledgment message, the method further includes:

[0109] Send a second direct link response / acknowledgment message, wherein the second direct link establishment response / acknowledgment message includes the serial number of the second user equipment where there is no source ID collision.

[0110] It should be noted that since the first user equipment sends the first direct link establishment response / acknowledgment message via broadcast, the second user equipment, which does not have a source ID collision, will also receive the first direct link establishment response / acknowledgment message. In order to avoid the second user equipment, which does not have a source ID collision, misjudging that the direct link establishment with the first user equipment has failed, this optional implementation will send a second direct link response / acknowledgment message after sending the first direct link response / acknowledgment message, so that the second user equipment, which does not have a source ID collision, can establish a link with the first user equipment based on the second direct link response / acknowledgment message.

[0111] As an optional implementation, step 102, in the case of source ID collision between at least two second user equipments, establishes a link with one of the at least two second user equipments with source ID collision, including:

[0112] Send a third direct link establishment response / acknowledgment message, wherein the third direct link establishment response / acknowledgment message includes the sequence number of each second user equipment determined by the first user equipment to establish the link, wherein each second user equipment includes one of at least two second user equipments with source ID collision, and a second user equipment without source ID collision.

[0113] In this optional implementation, the third direct link establishment response / acknowledgment message includes multiple sequence numbers. The second user equipment corresponding to each sequence number is the user equipment that needs to establish a link with the first user equipment. Thus, the second user equipment only needs to send the third direct link establishment response / acknowledgment message to determine whether to establish a direct link with the first user equipment based on the sequence number in the third direct link establishment response / acknowledgment message.

[0114] The ID collision handling method of this optional implementation will be explained below, taking the establishment of a unicast link as an example:

[0115] First, in slot n, UE A broadcasts a Direct Link Establishment Request (DIRECT LINK ESTABLISHMENT REQUEST) message;

[0116] Second, in slot (n+x), UEB sends a Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) message to UEB. The source ID in this message is 001, the SN is 005, and the QoS information matches the service requested by UEB.

[0117] Third, in slot (n+x+2), UE C sends a Direct Link Establishment Accept (DIRECT LINK ESTABLISHMENT ACCEPT) message. The source ID in this message is 001, the SN is 020, and the QoS information matches the service requested by UE A.

[0118] Fifth, in slot (n+x+2), UE A parses the Direct Link Establishment Accept message sent by UE B; UE A confirms that it needs to establish a unicast link with UE B;

[0119] Sixth, in slot (n+x+2+2), UE A parses the Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) message sent by UE C; based on the difference in SN in the Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) messages sent by UE B and UE C, UE A determines that UE B and UE C are different UEs, and UE A abandons the unicast link establishment with UE C;

[0120] Seventh, in slot (n+x+5), UE A sends a Direct Link Establishment Acknowledgment (DIRECT LINKESTABLISHMENT ACK) message to UE B. This message contains the SN from the Direct Link Establishment Acceptance (DIRECTLINK ESTABLISHMENT ACCEPT) messages sent by each second user equipment (including UE B and second user equipment without source ID collision (such as UE D)) that have established a direct link with UE A. UE A then forwards the relevant context information of UE B and the second user equipment without source ID collision within UE A.

[0121] Eighth, if UE B and the second user equipment where there is no source ID collision receive the third direct link establishment acknowledgment (DIRECT LINK ESTABLISHMENT ACK) message sent by UE A, and the SN in the message includes one of the SN sets maintained by UE B and sent to UE A, then the unicast link is considered to be successfully established, and the relevant context information of UE A is passed down within UE B and the second user equipment where there is no source ID collision.

[0122] Ninth, if UE C receives a direct link establishment acknowledgment (DIRECT LINKESTABLISHMENT ACK) message from UE A, but the SN in the received message does not include one of the SN sets it maintains and sends to UE A, then it considers the unicast link establishment to have failed.

[0123] It should be noted here that {n, n+x, n+x+2, n+x+5} is just one example:

[0124] On one hand, typically UE A sends a data packet in slot n. UE B receives it at the end of slot n, processes it, and parses it after several slots. Then, based on the parsed content, UE B determines whether to send a direct link establishment accept message or a direct link establishment reject message (this response is a PC5-S message, not much different from a service packet, and also requires scheduling). Therefore, UE B selects a resource and sends it out in the corresponding slot. Considering processing and scheduling, the actual time is longer. Here, UE C sends in slot (n+x+2), and UE A starts parsing in slot (n+x+2). The specific completion depends on the UE's capabilities; parsing in slot (n+x+2) is just an example.

[0125] On the other hand, in slot (n+x+5), UE A sends a Direct Link Establishment Acknowledgment (DIRECT LINKESTABLISHMENT ACK) message. This message is a scheduling result, and this is just an example. After parsing in slot (n+x+2) and determining which message to send, the packet is assembled and delivered from the higher layer down, triggering the lower layer. The specific timing here is just an example.

[0126] like Figure 2 The diagram shown is a second flowchart of an ID collision handling method according to an embodiment of this application. This method is applied to a second user equipment and includes:

[0127] After receiving a pass-through link establishment request message from a first user equipment, a pass-through link establishment acceptance message is sent to the first user equipment. The pass-through link establishment acceptance message is used to enable the first user equipment to determine whether there is a source ID collision between at least two second user equipments.

[0128] In the ID collision handling method of this application embodiment, after receiving a pass-through link establishment request message sent by a first user equipment, the second user equipment sends a pass-through link establishment acceptance message to the first user equipment. The pass-through link establishment acceptance message is used to enable the first user equipment to determine whether at least two second user equipments have source ID collisions. This avoids ID collisions during the pass-through link establishment process and provides standardized avoidance processing for ID collisions that may occur during pass-through link establishment.

[0129] Furthermore, as an optional implementation, the method also includes:

[0130] Receive a link release request sent by the first user equipment for at least two second user equipments where there is a source ID collision.

[0131] When the first user equipment determines that at least two second user equipments have source ID collisions, the first user equipment will not establish a link with the second user equipments with source ID collisions. At this time, the first user equipment sends a link release request to the second user equipment to release the link between the at least two second user equipments with source ID collisions, thereby abandoning the link establishment with the at least two second user equipments with source ID collisions.

[0132] Furthermore, as an optional implementation, the method also includes:

[0133] Receive a link release request from the first user equipment, requesting the second user equipment to abandon link establishment.

[0134] When the first user equipment determines that at least two second user equipments have source ID collisions, the first user equipment determines to establish a link with one of the at least two second user equipments with source ID collisions. At this time, the first user equipment sends a link release request to the second user equipment to release the link of the second user equipment that the first user equipment abandoned the link establishment with among the at least two second user equipments with source ID collisions.

[0135] Furthermore, as an optional implementation, the method also includes:

[0136] The system receives a first direct link establishment response / acknowledgment message sent by the first user equipment. The first direct link establishment response / acknowledgment message includes a sequence number, which is the sequence number of the second user equipment that establishes a link with the first user equipment among at least two second user equipments that have source ID collisions.

[0137] If the serial number is a serial number in the serial number set maintained by the second user equipment, the relevant context information of the first user equipment is passed to the underlying layer of the second user equipment.

[0138] The ID collision handling method of this optional implementation will be explained below, taking the establishment of a unicast link as an example:

[0139] First, in slot n, UE A broadcasts a Direct Link Establishment Request (DIRECT LINK ESTABLISHMENT REQUEST) message;

[0140] Second, in slot (n+x), UEB sends a Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) message to UEB. The source ID in this message is 001, the SN is 005, and the QoS information matches the service requested by UEB.

[0141] Third, in slot (n+x+2), UE C sends a Direct Link Establishment Accept (DIRECT LINK ESTABLISHMENT ACCEPT) message. The source ID in this message is 001, the SN is 020, and the QoS information matches the service requested by UE A.

[0142] Fourth, in slot (n+x+2), UE A parses the Direct Link Establishment Accept message sent by UE B; UE A confirms that it needs to establish a unicast link with UE B;

[0143] Fifth, in slot (n+x+5), UE A sends the first Direct Link Establishment Acknowledgment (DIRECT LINKESTABLISHMENT ACK) message to UE B. This message contains the SN from the Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) message sent by UE B. UE A then passes on the relevant context information of UE B internally.

[0144] Sixth, in slot (n+x+2+2), UE A parses the Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) message sent by UE C; based on the difference in SN in the Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) messages sent by UE B and UE C, UE A determines that UE B and UE C are different UEs, and UE A abandons the unicast link establishment with UE C;

[0145] Seventh, if UE B receives the first direct link establishment acknowledgment (DIRECT LINKESTABLISHMENT ACK) message sent by UE A, and the SN in the message is one of the SN sets that UE B maintains and sends to UE A, then the unicast link is considered to be successfully established, and the relevant context information of UE A is passed down within UE B.

[0146] Eighth, if UE C receives the first direct link establishment acknowledgment (DIRECT LINKESTABLISHMENT ACK) message sent by UE A, but the SN in the received message is not one of the SN sets it maintains and sends to UE A, then it considers the unicast link establishment to have failed.

[0147] This optional implementation involves adding two handshake processes during the direct link establishment process and including the identifier of the second user equipment in the direct link establishment response / acknowledgment message sent by the first user equipment. This allows the second user equipment to determine whether to establish a link with the first user equipment based on the sequence number in the direct link establishment response / acknowledgment message. This solves the source ID collision problem and provides standardized avoidance processing for the source ID collision problem.

[0148] Furthermore, as an optional implementation, the method also includes:

[0149] The system receives a second direct link establishment response / acknowledgment message sent by the first user equipment, the second direct link establishment response / acknowledgment message including the serial number of the second user equipment in which there is no source ID collision.

[0150] By establishing a response / acknowledgment message through the second direct link, the problem of a second user equipment without source ID collision being mistakenly judged as having failed to establish a direct link with the first user equipment due to receiving the first direct link establishment response / acknowledgment message is avoided. This allows the second user equipment without source ID collision to establish a link with the first user equipment based on the second direct link response / acknowledgment message.

[0151] Furthermore, as an optional implementation, the method also includes:

[0152] The system receives a third direct link establishment response / acknowledgment message sent by the first user equipment, wherein the third direct link establishment response / acknowledgment message includes the sequence number of each second user equipment determined by the first user equipment to establish the link, wherein each second user equipment includes one of at least two second user equipments with source ID collisions, and a second user equipment without source ID collisions.

[0153] It should be noted that after receiving the third direct link response / acknowledgment message, the second user equipment determines whether the link connection with the first user equipment has been successfully established based on the sequence number in the third direct link response / acknowledgment message.

[0154] The following explanation uses unicast link establishment as an example to illustrate this optional implementation method:

[0155] First, in slot n, UE A broadcasts a Direct Link Establishment Request (DIRECT LINK ESTABLISHMENT REQUEST) message;

[0156] Second, in slot (n+x), UEB sends a Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) message to UEB. The source ID in this message is 001, the SN is 005, and the QoS information matches the service requested by UEB.

[0157] Third, in slot (n+x+2), UE C sends a Direct Link Establishment Accept (DIRECT LINK ESTABLISHMENT ACCEPT) message. The source ID in this message is 001, the SN is 020, and the QoS information matches the service requested by UE A.

[0158] Fifth, in slot (n+x+2), UE A parses the Direct Link Establishment Accept message sent by UE B; UE A confirms that it needs to establish a unicast link with UE B;

[0159] Sixth, in slot (n+x+2+2), UE A parses the Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) message sent by UE C; based on the difference in SN in the Direct Link Establishment Acceptance (DIRECT LINKESTABLISHMENT ACCEPT) messages sent by UE B and UE C, UE A determines that UE B and UE C are different UEs, and UE A abandons the unicast link establishment with UE C;

[0160] Seventh, in slot (n+x+5), UE A broadcasts a Direct Link Establishment Acknowledgment (DIRECT LINKESTABLISHMENT ACK) message. This message contains the SN from the Direct Link Establishment Acceptance (DIRECTLINK ESTABLISHMENT ACCEPT) messages sent by each second user equipment (including UE B and second user equipment without source ID collision (such as UE D)) that have established a direct link with UE A. UE A then passes on the relevant context information of UE B and the second user equipment without source ID collision within UE A.

[0161] Eighth, if UE B and the second user equipment that does not have a source ID collision receive the third direct link establishment acknowledgment (DIRECT LINK ESTABLISHMENT ACK) message sent by UE A, and the SN in the message includes one of the SN sets that UE B maintains and sends to UE A, then the unicast link is considered to be successfully established, and the relevant context information of UE A is passed down within UE B and the second user equipment that does not have a source ID collision.

[0162] Ninth, if UE C receives a direct link establishment acknowledgment (DIRECT LINKESTABLISHMENT ACK) message from UE A, but the SN in the received message does not include one of the SN sets it maintains and sends to UE A, then it considers the unicast link establishment to have failed.

[0163] In this optional implementation, the third direct link establishment response / acknowledgment message includes multiple sequence numbers. The second user equipment corresponding to each sequence number is the user equipment that needs to establish a link with the first user equipment. Thus, the second user equipment only needs to send the third direct link establishment response / acknowledgment message to determine whether to establish a direct link with the first user equipment based on the sequence number in the third direct link establishment response / acknowledgment message.

[0164] like Figure 3The diagram shown is one of the structural schematic diagrams of an ID collision processing device according to an embodiment of this application. The device is applied to a first user equipment and includes:

[0165] The receiving module 301 is used to receive at least two direct link establishment acceptance messages sent by second user equipment after sending a direct link establishment request message;

[0166] The first processing module 302 is configured to either abandon link establishment with at least two second user devices that have source ID collisions, or establish a link with one of the at least two second user devices that have source ID collisions, in the event that at least two second user devices have source ID collisions.

[0167] The ID collision handling apparatus of this application embodiment firstly receives direct link establishment acceptance messages from at least two second user equipments after sending a direct link establishment request message. Secondly, if at least two second user equipments have source ID collisions, the first processing module 302 either abandons link establishment with the at least two second user equipments with source ID collisions, or establishes a link with one of the at least two second user equipments with source ID collisions. This avoids ID collisions during direct link establishment and provides standardized avoidance processing for ID collisions that may occur during direct link establishment.

[0168] Optionally, the device further includes:

[0169] The determination module is used to determine that the second user equipment that sent the at least two direct link establishment and acceptance messages has a source ID collision if the source IDs in the received at least two direct link establishment and acceptance messages are the same and the difference between the two sequence numbers is greater than a preset threshold.

[0170] Optionally, when the first processing module 302 abandons link establishment with at least two second user equipments where source ID collisions exist, it is specifically used for at least one of the following:

[0171] Release the maintained context information of the at least two second user devices with source ID collisions, and stop maintaining the context information of the at least two second user devices with source ID collisions.

[0172] Send a link release request to at least two second user equipments where source ID collision exists.

[0173] Optionally, the device further includes:

[0174] The second processing module, when establishing a link with one of the at least two second user equipments that have a source ID collision, is specifically used for at least one of the following:

[0175] In the at least two second user equipments where source ID collision exists, the relevant context information of the second user equipment that established the link with the first user equipment is passed to the underlying layer of the first user equipment;

[0176] In the at least two second user equipments where source ID collision exists, the relevant context information maintained by the second user equipment that the first user equipment abandoned link establishment is released, and the relevant context information of the second user equipment that the first user equipment abandoned link establishment is no longer maintained;

[0177] Send a link release request to the second user equipment that has given up establishing a link with the first user equipment.

[0178] Optionally, when the first processing module 302 establishes a link with one of the at least two second user equipments where there is a source ID collision, it is specifically used for:

[0179] Send a first direct link establishment response / acknowledgment message, wherein the first direct link establishment response / acknowledgment message includes the sequence number of the second user equipment that established the link with the first user equipment among the at least two second user equipments that have source ID collisions.

[0180] Optionally, the device further includes:

[0181] The sending module is used to send a second direct link response / acknowledgment message, wherein the second direct link establishment response / acknowledgment message includes the serial number of the second user equipment in which there is no source ID collision.

[0182] Optionally, when the first processing module 302 establishes a link with one of the at least two second user equipments where a source ID collision exists, it is specifically configured to:

[0183] Send a third direct link establishment response / acknowledgment message, wherein the third direct link establishment response / acknowledgment message includes the sequence number of each second user equipment determined by the first user equipment to establish the link, wherein each second user equipment includes one of at least two second user equipments with source ID collision, and a second user equipment without source ID collision.

[0184] like Figure 4As shown in the illustration, this application also provides an ID collision processing device, applied to a second user equipment, comprising:

[0185] The first sending module 401 is used to send a direct link establishment acceptance message to the first user equipment after receiving the direct link establishment request message sent by the first user equipment.

[0186] In the ID collision handling apparatus of this application embodiment, after receiving a pass-through link establishment request message sent by a first user equipment, the sending module 401 sends a pass-through link establishment acceptance message to the first user equipment. The pass-through link establishment acceptance message is used to enable the first user equipment to determine whether there is a source ID collision between at least two second user equipments. This avoids the problem of ID collisions occurring during the pass-through link establishment process and provides standardized avoidance processing for ID collisions that may occur during the pass-through link establishment process.

[0187] Optionally, the device further includes:

[0188] The first receiving module is configured to receive a link release request sent by the first user equipment for at least two second user equipments where there is a source ID collision.

[0189] Optionally, the device further includes:

[0190] The second receiving module is used to receive a link release request sent by the first user equipment, in which the second user equipment abandons the link establishment process with the first user equipment.

[0191] Optionally, the device further includes:

[0192] The third receiving module is used to receive a first direct link establishment response / confirmation message sent by the first user equipment. The first direct link establishment response / confirmation message includes a sequence number, which is the sequence number of the second user equipment that establishes a link with the first user equipment among at least two second user equipments that have source ID collisions.

[0193] The second sending module is used to transmit relevant context information of the first user equipment to the underlying layer of the second user equipment when the serial number is a serial number in the serial number set maintained by the second user equipment.

[0194] Optionally, the device further includes:

[0195] The fourth receiving module is used to receive the second direct link establishment response / acknowledgment message sent by the first user equipment, wherein the second direct link establishment response / acknowledgment message includes the serial number of the second user equipment in which there is no source ID collision.

[0196] Optionally, the device further includes:

[0197] The fifth receiving module is used to receive a third direct link establishment response / acknowledgment message sent by the first user equipment, wherein the third direct link establishment response / acknowledgment message includes the sequence number of each second user equipment determined by the first user equipment to establish the link, wherein each second user equipment includes one of at least two second user equipments with source ID collision, and a second user equipment without source ID collision.

[0198] like Figure 5 As shown, this application embodiment also provides a user equipment, including a transceiver 510, a memory 520, a processor 500, and a computer program stored in the memory 520 and running on the processor 500. When the processor 500 executes the computer program, it implements the various processes of the ID collision processing method embodiment applied to the first user equipment as described above, or the various processes of the ID collision processing method embodiment applied to the second user equipment as described above. To avoid repetition, these will not be described again here.

[0199] Among them, Figure 5 In this context, the bus architecture can include any number of interconnected buses and bridges, specifically linking various circuits together, represented by one or more processors (processor 500) and memory (memory 520). The bus architecture can also link various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and therefore will not be described further herein. The bus interface provides an interface. The transceiver 510 can be multiple elements, including transmitters and transceivers, providing a unit for communicating with various other devices over a transmission medium. For different terminals, the user interface 530 can also be an interface capable of connecting external or internal devices, including but not limited to keypads, displays, speakers, microphones, joysticks, etc. The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 can store data used by the processor 500 during operation.

[0200] Those skilled in the art will understand that all or part of the steps of the above embodiments can be implemented by hardware or by a computer program instructing the relevant hardware to implement them. The computer program includes instructions to perform some or all of the steps of the above methods; and the computer program can be stored in a readable storage medium, which can be any form of storage medium.

[0201] In addition, this application embodiment also provides a computer-readable storage medium storing a program. When executed by a processor, this program implements the various processes of the ID collision processing method embodiment described above and achieves the same technical effect. To avoid repetition, it will not be described again here. The computer-readable storage medium may be a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, etc.

[0202] Furthermore, it should be noted that in the apparatus and method of this application, it is obvious that the components or steps can be decomposed and / or recombined. These decompositions and / or recombinations should be considered equivalent solutions of this application. Moreover, the steps performing the above series of processes can naturally be executed in the order described or in chronological order, but are not necessarily required to be executed in chronological order; some steps can be executed in parallel or independently of each other. Those skilled in the art will understand that all or any step or component of the method and apparatus of this application can be implemented in any computing device (including processors, storage media, etc.) or network of computing devices, in hardware, firmware, software, or a combination thereof. This is something that those skilled in the art can achieve by using their basic programming skills after reading the description of this application.

[0203] Therefore, the object of this application can also be achieved by running a program or a set of programs on any computing device. The computing device can be a known general-purpose device. Therefore, the object of this application can also be achieved simply by providing a program product containing program code implementing the method or apparatus. That is, such a program product also constitutes this application, and a storage medium storing such a program product also constitutes this application. Obviously, the storage medium can be any known storage medium or any storage medium developed in the future.

[0204] Finally, it should be noted that in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or terminal apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0205] The above description is the preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principles described in this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A method of ID collision handling, characterized by, The method is applied to a first user equipment, and comprises: After sending a sidelink establishment request message, receiving sidelink establishment accept messages sent by at least two second user equipments; wherein the sidelink establishment accept messages comprise randomly generated serial numbers; In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; 2. The method of claim 1, wherein, The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises:

3. The method of claim 1, wherein, In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises:

4. The method of claim 1, wherein, In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises:

5. The method of claim 4, wherein, In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two second user equipments having source ID collision, or performing link establishment with one of the at least two second user equipments having source ID collision; The method further comprises: In the case where source ID collision exists among the at least two second user equipments, giving up link establishment with the at least two sending a second sidelink setup response / acknowledgement message, wherein the second sidelink setup response / acknowledgement message comprises a sequence number of the second user equipment without source ID collision.

6. The method of claim 1, wherein, in case that at least two second user equipments have source ID collision, performing link setup with one of the at least two second user equipments having source ID collision, comprising: sending a third sidelink setup response / acknowledgement message, wherein the third sidelink setup response / acknowledgement message comprises a sequence number of each second user equipment determined by the first user equipment to perform link setup, wherein each second user equipment comprises one of the at least two second user equipments having source ID collision, and a second user equipment without source ID collision.

7. An ID collision processing method characterized by, applying to a second user equipment, comprising: after receiving a sidelink setup request message sent by a first user equipment, sending a sidelink setup accept message to the first user equipment, wherein the sidelink setup accept message comprises a randomly generated sequence number, and the sidelink setup accept message is used for the first user equipment to determine whether at least two second user equipments have source ID collision; wherein for at least two sidelink setup accept messages with same source ID, if a difference of the sequence numbers is less than or equal to a preset threshold value, the at least two sidelink setup accept messages are messages repeatedly sent by a same second user equipment, and if the difference of the sequence numbers is greater than the preset threshold value, the at least two sidelink setup accept messages are messages sent by different second user equipments.

8. The method of claim 7, wherein, the method further comprises: receiving a link release request sent by the first user equipment for the at least two second user equipments having source ID collision.

9. The method of claim 7, wherein, the method further comprises: receiving a link release request sent by the first user equipment for a second user equipment which the first user equipment gives up to perform link setup.

10. The method of claim 7, wherein, the method further comprises: receiving a first sidelink setup response / acknowledgement message sent by the first user equipment, wherein the first sidelink setup response / acknowledgement message comprises a sequence number, and the sequence number is a sequence number of a second user equipment which performs link setup with the first user equipment among the at least two second user equipments having source ID collision; in case that the sequence number is a sequence number in a sequence number set maintained by the second user equipment, delivering relevant context information of the first user equipment to an underlying layer of the second user equipment.

11. The method of claim 10, wherein, the method further comprises: receiving a second sidelink setup response / acknowledgement message sent by the first user equipment, wherein the second sidelink setup response / acknowledgement message comprises a sequence number of a second user equipment without source ID collision.

12. The method of claim 7, wherein, the method further comprises: receive a third sidelink setup response / acknowledgement message sent by the first user equipment, wherein the third sidelink setup response / acknowledgement message comprises sequence numbers of each second user equipment determined by the first user equipment to perform link setup, wherein each second user equipment comprises one of at least two second user equipments with source ID collision, and a second user equipment without source ID collision.

13. A user equipment comprising a transceiver, a memory, a processor, and a computer program stored on the memory and run on the processor, wherein the computer program comprises program instructions operative to cause the processor to perform operations comprising: The processor executes the computer program to implement the ID collision processing method in any one of claims 1 to 6, or the ID collision processing method in any one of claims 7 to 12.

14. An ID collision processing apparatus characterized by comprising: The application is applied to a first user equipment, comprising: a receiving module, configured to receive sidelink setup accept messages sent by at least two second user equipments after sending a sidelink setup request message, wherein the sidelink setup accept message comprises a randomly generated sequence number; a first processing module, configured to, in a case where the at least two second user equipments have source ID collision, give up link setup with the at least two second user equipments with source ID collision, or perform link setup with one of the at least two second user equipments with source ID collision; The device further comprises: a determining module, configured to, in a case where source IDs of the received at least two sidelink setup accept messages are the same and a difference between the two sequence numbers is greater than a preset threshold value, determine that the second user equipments sending the at least two sidelink setup accept messages have source ID collision; wherein, for the at least two sidelink setup accept messages with the same source ID, if the difference between the sequence numbers is less than or equal to the preset threshold value, the at least two sidelink setup accept messages are messages repeatedly sent by the same second user equipment, and if the difference between the sequence numbers is greater than the preset threshold value, the at least two sidelink setup accept messages are messages sent by different second user equipments.

15. An ID collision processing apparatus characterized by comprising: The application is applied to a second user equipment, comprising: a first sending module, configured to, after receiving a sidelink setup request message sent by a first user equipment, send a sidelink setup accept message to the first user equipment, wherein the sidelink setup accept message comprises a randomly generated sequence number, and the sidelink setup accept message is used to make the first user equipment determine whether at least two second user equipments have source ID collision; wherein, for at least two sidelink setup accept messages with the same source ID, if a difference between the sequence numbers is less than or equal to a preset threshold value, the at least two sidelink setup accept messages are messages repeatedly sent by the same second user equipment, and if the difference between the sequence numbers is greater than the preset threshold value, the at least two sidelink setup accept messages are messages sent by different second user equipments.

16. A computer readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to implement the ID collision processing method in any one of claims 1 to 6, or the ID collision processing method in any one of claims 7 to 12.

Images