Local identifier allocation method and device, equipment and storage medium

Abstract

The invention relates to a local identifier allocation method and device, equipment and a storage medium. The method comprises the following steps: first U2U relay UE determines a local identifier which is allowed to be allocated to remote UE by the first U2U relay UE according to first information; wherein the first information at least comprises a local identification list of the remote UE. By adopting the method provided by the invention, the problem that the U2U relay UE cannot select a correct route for the received data due to the fact that the local identifiers distributed by different U2U relay UEs for different remote UEs in a multi-hop U2U relay scene conflict is avoided.

Description

Technical Field

[0001] This application relates to the field of wireless communication technologies, and in particular, to a method, apparatus, device, and storage medium for local identifier allocation. Background Art

[0002] With the development of communication technologies, direct communication technologies have emerged. Direct communication refers to a technology in which neighboring user equipments (UEs) can perform data transmission within a short distance through a direct communication link (also known as Sidelink or PC5).

[0003] To expand the coverage of direct communication, it is possible to consider introducing user equipment to user equipment (U2U) relay UEs between UEs. After introducing U2U relay UEs, the UEs that use U2U relay UEs for U2U communication can be referred to as remote UEs. For a single-hop U2U relay scenario, the U2U relay UE allocates local identifiers to the remote UEs.

[0004] To further expand the coverage of the direct communication link, a multi-hop U2U relay scenario can be introduced based on the U2U relay UE. That is, the remote UEs communicate with each other through multiple U2U relay UEs. In a multi-hop U2U relay scenario, it is necessary to consider how to perform local identifier allocation to avoid the problem that the local identifiers allocated by different U2U relay UEs to different remote UEs conflict, resulting in the U2U relay UE being unable to select the correct route for the received data. Summary of the Invention

[0005] Embodiments of this application provide a method, apparatus, device, and storage medium for local identifier allocation to avoid the problem that the local identifiers allocated by different U2U relay UEs to different remote UEs conflict, resulting in the U2U relay UE being unable to select the correct route for the received data.

[0006] In a first aspect, a method for local identifier allocation is provided. The method includes:

[0007] A first U2U relay UE determines local identifiers that the first U2U relay UE is allowed to allocate to remote UEs according to first information; wherein the first information includes at least a local identifier list of the remote UEs.

[0008] In one embodiment, the method for obtaining the first information includes at least one of the following: the first U2U relay UE receives a target message sent by a second U2U relay UE through a direct communication interface, where the target message carries the first information, and the number of the second U2U relay UEs is one or more; the first U2U relay UE obtains the first information according to pre-configured information.

[0009] In one embodiment, the target message includes at least one of the following messages: a message related to relay discovery; a message related to PC5-S connection establishment; a message related to PC5-RRC reconfiguration.

[0010] In one embodiment, the second U2U relay UE is a relay UE that establishes a PC5-S connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that establishes a PC5-RRC connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that can be discovered by the first U2U relay UE through a direct communication interface discovery process.

[0011] In one embodiment, the first information includes one of the following: a first local identifier list, where the first local identifier list includes a set of local identifiers corresponding to a first remote UE that uses the second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has assigned to a remote UE; a second local identifier list, where the second local identifier list includes a set of local identifiers corresponding to a second remote UE that uses the second U2U relay UE for U2U communication and does not use the first U2U relay UE for U2U communication; a third local identifier list, where the third local identifier list includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not assigned by the second U2U relay UE to a remote UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for assignment to a remote UE.

[0012] In one embodiment, the remote UE that uses the second U2U relay UE for U2U communication includes: a remote UE that uses the second U2U relay UE for U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method; the remote UE that does not use the first U2U relay UE for U2U communication includes: a remote UE that does not use the first U2U relay UE for U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

[0013] In one embodiment, the first U2U relay UE determines the local identifier that the first U2U relay UE allows to be allocated to the remote UE according to the first information, including: the first U2U relay UE determines the local identifier that the first U2U relay UE allows to be allocated to the remote UE according to the first information, the local identifier that the first U2U relay UE has already allocated to the remote UE, and / or the local identifier of the remote UE using the first U2U relay UE for U2U communication.

[0014] In one embodiment, the first U2U relay UE determines the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE according to the first information, the local identifiers that the first U2U relay UE has already allocated to the remote UE, and / or the local identifiers of the remote UE that uses the first U2U relay UE for U2U communication, including at least one of the following: the first U2U relay UE deducts the local identifiers in the first local identifier list, the local identifiers that the first U2U relay UE has already allocated to the remote UE, and / or the local identifiers of the remote UE that uses the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE, so as to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE; the first U2U relay UE deducts the local identifiers in the second local identifier list, the local identifiers that the first U2U relay UE has already allocated to the remote UE, and / or the local identifiers of the remote UE that uses the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE, so as to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE; the first U2U relay UE deducts the local identifiers that the first U2U relay UE has already allocated to the remote UE and / or the local identifiers of the remote UE that uses the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE to obtain a fourth local identifier list, the first U2U relay UE takes a first intersection of the fourth local identifier list and the third local identifier list sent by one or more second U2U relay UEs, and determines the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE according to the first intersection; the first U2U relay UE takes a second intersection of the local identifier list corresponding to the first U2U relay UE and the third local identifier list sent by one or more second U2U relay UEs, the first U2U relay UE deducts the local identifiers that the first U2U relay UE has already allocated to the remote UE and / or the local identifiers of the remote UE that uses the first U2U relay UE for U2U communication in the second intersection to obtain a fifth local identifier list, and determines the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE according to the fifth local identifier list.

[0015] In one embodiment, the local identifier list corresponding to the first U2U relay UE is pre-configured or configured by a network device.

[0016] In one embodiment, the first U2U relay UE obtains the first information according to preconfigured information, including: the first U2U relay UE obtains, as the first information, a sixth local identifier list that the first U2U relay UE is allowed to allocate to a remote UE in the preconfigured information.

[0017] In one embodiment, the first U2U relay UE determines, according to the first information, a local identifier that the first U2U relay UE is allowed to allocate to a remote UE, including: the first U2U relay UE determines, according to the sixth local identifier list, the local identifier that the first U2U relay UE is allowed to allocate to a remote UE.

[0018] In one embodiment, the method further includes: after a first target remote UE and a second target remote UE establish a U2U connection through the first U2U relay UE, the first U2U relay UE allocates local identifiers to the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate to a remote UE.

[0019] In one embodiment, the first U2U relay UE allocates local identifiers to the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate to a remote UE, including: the first U2U relay UE allocates different local identifiers to the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate to a remote UE; or, the first U2U relay UE allocates the same local identifier to the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate to a remote UE.

[0020] In a second aspect, a local identifier allocation method is provided, and the method includes:

[0021] A second U2U relay UE sends a target message to a first U2U relay UE through a direct communication interface, where the target message carries first information, and the first information at least includes a local identifier list of a remote UE.

[0022] In one embodiment, the target message includes at least one of the following messages: a message related to relay discovery; a message related to PC5-S connection establishment; a message related to PC5-RRC reconfiguration.

[0023] In one embodiment, the first U2U relay UE is a relay UE that establishes a PC5-S connection with the second U2U relay UE; or, the first U2U relay UE is a relay UE that establishes a PC5-RRC connection with the second U2U relay UE; or, the first U2U relay UE is a relay UE that can be discovered by the second U2U relay UE through a direct communication interface discovery process.

[0024] In one embodiment, the first information carried in the target message includes one of the following: a first local identifier list, where the first local identifier list includes a set of local identifiers corresponding to the first remote UE that uses the second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has allocated to the remote UE; a second local identifier list, where the second local identifier list includes a set of local identifiers corresponding to the second remote UE that uses the second U2U relay UE for U2U communication and does not use the first U2U relay UE for U2U communication; a third local identifier list, where the third local identifier list includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not allocated by the second U2U relay UE to the remote UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for allocation to the remote UE.

[0025] In one embodiment, the remote UE that uses the second U2U relay UE for U2U communication includes: a remote UE that uses the second U2U relay UE for U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method; the remote UE that does not use the first U2U relay UE for U2U communication includes: a remote UE that does not use the first U2U relay UE for U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

[0026] In a third aspect, a local identifier allocation device for a first U2U relay UE is provided, and the device includes:

[0027] A determination unit, configured to determine, according to the first information, local identifiers that the first U2U relay UE is allowed to allocate to the remote UE; where the first information includes at least a local identifier list of the remote UE.

[0028] In one embodiment, the apparatus further includes an obtaining unit, where the obtaining unit is configured to perform at least one of the following: receive a target message sent by a second U2U relay UE through a direct communication interface, where the target message carries the first information, and the number of the second U2U relay UEs is one or more; obtain the first information according to pre-configured information.

[0029] In one embodiment, the target message includes at least one of the following messages: a message related to relay discovery; a message related to PC5-S connection establishment; a message related to PC5-RRC reconfiguration.

[0030] In one embodiment, the second U2U relay UE is a relay UE that establishes a PC5-S connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that establishes a PC5-RRC connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that can be discovered by the first U2U relay UE through a direct communication interface discovery process.

[0031] In one embodiment, the first information includes one of the following: a first local identifier list, where the first local identifier list includes a set of local identifiers corresponding to a first remote UE that uses the second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has assigned to a remote UE; a second local identifier list, where the second local identifier list includes a set of local identifiers corresponding to a second remote UE that uses the second U2U relay UE for U2U communication and does not use the first U2U relay UE for U2U communication; a third local identifier list, where the third local identifier list includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not assigned by the second U2U relay UE to a remote UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for assignment to a remote UE.

[0032] In one embodiment, the remote UE that uses the second U2U relay UE for U2U communication includes: a remote UE that uses the second U2U relay UE for U2U communication through a single-hop U2U relay manner and / or a multi-hop U2U relay manner; the remote UE that does not use the first U2U relay UE for U2U communication includes: a remote UE that does not use the first U2U relay UE for U2U communication through a single-hop U2U relay manner and / or a multi-hop U2U relay manner.

[0033] In one embodiment, the determining unit is specifically configured to: determine the local identifier that the first U2U relay UE is allowed to allocate to the remote UE according to the first information, the local identifier that the first U2U relay UE has already allocated to the remote UE, and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication.

[0034] In one embodiment, the determining unit is specifically configured to perform at least one of the following: deduct the local identifiers in the first local identifier list from the local identifier list corresponding to the first U2U relay UE, deduct the local identifier that the first U2U relay UE has already allocated to the remote UE, and / or deduct the local identifier of the remote UE that uses the first U2U relay UE for U2U communication, so as to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE; deduct the local identifiers in the second local identifier list from the local identifier list corresponding to the first U2U relay UE, deduct the local identifier that the first U2U relay UE has already allocated to the remote UE, and / or deduct the local identifier of the remote UE that uses the first U2U relay UE for U2U communication, so as to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE; deduct the local identifier that the first U2U relay UE has already allocated to the remote UE and / or deduct the local identifier of the remote UE that uses the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE to obtain a fourth local identifier list, the first U2U relay UE takes a first intersection of the fourth local identifier list and the third local identifier list sent by one or more second U2U relay UEs, and determines the local identifier that the first U2U relay UE is allowed to allocate to the remote UE according to the first intersection; take a second intersection of the local identifier list corresponding to the first U2U relay UE and the third local identifier list sent by one or more second U2U relay UEs, the first U2U relay UE deducts the local identifier that the first U2U relay UE has already allocated to the remote UE and / or deducts the local identifier of the remote UE that uses the first U2U relay UE for U2U communication from the second intersection to obtain a fifth local identifier list, and determines the local identifier that the first U2U relay UE is allowed to allocate to the remote UE according to the fifth local identifier list.

[0035] In one embodiment, the local identifier list corresponding to the first U2U relay UE is pre-configured or configured by a network device.

[0036] In one embodiment, the obtaining unit is specifically configured to: obtain the sixth local identifier list that the first U2U relay UE is allowed to allocate to the remote UE in the pre-configured information as the first information.

[0037] In one embodiment, the determining unit is specifically configured to: determine, according to the sixth local identifier list, the local identifiers that the first U2U relay UE is allowed to allocate to the remote UEs.

[0038] In one embodiment, the apparatus further includes an allocating unit; the allocating unit is configured to, after a first target remote UE and a second target remote UE establish a U2U connection through the first U2U relay UE, allocate local identifiers to the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate to the remote UEs.

[0039] In one embodiment, the allocating unit is specifically configured to: allocate different local identifiers to the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate to the remote UEs; or allocate the same local identifiers to the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate to the remote UEs.

[0040] In a fourth aspect, a local identifier allocation apparatus for a second U2U relay UE is provided, and the apparatus includes:

[0041] a sending unit, configured to send a target message to a first U2U relay UE through a direct communication interface, where the target message carries first information, and the first information at least includes a local identifier list of a remote UE.

[0042] In one embodiment, the target message includes at least one of the following messages: a message related to relay discovery; a message related to PC5-S connection establishment; a message related to PC5-RRC reconfiguration.

[0043] In one embodiment, the first U2U relay UE is a relay UE that establishes a PC5-S connection with the second U2U relay UE; or the first U2U relay UE is a relay UE that establishes a PC5-RRC connection with the second U2U relay UE; or the first U2U relay UE is a relay UE that can be discovered by the second U2U relay UE through a direct communication interface discovery process.

[0044] In one embodiment, the first information carried in the target message includes one of the following: a first local identifier list, which includes a set of local identifiers corresponding to a first remote UE that uses the second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has assigned to remote UEs; a second local identifier list, which includes a set of local identifiers corresponding to a second remote UE that uses the second U2U relay UE for U2U communication and does not use the first U2U relay UE for U2U communication; a third local identifier list, which includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not assigned by the second U2U relay UE to remote UEs, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for assignment to remote UEs.

[0045] In one embodiment, the remote UEs that use the second U2U relay UE for U2U communication include: remote UEs that use the second U2U relay UE for U2U communication through single-hop U2U relay mode and / or multi-hop U2U relay mode; the remote UEs that do not use the first U2U relay UE for U2U communication include: remote UEs that do not use the first U2U relay UE for U2U communication through single-hop U2U relay mode and / or multi-hop U2U relay mode.

[0046] In a fifth aspect, a first U2U relay UE is provided, including a memory, a transceiver, and a processor:

[0047] The memory is used for storing a computer program; the transceiver is used for transceiving data under the control of the processor; the processor is used for reading the computer program in the memory and performing the following operations:

[0048] Determine the local identifiers that the first U2U relay UE is allowed to assign to remote UEs according to the first information; wherein, the first information at least includes a local identifier list of remote UEs.

[0049] In one embodiment, the processor is further used for performing at least one of the following operations: controlling the transceiver to receive a target message sent by a second U2U relay UE through a direct communication interface, the target message carrying the first information, and the number of the second U2U relay UEs is one or more; obtaining the first information according to pre-configured information.

[0050] In one embodiment, the target message includes at least one of the following messages: a message related to relay discovery; a message related to PC5-S connection establishment; a message related to PC5-RRC reconfiguration.

[0051] In one embodiment, the second U2U relay UE is a relay UE that establishes a PC5-S connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that establishes a PC5-RRC connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that can be discovered by the first U2U relay UE through a direct communication interface discovery process.

[0052] In one embodiment, the first information includes one of the following: a first local identifier list, where the first local identifier list includes a set of local identifiers corresponding to a first remote UE that uses the second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has assigned to remote UEs; a second local identifier list, where the second local identifier list includes a set of local identifiers corresponding to a second remote UE that uses the second U2U relay UE for U2U communication and does not use the first U2U relay UE for U2U communication; a third local identifier list, where the third local identifier list includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that have not been assigned by the second U2U relay UE to remote UEs, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for assignment to remote UEs.

[0053] In one embodiment, the remote UEs that use the second U2U relay UE for U2U communication include: remote UEs that use the second U2U relay UE for U2U communication through a single-hop U2U relay manner and / or a multi-hop U2U relay manner; the remote UEs that do not use the first U2U relay UE for U2U communication include: remote UEs that do not use the first U2U relay UE for U2U communication through a single-hop U2U relay manner and / or a multi-hop U2U relay manner.

[0054] In one embodiment, the processor is specifically configured to perform the following operations: determine the local identifiers that the first U2U relay UE is allowed to assign to remote UEs according to the first information, the local identifiers that the first U2U relay UE has already assigned to remote UEs, and / or the local identifiers of the remote UEs that use the first U2U relay UE for U2U communication.

[0055] In one embodiment, the processor is specifically configured to perform at least one of the following operations: deduct the local identifiers in the first local identifier list from the local identifier list corresponding to the first U2U relay UE, deduct the local identifiers already allocated by the first U2U relay UE to the remote UE, and / or deduct the local identifiers of the remote UE using the first U2U relay UE for U2U communication, so as to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE; deduct the local identifiers in the second local identifier list from the local identifier list corresponding to the first U2U relay UE, deduct the local identifiers already allocated by the first U2U relay UE to the remote UE, and / or deduct the local identifiers of the remote UE using the first U2U relay UE for U2U communication, so as to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE; deduct the local identifiers already allocated by the first U2U relay UE to the remote UE and / or deduct the local identifiers of the remote UE using the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE to obtain a fourth local identifier list, and the first U2U relay UE takes a first intersection of the fourth local identifier list and the third local identifier list sent by one or more of the second U2U relay UEs, and determines the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE according to the first intersection; take a second intersection of the local identifier list corresponding to the first U2U relay UE and the third local identifier list sent by one or more of the second U2U relay UEs, and the first U2U relay UE deducts the local identifiers already allocated by the first U2U relay UE to the remote UE and / or deducts the local identifiers of the remote UE using the first U2U relay UE for U2U communication from the second intersection to obtain a fifth local identifier list, and determines the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE according to the fifth local identifier list.

[0056] In one embodiment, the local identifier list corresponding to the first U2U relay UE is pre-configured or configured by a network device.

[0057] In one embodiment, the processor is specifically configured to perform the following operation: obtain the sixth local identifier list that the first U2U relay UE is allowed to allocate to the remote UE in the pre-configuration information as the first information.

[0058] In one embodiment, the processor is specifically configured to perform the following operation: determine the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE according to the sixth local identifier list.

[0059] In one embodiment, the processor is further configured to perform the following operations: after a first target remote UE and a second target remote UE establish a U2U connection through the first U2U relay UE, allocate local identifiers for the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate for remote UEs.

[0060] In one embodiment, the processor is specifically configured to perform the following operations: allocate different local identifiers for the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate for remote UEs; or, allocate the same local identifiers for the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate for remote UEs.

[0061] In a sixth aspect, a second U2U relay UE is provided, including a memory, a transceiver, and a processor:

[0062] The memory is used for storing a computer program; the transceiver is used for transceiving data under the control of the processor; the processor is used for reading the computer program in the memory and performing the following operations:

[0063] Control the transceiver to send a target message to a first U2U relay UE through a direct communication interface, where the target message carries first information, and the first information at least includes a list of local identifiers of remote UEs.

[0064] In one embodiment, the target message includes at least one of the following messages: a message related to relay discovery; a message related to PC5-S connection establishment; a message related to PC5-RRC reconfiguration.

[0065] In one embodiment, the first U2U relay UE is a relay UE that establishes a PC5-S connection with the second U2U relay UE; or, the first U2U relay UE is a relay UE that establishes a PC5-RRC connection with the second U2U relay UE; or, the first U2U relay UE is a relay UE that can be discovered by the second U2U relay UE through a direct communication interface discovery process.

[0066] In one embodiment, the first information carried by the target message includes one of the following: a first local identifier list, which includes a set of local identifiers corresponding to a first remote UE that uses the second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has assigned to remote UEs; a second local identifier list, which includes a set of local identifiers corresponding to a second remote UE that uses the second U2U relay UE for U2U communication and does not use the first U2U relay UE for U2U communication; a third local identifier list, which includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not assigned by the second U2U relay UE to remote UEs, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for assignment to remote UEs.

[0067] In one embodiment, the remote UEs that use the second U2U relay UE for U2U communication include: remote UEs that use the second U2U relay UE for U2U communication through single-hop U2U relay mode and / or multi-hop U2U relay mode; the remote UEs that do not use the first U2U relay UE for U2U communication include: remote UEs that do not use the first U2U relay UE for U2U communication through single-hop U2U relay mode and / or multi-hop U2U relay mode.

[0068] In a seventh aspect, a processor-readable storage medium is provided, and the processor-readable storage medium stores a program, and the program is used to cause a processor to execute the method according to any one of the first aspects above.

[0069] In an eighth aspect, a processor-readable storage medium is provided, and the processor-readable storage medium stores a program, and the program is used to cause a processor to execute the method according to any one of the second aspects above.

[0070] The above-mentioned local identifier allocation method, apparatus, device, and storage medium enable a first U2U relay UE to determine, according to first information, the local identifiers that the first U2U relay UE is allowed to allocate to a remote UE. The first information includes at least a list of local identifiers of the remote UE. In this way, the first U2U relay UE can determine the local identifiers that it is allowed to allocate to the remote UE before allocating local identifiers to the remote UE, and thus can allocate local identifiers to the remote UE based on the local identifiers that it is allowed to allocate to the remote UE. This can ensure that each U2U relay UE in the system can only allocate local identifiers to a remote UE that it is allowed to allocate, so as to avoid the problem that different U2U relay UEs allocate conflicting local identifiers to different remote UEs, resulting in the U2U relay UE being unable to select the correct route for the received data. Description of the Drawings

[0071] Figure 1 Schematic diagram of the traditional cellular network communication method in an embodiment;

[0072] Figure 2 Schematic diagram of the communication method of direct communication in an embodiment;

[0073] Figure 3 Schematic diagram of the single-hop connection of a remote UE in an embodiment;

[0074] Figure 4 Schematic diagram of the multi-hop connection of a remote UE in an embodiment;

[0075] Figure 5 Schematic diagram of the direct communication architecture in an embodiment;

[0076] Figure 6 Schematic flow chart of the local identifier allocation method in an embodiment;

[0077] Figure 7 Schematic flow chart of another local identifier allocation method in an embodiment;

[0078] Figure 8 Schematic diagram of the direct communication architecture in an embodiment;

[0079] Figure 9 Schematic flow chart of another local identifier allocation method in an embodiment;

[0080] Figure 10 Schematic flow chart of another local identifier allocation method in an embodiment;

[0081] Figure 11 Schematic flow chart of another local identifier allocation method in an embodiment;

[0082] Figure 12Schematic diagram of another method for allocating local identifiers in an embodiment;

[0083] Figure 13 Block diagram of a local identifier allocation device in an embodiment;

[0084] Figure 14 Block diagram of another local identifier allocation device in an embodiment;

[0085] Figure 15 Block diagram of another local identifier allocation device in an embodiment;

[0086] Figure 16 Internal structure diagram of a U2U relay UE in an embodiment. Detailed implementation manners

[0087] In order to make the objectives, technical solutions and advantages of the present application clearer and more understandable, the present application will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0088] Please refer to Figure 1 , which shows a traditional cellular network communication method. In this communication method, a UE (English: User Equipment; Chinese: user equipment) communicates with an access network device through the Uu interface (air interface), and the access network device communicates with network elements / network functions in the core network.

[0089] Please refer to Figure 2 , which shows a direct communication method. In this communication method, neighboring UEs can communicate within a short distance through a direct communication link (also called a Sidelink link or a PC5 link). Among them, the wireless interface corresponding to the direct communication link is called a direct communication interface (also called a Sidelink interface, a PC5 interface or a bypass interface).

[0090] In order to expand the coverage of the direct communication interface, it is possible to consider introducing a User Equipment to User Equipment (U2U) relay UE. Among them, in some descriptions, the U2U relay UE can also be called a U2U Relay. The U2U relay UE itself can be a UE with a relay function. After introducing the U2U relay UE, a single U2U relay UE can be used to implement a single-hop connection of a remote UE, or multiple U2U relay UEs can be used to implement a multi-hop connection of a remote UE.

[0091] Please refer to Figure 3 and Figure 4 , where Figure 3Schematic diagram of single-hop connection for remote UE Figure 4 Schematic diagram of multi-hop connection for remote UE, such as Figure 3 As shown, one U2U relay UE can be set between remote UEs. Among them, the remote UE and the U2U relay UE communicate using a direct communication interface, such as Figure 4 As shown, three U2U relay UEs can be set between remote UEs (this is only an example here, and actually more or fewer U2U relay UEs than three can be set). Among them, the remote UE and the U2U relay UE communicate using a direct communication interface, and adjacent U2U relay UEs also communicate using a direct communication interface.

[0092] Generally speaking, a pair of remote UEs communicating through a U2U relay UE can be identified by a source L2 ID and a destination L2 ID, so as to achieve routing. Among them, L2 ID refers to layer 2 ID. The lengths of the source L2 ID and the destination L2 ID are both 24 bits. Since the number of bits of the L2 ID is relatively large, if it is directly carried in the SRAP (English: Sidelink Relay Adaptation Layer; Chinese: Sidelink relay adaptation layer) header, the SRAP header overhead will be relatively large. Therefore, 3GPP has made an optimization: for a pair of remote UEs communicating through a U2U relay UE, the U2U relay UE can respectively allocate local identifiers corresponding to the source L2 ID and the destination L2 ID for this pair of remote UEs. Among them, the lengths of the local identifiers corresponding to the source L2 ID and the destination L2 are both 8 bits.

[0093] In 3GPP Rel-19, the multi-hop U2U relay communication scenario shown above will be introduced. In this multi-hop U2U relay communication scenario, it is necessary to consider how to allocate local identifiers to avoid the problem that different U2U relay UEs allocate conflicting local identifiers for different remote UEs, resulting in the U2U relay UE being unable to select the correct route for the received data. Figure 4

[0094] Figure 5 Please refer to Figure 5 In Figure 5Among them, the local identifiers of the remote UE1 and the remote UE2 are assigned by the U2U relay UE1, which are 0100111 and 01001110 respectively. The local identifiers of the remote UE3 and the remote UE4 are assigned by the U2U relay UE2, which are 0100111 and 01001110 respectively. That is to say, the local identifiers of the remote UE1 and the remote UE2 are exactly the same as those of the remote UE3 and the remote UE4. And the U2U relay UE2 serves both the remote UE1 and the remote UE2 and the remote UE3 and the remote UE4. Therefore, the U2U relay UE2 cannot distinguish between the two pairs of remote UEs, namely the remote UE1 and the remote UE2 and the remote UE3 and the remote UE4, resulting in its inability to route correctly and causing communication interruption.

[0095] In view of this, the embodiments of the present application provide a local identifier allocation method, device, equipment and storage medium. The first U2U relay UE determines the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE according to the first information. Wherein, the first information at least includes the local identifier list of the remote UE. In this way, before allocating the local identifier to the remote UE, the first U2U relay UE can determine the local identifiers that it is allowed to allocate to the remote UE, and thus can allocate the local identifier to the remote UE based on the local identifiers that it is allowed to allocate to the remote UE. In this way, it can be ensured that each U2U relay UE in the system can only allocate the local identifiers that it is allowed to allocate to the remote UE, so as to avoid the problem that different U2U relay UEs allocate conflicting local identifiers to different remote UEs, resulting in the U2U relay UE being unable to select the correct route for the received data.

[0096] It should be noted that the beneficial effects or the technical problems solved by the embodiments of the present application are not limited to this one, and there may also be other implicit or related problems. For specific details, please refer to the descriptions of the following embodiments.

[0097] The technical solutions of the present application and how the technical solutions of the present application solve the above technical problems will be described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. The embodiments of the present application will be described below with reference to the accompanying drawings.

[0098] In one embodiment, as Figure 6 shown, a local identifier allocation method is provided. This method is described by applying it to the first U2U relay UE, and includes the following steps:

[0099] Step 601, the first U2U relay UE determines the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE according to the first information.

[0100] In an alternative embodiment of the present application, the first U2U relay UE may be a U2U relay UE in a multi-hop U2U relay communication scenario, or may also be a U2U relay UE in a communication scenario where single-hop U2U relay communication scenarios and multi-hop U2U relay communication scenarios are mixedly deployed. The first U2U relay UE may serve a remote UE in a single-hop U2U relay manner and / or the first U2U relay UE may serve a remote UE in a multi-hop U2U relay manner. The first U2U relay UE may serve a pair of remote UEs, or may also serve multiple pairs of remote UEs simultaneously.

[0101] In an alternative embodiment of the present application, the first information at least includes a local identifier list of the remote UE, that is, the first information includes one or more local identifiers. It should be noted that in actual implementation, in addition to one or more local identifiers, the first information may also include other content, which is not limited in the embodiments of the present application.

[0102] Please refer to Table 1, which gives an optional example of the local identifier list included in the first information.

[0103] Table 1

[0104] Local identifier Local identifier A Local identifier B Local identifier C ……

[0105] In an alternative embodiment of the present application, the local identifier that the first U2U relay UE is allowed to allocate to a remote UE refers to: a local identifier that does not cause conflicts and is available for the first U2U relay UE to allocate, or a local identifier that does not cause conflicts within a certain area range.

[0106] In a possible implementation manner, within a certain area range (such as globally or within a certain geographical area), all remote UEs in the system will be allocated different local identifiers, so as to ensure that the local identifiers of the remote UEs in the system do not conflict. At this time, the local identifier that does not cause conflicts and is available for the first U2U relay UE to allocate, or the local identifier that does not cause conflicts within a certain area range, refers to: a local identifier that is different from the local identifiers that have been allocated to other remote UEs and is available for the first U2U relay UE to allocate.

[0107] In another possible implementation manner, different local identifiers will be allocated to each remote UE served by the first U2U relay UE, so as to ensure that the local identifiers of each remote UE served by the first U2U relay UE do not conflict. At this time, the local identifier that does not cause conflicts and is available for the first U2U relay UE to allocate, or the local identifier that does not cause conflicts within a certain area range, refers to: a local identifier that is different from the local identifiers of other remote UEs that communicate using the first U2U relay UE and is available for the first U2U relay UE to allocate.

[0108] The local identifier allocation method provided in this embodiment enables the first U2U relay UE to determine the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE based on the first information. The first information at least includes the local identifier list of the remote UE. In this way, before allocating local identifiers to the remote UE, the first U2U relay UE can determine the local identifiers that it is allowed to allocate to the remote UE, and thus can allocate local identifiers to the remote UE based on the local identifiers that it is allowed to allocate to the remote UE. This can ensure that each U2U relay UE in the system can only allocate local identifiers to the remote UE that it is allowed to allocate, so as to avoid the problem that the local identifiers allocated by different U2U relay UEs to different remote UEs conflict, resulting in the U2U relay UE being unable to select the correct route for the received data.

[0109] The embodiments of this application provide two alternative ways for the first U2U relay UE to obtain the first information, which will be described separately below.

[0110] In the first way to obtain the first information, the first U2U relay UE receives a target message sent by the second U2U relay UE through a direct communication interface. The target message carries the first information, and the number of the second U2U relay UEs is one or more.

[0111] In an alternative embodiment of this application, the second U2U relay UE can be one of the following U2U relay UEs: A. A relay UE that establishes a PC5-S connection with the first U2U relay UE; B. A relay UE that establishes a PC5-RRC connection with the first U2U relay UE; C. A relay UE that can be discovered by the first U2U relay UE through the direct communication interface discovery process.

[0112] In an alternative embodiment of this application, the target message can include at least one of the following messages: A. Messages related to relay discovery, for example, the PROSE PC5 DISCOVERY message for UE-to-UE relay discovery announcement message (Chinese: Discovery message for U2U relay discovery announcement) and / or the PROSE PC5 DISCOVERY message for UE-to-UE relay discovery solicitation message (Chinese: Discovery message for U2U relay discovery request); B. Messages related to the establishment of a PC5-S connection, for example, the Direct Communication Request message (Chinese: Direct communication request message); C. Messages related to PC5-RRC reconfiguration, for example, the RRCReconfigurationSidelink message of the PC5 interface (Chinese: RRC reconfiguration message).

[0113] In an alternative embodiment of the present application, the first information carried in the target message may include one of the following:

[0114] A. A first local identifier list, where the first local identifier list includes the local identifier corresponding to the first remote UE that uses the second U2U relay UE for U2U communication or the set of local identifiers that the second U2U relay UE has assigned to the remote UE.

[0115] In an alternative embodiment of the present application, the first remote UE that uses the second U2U relay UE for U2U communication includes: the remote UE that uses the second U2U relay UE for U2U communication through the single-hop U2U relay method and / or the multi-hop U2U relay method. In an alternative embodiment of the present application, the number of the first remote UEs may be one or more.

[0116] For example, please refer back to Figure 4 , in Figure 4 , assuming that the U2U relay UE1 is the first U2U relay UE, then the U2U relay UE2 is the second U2U relay UE. The first information carried in the target message sent by the U2U relay UE2 to the U2U relay UE1 may include the first local identifier list. Since the remote UEs that use the U2U relay UE2 for U2U communication include the remote UE1, the remote UE2, the remote UE3, and the remote UE4, therefore, the first local identifier list may include the local identifier of the remote UE1, the local identifier of the remote UE2, the local identifier of the remote UE3, and the local identifier of the remote UE4. In subsequent steps, the U2U relay UE1 may determine the local identifiers that it allows to be assigned to the remote UE according to the first local identifier list. In this way, if there is another remote UE that wishes to perform U2U communication through the U2U relay UE1, the U2U relay UE1 may assign local identifiers to the other remote UE according to the local identifiers that it allows to be assigned to the remote UE.

[0117] In an alternative embodiment of the present application, the set of local identifiers that the second U2U relay UE has assigned to the remote UE includes: the set of local identifiers that the second U2U relay UE has assigned to the remote UEs it serves, where the number of the remote UEs served by the second U2U relay UE may be one or more.

[0118] For example, please continue to refer back to Figure 4, similarly to the above description, assuming that the U2U relay UE1 is the first U2U relay UE, then the U2U relay UE2 is the second U2U relay UE. The first information carried in the target message sent by the U2U relay UE2 to the U2U relay UE1 may include a first local identifier list. Since the U2U relay UE2 has already assigned local identifiers to the remote UEs 1, 2, 3, and 4, therefore, this first local identifier list may include the local identifiers of the remote UE1, the local identifier of the remote UE2, the local identifier of the remote UE3, and the local identifier of the remote UE4. In subsequent steps, the U2U relay UE1 can determine the local identifiers that it is allowed to assign to the remote UEs according to this first local identifier list. In this way, if there is another remote UE that wishes to perform U2U communication through the U2U relay UE1, the U2U relay UE1 can assign local identifiers to this other remote UE according to the local identifiers that it is allowed to assign to the remote UEs.

[0119] B. A second local identifier list, where the second local identifier list includes a set of local identifiers corresponding to second remote UEs that perform U2U communication using the second U2U relay UE and do not perform U2U communication using the first U2U relay UE.

[0120] Among them, the second remote UEs that do not perform U2U communication using the first U2U relay UE include: remote UEs that do not perform U2U communication using the first U2U relay UE through the single-hop U2U relay method and / or the multi-hop U2U relay method. The number of such second remote UEs can be one or more.

[0121] For example, please continue to refer back to Figure 4 , similarly to the above description, assuming Figure 4 the U2U relay UE1 in is the first U2U relay UE, then the U2U relay UE2 is the second U2U relay UE. The first information carried in the target message sent by the U2U relay UE2 to the U2U relay UE1 may include a second local identifier list. Since the remote UEs that perform U2U communication using the U2U relay UE2 include remote UEs 1, 2, 3, and 4, and among them, the remote UEs that do not perform U2U communication using the U2U relay UE1 include remote UEs 3 and 4, therefore, this second local identifier list may include the local identifier of the remote UE3 and the local identifier of the remote UE4. In subsequent steps, the U2U relay UE1 can determine the local identifiers that it is allowed to assign to the remote UEs according to this second local identifier list. In this way, if there is another remote UE that wishes to perform U2U communication through the U2U relay UE1, the U2U relay UE1 can assign local identifiers to this other remote UE according to the local identifiers that it is allowed to assign to the remote UEs.

[0122] It should be noted that according to the above description, the second local identifier list can be understood as the local identifier list obtained by deducting the local identifiers of the remote UEs that use the first U2U relay UE for U2U communication from the first local identifier list. Generally, the first U2U relay UE can obtain the local identifiers of the remote UEs that use itself for U2U communication. Therefore, sending the second local identifier list can reduce the data volume and save communication resources.

[0123] C. The third local identifier list, where the third local identifier list includes the local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE described above or the local identifiers in the local identifier list corresponding to the second U2U relay UE that are not allocated by the second U2U relay UE to the remote UEs.

[0124] In an alternative embodiment of the present application, each U2U relay UE in the system can correspond to a local identifier list. Among them, the local identifier lists corresponding to each U2U relay UE can be the same or different. In an alternative embodiment of the present application, the local identifier lists corresponding to each U2U relay UE can be pre-configured or configured by a network device.

[0125] In an alternative embodiment of the present application, the local identifier list corresponding to each U2U relay UE includes one or more local identifiers that can be used to allocate to remote UEs. Among them, the local identifiers included in the local identifier list corresponding to each U2U relay UE are the local identifiers that are allowed to be allocated to remote UEs in the initial state.

[0126] According to the above description, the local identifier list corresponding to the second U2U relay UE can be pre-configured or configured by a network device. The local identifier list corresponding to the second U2U relay UE can be the same as or different from the local identifier list corresponding to the first U2U relay UE. The local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to remote UEs. Among them, the local identifiers included in the local identifier list corresponding to the second U2U relay UE are the local identifiers that are allowed to be allocated to remote UEs in the initial state.

[0127] For example, please continue to refer back to Figure 4 , similar to the above description, assume that Figure 4If the U2U relay UE1 in [[ ]] is the first U2U relay UE, then the U2U relay UE2 is the second U2U relay UE. The first information carried in the target message sent by the U2U relay UE2 to the U2U relay UE1 may include a third local identifier list. Since the remote UEs (i.e., the first remote UEs) using the U2U relay UE2 for U2U communication include remote UE1, remote UE2, remote UE3, and remote UE4, the third local identifier list is the local identifier list obtained by deducting the local identifiers of remote UE1, remote UE2, remote UE3, and remote UE4 from the local identifier list corresponding to the second U2U relay UE. In subsequent steps, the U2U relay UE1 can determine the local identifiers that it allows to be allocated to remote UEs according to this third local identifier list. Thus, if there is another remote UE that hopes to perform U2U communication through the U2U relay UE1, the U2U relay UE1 can allocate local identifiers to this other remote UE according to the local identifiers that it allows to be allocated to remote UEs.

[0128] For example, please continue to refer back to Figure 4 , similar to the above description, assume Figure 4 If the U2U relay UE1 in [[ ]] is the first U2U relay UE, then the U2U relay UE2 is the second U2U relay UE. The first information carried in the target message sent by the U2U relay UE2 to the U2U relay UE1 may include a third local identifier list. Since the U2U relay UE2 has already allocated local identifiers to remote UE1, remote UE2, remote UE3, and remote UE4, the third local identifier list is the local identifier list obtained by deducting the local identifiers of remote UE1, remote UE2, remote UE3, and remote UE4 from the local identifier list corresponding to the second U2U relay UE. In subsequent steps, the U2U relay UE1 can determine the local identifiers that it allows to be allocated to remote UEs according to this third local identifier list. Thus, if there is another remote UE that hopes to perform U2U communication through the U2U relay UE1, the U2U relay UE1 can allocate local identifiers to this other remote UE according to the local identifiers that it allows to be allocated to remote UEs.

[0129] The second way to obtain the first information is that the first U2U relay UE obtains the first information according to pre-configured information.

[0130] In an alternative embodiment of the present application, different local identifier lists that are allowed to be allocated to remote UEs can be pre-configured for different U2U relay UEs within a certain area range (such as globally or a specified geographical area), and there may be no intersection between the local identifier lists pre-configured for different U2U relay UEs.

[0131] The first U2U relay UE may obtain, from the preconfigured information, a list of sixth local identifiers preconfigured for the first U2U relay UE and allowed to be allocated to the remote UE, and use the list of sixth local identifiers as the first information.

[0132] For the second manner of obtaining the first information, that is, for the manner of obtaining the first information according to the preconfigured information, an embodiment of the present application provides an optional manner for the first U2U relay UE to determine the local identifier allowed to be allocated to the remote UE according to the first information. Among them, the manner includes: The first U2U relay UE determines the local identifier allowed to be allocated to the remote UE according to the list of sixth local identifiers. Optionally, the first U2U relay UE may determine the local identifiers in the list of sixth local identifiers as the local identifiers allowed to be allocated to the remote UE by itself.

[0133] In addition, for the first manner of obtaining the first information described above, that is, for the manner of obtaining the first information from the target message sent by the second U2U relay UE, an embodiment of the present application provides an optional manner for the first U2U relay UE to determine the local identifier allowed to be allocated to the remote UE according to the first information.

[0134] Among them, the manner includes: The first U2U relay UE determines the local identifier allowed to be allocated to the remote UE according to the first information, the local identifier that the first U2U relay UE has already allocated to the remote UE, and / or the local identifier of the remote UE using the first U2U relay UE for U2U communication.

[0135] For the sake of simplicity of description, in the following method embodiments, the already allocated local identifier is used to represent the local identifier that the first U2U relay UE has already allocated to the remote UE, and the already used local identifier is used to represent the local identifier of the remote UE using the first U2U relay UE for U2U communication.

[0136] In practical applications, the already allocated local identifier and the already used local identifier cannot be allocated by the first U2U relay UE to a new remote UE anymore, otherwise local identifier conflicts will occur. Therefore, in an optional embodiment of the present application, the first U2U relay UE may determine the local identifier allowed to be allocated to the remote UE according to the first information, the already allocated local identifier, and / or the already used local identifier.

[0137] For example, the first U2U relay UE may determine the local identifier that the first U2U relay UE is allowed to allocate to the remote UE based on the first information and the allocated local identifier (for example, there is currently no remote UE using the first U2U relay UE for U2U communication). Another example is that the first U2U relay UE may determine the local identifier that the first U2U relay UE is allowed to allocate to the remote UE based on the first information and the used local identifier (for example, the first U2U relay UE has not yet allocated a local identifier to the remote UE). Another example is that the first U2U relay UE may determine the local identifier that the first U2U relay UE is allowed to allocate to the remote UE based on the first information, the allocated local identifier, and the used local identifier. Of course, the first U2U relay UE may separately determine the local identifier that the first U2U relay UE is allowed to allocate to the remote UE based on the first information (for example, there is currently no remote UE using the first U2U relay UE for U2U communication, and at the same time, the first U2U relay UE has not yet allocated a local identifier to the remote UE).

[0138] Further, the first U2U relay UE determines the local identifier that the first U2U relay UE is allowed to allocate to the remote UE based on the first information, the allocated local identifier, and / or the used local identifier, including at least one of the following implementation manners:

[0139] Implementation manner A: The first U2U relay UE deducts the local identifiers in the first local identifier list, the allocated local identifier, and / or the used local identifier from the local identifier list corresponding to the first U2U relay UE to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE.

[0140] For the sake of simplicity in description, in the following method embodiments, the local identifier list A is used to represent the local identifier list corresponding to the first U2U relay UE.

[0141] Similar to the local identifier list corresponding to the second U2U relay UE described above, the local identifier list A may be pre-configured or configured by a network device. The local identifier list A may be the same as or different from the local identifier list corresponding to the second U2U relay UE. The local identifier list A includes one or more local identifiers that can be used to allocate to the remote UE. Among them, the local identifiers included in the local identifier list A are the local identifiers that are allowed to be allocated to the remote UE in the initial state.

[0142] In implementation mode A, for example, the first U2U relay UE can deduct the local identifiers in the first local identifier list and the allocated local identifiers from the local identifier list A to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE. For another example, the first U2U relay UE can deduct the local identifiers in the first local identifier list and the used local identifiers from the local identifier list A to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE. For another example, the first U2U relay UE can deduct the local identifiers in the first local identifier list, the allocated local identifiers, and the used local identifiers from the local identifier list A to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE. For another example, the first U2U relay UE can only deduct the local identifiers in the first local identifier list from the local identifier list A to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE.

[0143] Please return for reference Figure 4 , according to the examples above, the first local identifier list may include the local identifiers of remote UE1, the local identifiers of remote UE2, the local identifiers of remote UE3, and the local identifiers of remote UE4. Then, in implementation mode A, for example, the first U2U relay UE can deduct the local identifiers of remote UE1, the local identifiers of remote UE2, the local identifiers of remote UE3, and the local identifiers of remote UE4 from the local identifier list A, and at the same time deduct the allocated local identifiers and the used local identifiers (in Figure 4 , the used local identifiers include the local identifiers of remote UE1 and the local identifiers of remote UE2), to obtain the local identifiers that U2U relay UE1 is allowed to allocate to the remote UE.

[0144] In implementation mode B, the first U2U relay UE deducts the local identifiers in the second local identifier list, the allocated local identifiers, and / or the used local identifiers from the local identifier list A to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE.

[0145] In Implementation B, for example, the first U2U relay UE may deduct the local identifiers in the second local identifier list and the allocated local identifiers from the local identifier list A to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE. For another example, the first U2U relay UE may deduct the local identifiers in the second local identifier list and the used local identifiers from the local identifier list A to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE. For another example, the first U2U relay UE may deduct the local identifiers in the second local identifier list, the allocated local identifiers, and the used local identifiers from the local identifier list A to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE. For another example, the first U2U relay UE may only deduct the local identifiers in the second local identifier list from the local identifier list A to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE.

[0146] Please return for reference Figure 4 , according to the examples above, the second local identifier list may include the local identifiers of remote UE3 and remote UE4. Then, in Implementation B, for example, the first U2U relay UE may deduct the local identifiers of remote UE3 and remote UE4 from the local identifier list A, and at the same time deduct the allocated local identifiers and the used local identifiers (in Figure 4 , the used local identifiers include the local identifiers of remote UE1 and remote UE2), to obtain the local identifiers that U2U relay UE1 is allowed to allocate to the remote UE.

[0147] In Implementation C, the first U2U relay UE deducts the allocated local identifiers and / or the used local identifiers from the local identifier list A to obtain the fourth local identifier list. The first U2U relay UE takes the first intersection of the fourth local identifier list and the third local identifier lists sent by one or more second U2U relay UEs, and determines the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE according to the first intersection.

[0148] For example, the first U2U relay UE may deduct the allocated local identifiers from the local identifier list A to obtain the fourth local identifier list. For another example, the first U2U relay UE may deduct the used local identifiers from the local identifier list A to obtain the fourth local identifier list. For another example, the first U2U relay UE may deduct the allocated local identifiers and the used local identifiers from the local identifier list A to obtain the fourth local identifier list. For another example, the first U2U relay UE may directly use the local identifier list A as the fourth local identifier list.

[0149] After obtaining the fourth local identifier list, the first U2U relay UE may take the first intersection of the fourth local identifier list and the third local identifier lists sent by one or more second U2U relay UEs. In an alternative embodiment of the present application, the first U2U relay UE may use the local identifiers in the first intersection as the local identifiers that the first U2U relay UE allows to be allocated to the remote UE.

[0150] Implementation D: The first U2U relay UE takes the second intersection of the local identifier list A and the third local identifier lists sent by one or more second U2U relay UEs. The first U2U relay UE deducts the allocated local identifiers and / or the used local identifiers from the second intersection to obtain the fifth local identifier list, and determines the local identifiers that the first U2U relay UE allows to be allocated to the remote UE according to the fifth local identifier list.

[0151] For example, after obtaining the second intersection, the first U2U relay UE may deduct the allocated local identifiers from the second intersection to obtain the fifth local identifier list. For another example, the first U2U relay UE may deduct the used local identifiers from the second intersection to obtain the fifth local identifier list. For yet another example, the first U2U relay UE may deduct the allocated local identifiers and the used local identifiers from the second intersection to obtain the fifth local identifier list. For still another example, the first U2U relay UE may directly use the second intersection as the fifth local identifier list. In an alternative embodiment of the present application, the first U2U relay UE may use the local identifiers in the fifth local identifier list as the local identifiers that the first U2U relay UE allows to be allocated to the remote UE.

[0152] In an alternative embodiment of the present application, after the first U2U relay UE determines the local identifiers that it allows to be allocated to the remote UE, the first U2U relay UE may further perform the following steps: After the first target remote UE and the second target remote UE establish a U2U connection through the first U2U relay UE, the first U2U relay UE allocates local identifiers to the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE allows to be allocated to the remote UE.

[0153] Optionally, in an alternative embodiment of the present application, the manner in which the first U2U relay UE allocates local identifiers to the two remote UEs may be one of the following two manners:

[0154] Manner A: The first U2U relay UE allocates different local identifiers to the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE allows to be allocated to the remote UE.

[0155] In an alternative embodiment of the present application, a pair of remote UEs performing U2U communication may be assigned different local identifiers. In this case, after the first target remote UE and the second target remote UE establish a U2U connection through the first U2U relay UE, the first U2U relay UE may assign different local identifiers to the first target remote UE and the second target remote UE according to the local identifiers that it is allowed to assign to remote UEs.

[0156] Mode B: The first U2U relay UE assigns the same local identifier to the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to assign to remote UEs.

[0157] In an alternative embodiment of the present application, a pair of remote UEs performing U2U communication may be assigned the same local identifier. In this case, after the first target remote UE and the second target remote UE establish a U2U connection through the first U2U relay UE, the first U2U relay UE may assign the same local identifier to the first target remote UE and the second target remote UE according to the local identifiers that it is allowed to assign to remote UEs.

[0158] In one embodiment, as Figure 7 shown, a method for local identifier assignment is provided. This method is described by applying it to a second U2U relay UE and includes the following steps:

[0159] Step 701: The second U2U relay UE sends a target message to the first U2U relay UE through a direct communication interface.

[0160] Wherein, the target message carries first information, and the first information at least includes a list of local identifiers of remote UEs.

[0161] In an alternative embodiment of the present application, the target message may include at least one of the following messages: A. A message related to relay discovery, B. A message related to PC5-S connection establishment, C. A message related to PC5-RRC reconfiguration.

[0162] In an alternative embodiment of the present application, the first U2U relay UE may be one of the following U2U relay UEs: A. A relay UE that establishes a PC5-S connection with the second U2U relay UE, B. A relay UE that establishes a PC5-RRC connection with the second U2U relay UE, C. A relay UE that can be discovered by the second U2U relay UE through a direct communication interface discovery process.

[0163] In an alternative embodiment of the present application, the first information carried by the target message includes one of the following:

[0164] A. The first local identifier list, where the first local identifier list includes the local identifier corresponding to the first remote UE that uses the second U2U relay UE for U2U communication or the set of local identifiers that the second U2U relay UE has assigned to the remote UE.

[0165] B. The second local identifier list, where the second local identifier list includes the set of local identifiers corresponding to the second remote UE that uses the second U2U relay UE for U2U communication and does not use the first U2U relay UE for U2U communication.

[0166] C. The third local identifier list, where the third local identifier list includes the local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or the local identifiers in the local identifier list corresponding to the second U2U relay UE that are not assigned by the second U2U relay UE to the remote UE.

[0167] The above content has been described in detail in the method embodiments corresponding to the first U2U relay UE in the embodiments of the present application. To avoid repetition, the embodiments of the present application will not be described in detail here, and reference can be made to the relevant descriptions in the embodiments corresponding to the first U2U relay UE.

[0168] To facilitate understanding of the technical solutions provided by the embodiments of the present application, hereinafter, 4 alternative embodiments will be provided to exemplarily illustrate the technical solutions provided by the embodiments of the present application.

[0169] Among them, the 4 alternative embodiments are all described by taking the Figure 8 scenario shown as an example. As Figure 8 shown, the remote UE1 and the remote UE2 use the U2U relay UE1 and the U2U relay UE3 for U2U communication in a multi-hop U2U relay manner. The remote UE3 and the remote UE4 perform end-to-end communication using the U2U relay UE2 in a single-hop U2U relay manner. On this basis, the remote UE5 and the remote UE6 expect to use the U2U relay UE1 and the U2U relay UE2 for U2U communication in a multi-hop U2U relay manner. At this time, the U2U relay UE1 can assign local identifiers to the remote UE5 and the remote UE6. The following 4 embodiments all introduce how the U2U relay UE1 determines the local identifiers of the remote UEs that it is allowed to assign, and assigns local identifiers to the remote UE5 and the remote UE6 based on the local identifiers of the remote UEs that it is allowed to assign.

[0170] Please refer to Figure 9 , which is the flowchart corresponding to the first embodiment. As Figure 9 shown, it includes the following steps:

[0171] Step 901, the U2U relay UE1 receives the target messages sent by the U2U relay UE2 and the U2U relay UE3.

[0172] Among them, the target message may include at least one of the following messages: A. A message related to relay discovery; B. A message related to PC5-S connection establishment; C. A message related to PC5-RRC reconfiguration.

[0173] Among them, the target message carries first information. The first information carried in the target message sent by the U2U relay UE2 includes a local identifier list 1, and the local identifier list 1 includes a set of local identifiers corresponding to the remote UEs that perform U2U communication using the U2U relay UE2 or the local identifiers that the U2U relay UE2 has assigned to the remote UEs. Taking the case where the local identifier list 1 includes a set of local identifiers corresponding to the remote UEs that perform U2U communication using the U2U relay UE2 as an example, the first information carried in the target message sent by the U2U relay UE3 includes a local identifier list 2, and the local identifier list 2 includes a set of local identifiers corresponding to the remote UEs that perform U2U communication using the U2U relay UE3 or the local identifiers that the U2U relay UE3 has assigned to the remote UEs. Taking the case where the local identifier list 2 includes a set of local identifiers corresponding to the remote UEs that perform U2U communication using the U2U relay UE3 as an example.

[0174] Step 902: The U2U relay UE1 determines the local identifiers that the U2U relay UE1 allows to be assigned to the remote UEs according to the local identifier list 1 and the local identifier list 2.

[0175] The U2U relay UE1 deducts the local identifiers in the local identifier list 1, deducts the local identifiers in the local identifier list 2, deducts the local identifiers that the U2U relay UE1 has already assigned to the remote UEs, and / or deducts the local identifiers of the remote UEs that perform U2U communication using the U2U relay UE1 from its own corresponding local identifier list, so as to obtain the local identifiers that the U2U relay UE1 allows to be assigned to the remote UEs.

[0176] Step 903: The U2U relay UE1 assigns local identifiers to the remote UE5 and the remote UE6 according to the local identifiers that the U2U relay UE1 itself allows to be assigned to the remote UEs.

[0177] If the local identifiers are assigned based on each remote UE, after the remote UE5 and the remote UE6 establish a multi-hop connection through the U2U relay UE1 and the U2U relay UE2, the U2U relay UE1 respectively selects one allowed local identifier of the remote UE that can be assigned to the remote UE5 and the remote UE6 from the local identifiers of the remote UEs that the U2U relay UE1 itself allows to be assigned.

[0178] If the local identifier is allocated based on each pair of remote UEs, after the remote UE5 and the remote UE6 establish a multi-hop end-to-end connection through the U2U relay UE1 and the U2U relay UE2, the U2U relay UE1 allocates a local identifier for the pair of remote UEs composed of the remote UE5 and the remote UE6 respectively from the local identifiers of the remote UEs that it is allowed to allocate.

[0179] Please refer to Figure 10 , which is the flowchart corresponding to the second embodiment. As Figure 10 shown, it includes the following steps:

[0180] Step 1001, the U2U relay UE1 receives the target messages sent by the U2U relay UE2 and the U2U relay UE3.

[0181] Among them, the target message may include at least one of the following messages: A. Messages related to relay discovery, B. Messages related to PC5-S connection establishment, C. Messages related to PC5-RRC reconfiguration.

[0182] Among them, the target message carries the first information. The first information carried by the target message sent by the U2U relay UE2 includes the local identifier list 3, and the local identifier list 3 includes the set of local identifiers corresponding to the remote UEs that use the U2U relay UE2 for U2U communication and do not use the U2U relay UE1 for U2U communication. The first information carried by the target message sent by the U2U relay UE3 includes the local identifier list 4, and the local identifier list 4 includes the set of local identifiers corresponding to the remote UEs that use the U2U relay UE3 for U2U communication and do not use the U2U relay UE1 for U2U communication.

[0183] Step 1002, the U2U relay UE1 determines the local identifiers that the U2U relay UE1 is allowed to allocate for the remote UEs according to the local identifier list 3 and the local identifier list 4.

[0184] The U2U relay UE1 deducts the local identifiers in the local identifier list 3, deducts the local identifiers in the local identifier list 4, deducts the local identifiers that the U2U relay UE1 has already allocated for the remote UEs, and / or deducts the local identifiers of the remote UEs that use the U2U relay UE1 for U2U communication from its own corresponding local identifier list, so as to obtain the local identifiers that the U2U relay UE1 is allowed to allocate for the remote UEs.

[0185] Step 1003, the U2U relay UE1 allocates local identifiers for the remote UE5 and the remote UE6 according to the local identifiers that it is allowed to allocate for the remote UEs.

[0186] If the local identifier is allocated based on each remote UE, after the remote UE5 and the remote UE6 establish a multi-hop connection through the U2U relay UE1 and the U2U relay UE2, the U2U relay UE1 respectively selects an allowed local identifier of the remote UE from the local identifiers of the remote UEs allowed to be allocated by itself for the remote UE5 and the remote UE6.

[0187] If the local identifier is allocated based on each pair of remote UEs, after the remote UE5 and the remote UE6 establish a multi-hop end-to-end connection through the U2U relay UE1 and the U2U relay UE2, the U2U relay UE1 allocates a local identifier for the pair of remote UEs composed of the remote UE5 and the remote UE6 from the local identifiers of the remote UEs allowed to be allocated by itself.

[0188] Please refer to Figure 11 , which is the flowchart corresponding to the third embodiment. As Figure 11 shown, it includes the following steps:

[0189] Step 1101, the U2U relay UE1 receives the target messages sent by the U2U relay UE2 and the U2U relay UE3.

[0190] Among them, the target message may include at least one of the following messages: A. A message related to relay discovery, B. A message related to PC5-S connection establishment, C. A message related to PC5-RRC reconfiguration.

[0191] Among them, the target message carries first information. The first information carried by the target message sent by the U2U relay UE2 includes a local identifier list 5, and the local identifier list 5 includes local identifiers not occupied by remote UEs that have not used the U2U relay UE2 for U2U communication in the local identifier list corresponding to the U2U relay UE2 or local identifiers not allocated by the U2U relay UE2 to remote UEs in the local identifier list corresponding to the U2U relay UE2. Taking the local identifier list 5 including local identifiers not occupied by remote UEs that have not used the U2U relay UE2 for U2U communication in the local identifier list corresponding to the U2U relay UE2 as an example, the first information carried by the target message sent by the U2U relay UE3 includes a local identifier list 6, and the local identifier list 6 includes local identifiers not occupied by remote UEs that have not used the U2U relay UE3 for U2U communication in the local identifier list corresponding to the U2U relay UE3 or local identifiers not allocated by the U2U relay UE3 to remote UEs in the local identifier list corresponding to the U2U relay UE3. Taking the local identifier list 6 including local identifiers not occupied by remote UEs that have not used the U2U relay UE3 for U2U communication in the local identifier list corresponding to the U2U relay UE3 as an example.

[0192] Step 1102: The U2U relay UE1 determines the local identifiers that the U2U relay UE1 is allowed to allocate to the remote UEs according to the local identifier list 5 and the local identifier list 6.

[0193] For example, the U2U relay UE1 deducts the local identifiers that the U2U relay UE1 has already allocated to the remote UEs and / or deducts the local identifiers of the remote UEs using the U2U relay UE1 for U2U communication from its corresponding local identifier list to obtain the local identifier list 7. The U2U relay UE1 takes the first intersection of the local identifier list 7, the local identifier list 5 sent by the U2U relay UE2, and the local identifier list 6 sent by the U2U relay UE3, and determines the local identifiers that the U2U relay UE1 is allowed to allocate to the remote UEs according to the first intersection.

[0194] For another example, the U2U relay UE1 takes the second intersection of its own corresponding local identifier list, the local identifier list 5 sent by the U2U relay UE2, and the local identifier list 6 sent by the U2U relay UE3. The U2U relay UE1 deducts the local identifiers that the U2U relay UE1 has already allocated to the remote UEs and / or deducts the local identifiers of the remote UEs using the U2U relay UE1 for U2U communication from the second intersection to obtain the local identifier list 8, and determines the local identifiers that the U2U relay UE1 is allowed to allocate to the remote UEs according to the local identifier list 8.

[0195] Step 1103: The U2U relay UE1 allocates local identifiers to the remote UE5 and the remote UE6 according to the local identifiers that it is allowed to allocate to the remote UEs.

[0196] If the local identifier is allocated based on each remote UE, after the remote UE5 and the remote UE6 establish a multi-hop connection through the U2U relay UE1 and the U2U relay UE2, the U2U relay UE1 respectively selects one local identifier that is allowed to be allocated to the remote UE from the local identifiers of the remote UEs that it is allowed to allocate for the remote UE5 and the remote UE6.

[0197] If the local identifier is allocated based on each pair of remote UEs, after the remote UE5 and the remote UE6 establish a multi-hop end-to-end connection through the U2U relay UE1 and the U2U relay UE2, the U2U relay UE1 allocates one local identifier to the pair of remote UEs composed of the remote UE5 and the remote UE6 from the local identifiers of the remote UEs that it is allowed to allocate.

[0198] Please refer to Figure 12 , which is the flowchart corresponding to the fourth embodiment. As Figure 12 shown, it includes the following steps:

[0199] Step 1201: The U2U relay UE1 obtains the pre-configured information and obtains the first information according to the pre-configured information.

[0200] The U2U relay UE1 can obtain the list 9 of local identifiers that the U2U relay UE1 is allowed to allocate to the remote UE from the pre-configured information, and use this list 9 of local identifiers as the first information.

[0201] Step 1202: The U2U relay UE1 determines the local identifiers that the U2U relay UE1 is allowed to allocate to the remote UE according to the first information obtained from the pre-configured information.

[0202] The U2U relay UE1 uses the local identifiers in the list 9 of local identifiers as the local identifiers that the U2U relay UE1 is allowed to allocate to the remote UE.

[0203] Step 1203: The U2U relay UE1 allocates local identifiers to the remote UE5 and the remote UE6 according to the local identifiers that it is allowed to allocate to the remote UE.

[0204] If the local identifiers are allocated based on each remote UE, then after the remote UE5 and the remote UE6 establish a multi-hop connection through the U2U relay UE1 and the U2U relay UE2, the U2U relay UE1 respectively selects one local identifier that is allowed to be allocated to the remote UE from the local identifiers of the remote UE that it is allowed to allocate for the remote UE5 and the remote UE6.

[0205] If the local identifiers are allocated based on each pair of remote UEs, then after the remote UE5 and the remote UE6 establish a multi-hop end-to-end connection through the U2U relay UE1 and the U2U relay UE2, the U2U relay UE1 allocates one local identifier to the pair of remote UEs composed of the remote UE5 and the remote UE6 from the local identifiers of the remote UE that it is allowed to allocate.

[0206] It should be understood that although Figure 6 - 12 the steps in the flowchart are shown in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, Figure 6 - 12 at least a part of the steps in

[0207] In one embodiment, as Figure 13 shown, a local identifier allocation device 1300 for the first U2U relay UE is provided, including: a determination unit 1301.

[0208] Among them, the determination unit 1301 is configured to determine, according to the first information, a local identifier that the first U2U relay UE is allowed to allocate to the remote UE; wherein, the first information at least includes a list of local identifiers of the remote UE.

[0209] Please refer to Figure 14 , which shows another local identifier allocation device 1400 provided by an embodiment of the present application. Optionally, in addition to the determination unit 1301, the local identifier allocation device 1400 further includes an acquisition unit 1302 and an allocation unit 1303.

[0210] The acquisition unit 1302 is configured to perform at least one of the following: receive a target message sent by a second U2U relay UE through a direct communication interface, where the target message carries the first information, and the number of second U2U relay UEs is one or more; acquire the first information according to pre-configured information.

[0211] In an optional embodiment of the present application, the target message includes at least one of the following messages: a message related to relay discovery; a message related to PC5-S connection establishment; a message related to PC5-RRC reconfiguration.

[0212] In an optional embodiment of the present application, the second U2U relay UE is a relay UE that establishes a PC5-S connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that establishes a PC5-RRC connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that can be discovered by the first U2U relay UE through a direct communication interface discovery process.

[0213] In an optional embodiment of the present application, the first information includes one of the following: a first local identifier list, where the first local identifier list includes local identifiers corresponding to first remote UEs that perform U2U communication using the second U2U relay UE or a set of local identifiers that the second U2U relay UE has already allocated to remote UEs; a second local identifier list, where the second local identifier list includes a set of local identifiers corresponding to second remote UEs that perform U2U communication using the second U2U relay UE and do not perform U2U communication using the first U2U relay UE; a third local identifier list, where the third local identifier list includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not allocated by the second U2U relay UE to remote UEs, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for allocation to remote UEs.

[0214] In an alternative embodiment of the present application, the remote UE that uses the second U2U relay UE for U2U communication includes: a remote UE that uses the second U2U relay UE for U2U communication through a single-hop U2U relay mode and / or a multi-hop U2U relay mode; a remote UE that does not use the first U2U relay UE for U2U communication includes: a remote UE that does not use the first U2U relay UE for U2U communication through a single-hop U2U relay mode and / or a multi-hop U2U relay mode.

[0215] In an alternative embodiment of the present application, the determining unit 1301 is specifically configured to: determine the local identifier that the first U2U relay UE allows to allocate to the remote UE according to the first information, the local identifier that the first U2U relay UE has already allocated to the remote UE, and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication.

[0216] In an alternative embodiment of the present application, the determining unit 1301 is specifically configured to perform at least one of the following: deduct the local identifiers in the first local identifier list, the local identifier that the first U2U relay UE has already allocated to the remote UE, and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE to obtain the local identifier that the first U2U relay UE allows to allocate to the remote UE; deduct the local identifiers in the second local identifier list, the local identifier that the first U2U relay UE has already allocated to the remote UE, and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE to obtain the local identifier that the first U2U relay UE allows to allocate to the remote UE; deduct the local identifier that the first U2U relay UE has already allocated to the remote UE and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE to obtain a fourth local identifier list, and the first U2U relay UE takes a first intersection of the fourth local identifier list and the third local identifier list sent by one or more second U2U relay UEs, and determines the local identifier that the first U2U relay UE allows to allocate to the remote UE according to the first intersection; take a second intersection of the local identifier list corresponding to the first U2U relay UE and the third local identifier list sent by one or more second U2U relay UEs, and the first U2U relay UE deducts the local identifier that the first U2U relay UE has already allocated to the remote UE and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication from the second intersection to obtain a fifth local identifier list, and determines the local identifier that the first U2U relay UE allows to allocate to the remote UE according to the fifth local identifier list.

[0217] In an alternative embodiment of the present application, the local identifier list corresponding to the first U2U relay UE is pre-configured or configured by a network device.

[0218] In an alternative embodiment of the present application, the obtaining unit 1302 is specifically configured to: obtain, as the first information, the sixth local identifier list that the first U2U relay UE is allowed to allocate to a remote UE from the pre-configured information.

[0219] In an alternative embodiment of the present application, the determining unit 1301 is specifically configured to: determine, according to the sixth local identifier list, the local identifier that the first U2U relay UE is allowed to allocate to a remote UE.

[0220] The allocating unit 1303 is configured to, after a first target remote UE and a second target remote UE establish a U2U connection through the first U2U relay UE, allocate local identifiers to the first target remote UE and the second target remote UE according to the local identifier that the first U2U relay UE is allowed to allocate to a remote UE.

[0221] In an alternative embodiment of the present application, the allocating unit 1303 is specifically configured to: allocate different local identifiers to the first target remote UE and the second target remote UE according to the local identifier that the first U2U relay UE is allowed to allocate to a remote UE; or, allocate the same local identifier to the first target remote UE and the second target remote UE according to the local identifier that the first U2U relay UE is allowed to allocate to a remote UE.

[0222] In one embodiment, as Figure 15 shown, a local identifier allocation device 1500 for a second U2U relay UE is provided, including: a sending unit 1501.

[0223] The sending unit 1501 is configured to send a target message to the first U2U relay UE through a direct communication interface, where the target message carries the first information, and the first information includes at least the local identifier list of the remote UE.

[0224] In an alternative embodiment of the present application, the target message includes at least one of the following messages: a message related to relay discovery; a message related to PC5-S connection establishment; a message related to PC5-RRC reconfiguration.

[0225] In an alternative embodiment of the present application, the first U2U relay UE is a relay UE that establishes a PC5-S connection with the second U2U relay UE; or, the first U2U relay UE is a relay UE that establishes a PC5-RRC connection with the second U2U relay UE; or, the first U2U relay UE is a relay UE that can be discovered by the second U2U relay UE through a direct communication interface discovery process.

[0226] In an alternative embodiment of the present application, the first information carried by the target message includes one of the following: a first local identifier list, where the first local identifier list includes local identifiers corresponding to first remote UEs that use a second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has assigned to the remote UEs; a second local identifier list, where the second local identifier list includes a set of local identifiers corresponding to second remote UEs that use the second U2U relay UE for U2U communication and do not use the first U2U relay UE for U2U communication; a third local identifier list, where the third local identifier list includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not assigned by the second U2U relay UE to the remote UEs, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for assignment to the remote UEs.

[0227] In an alternative embodiment of the present application, the remote UEs that use the second U2U relay UE for U2U communication include: remote UEs that use the second U2U relay UE for U2U communication through single-hop U2U relay mode and / or multi-hop U2U relay mode; the remote UEs that do not use the first U2U relay UE for U2U communication include: remote UEs that do not use the first U2U relay UE for U2U communication through single-hop U2U relay mode and / or multi-hop U2U relay mode.

[0228] For the specific limitations on the local identifier allocation device, reference can be made to the limitations on the local identifier allocation method in the foregoing text, which will not be elaborated here. Each unit in the above local identifier allocation device can be implemented in whole or in part by software, hardware, and their combination. The above units can be embedded in the processor in the U2U relay UE in hardware form or be independent of it, or can be stored in the memory in the U2U relay UE in software form, so that the processor can call and execute the operations corresponding to each of the above units.

[0229] It should be noted that the division of units in the embodiments of the present application is illustrative, merely a logical function division, and there may be other division methods in actual implementation. Additionally, in each embodiment of the present application, the functional units can be integrated in one processing unit, or each unit can exist physically alone, or two or more units can be integrated in one unit. The above integrated units can be implemented in the form of hardware or in the form of software functional units.

[0230] When the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to enable a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of this application.

[0231] It should be noted here that the above-mentioned device provided in the embodiments of this application can implement all the method steps implemented in the above-mentioned method embodiments and can achieve the same technical effects. The same parts and beneficial effects as those in the method embodiments will not be specifically described in this embodiment.

[0232] In one embodiment, a U2U relay UE is provided. Refer to Figure 16 . Figure 16 The U2U relay UE1600 shown includes at least one processor 1601 and a memory 1602. Each component in the U2U relay UE1600 is coupled together through a bus system 1603. It can be understood that the bus system 1603 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 1603 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clear illustration, in Figure 16 all kinds of buses are labeled as the bus system 1603. In addition, in the embodiments of this application, a transceiver 1604 is also included. The transceiver can be multiple components, that is, it includes a transmitter and a receiver, and provides a unit for communicating with various other devices on the transmission medium.

[0233] In addition, the U2U relay UE may further include a user interface, and the user interface may include a display, a keyboard, or a pointing device (for example, a mouse, a trackball, a touchpad, or a touch screen, etc.).

[0234] It can be understood that the memory 1602 in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (abbreviation: ROM), a programmable read-only memory (abbreviation: PROM), an erasable programmable read-only memory (abbreviation: EPROM), an electrically erasable programmable read-only memory (abbreviation: EEPROM), or a flash memory. The volatile memory can be a random access memory (abbreviation: RAM), which is used as an external cache. By way of example but not limitation, many forms of RAM are available, such as static random access memory (abbreviation: SRAM), dynamic random access memory (abbreviation: DRAM), synchronous dynamic random access memory (abbreviation: SDRAM), double data rate synchronous dynamic random access memory (abbreviation: DDR SDRAM), enhanced synchronous dynamic random access memory (abbreviation: ESDRAM), synchlink dynamic random access memory (abbreviation: SLDRAM), and direct rambus random access memory (abbreviation: DRRAM). The memory 1602 of the systems and methods described in the embodiments of the present application is intended to include but not be limited to these and any other suitable types of memories.

[0235] In some embodiments, the memory 1602 stores the following elements, executable modules, or data structures, or subsets thereof, or extended sets thereof: an operating system 16021 and an application program 16022.

[0236] Among them, the operating system 16021 includes various system programs, such as a framework layer, a core library layer, a driver layer, etc., and is used to implement various basic services and process hardware-based tasks. The application program 16022 includes various application programs, such as a media player (abbreviation: Media Player), a browser (abbreviation: Browser), etc., and is used to implement various application services. The program for implementing the method of the embodiments of the present application can be included in the application program 16022.

[0237] Some or all of the methods disclosed in the embodiments of the present application can be applied to the processor 1601, or implemented by the processor 1601, or implemented in cooperation with other components (such as a transceiver) by the processor 1601. The processor 1601 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit in the hardware of the processor 1601 or the instructions in the form of software. The above-mentioned processor 1601 may be a general-purpose processor, a digital signal processor (abbreviation: DSP for Digital Signal Processor in English), an application-specific integrated circuit (abbreviation: ASIC for Application Specific Integrated Circuit in English), a field-programmable gate array (abbreviation: FPGA for Field Programmable Gate Array in English), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. It can implement or execute various methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc. The steps of the method disclosed in combination with the embodiments of the present application can be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor. The software module may be located in a mature storage medium in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. This storage medium is located in the memory 1602, and the processor 1601 reads the information in the memory 1602 and combines its hardware to complete the steps of the above method.

[0238] It can be understood that these embodiments described in the embodiments of the present application can be implemented by hardware, software, firmware, middleware, microcode, or a combination thereof. For hardware implementation, the processing unit can be implemented in one or more application-specific integrated circuits (abbreviation: ASIC for Application Specific Integrated Circuits in English), digital signal processors (abbreviation: DSP for Digital Signal Processing in English), digital signal processing devices (abbreviation: DSPD for DSP Device in English), programmable logic devices (abbreviation: PLD for Programmable Logic Device in English), field-programmable gate arrays (abbreviation: FPGA for Field-Programmable Gate Array in English), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the present application, or a combination thereof.

[0239] For software implementation, the technologies described in the embodiments of the present application can be implemented by modules (such as procedures, functions, etc.) that execute the functions described in the embodiments of the present application. The software code can be stored in the memory and executed by the processor 1601. The memory can be implemented inside or outside the processor 1601.

[0240] Specifically, Figure 16 The U2U relay UE shown can execute the method steps corresponding to the first U2U relay UE in the above method embodiments, or can execute the method steps corresponding to the second U2U relay UE in the above method embodiments.

[0241] When executing the method steps corresponding to the first U2U relay UE in the above method embodiments:

[0242] The processor 1601 is configured to perform the following operations: determine a local identifier that the first U2U relay UE is allowed to allocate to the remote UE according to the first information; wherein, the first information at least includes a list of local identifiers of the remote UE.

[0243] In one embodiment, the processor 1601 is further configured to perform at least one of the following operations: control the transceiver to receive a target message sent by the second U2U relay UE through a direct communication interface, the target message carries the first information, and the number of the second U2U relay UEs is one or more; obtain the first information according to pre-configured information.

[0244] In one embodiment, the target message includes at least one of the following messages: a message related to relay discovery; a message related to PC5-S connection establishment; a message related to PC5-RRC reconfiguration.

[0245] In one embodiment, the second U2U relay UE is a relay UE that establishes a PC5-S connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that establishes a PC5-RRC connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that can be discovered by the first U2U relay UE through a direct communication interface discovery process.

[0246] In one embodiment, the first information includes one of the following: a first local identifier list, which includes local identifiers corresponding to first remote UEs that use a second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has assigned to remote UEs; a second local identifier list, which includes a set of local identifiers corresponding to second remote UEs that use the second U2U relay UE for U2U communication and do not use a first U2U relay UE for U2U communication; a third local identifier list, which includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not assigned by the second U2U relay UE to remote UEs, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for assignment to remote UEs.

[0247] In one embodiment, remote UEs that use a second U2U relay UE for U2U communication include: remote UEs that use the second U2U relay UE for U2U communication through single-hop U2U relay mode and / or multi-hop U2U relay mode; remote UEs that do not use a first U2U relay UE for U2U communication include: remote UEs that do not use the first U2U relay UE for U2U communication through single-hop U2U relay mode and / or multi-hop U2U relay mode.

[0248] In one embodiment, the processor 1601 is specifically configured to perform the following operations: determine local identifiers that the first U2U relay UE is allowed to assign to remote UEs according to the first information, local identifiers that the first U2U relay UE has already assigned to remote UEs, and / or local identifiers of remote UEs that use the first U2U relay UE for U2U communication.

[0249] In one embodiment, the processor 1601 is specifically configured to perform at least one of the following operations: deduct the local identifiers in the first local identifier list from the local identifier list corresponding to the first U2U relay UE, deduct the local identifiers already allocated by the first U2U relay UE to the remote UE, and / or deduct the local identifiers of the remote UE using the first U2U relay UE for U2U communication, so as to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE; deduct the local identifiers in the second local identifier list from the local identifier list corresponding to the first U2U relay UE, deduct the local identifiers already allocated by the first U2U relay UE to the remote UE, and / or deduct the local identifiers of the remote UE using the first U2U relay UE for U2U communication, so as to obtain the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE; deduct the local identifiers already allocated by the first U2U relay UE to the remote UE and / or deduct the local identifiers of the remote UE using the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE to obtain a fourth local identifier list, and the first U2U relay UE takes a first intersection of the fourth local identifier list and the third local identifier list sent by one or more second U2U relay UEs, and determines the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE according to the first intersection; take a second intersection of the local identifier list corresponding to the first U2U relay UE and the third local identifier list sent by one or more second U2U relay UEs, and the first U2U relay UE deducts the local identifiers already allocated by the first U2U relay UE to the remote UE and / or deducts the local identifiers of the remote UE using the first U2U relay UE for U2U communication from the second intersection to obtain a fifth local identifier list, and determines the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE according to the fifth local identifier list.

[0250] In one embodiment, the local identifier list corresponding to the first U2U relay UE is pre-configured or configured by a network device.

[0251] In one embodiment, the processor 1601 is specifically configured to perform the following operation: obtain the sixth local identifier list that the first U2U relay UE is allowed to allocate to the remote UE in the pre-configured information as the first information.

[0252] In one embodiment, the processor 1601 is specifically configured to perform the following operation: determine the local identifiers that the first U2U relay UE is allowed to allocate to the remote UE according to the sixth local identifier list.

[0253] In one embodiment, the processor 1601 is further configured to perform the following operations: after the first target remote UE and the second target remote UE establish a U2U connection through the first U2U relay UE, allocate local identifiers for the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate for remote UEs.

[0254] In one embodiment, the processor 1601 is specifically configured to perform the following operations: allocate different local identifiers for the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate for remote UEs; or allocate the same local identifiers for the first target remote UE and the second target remote UE according to the local identifiers that the first U2U relay UE is allowed to allocate for remote UEs.

[0255] When performing the method steps corresponding to the second U2U relay UE in the above method embodiments:

[0256] The processor 1601 is configured to perform the following operations: control the transceiver to send a target message to the first U2U relay UE through a direct communication interface, where the target message carries first information, and the first information at least includes a list of local identifiers of remote UEs.

[0257] In one embodiment, the target message includes at least one of the following messages: a message related to relay discovery; a message related to PC5-S connection establishment; a message related to PC5-RRC reconfiguration.

[0258] In one embodiment, the first U2U relay UE is a relay UE that establishes a PC5-S connection with the second U2U relay UE; or the first U2U relay UE is a relay UE that establishes a PC5-RRC connection with the second U2U relay UE; or the first U2U relay UE is a relay UE that can be discovered by the second U2U relay UE through a direct communication interface discovery process.

[0259] In one embodiment, the first information carried by the target message includes one of the following: a first local identifier list, where the first local identifier list includes the local identifier corresponding to the first remote UE that uses the second U2U relay UE for U2U communication or the set of local identifiers that the second U2U relay UE has assigned to the remote UE; a second local identifier list, where the second local identifier list includes the set of local identifiers corresponding to the second remote UE that uses the second U2U relay UE for U2U communication and does not use the first U2U relay UE for U2U communication; a third local identifier list, where the third local identifier list includes the local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or the local identifiers in the local identifier list corresponding to the second U2U relay UE that are not assigned by the second U2U relay UE to the remote UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for assignment to the remote UE.

[0260] In one embodiment, the remote UE that uses the second U2U relay UE for U2U communication includes: the remote UE that uses the second U2U relay UE for U2U communication through the single-hop U2U relay method and / or the multi-hop U2U relay method; the remote UE that does not use the first U2U relay UE for U2U communication includes: the remote UE that does not use the first U2U relay UE for U2U communication through the single-hop U2U relay method and / or the multi-hop U2U relay method.

[0261] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented: determining the local identifiers that the first U2U relay UE is allowed to assign to the remote UE according to the first information; where the first information at least includes the local identifier list of the remote UE.

[0262] In one embodiment, the acquisition method of the first information includes at least one of the following: the first U2U relay UE receives a target message sent by the second U2U relay UE through a direct communication interface, the target message carries the first information, and the number of second U2U relay UEs is one or more; the first U2U relay UE obtains the first information according to pre-configured information.

[0263] In one embodiment, the target message includes at least one of the following messages: a message related to relay discovery; a message related to PC5-S connection establishment; a message related to PC5-RRC reconfiguration.

[0264] In one embodiment, the second U2U relay UE is a relay UE that establishes a PC5-S connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that establishes a PC5-RRC connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that can be discovered by the first U2U relay UE through the direct communication interface discovery process.

[0265] In one embodiment, the first information includes one of the following: a first local identifier list, the first local identifier list includes local identifiers corresponding to first remote UEs that use the second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has assigned to remote UEs; a second local identifier list, the second local identifier list includes a set of local identifiers corresponding to second remote UEs that use the second U2U relay UE for U2U communication and do not use the first U2U relay UE for U2U communication; a third local identifier list, the third local identifier list includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not assigned by the second U2U relay UE to remote UEs, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for assignment to remote UEs.

[0266] In one embodiment, the remote UEs that use the second U2U relay UE for U2U communication include: remote UEs that use the second U2U relay UE for U2U communication through single-hop U2U relay mode and / or multi-hop U2U relay mode; the remote UEs that do not use the first U2U relay UE for U2U communication include: remote UEs that do not use the first U2U relay UE for U2U communication through single-hop U2U relay mode and / or multi-hop U2U relay mode.

[0267] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented: determining local identifiers that the first U2U relay UE is allowed to assign to remote UEs according to the first information, local identifiers that the first U2U relay UE has already assigned to remote UEs, and / or local identifiers of remote UEs that use the first U2U relay UE for U2U communication.

[0268] In one embodiment, when the computer program is executed by a processor, it further implements at least one of the following steps: deducting local identifiers in the first local identifier list from the local identifier list corresponding to the first U2U relay UE, deducting local identifiers already allocated by the first U2U relay UE to remote UEs, and / or deducting local identifiers of remote UEs using the first U2U relay UE for U2U communication, so as to obtain local identifiers that the first U2U relay UE is allowed to allocate to remote UEs; deducting local identifiers in the second local identifier list from the local identifier list corresponding to the first U2U relay UE, deducting local identifiers already allocated by the first U2U relay UE to remote UEs, and / or deducting local identifiers of remote UEs using the first U2U relay UE for U2U communication, so as to obtain local identifiers that the first U2U relay UE is allowed to allocate to remote UEs; deducting local identifiers already allocated by the first U2U relay UE to remote UEs and / or deducting local identifiers of remote UEs using the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE to obtain a fourth local identifier list, the first U2U relay UE taking a first intersection of the fourth local identifier list and a third local identifier list sent by one or more second U2U relay UEs, and determining, according to the first intersection, local identifiers that the first U2U relay UE is allowed to allocate to remote UEs; taking a second intersection of the local identifier list corresponding to the first U2U relay UE and a third local identifier list sent by one or more second U2U relay UEs, the first U2U relay UE deducting local identifiers already allocated by the first U2U relay UE to remote UEs and / or deducting local identifiers of remote UEs using the first U2U relay UE for U2U communication in the second intersection to obtain a fifth local identifier list, and determining, according to the fifth local identifier list, local identifiers that the first U2U relay UE is allowed to allocate to remote UEs.

[0269] In one embodiment, the local identifier list corresponding to the first U2U relay UE is pre-configured or configured by a network device.

[0270] In one embodiment, when the computer program is executed by a processor, it further implements the following step: obtaining, as a first piece of information, a sixth local identifier list that the first U2U relay UE is allowed to allocate to remote UEs in the pre-configured information.

[0271] In one embodiment, when the computer program is executed by a processor, it further implements the following step: determining, according to the sixth local identifier list, local identifiers that the first U2U relay UE is allowed to allocate to remote UEs.

[0272] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented: after a U2U connection is established between a first target remote UE and a second target remote UE through a first U2U relay UE, local identifiers are assigned to the first target remote UE and the second target remote UE according to the local identifiers allowed to be assigned to remote UEs by the first U2U relay UE.

[0273] In one embodiment, when the computer program is executed by a processor, the following steps are further implemented: different local identifiers are assigned to the first target remote UE and the second target remote UE according to the local identifiers allowed to be assigned to remote UEs by the first U2U relay UE; or the same local identifier is assigned to the first target remote UE and the second target remote UE according to the local identifiers allowed to be assigned to remote UEs by the first U2U relay UE.

[0274] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0275] A target message is sent to the first U2U relay UE through a direct communication interface. The target message carries first information, where the first information at least includes a list of local identifiers of remote UEs.

[0276] In one embodiment, the target message includes at least one of the following messages: a message related to relay discovery; a message related to PC5-S connection establishment; a message related to PC5-RRC reconfiguration.

[0277] In one embodiment, the first U2U relay UE is a relay UE that establishes a PC5-S connection with a second U2U relay UE; or the first U2U relay UE is a relay UE that establishes a PC5-RRC connection with a second U2U relay UE; or the first U2U relay UE is a relay UE that can be discovered by the second U2U relay UE through a direct communication interface discovery process.

[0278] In one embodiment, the first information carried in the target message includes one of the following: a first local identifier list, which includes local identifiers corresponding to first remote UEs that use a second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has assigned to remote UEs; a second local identifier list, which includes a set of local identifiers corresponding to second remote UEs that use the second U2U relay UE for U2U communication and do not use a first U2U relay UE for U2U communication; a third local identifier list, which includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not assigned by the second U2U relay UE to remote UEs, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for assignment to remote UEs.

[0279] In one embodiment, remote UEs that use a second U2U relay UE for U2U communication include: remote UEs that use the second U2U relay UE for U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method; remote UEs that do not use a first U2U relay UE for U2U communication include: remote UEs that do not use the first U2U relay UE for U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

[0280] Those of ordinary skill in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the various embodiments provided in this application can include at least one of non-volatile and volatile memories. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0281] The technical features of the above embodiments can be combined arbitrarily. For the sake of concise description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.

[0282] The above-described embodiments merely represent several implementation manners of the present application. The description is relatively specific and detailed, but it should not be construed as a limitation on the scope of the invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the appended claims.

Claims

1. A method for local identifier allocation, characterized in that, the method includes: A first user equipment to user equipment U2U relay UE determines local identifiers that the first U2U relay UE is allowed to allocate to a remote UE according to first information; wherein, the first information at least includes a local identifier list of the remote UE.

2. The method according to claim 1, characterized in that, the obtaining manner of the first information includes at least one of the following: The first U2U relay UE receives a target message sent by a second U2U relay UE through a direct communication interface, the target message carries the first information, and the number of the second U2U relay UEs is one or more; The first U2U relay UE obtains the first information according to pre-configured information.

3. The method according to claim 2, characterized in that, the target message includes at least one of the following messages: A message related to relay discovery; A message related to PC5-S connection establishment; A message related to PC5-RRC reconfiguration.

4. The method according to claim 2, characterized in that, the second U2U relay UE is a relay UE that establishes a PC5-S connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that establishes a PC5-RRC connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that can be discovered by the first U2U relay UE through a direct communication interface discovery process.

5. The method according to claim 2, characterized in that, the first information includes one of the following: A first local identifier list, the first local identifier list includes a set of local identifiers corresponding to a first remote UE that uses the second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has already allocated to remote UEs; A second local identifier list, the second local identifier list includes a set of local identifiers corresponding to a second remote UE that uses the second U2U relay UE for U2U communication and does not use the first U2U relay UE for U2U communication; A third local identifier list, the third local identifier list includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not allocated by the second U2U relay UE to remote UEs, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for allocation to remote UEs.

6. The method according to claim 5, characterized in that, the remote UEs that use the second U2U relay UE for U2U communication include: remote UEs that use the second U2U relay UE for U2U communication through a single-hop U2U relay manner and / or a multi-hop U2U relay manner; The remote UE that does not use the first U2U relay UE for U2U communication includes: a remote UE that does not use the first U2U relay UE for U2U communication through a single-hop U2U relay manner and / or a multi-hop U2U relay manner.

7. The method according to claim 5, wherein, the first user equipment-to-user equipment U2U relay UE determines the local identifier allowed to be allocated to the remote UE according to the first information, including: the first U2U relay UE determines the local identifier allowed to be allocated to the remote UE according to the first information, the local identifier already allocated by the first U2U relay UE to the remote UE, and / or the local identifier of the remote UE using the first U2U relay UE for U2U communication.

8. The method according to claim 7, wherein, the first U2U relay UE determines the local identifier allowed to be allocated to the remote UE according to the first information, the local identifier already allocated by the first U2U relay UE to the remote UE, and / or the local identifier of the remote UE using the first U2U relay UE for U2U communication, including at least one of the following: the first U2U relay UE deducts the local identifiers in the first local identifier list, the local identifier already allocated by the first U2U relay UE to the remote UE, and / or the local identifier of the remote UE using the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE, so as to obtain the local identifier allowed to be allocated to the remote UE by the first U2U relay UE; the first U2U relay UE deducts the local identifiers in the second local identifier list, the local identifier already allocated by the first U2U relay UE to the remote UE, and / or the local identifier of the remote UE using the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE, so as to obtain the local identifier allowed to be allocated to the remote UE by the first U2U relay UE; the first U2U relay UE deducts the local identifier already allocated by the first U2U relay UE to the remote UE and / or the local identifier of the remote UE using the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE to obtain a fourth local identifier list, and the first U2U relay UE takes a first intersection of the fourth local identifier list and the third local identifier list sent by one or more of the second U2U relay UEs, and determines the local identifier allowed to be allocated to the remote UE by the first U2U relay UE according to the first intersection; The first U2U relay UE takes a second intersection of the local identity list corresponding to the first U2U relay UE and the third local identity list sent by one or more of the second U2U relay UEs, and the first U2U relay UE deducts the local identities already allocated by the first U2U relay UE for remote UEs and / or deducts the local identities of the remote UEs using the first U2U relay UE for U2U communication from the second intersection to obtain a fifth local identity list, and determines the local identities that the first U2U relay UE is allowed to allocate for remote UEs according to the fifth local identity list.

9. The method according to claim 8, wherein, the local identity list corresponding to the first U2U relay UE is pre-configured or configured by a network device.

10. The method according to claim 2, wherein, the first U2U relay UE obtains the first information according to pre-configured information, including: the first U2U relay UE obtains the sixth local identity list that the first U2U relay UE is allowed to allocate for remote UEs in the pre-configured information as the first information.

11. The method according to claim 10, wherein, the first user equipment to user equipment U2U relay UE determines the local identities that the first U2U relay UE is allowed to allocate for remote UEs according to the first information, including: the first U2U relay UE determines the local identities that the first U2U relay UE is allowed to allocate for remote UEs according to the sixth local identity list.

12. The method according to any one of claims 1 to 11, wherein, the method further includes: after a first target remote UE and a second target remote UE establish a U2U connection through the first U2U relay UE, the first U2U relay UE allocates local identities for the first target remote UE and the second target remote UE according to the local identities that the first U2U relay UE is allowed to allocate for remote UEs.

13. The method according to claim 12, wherein, the first U2U relay UE allocates local identities for the first target remote UE and the second target remote UE according to the local identities that the first U2U relay UE is allowed to allocate for remote UEs, including: the first U2U relay UE allocates different local identities for the first target remote UE and the second target remote UE according to the local identities that the first U2U relay UE is allowed to allocate for remote UEs; or, the first U2U relay UE allocates the same local identities for the first target remote UE and the second target remote UE according to the local identities that the first U2U relay UE is allowed to allocate for remote UEs.

14. A method for local identity allocation, wherein, the method includes: a second U2U relay UE sends a target message to a first U2U relay UE through a direct communication interface, the target message carrying first information, wherein the first information includes at least a local identity list of a remote UE.

15. The method according to claim 14, It is characterized in that the target message includes at least one of the following messages: messages related to relay discovery; messages related to the establishment of a PC5-S connection; messages related to PC5-RRC reconfiguration.

16. The method according to claim 14, It is characterized in that the first U2U relay UE is a relay UE that establishes a PC5-S connection with the second U2U relay UE; or, the first U2U relay UE is a relay UE that establishes a PC5-RRC connection with the second U2U relay UE; or, the first U2U relay UE is a relay UE that can be discovered by the second U2U relay UE through a direct communication interface discovery process.

17. The method according to claim 14, It is characterized in that the first information carried by the target message includes one of the following: a first local identifier list, which includes a set of local identifiers corresponding to a first remote UE that uses the second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has assigned to remote UEs; a second local identifier list, which includes a set of local identifiers corresponding to a second remote UE that uses the second U2U relay UE for U2U communication and does not use the first U2U relay UE for U2U communication; a third local identifier list, which includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not assigned by the second U2U relay UE to remote UEs, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for assignment to remote UEs.

18. The method according to claim 17, It is characterized in that the remote UE that uses the second U2U relay UE for U2U communication includes: a remote UE that uses the second U2U relay UE for U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method; the remote UE that does not use the first U2U relay UE for U2U communication includes: a remote UE that does not use the first U2U relay UE for U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

19. A local identifier allocation device, It is characterized in that for a first U2U relay UE, the device includes: a determination unit, configured to determine local identifiers that the first U2U relay UE is allowed to allocate to remote UEs according to first information; wherein the first information includes at least a local identifier list of remote UEs.

20. A local identifier allocation device, It is characterized in that for a second U2U relay UE, the device includes: a sending unit, configured to send a target message carrying first information to the first U2U relay UE through a direct communication interface, where the first information includes at least a local identifier list of remote UEs.

21. A first U2U relay UE, characterized in that, it includes a memory, a transceiver, and a processor: The memory is used to store computer programs; the transceiver is used to send and receive data under the control of the processor; the processor is used to read the computer programs in the memory and perform the following operations: Determine the local identifier that the first U2U relay UE is allowed to allocate to a remote UE according to the first information; wherein, the first information at least includes a list of local identifiers of the remote UE.

22. The first U2U relay UE according to claim 21, characterized in that, the processor is further used to perform at least one of the following operations: Control the transceiver to receive a target message sent by a second U2U relay UE through a direct communication interface, the target message carries the first information, and the number of the second U2U relay UEs is one or more; Obtain the first information according to pre-configured information.

23. The first U2U relay UE according to claim 22, characterized in that, the target message includes at least one of the following messages: A message related to relay discovery; A message related to the establishment of a PC5-S connection; A message related to PC5-RRC reconfiguration.

24. The first U2U relay UE according to claim 22, characterized in that, the second U2U relay UE is a relay UE that establishes a PC5-S connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that establishes a PC5-RRC connection with the first U2U relay UE; or, the second U2U relay UE is a relay UE that can be discovered by the first U2U relay UE through a direct communication interface discovery process.

25. The first U2U relay UE according to claim 22, characterized in that, the first information includes one of the following: A first local identifier list, the first local identifier list includes a set of local identifiers corresponding to a first remote UE that uses the second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has allocated to remote UEs; A second local identifier list, the second local identifier list includes a set of local identifiers corresponding to a second remote UE that uses the second U2U relay UE for U2U communication and does not use the first U2U relay UE for U2U communication; A third local identifier list, the third local identifier list includes local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not allocated by the second U2U relay UE to remote UEs, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for allocation to remote UEs.

26. The first U2U relay UE according to claim 25, characterized in that, The remote UE that uses the second U2U relay UE for U2U communication includes: a remote UE that uses the second U2U relay UE for U2U communication through a single-hop U2U relay mode and / or a multi-hop U2U relay mode; The remote UE that does not use the first U2U relay UE for U2U communication includes: a remote UE that does not use the first U2U relay UE for U2U communication through a single-hop U2U relay mode and / or a multi-hop U2U relay mode.

27. The first U2U relay UE according to claim 25, wherein, the processor is specifically configured to perform the following operations: determine the local identifier that the first U2U relay UE is allowed to allocate to a remote UE according to the first information, the local identifier that the first U2U relay UE has already allocated to a remote UE, and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication.

28. The first U2U relay UE according to claim 27, wherein, the processor is specifically configured to perform at least one of the following operations: deduct the local identifiers in the first local identifier list, the local identifier that the first U2U relay UE has already allocated to a remote UE, and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE to obtain the local identifier that the first U2U relay UE is allowed to allocate to a remote UE; deduct the local identifiers in the second local identifier list, the local identifier that the first U2U relay UE has already allocated to a remote UE, and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE to obtain the local identifier that the first U2U relay UE is allowed to allocate to a remote UE; deduct the local identifier that the first U2U relay UE has already allocated to a remote UE and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication from the local identifier list corresponding to the first U2U relay UE to obtain a fourth local identifier list, the first U2U relay UE takes a first intersection of the fourth local identifier list and the third local identifier list sent by one or more of the second U2U relay UEs, and determines the local identifier that the first U2U relay UE is allowed to allocate to a remote UE according to the first intersection; Take a second intersection of the local identifier list corresponding to the first U2U relay UE and the third local identifier list sent by one or more of the second U2U relay UEs. The first U2U relay UE deducts the local identifiers already allocated by the first U2U relay UE to the remote UEs and / or deducts the local identifiers of the remote UEs using the first U2U relay UE for U2U communication from the second intersection to obtain a fifth local identifier list, and determines the local identifiers allowed to be allocated by the first U2U relay UE to the remote UEs according to the fifth local identifier list.

29. The first U2U relay UE according to claim 28, wherein, the local identifier list corresponding to the first U2U relay UE is pre-configured or configured by a network device.

30. The first U2U relay UE according to claim 22, wherein, the processor is specifically configured to perform the following operations: Obtain the sixth local identifier list allowed to be allocated by the first U2U relay UE to the remote UEs in the pre-configuration information as the first information.

31. The first U2U relay UE according to claim 30, wherein, the processor is specifically configured to perform the following operations: Determine the local identifiers allowed to be allocated by the first U2U relay UE to the remote UEs according to the sixth local identifier list.

32. The first U2U relay UE according to any one of claims 21 to 31, wherein, the processor is further configured to perform the following operations: After a U2U connection is established between a first target remote UE and a second target remote UE through the first U2U relay UE, allocate local identifiers for the first target remote UE and the second target remote UE according to the local identifiers allowed to be allocated by the first U2U relay UE to the remote UEs.

33. The first U2U relay UE according to claim 32, wherein, the processor is specifically configured to perform the following operations: Allocate different local identifiers for the first target remote UE and the second target remote UE according to the local identifiers allowed to be allocated by the first U2U relay UE to the remote UEs; or, Allocate the same local identifiers for the first target remote UE and the second target remote UE according to the local identifiers allowed to be allocated by the first U2U relay UE to the remote UEs.

34. A second U2U relay UE, wherein, it includes a memory, a transceiver, and a processor: The memory is used to store a computer program; the transceiver is used to transmit and receive data under the control of the processor; the processor is used to read the computer program in the memory and perform the following operations: Control the transceiver to send a target message to the first U2U relay UE through a direct communication interface, where the target message carries first information, and the first information at least includes a local identifier list of a remote UE.

35. The second U2U relay UE according to claim 34, wherein, the target message includes at least one of the following messages: A message related to relay discovery; Messages related to the establishment of a PC5-S connection; Messages related to PC5-RRC reconfiguration.

36. The second U2U relay UE according to claim 34, wherein, the first U2U relay UE is a relay UE that establishes a PC5-S connection with the second U2U relay UE; or, the first U2U relay UE is a relay UE that establishes a PC5-RRC connection with the second U2U relay UE; or, the first U2U relay UE is a relay UE that can be discovered by the second U2U relay UE through the direct communication interface discovery process.

37. The second U2U relay UE according to claim 34, wherein, the first information carried by the target message includes one of the following: a first local identifier list, the first local identifier list including a set of local identifiers corresponding to a first remote UE that uses the second U2U relay UE for U2U communication or a set of local identifiers that the second U2U relay UE has assigned to remote UEs; a second local identifier list, the second local identifier list including a set of local identifiers corresponding to a second remote UE that uses the second U2U relay UE for U2U communication and does not use the first U2U relay UE for U2U communication; a third local identifier list, the third local identifier list including local identifiers in the local identifier list corresponding to the second U2U relay UE that are not occupied by the first remote UE or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not assigned by the second U2U relay UE to remote UEs, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers available for assignment to remote UEs.

38. The second U2U relay UE according to claim 37, wherein, the remote UEs that use the second U2U relay UE for U2U communication include: remote UEs that use the second U2U relay UE for U2U communication through single-hop U2U relay mode and / or multi-hop U2U relay mode; the remote UEs that do not use the first U2U relay UE for U2U communication include: remote UEs that do not use the first U2U relay UE for U2U communication through single-hop U2U relay mode and / or multi-hop U2U relay mode.

39. A processor-readable storage medium, wherein, the processor-readable storage medium stores a program, and the program is used to cause the processor to execute the method according to any one of claims 1 to 13.

40. A processor-readable storage medium, wherein, the processor-readable storage medium stores a program, and the program is used to cause the processor to execute the method according to any one of claims 14 to 18.

Images