Method and apparatus for allocating local identifier, and device and storage medium

Abstract

The present application relates to a method and apparatus for allocating a local identifier, and a device and a storage medium. The method comprises: a first U2U relay UE determining, on the basis of first information, a local identifier that the first U2U relay UE is allowed to allocate to a remote UE, wherein the first information at least comprises a local identifier list of the remote UE. The use of the method avoids the problem whereby a U2U relay UE cannot select a correct route for received data due to the fact that local identifiers allocated by different U2U relay UEs to different remote UEs conflict in a multi-hop U2U relay scenario.

Description

Local identification allocation method, device, equipment and storage medium Cross-references

[0001] This application refers to Chinese Patent Application No. 2023116829790, filed on December 8, 2023, entitled “Local Identifier Allocation Method, Apparatus, Device and Storage Medium,” which is incorporated herein by reference in its entirety. Technical Field

[0002] The present application relates to the field of wireless communication technology, and in particular to a local identifier allocation method, apparatus, device, and storage medium. Background Art

[0003] With the development of communication technology, direct communication technology has emerged. The so-called direct communication refers to a technology that allows nearby user equipment (UE) to transmit data over a direct communication link (also called Sidelink or PC5) within a short range.

[0004] To expand the coverage of direct communication, consider introducing a User Equipment to User Equipment (U2U) relay UE between UEs. With the introduction of a U2U relay UE, UEs that use the U2U relay UE for U2U communication are referred to as remote UEs. In single-hop U2U relay scenarios, the U2U relay UE assigns a local identity to the remote UE.

[0005] To further expand the coverage of direct communication links, a multi-hop U2U relay scenario can be introduced based on U2U relay UEs. This allows remote UEs to communicate via multiple U2U relay UEs. In this multi-hop U2U relay scenario, local identity allocation must be considered to avoid conflicts between local identities assigned by different U2U relay UEs to different remote UEs, which could prevent the U2U relay UEs from correctly routing received data. Summary of the Invention

[0006] Embodiments of the present application provide a local identifier allocation method, apparatus, device, and storage medium to avoid conflicts in local identifiers allocated by different U2U relay UEs to different remote UEs, which may result in the U2U relay UE being unable to select the correct route for received data.

[0007] In a first aspect, a method for allocating a local identifier is provided, the method comprising:

[0008] The first U2U relay UE determines, based on the first information, the local identifiers 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.

[0009] In one of the embodiments, 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 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 UE is one or more; the first U2U relay UE obtains the first information according to pre-configured information.

[0010] 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; and a message related to PC5-RRC reconfiguration.

[0011] In one of the embodiments, 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.

[0012] In one embodiment, 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 a 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, 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 to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

[0013] In one of the embodiments, the remote UE that uses the second U2U relay UE to perform U2U communication includes: a remote UE that uses the second U2U relay UE to perform 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 to perform U2U communication includes: a remote UE that does not use the first U2U relay UE to perform U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

[0014] In one of the embodiments, 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, including: 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 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.

[0015] In one embodiment, the first U2U relay UE determines the local identifier that the first U2U relay UE is allowed to assign to the remote UE based on the first information, the local identifier that the first U2U relay UE has assigned to the remote UE, and / or the local identifier 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 identifier in the first local identifier list from the local identifier list corresponding to the first U2U relay UE, deducts the local identifier that the first U2U relay UE has assigned to the remote UE, and The first U2U relay UE deducts the local identifier in the second local identifier list from the local identifier list corresponding to 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, to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE. 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 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, based on the first intersection, the local identifier that the first U2U relay UE is allowed to allocate to the remote UE. local identifier; 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, and the first U2U relay UE deducts the local identifier that the first U2U relay UE has 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.

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

[0017] In one embodiment, the first U2U relay UE obtains the first information according to the pre-configuration information, including: the first U2U relay UE obtains the sixth local identifier list allowed by the first U2U relay UE to allocate to the remote UE in the pre-configuration information as the first information.

[0018] In one embodiment, 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, including: 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 sixth local identifier list.

[0019] In one of the embodiments, the method also includes: 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 allowed by the first U2U relay UE to be allocated to the remote UE.

[0020] In one of the embodiments, the first U2U relay UE allocates local identities to 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 to the remote UE, including: the first U2U relay UE allocates different local identities to 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 to the remote UE; or, the first U2U relay UE allocates the same local identity to 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 to the remote UE.

[0021] In a second aspect, a local identity allocation method is provided, the method comprising:

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

[0023] 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; and a message related to PC5-RRC reconfiguration.

[0024] 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.

[0025] In one of the embodiments, the first information carried by the target message includes one of the following: a first local identifier list, 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, 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, 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 to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

[0026] In one of the embodiments, the remote UE that uses the second U2U relay UE to perform U2U communication includes: a remote UE that uses the second U2U relay UE to perform 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 to perform U2U communication includes: a remote UE that does not use the first U2U relay UE to perform U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

[0027] In a third aspect, a local identity allocation device is provided for a first U2U relay UE, the device including:

[0028] A determining unit is configured to determine, based on first information, local identifiers that the first U2U relay UE is allowed to allocate to a remote UE; wherein the first information at least includes a list of local identifiers of the remote UE.

[0029] In a fourth aspect, a local identity allocation device is provided for a second U2U relay UE, the device including:

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

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

[0032] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of a processor; and a processor for reading the computer program in the memory and performing the following operations:

[0033] Determine, based on the first information, the local identifiers 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.

[0034] In one of the embodiments, the processor is further used to perform at least one of the following operations: controlling the transceiver to receive a target message sent by the second U2U relay UE through the direct communication interface, where the target message carries the first information, and the number of the second U2U relay UE is one or more; and obtaining the first information according to the pre-configuration information.

[0035] 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; and a message related to PC5-RRC reconfiguration.

[0036] In one of the embodiments, 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.

[0037] In one embodiment, 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 a 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, 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 to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

[0038] In one of the embodiments, the remote UE that uses the second U2U relay UE to perform U2U communication includes: a remote UE that uses the second U2U relay UE to perform 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 to perform U2U communication includes: a remote UE that does not use the first U2U relay UE to perform U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

[0039] In one of the embodiments, the processor is specifically configured to perform the following operations: determine, based on the first information, the local identifier that the first U2U relay UE has allocated to the remote UE, and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication, the local identifier that the first U2U relay UE is allowed to allocate to the remote UE.

[0040] In one embodiment, the processor is specifically configured to perform at least one of the following operations: deducting, from the local identifier list corresponding to the first U2U relay UE, the local identifier in the first local identifier list, deducting the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting the local identifier of the remote UE that uses the first U2U relay UE for U2U communication, to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE; deducting, from the local identifier list corresponding to the first U2U relay UE, the local identifier in the second local identifier list, deducting the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting the local identifier of the remote UE that uses the first U2U relay UE for U2U communication, to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE; deducting, from the local identifier list corresponding to the first U2U relay UE, the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting the local identifier of the remote UE that uses the first U2U relay UE for U2U communication The first U2U relay UE obtains a fourth local identifier list by taking the local identifier assigned to the remote UE and / or deducting the local identifier of the remote UE that uses the first U2U relay UE for U2U communication, 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 assign to the remote UE based on the first intersection; 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 are taken a second intersection, the first U2U relay UE deducts the local identifier that the first U2U relay UE has already assigned 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 assign to the remote UE based on the fifth local identifier list.

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

[0042] In one embodiment, the processor is specifically configured to perform the following operations: acquiring, in the pre-configuration information, a list of sixth local identities that the first U2U relay UE is allowed to allocate to the remote UE as the first information.

[0043] In one embodiment, the processor is specifically configured to perform the following operations: determining, according to the sixth local identifier list, a local identifier that the first U2U relay UE is allowed to allocate to the remote UE.

[0044] In one of the embodiments, the processor 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 to the first target remote UE and the second target remote UE according to the local identifiers allowed by the first U2U relay UE to be allocated to the remote UE.

[0045] In one embodiment, the processor is specifically configured to perform the following operations: assigning different local identifiers to the first target remote UE and the second target remote UE based on the local identifier that the first U2U relay UE allows to be assigned to the remote UE; or assigning the same local identifier to the first target remote UE and the second target remote UE based on the local identifier that the first U2U relay UE allows to be assigned to the remote UE.

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

[0047] A memory for storing a computer program; a transceiver for transmitting and receiving data under the control of a processor; and a processor for reading the computer program in the memory and performing the following operations:

[0048] The control transceiver sends a target message to the first U2U relay UE through the direct communication interface, where the target message carries first information, wherein the first information at least includes a local identifier list of the remote UE.

[0049] 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; and a message related to PC5-RRC reconfiguration.

[0050] 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.

[0051] In one of the embodiments, the first information carried by the target message includes one of the following: a first local identifier list, 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, 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, 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 to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

[0052] In one of the embodiments, the remote UE that uses the second U2U relay UE to perform U2U communication includes: a remote UE that uses the second U2U relay UE to perform 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 to perform U2U communication includes: a remote UE that does not use the first U2U relay UE to perform U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

[0053] In a seventh aspect, a processor-readable storage medium is provided, wherein the processor-readable storage medium stores a program for causing a processor to execute any of the methods described in the first aspect.

[0054] In an eighth aspect, a processor-readable storage medium is provided, wherein the processor-readable storage medium stores a program, and the program is used to enable the processor to execute any method described in the second aspect.

[0055] The above-mentioned local identity allocation method, apparatus, device and storage medium determine, by the first U2U relay UE, the local identity that the first U2U relay UE is allowed to allocate to the remote UE based on the first information, wherein the first information at least includes a local identity list of the remote UE. In this way, the first U2U relay UE can determine the local identity that it is allowed to allocate to the remote UE before allocating the local identity to the remote UE, thereby allocating the local identity to the remote UE based on the local identity allowed to be allocated to the remote UE. In this way, it can be ensured that each U2U relay UE in the system can only allocate the local identity that it is allowed to allocate to the remote UE, so as to avoid conflicts between local identities allocated by different U2U relay UEs to different remote UEs, resulting in the problem that the U2U relay UE cannot select the correct route for the received data. BRIEF DESCRIPTION OF THE DRAWINGS

[0056] FIG1 is a schematic diagram of a traditional cellular network communication method according to an embodiment;

[0057] FIG2 is a schematic diagram of a communication method of direct communication in one embodiment;

[0058] FIG3 is a schematic diagram of a single-hop connection of a remote UE in one embodiment;

[0059] FIG4 is a schematic diagram of a multi-hop connection of a remote UE according to an embodiment;

[0060] FIG5 is a schematic diagram of a direct communication architecture according to an embodiment;

[0061] FIG6 is a schematic diagram of a flow chart of a method for allocating a local identifier in one embodiment;

[0062] FIG7 is a schematic flow chart of another local identifier allocation method according to an embodiment;

[0063] FIG8 is a schematic diagram of a direct communication architecture according to an embodiment;

[0064] FIG9 is a schematic flow chart of another local identifier allocation method according to an embodiment;

[0065] FIG10 is a schematic flow chart of another local identifier allocation method according to an embodiment;

[0066] FIG11 is a schematic flow chart of another local identifier allocation method according to an embodiment;

[0067] FIG12 is a flow chart of another local identifier allocation method according to an embodiment;

[0068] FIG13 is a structural block diagram of a local identifier allocation device according to an embodiment;

[0069] FIG14 is a structural block diagram of another local identifier allocation device according to one embodiment;

[0070] FIG15 is a block diagram of another local identifier allocation device according to an embodiment;

[0071] FIG16 is a diagram showing the internal structure of a U2U relay UE in one embodiment. DETAILED DESCRIPTION

[0072] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

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

[0074] Please refer to Figure 2, which shows a direct communication mode, in which adjacent UEs can communicate within a short range through a direct communication link (also called a Sidelink link or a PC5 link), wherein 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).

[0075] To expand the coverage of direct communication interfaces, the introduction of a User Equipment to User Equipment (U2U) relay UE can be considered. In some descriptions, a U2U relay UE may also be referred to as a U2U Relay. A U2U relay UE itself can be a UE with relay functionality. With the introduction of a U2U relay UE, a single U2U relay UE can be used to achieve a single-hop connection to a remote UE, or multiple U2U relay UEs can be used to achieve a multi-hop connection to a remote UE.

[0076] Please refer to Figures 3 and 4, where Figure 3 is a schematic diagram of a single-hop connection of a remote UE, and Figure 4 is a schematic diagram of a multi-hop connection of a remote UE. As shown in Figure 3, one U2U relay UE can be set between the remote UEs, wherein the remote UE and the U2U relay UE use a direct communication interface to communicate. As shown in Figure 4, three U2U relay UEs can be set between the remote UEs (this is only an example, and more or less U2U relay UEs can actually be set), wherein the remote UE and the U2U relay UE use a direct communication interface to communicate, and adjacent U2U relay UEs also use a direct communication interface to communicate.

[0077] Generally speaking, a pair of remote UEs communicating through a U2U relay UE can be identified by the source L2 ID and the target L2 ID to achieve routing, where L2 ID refers to the layer 2 ID. The source L2 ID and the target L2 ID are both 24 bits long. 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. To this end, 3GPP has made an optimization: for a pair of remote UEs communicating through a U2U relay UE, the U2U relay UE can allocate local identifiers corresponding to the source L2 ID and the target L2 ID to the pair of remote UEs, respectively, where the local identifiers corresponding to the source L2 ID and the target L2 are both 8 bits long.

[0078] 3GPP Rel-19 will introduce the multi-hop U2U relay communication scenario shown in Figure 4 above. In this multi-hop U2U relay communication scenario, it is necessary to consider how to allocate local identities to avoid conflicts between local identities allocated by different U2U relay UEs to different remote UEs, which may cause the U2U relay UE to be unable to select the correct route for the received data.

[0079] Please refer to Figure 5. In Figure 5, the local identifiers of remote UE1 and remote UE2 are allocated by U2U relay UE1, which are 0100111 and 01001110 respectively. The local identifiers of remote UE3 and remote UE4 are allocated by U2U relay UE2, which are 0100111 and 01001110 respectively. That is, the local identifiers of remote UE1 and remote UE2 are exactly the same as the local identifiers of remote UE3 and remote UE4. U2U relay UE2 serves both remote UE1 and remote UE2 and remote UE3 and remote UE4. Therefore, U2U relay UE2 cannot distinguish between the two pairs of remote UEs, remote UE1 and remote UE2 and remote UE3 and remote UE4, which makes it unable to route correctly, resulting in communication interruption.

[0080] An embodiment of the present application provides a local identifier allocation method, apparatus, device and storage medium, wherein a first U2U relay UE determines, based on first information, a local identifier that the first U2U relay UE is allowed to allocate to a remote UE, wherein the first information at least includes a local identifier list of the remote UE. In this way, the first U2U relay UE can determine the local identifier that it is allowed to allocate to the remote UE before allocating the local identifier to the remote UE, thereby allocating a local identifier to the remote UE based on the local identifier 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 identifier that it is allowed to allocate to the remote UE, so as to avoid conflicts between local identifiers allocated by different U2U relay UEs to different remote UEs, resulting in the problem that the U2U relay UE cannot select the correct route for the received data.

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

[0082] The following specific embodiments describe in detail the technical solution of the present application and how the technical solution of the present application solves the above-mentioned technical problems. The following 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 in conjunction with the accompanying drawings.

[0083] In one embodiment, as shown in FIG6 , a local identity allocation method is provided, which is described by applying the method to a first U2U relay UE, and includes the following steps:

[0084] Step 601: The first U2U relay UE determines, based on first information, a local identifier that the first U2U relay UE is allowed to allocate to a remote UE.

[0085] In an optional 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 be a U2U relay UE in a communication scenario in which a single-hop U2U relay communication scenario and a multi-hop U2U relay communication scenario are deployed in a mixed manner. The first U2U relay UE may serve the remote UE via a single-hop U2U relay and / or the first U2U relay UE may serve the remote UE via a multi-hop U2U relay. The first U2U relay UE may serve a pair of remote UEs, or may serve multiple pairs of remote UEs simultaneously.

[0086] In an optional embodiment of the present application, the first information includes at least a list of local identifiers of the remote UE, that is, the first information includes one or more local identifiers. It should be noted that, in actual implementation, the first information may include other content in addition to one or more local identifiers, and the embodiment of the present application does not limit this.

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

[0088] Table 1

[0089] In an optional embodiment of the present application, the local identifier that the first U2U relay UE is allowed to allocate to the remote UE refers to: a local identifier that does not cause conflict and can be allocated by the first U2U relay UE or a local identifier that does not cause conflict within a certain area.

[0090] In one possible implementation, all remote UEs in the system will be assigned different local identifiers within a certain area (such as the world or a certain geographical area), 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 conflict and can be allocated to the first U2U relay UE or the local identifier that does not conflict within a certain area refers to: a local identifier that can be allocated to the first U2U relay UE that is different from the local identifier currently allocated to other remote UEs.

[0091] In another possible implementation, each remote UE served by the first U2U relay UE will be assigned a different local identifier, 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 conflict and can be assigned to the first U2U relay UE or the local identifier that does not conflict within a certain area refers to: a local identifier that can be assigned to the first U2U relay UE and is different from the local identifiers of other remote UEs that use the first U2U relay UE to communicate.

[0092] The local identifier allocation method provided in this embodiment determines, by the first U2U relay UE, the local identifier that the first U2U relay UE is allowed to allocate to the remote UE based on the first information, wherein the first information at least includes a local identifier list of the remote UE. In this way, the first U2U relay UE can determine the local identifier that it is allowed to allocate to the remote UE before allocating the local identifier to the remote UE, and thus can allocate the local identifier to the remote UE based on the local identifier 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 identifier that it is allowed to allocate to the remote UE, so as to avoid conflicts in local identifiers allocated by different U2U relay UEs to different remote UEs, resulting in the problem that the U2U relay UE cannot select the correct route for the received data.

[0093] The embodiment of the present application provides two optional methods for the first U2U relay UE to obtain the first information, and the two methods are described below respectively.

[0094] In a first manner of obtaining the first information, a first U2U relay UE receives a target message sent by a second U2U relay UE via a direct communication interface, wherein the target message carries the first information, and the number of the second U2U relay UE is one or more.

[0095] In an optional embodiment of the present 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 a direct communication interface discovery process.

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

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

[0098] A. A first local identifier list, where the first local identifier list includes 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 the remote UE.

[0099] In an optional embodiment of the present application, the first remote UE using the second U2U relay UE for U2U communication includes: a remote UE using the second U2U relay UE for U2U communication via a single-hop U2U relay mode and / or a multi-hop U2U relay mode. In an optional embodiment of the present application, the number of the first remote UEs may be one or more.

[0100] For example, please refer back to Figure 4. In Figure 4, assuming that U2U relay UE1 is the first U2U relay UE, and U2U relay UE2 is the second U2U relay UE, the first information carried in the target message sent by U2U relay UE2 to U2U relay UE1 may include a first local identifier list. Since the remote UEs using U2U relay UE2 for U2U communication include remote UE1, remote UE2, remote UE3, and remote UE4, the first local identifier list may include the local identifier of remote UE1, the local identifier of remote UE2, the local identifier of remote UE3, and the local identifier of remote UE4. In subsequent steps, U2U relay UE1 can determine the local identifiers that it is allowed to allocate to the remote UEs based on the first local identifier list. In this way, if another remote UE wishes to conduct U2U communication through U2U relay UE1, U2U relay UE1 can allocate a local identifier to the other remote UE based on the local identifiers that it is allowed to allocate to the remote UEs.

[0101] In an optional embodiment of the present application, the local identifier set that the second U2U relay UE has allocated to the remote UE includes: the local identifier set that the second U2U relay UE has allocated to the remote UE it serves, where the number of remote UEs served by the second U2U relay UE can be one or more.

[0102] For example, please return to reference Figure 4. Similar to the above description, assuming that U2U relay UE1 is the first U2U relay UE, and U2U relay UE2 is the second U2U relay UE, the first information carried in the target message sent by U2U relay UE2 to U2U relay UE1 may include a first local identifier list. Since U2U relay UE2 has already allocated local identifiers to remote UE1, remote UE2, remote UE3, and remote UE4, the first local identifier list may include the local identifier of remote UE1, the local identifier of remote UE2, the local identifier of remote UE3, and the local identifier of remote UE4. In subsequent steps, U2U relay UE1 can determine the local identifiers that it is allowed to allocate to remote UEs based on the first local identifier list. In this way, if another remote UE wishes to conduct U2U communication through U2U relay UE1, U2U relay UE1 can allocate a local identifier to the other remote UE based on the local identifiers that it is allowed to allocate to the remote UE.

[0103] B. 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.

[0104] Among them, the second 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. The number of the second remote UEs can be one or more.

[0105] For example, please continue to return to reference Figure 4. Similar to the above, assuming that the U2U relay UE1 in Figure 4 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 use the U2U relay UE2 for U2U communication include remote UE1, remote UE2, remote UE3 and remote UE4, where the remote UEs that do not use the U2U relay UE1 for U2U communication include remote UE3 and remote UE4, the 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 allocate to the remote UE based on the second local identifier list. In this way, if another remote UE wants to conduct U2U communication through the U2U relay UE1, the U2U relay UE1 can allocate a local identifier to the other remote UE based on the local identifiers that it is allowed to allocate to the remote UE.

[0106] 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 identifier of the remote UE that uses the first U2U relay UE for U2U communication from the first local identifier list. In general, the first U2U relay UE is able to obtain the local identifier of the remote UE that uses itself for U2U communication. Therefore, sending the second local identifier list can reduce the amount of data and save communication resources.

[0107] C. 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 mentioned above, or local identifiers in the local identifier list corresponding to the second U2U relay UE that are not allocated to the remote UE by the second U2U relay UE.

[0108] In an optional embodiment of the present application, each U2U relay UE in the system may correspond to a local identifier list, wherein the local identifier lists corresponding to each U2U relay UE may be the same or different. In an optional embodiment of the present application, the local identifier list corresponding to each U2U relay UE may be pre-configured or configured by a network device.

[0109] In an optional 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 a remote UE, wherein the local identifiers included in the local identifier list corresponding to each U2U relay UE are local identifiers allowed to be allocated to a remote UE in an initial state.

[0110] According to the above description, the local identifier list corresponding to the second U2U relay UE can be pre-configured or configured by the 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 the remote UE, wherein the local identifiers included in the local identifier list corresponding to the second U2U relay UE are local identifiers allowed to be allocated to the remote UE in the initial state.

[0111] For example, please continue to refer back to Figure 4. Similar to the above, assuming that the U2U relay UE1 in Figure 4 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 UE (that is, the first remote UE) using the U2U relay UE2 for U2U communication includes remote UE1, remote UE2, remote UE3 and remote UE4, the third local identifier list is the local identifier list obtained by deducting 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 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 is allowed to allocate to the remote UE based on the third local identifier list. In this way, if another remote UE wants to conduct U2U communication through the U2U relay UE1, the U2U relay UE1 can allocate a local identifier to the other remote UE based on the local identifiers that it is allowed to allocate to the remote UE.

[0112] For example, please continue to refer back to Figure 4. Similar to the above, assuming that the U2U relay UE1 in Figure 4 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 assigned local identifiers to the remote UE1, remote UE2, remote UE3 and remote UE4, the third local identifier list is the local identifier list obtained by deducting 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 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 is allowed to allocate to the remote UE based on the third local identifier list. In this way, if another remote UE wants to conduct U2U communication through the U2U relay UE1, the U2U relay UE1 can allocate a local identifier to the other remote UE based on the local identifiers that it is allowed to allocate to the remote UE.

[0113] A second manner of obtaining the first information: the first U2U relay UE obtains the first information according to pre-configured information.

[0114] In an optional embodiment of the present application, different local identifier lists allowed to be allocated to remote UEs can be pre-configured for different U2U relay UEs within a certain area (such as the world or a specified geographical area), wherein there may be no intersection between the local identifier lists allowed to be allocated to remote UEs pre-configured by different U2U relay UEs.

[0115] The first U2U relay UE may obtain, from the pre-configuration information, a sixth local identifier list that is pre-configured for the first U2U relay UE and allowed to be allocated to the remote UE, and use the sixth local identifier list as the first information.

[0116] With respect to the second method for obtaining the first information, that is, with respect to the method for obtaining the first information based on pre-configured information, an embodiment of the present application provides an optional method for a first U2U relay UE to determine, based on the first information, a local identifier that the first U2U relay UE is permitted to allocate to a remote UE. The method includes: the first U2U relay UE determining, based on a sixth local identifier list, a local identifier that the first U2U relay UE is permitted to allocate to a remote UE. Optionally, the first U2U relay UE may determine a local identifier in the sixth local identifier list as a local identifier that it is permitted to allocate to the remote UE.

[0117] In addition, for the first method of obtaining the first information described above, that is, for the method 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 method for the first U2U relay UE to determine the local identifier allowed to be allocated by the first U2U relay UE to the remote UE based on the first information.

[0118] The method includes: 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 local identifier that the first U2U relay UE has allocated to the remote UE and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication.

[0119] To simplify the description, in the following method embodiments, the allocated local identity refers to the local identity that the first U2U relay UE has allocated to the remote UE, and the used local identity refers to the local identity of the remote UE that uses the first U2U relay UE for U2U communication.

[0120] In actual applications, the allocated local identifier and the used local identifier cannot be allocated to a new remote UE by the first U2U relay UE, otherwise a local identifier conflict will occur. Therefore, in an optional embodiment of the present application, the first U2U relay UE can 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 / or the used local identifier.

[0121] For example, the first U2U relay UE can 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). For another example, the first U2U relay UE can 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 currently allocated a local identifier for the remote UE). For another example, the first U2U relay UE can 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 can determine the local identifier that the first U2U relay UE is allowed to allocate to the remote UE based on the first information alone (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 currently allocated a local identifier for the remote UE).

[0122] Furthermore, the first U2U relay UE determines, based on the first information, the allocated local identity, and / or the used local identity, a local identity that the first U2U relay UE is allowed to allocate to the remote UE, including at least one of the following implementations:

[0123] Implementation method A: The first U2U relay UE deducts the local identifier in the first local identifier list, deducts the allocated local identifier and / or deducts 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.

[0124] To simplify the description, in the following method embodiments, the local identity list A refers to the local identity list corresponding to the first U2U relay UE.

[0125] Similar to the local identifier list corresponding to the second U2U relay UE described above, the local identifier list A can be pre-configured or configured by a network device. The local identifier list A can 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, wherein the local identifiers included in the local identifier list A are local identifiers allowed to be allocated to the remote UE in the initial state.

[0126] In implementation method A, for example, the first U2U relay UE can deduct the local identifiers in the first local identifier list and the allocated local identifier from the local identifier list A to obtain the local identifier 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 identifier from the local identifier list A to obtain the local identifier 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 identifier 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 identifier that the first U2U relay UE is allowed to allocate to the remote UE.

[0127] Please refer back to Figure 4. According to the above example, 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 implementation method A, for example, the first U2U relay UE can deduct 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 from the local identifier list A, and at the same time deduct the allocated local identifier and the used local identifier (in Figure 4, the used local identifier includes the local identifier of the remote UE1 and the local identifier of the remote UE2) to obtain the local identifier that the U2U relay UE1 is allowed to allocate to the remote UE.

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

[0129] In implementation method B, for example, the first U2U relay UE can deduct the local identifiers in the second local identifier list and the allocated local identifier from the local identifier list A to obtain the local identifier 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 second local identifier list and the used local identifier from the local identifier list A to obtain the local identifier 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 second local identifier list, the allocated local identifier, and the used local identifier from the local identifier list A to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE. For another example, the first U2U relay UE can deduct only the local identifiers in the second local identifier list from the local identifier list A to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE.

[0130] Please refer back to Figure 4. According to the above example, the second local identifier list may include the local identifier of the remote UE3 and the local identifier of the remote UE4. In implementation method B, for example, the first U2U relay UE can deduct the local identifier of the remote UE3 and the local identifier of the remote UE4 from the local identifier list A, and at the same time deduct the allocated local identifier and the used local identifier (in Figure 4, the used local identifier includes the local identifier of the remote UE1 and the local identifier of the remote UE2) to obtain the local identifier that the U2U relay UE1 is allowed to allocate to the remote UE.

[0131] Implementation method C: The first U2U relay UE deducts the allocated local identifier and / or the used local identifier from the local identifier list A 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, based on the first intersection, the local identifier that the first U2U relay UE is allowed to allocate to the remote UE.

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

[0133] After obtaining the fourth local identifier list, the first U2U relay UE may take a first intersection of the fourth local identifier list and the third local identifier list sent by one or more second U2U relay UEs. In an optional embodiment of the present application, the first U2U relay UE may use the local identifier in the first intersection as the local identifier that the first U2U relay UE is allowed to allocate to the remote UE.

[0134] Implementation method D: The first U2U relay UE takes a second intersection of the local identifier list A and the third local identifier list sent by one or more second U2U relay UEs. The first U2U relay UE deducts the allocated local identifier and / or the used local identifier 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 based on the fifth local identifier list.

[0135] For example, after obtaining the second intersection, the first U2U relay UE can deduct the allocated local identifier from the second intersection to obtain a fifth local identifier list. For another example, the first U2U relay UE can deduct the used local identifier from the second intersection to obtain a fifth local identifier list. For another example, the first U2U relay UE can deduct the allocated local identifier and the used local identifier from the second intersection to obtain a fifth local identifier list. For another example, the first U2U relay UE can directly use the second intersection as the fifth local identifier list. In an optional embodiment of the present application, the first U2U relay UE can use the local identifier in the fifth local identifier list as the local identifier that the first U2U relay UE is allowed to allocate to the remote UE.

[0136] In an optional embodiment of the present application, after the first U2U relay UE determines the local identifier that it is allowed to allocate 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 identifier that the first U2U relay UE is allowed to allocate to the remote UE.

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

[0138] Mode 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 is allowed to allocate to remote UEs.

[0139] In an optional 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 based on the local identifiers that it allows to be assigned to the remote UEs.

[0140] Mode B: 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 identifier that the first U2U relay UE is allowed to allocate to the remote UE.

[0141] In an optional 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 based on the local identifier that it is allowed to assign to the remote UE.

[0142] In one embodiment, as shown in FIG7 , a local identity allocation method is provided, which is described by applying the method to a second U2U relay UE, and includes the following steps:

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

[0144] The target message carries first information, wherein the first information at least includes a local identifier list of the remote UE.

[0145] In an optional 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.

[0146] In an optional embodiment of the present application, the first U2U relay UE can 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.

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

[0148] A. A first local identifier list, where the first local identifier list includes 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 the remote UE.

[0149] B. 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.

[0150] C. 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 to the remote UE by the second U2U relay UE.

[0151] The above contents of the embodiments of the present application are all described in detail in the method embodiments corresponding to the first U2U relay UE. In order to avoid redundancy, the embodiments of the present application will not be described in detail here. Please refer to the relevant description in the embodiments corresponding to the first U2U relay UE.

[0152] In order to facilitate understanding of the technical solutions provided by the embodiments of the present application, four optional embodiments are provided below to exemplarily illustrate the technical solutions provided by the embodiments of the present application.

[0153] The four optional embodiments are all described using the scenario shown in FIG8 as an example. As shown in FIG8 , remote UE1 and remote UE2 use U2U relay UE1 and U2U relay UE3 to perform U2U communication in a multi-hop U2U relay manner. Remote UE3 and remote UE4 use U2U relay UE2 to perform end-to-end communication in a single-hop U2U relay manner. On this basis, remote UE5 and remote UE6 desire to use U2U relay UE1 and U2U relay UE2 to perform U2U communication in a multi-hop U2U relay manner. In this case, U2U relay UE1 can allocate local identities to remote UE5 and remote UE6. The four embodiments below all describe how U2U relay UE1 determines the local identities of the remote UEs that it is allowed to allocate, and allocates local identities to remote UE5 and remote UE6 based on the local identities of the remote UEs that it is allowed to allocate.

[0154] Please refer to FIG9 , which is a flowchart corresponding to the first embodiment. As shown in FIG9 , the process includes the following steps:

[0155] Step 901: U2U relay UE1 receives target messages sent by U2U relay UE2 and U2U relay UE3.

[0156] 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, or C. a message related to PC5-RRC reconfiguration.

[0157] Among them, the target message carries the first information, and the first information carried by the target message sent by U2U relay UE2 includes a local identifier list 1, which includes a local identifier set corresponding to the remote UE that uses U2U relay UE2 for U2U communication or a local identifier that U2U relay UE2 has assigned to the remote UE. Taking the local identifier list 1 including the local identifier set corresponding to the remote UE that uses U2U relay UE2 for U2U communication as an example, the first information carried by the target message sent by U2U relay UE3 includes a local identifier list 2, which includes a local identifier set corresponding to the remote UE that uses U2U relay UE3 for U2U communication or a local identifier that U2U relay UE3 has assigned to the remote UE. Taking the local identifier list 2 including the local identifier set corresponding to the remote UE that uses U2U relay UE3 for U2U communication as an example.

[0158] Step 902: The U2U relay UE1 determines the local identifiers that the U2U relay UE1 is allowed to allocate to the remote UE according to the local identifier list 1 and the local identifier list 2.

[0159] The U2U relay UE1 deducts the local identifier in the local identifier list 1 from its own corresponding local identifier list, deducts the local identifier in the local identifier list 2, deducts the local identifier that the U2U relay UE1 has already allocated to the remote UE and / or deducts the local identifier of the remote UE that uses the U2U relay UE1 for U2U communication, to obtain the local identifier that the U2U relay UE1 is allowed to allocate to the remote UE.

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

[0161] 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 selects a local identifier of the remote UE that it allows to be allocated for the remote UE5 and the remote UE6 respectively.

[0162] 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 to the remote UE pair consisting of the remote UE5 and the remote UE6 from the local identifiers of the remote UEs that it is allowed to allocate.

[0163] Please refer to FIG10 , which is a flowchart corresponding to the second embodiment. As shown in FIG10 , the following steps are included:

[0164] Step 1001: U2U relay UE1 receives a target message sent by U2U relay UE2 and U2U relay UE3.

[0165] 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, or C. a message related to PC5-RRC reconfiguration.

[0166] Among them, the target message carries the first information, and the first information carried by the target message sent by the U2U relay UE2 includes a local identification list 3, which includes a local identification set corresponding to the remote UE that uses the U2U relay UE2 for U2U communication and does not use the U2U relay UE1 for U2U communication. The first information carried by the target message sent by the U2U relay UE3 includes a local identification list 4, which includes a local identification set corresponding to the remote UE that uses the U2U relay UE3 for U2U communication and does not use the U2U relay UE1 for U2U communication.

[0167] Step 1002: The U2U relay UE1 determines the local identifiers that the U2U relay UE1 is allowed to allocate to the remote UE according to the local identifier list 3 and the local identifier list 4.

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

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

[0170] 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 selects a local identifier of the remote UE that it allows to be allocated for the remote UE5 and the remote UE6 respectively.

[0171] 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 to the remote UE pair consisting of the remote UE5 and the remote UE6 from the local identifiers of the remote UEs that it is allowed to allocate.

[0172] Please refer to FIG11, which is a flowchart corresponding to the third embodiment. As shown in FIG11, the following steps are included:

[0173] Step 1101: U2U relay UE1 receives target messages sent by U2U relay UE2 and U2U relay UE3.

[0174] 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, or C. a message related to PC5-RRC reconfiguration.

[0175] Among them, the target message carries the first information, and 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 the local identifiers in the local identifier list corresponding to the U2U relay UE2 that are not occupied by the remote UE using the U2U relay UE2 for U2U communication or the local identifier list corresponding to the U2U relay UE2 that are not allocated to the remote UE by the U2U relay UE2, and only the local identifier list 5 includes the local identifier list corresponding to the U2U relay UE2 that is not occupied by the remote UE using the U2U relay UE2 for U2U communication Taking the local identifier as an example, the first information carried by the target message sent by the U2U relay UE3 includes a local identifier list 6, which includes the local identifiers in the local identifier list corresponding to the U2U relay UE3 that are not occupied by the remote UE using the U2U relay UE3 for U2U communication, or the local identifiers in the local identifier list corresponding to the U2U relay UE3 that are not allocated to the remote UE by the U2U relay UE3. Only the local identifier list 6 includes the local identifier in the local identifier list corresponding to the U2U relay UE3 that is not occupied by the remote UE using the U2U relay UE3 for U2U communication as an example.

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

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

[0178] For another example, U2U relay UE1 takes the second intersection of its own corresponding local identification list, the local identification list 5 sent by U2U relay UE2, and the local identification list 6 sent by U2U relay UE3. U2U relay UE1 deducts the local identification that U2U relay UE1 has already allocated to the remote UE and / or deducts the local identification of the remote UE that uses U2U relay UE1 for U2U communication from the second intersection to obtain local identification list 8, and determines the local identification that U2U relay UE1 is allowed to allocate to the remote UE based on local identification list 8.

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

[0180] 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 selects a local identifier of the remote UE that it allows to be allocated for the remote UE5 and the remote UE6 respectively.

[0181] 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 to the remote UE pair consisting of the remote UE5 and the remote UE6 from the local identifiers of the remote UEs that it is allowed to allocate.

[0182] Please refer to FIG12, which is a flowchart corresponding to the fourth embodiment. As shown in FIG12, the following steps are included:

[0183] Step 1201: The U2U relay UE1 obtains pre-configuration information, and obtains first information according to the pre-configuration information.

[0184] The U2U relay UE1 may obtain the local identity list 9 that the U2U relay UE1 is allowed to allocate to the remote UE from the pre-configuration information, and use the local identity list 9 as the first information.

[0185] Step 1202: The U2U relay UE1 determines, based on the first information obtained from the pre-configuration information, a local identifier that the U2U relay UE1 is allowed to allocate to the remote UE.

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

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

[0188] 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 selects a local identifier of the remote UE that it allows to be allocated for the remote UE5 and the remote UE6 respectively.

[0189] 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 to the remote UE pair consisting of the remote UE5 and the remote UE6 from the local identifiers of the remote UEs that it is allowed to allocate.

[0190] It should be understood that although the various steps in the flow charts of Figures 6-12 are shown in sequence according to the instructions of the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless otherwise specified herein, the execution of these steps is not strictly limited in order, and these steps can be performed in other orders. Moreover, at least a portion of the steps in Figures 6-12 may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these steps or stages is not necessarily performed in sequence, but can be performed in turn or alternately with other steps or at least a portion of the steps or stages in other steps.

[0191] In one embodiment, as shown in FIG13 , a local identity allocation apparatus 1300 is provided, for use with a first U2U relay UE, and includes: a determining unit 1301 .

[0192] The determining unit 1301 is configured to determine, based on the first information, local identities 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 identities of the remote UE.

[0193] Please refer to FIG. 14 , which shows another local identity allocation device 1400 provided in an embodiment of the present application. In addition to the determination unit 1301 , the local identity allocation device 1400 optionally further includes an acquisition unit 1302 and an allocation unit 1303 .

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

[0195] 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; and a message related to PC5-RRC reconfiguration.

[0196] 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 the direct communication interface discovery process.

[0197] In an optional embodiment of the present application, the first information includes one of the following: a first local identifier list, 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 local identifier set that the second U2U relay UE has allocated to the remote UE; a second local identifier list, the second local identifier list includes the local identifier set 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, 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 allocated to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

[0198] In an optional embodiment of the present application, the remote UE that uses the second U2U relay UE to perform U2U communication includes: a remote UE that uses the second U2U relay UE to perform 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 to perform U2U communication includes: a remote UE that does not use the first U2U relay UE to perform U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

[0199] In an optional embodiment of the present application, the determination unit 1301 is specifically used to: determine the local identifier that the first U2U relay UE is allowed to allocate to the remote UE based on the first information, the local identifier that the first U2U relay UE has allocated to the remote UE and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication.

[0200] In an optional embodiment of the present application, the determining unit 1301 is specifically used for at least one of the following: deducting the local identifier in the first local identifier list, deducting the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting 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 the remote UE; deducting the local identifier in the second local identifier list, deducting the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting the local identifier of the remote UE that uses the first U2U relay UE for U2U communication, to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE; deducting the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting 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. The local identifier allocated by the remote UE and / or the local identifier of the remote UE using the first U2U relay UE for U2U communication is deducted 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 based on the first intersection; 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 are taken to obtain a second intersection, the first U2U relay UE deducts the local identifier that the first U2U relay UE has allocated to the remote UE and / or deducts the local identifier 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 identifier that the first U2U relay UE is allowed to allocate to the remote UE based on the fifth local identifier list.

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

[0202] In an optional embodiment of the present application, the acquiring unit 1302 is specifically configured to: acquire, in the pre-configuration information, a list of sixth local identities that the first U2U relay UE is allowed to allocate to the remote UE as the first information.

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

[0204] The allocating unit 1303 is configured to allocate local identities to the first target remote UE and the second target remote UE according to the local identities allowed by the first U2U relay UE to allocate to remote UEs after the first target remote UE and the second target remote UE establish a U2U connection through the first U2U relay UE.

[0205] In an optional embodiment of the present application, the allocation unit 1303 is specifically used to: allocate different local identifiers to the first target remote UE and the second target remote UE according to the local identifier allowed by the first U2U relay UE to allocate to the 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 allowed by the first U2U relay UE to allocate to the remote UE.

[0206] In one embodiment, as shown in FIG15 , a local identity allocation apparatus 1500 is provided, which is used for a second U2U relay UE and includes: a sending unit 1501 .

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

[0208] 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; and a message related to PC5-RRC reconfiguration.

[0209] In an optional 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.

[0210] In an optional embodiment of the present application, the first information carried by the target message includes one of the following: a first local identifier list, 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 local identifier set that the second U2U relay UE has allocated to the remote UE; a second local identifier list, the second local identifier list includes the local identifier set 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, 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 allocated to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

[0211] In an optional embodiment of the present application, the remote UE that uses the second U2U relay UE to perform U2U communication includes: a remote UE that uses the second U2U relay UE to perform 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 to perform U2U communication includes: a remote UE that does not use the first U2U relay UE to perform U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

[0212] For the specific definition of the local identity allocation device, please refer to the definition of the local identity allocation method above, which will not be repeated here. Each unit in the above-mentioned local identity allocation device can be implemented in whole or in part by software, hardware, or a combination thereof. The above-mentioned units can be embedded in or independent of the processor in the U2U relay UE in hardware form, or can be stored in the memory in the U2U relay UE in software form, so that the processor can call and execute the corresponding operations of the above-mentioned units.

[0213] It should be noted that the division of units in the embodiments of the present application is schematic and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0214] If 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 the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application.

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

[0216] In one embodiment, a U2U relay UE is provided, see Figure 16. The U2U relay UE 1600 shown in Figure 16 includes: at least one processor 1601 and a memory 1602. The various components in the U2U relay UE 1600 are coupled together through a bus system 1603. It can be understood that the bus system 1603 is used to achieve 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 clarity, various buses are labeled as bus systems 1603 in Figure 16. In addition, in an embodiment of the present application, a transceiver 1604 is also included. The transceiver can be multiple elements, that is, including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium.

[0217] In addition, the U2U relay UE may further include a user interface, which may include a display, a keyboard, or a pointing device (eg, a mouse, a trackball, a touchpad, or a touch screen).

[0218] It is understood that the memory 1602 in the embodiment 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 (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct RAM bus random access memory (DRRAM). The memory 1602 of the systems and methods described in the embodiments of the present application is intended to include, but is not limited to, these and any other suitable types of memory.

[0219] In some embodiments, the memory 1602 stores the following elements, executable modules or data structures, or a subset thereof, or an extended set thereof: an operating system 16021 and application programs 16022 .

[0220] The operating system 16021 includes various system programs, such as a framework layer, a core library layer, and a driver layer, for implementing various basic services and processing hardware-based tasks. Application programs 16022 include various application programs, such as a media player (English: MediaPlayer) and a browser (English: Browser), for implementing various application services. Programs implementing the methods of the embodiments of the present application may be included in application programs 16022.

[0221] Some or all of the methods disclosed in the above embodiments of the present application can be applied to the processor 1601, or implemented by the processor 1601, or implemented by the processor 1601 in conjunction with other components (such as a transceiver). The processor 1601 may be an integrated circuit chip with signal processing capabilities. During implementation, the steps of the above method can be completed by hardware integrated logic circuits or software instructions in the processor 1601. The above-mentioned processor 1601 can be a general-purpose processor, a digital signal processor (English: Digital Signal Processor, abbreviated: DSP), an application-specific integrated circuit (English: Application Specific Integrated Circuit, abbreviated: ASIC), a readily available programmable gate array (English: Field Programmable Gate Array, abbreviated: FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The various methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of this application can be directly implemented as being executed by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium well-known in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. The storage medium is located in memory 1602, and processor 1601 reads the information in memory 1602 and, in conjunction with its hardware, completes the steps of the above method.

[0222] It is understood that the embodiments described in the embodiments of the present application can be implemented using 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 (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers, microprocessors, other electronic units for performing the functions described in the present application, or a combination thereof.

[0223] For software implementation, the technology described in the embodiments of the present application can be implemented by modules (e.g., procedures, functions, etc.) that perform the functions described in the embodiments of the present application. The software code can be stored in a memory and executed by the processor 1601. The memory can be implemented in the processor 1601 or outside the processor 1601.

[0224] Specifically, the U2U relay UE shown in FIG16 may execute the method steps corresponding to the first U2U relay UE in the above method embodiment, and may also execute the method steps corresponding to the second U2U relay UE in the above method embodiment.

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

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

[0227] In one embodiment, the processor 1601 is further used to perform at least one of the following operations: controlling the transceiver to receive a target message sent by the 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 UE is one or more; obtaining the first information according to the pre-configuration information.

[0228] 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; and a message related to PC5-RRC reconfiguration.

[0229] In one of the embodiments, 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.

[0230] In one embodiment, the first information includes one of the following: a first local identifier list, 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 local identifier set that the second U2U relay UE has allocated to the remote UE; a second local identifier list, the second local identifier list includes the local identifier set 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, 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 allocated to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

[0231] In one of the embodiments, the remote UE that uses the second U2U relay UE to perform U2U communication includes: a remote UE that uses the second U2U relay UE to perform 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 to perform U2U communication includes: a remote UE that does not use the first U2U relay UE to perform U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

[0232] In one of the embodiments, the processor 1601 is specifically configured to perform the following operations: determine, based on the first information, the local identifier that the first U2U relay UE has allocated to the remote UE, and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication, the local identifier that the first U2U relay UE is allowed to allocate to the remote UE.

[0233] In one embodiment, the processor 1601 is specifically configured to perform at least one of the following operations: deducting, from the local identifier list corresponding to the first U2U relay UE, the local identifier in the first local identifier list, deducting the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting the local identifier of the remote UE that uses the first U2U relay UE for U2U communication, to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE; deducting, from the local identifier list corresponding to the first U2U relay UE, the local identifier in the second local identifier list, deducting the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting the local identifier of the remote UE that uses the first U2U relay UE for U2U communication, to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE; deducting, from the local identifier list corresponding to the first U2U relay UE, the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting the local identifier of the remote UE that uses the first U2U relay UE for U2U communication The local identifier allocated to the remote UE and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication is deducted 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 based on the first intersection; 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 are taken to obtain a second intersection. The first U2U relay UE deducts the local identifier that the first U2U relay UE has 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 is allowed to allocate to the remote UE based on the fifth local identifier list.

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

[0235] In one embodiment, the processor 1601 is specifically configured to perform the following operations: acquiring, in the pre-configuration information, a list of sixth local identities that the first U2U relay UE is allowed to allocate to the remote UE as first information.

[0236] In one embodiment, the processor 1601 is specifically configured to perform the following operations: determine, according to the sixth local identity list, a local identity that the first U2U relay UE is allowed to allocate to the remote UE.

[0237] In one of the embodiments, 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 to the first target remote UE and the second target remote UE according to the local identifiers allowed by the first U2U relay UE to be allocated to the remote UE.

[0238] In one embodiment, the processor 1601 is specifically configured to perform the following operations: assigning different local identifiers to the first target remote UE and the second target remote UE based on the local identifier that the first U2U relay UE allows to be assigned to the remote UE; or assigning the same local identifier to the first target remote UE and the second target remote UE based on the local identifier that the first U2U relay UE allows to be assigned to the remote UE.

[0239] When executing the method steps corresponding to the second U2U relay UE in the above method embodiment:

[0240] 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 the direct communication interface, where the target message carries first information, wherein the first information at least includes a local identifier list of the remote UE.

[0241] 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; and a message related to PC5-RRC reconfiguration.

[0242] 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.

[0243] In one of the embodiments, the first information carried by the target message includes one of the following: a first local identifier list, 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 allocated to the remote UE; a second local identifier list, 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, 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 allocated to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

[0244] In one of the embodiments, the remote UE that uses the second U2U relay UE to perform U2U communication includes: a remote UE that uses the second U2U relay UE to perform 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 to perform U2U communication includes: a remote UE that does not use the first U2U relay UE to perform U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

[0245] 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, based on first information, local identifiers that a first U2U relay UE is allowed to allocate to a remote UE; wherein the first information includes at least a list of local identifiers of the remote UE.

[0246] 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 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.

[0247] 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; and a message related to PC5-RRC reconfiguration.

[0248] 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.

[0249] In one embodiment, the first information includes one of the following: a first local identifier list, 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 local identifier set that the second U2U relay UE has allocated to the remote UE; a second local identifier list, the second local identifier list includes the local identifier set 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, 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 allocated to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

[0250] 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 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: the 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.

[0251] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: determining the local identifier that the first U2U relay UE is allowed to allocate to the remote UE based on the first information, the local identifier that the first U2U relay UE has allocated to the remote UE, and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication.

[0252] In one embodiment, when the computer program is executed by the processor, it further implements at least one of the following steps: deducting the local identifiers in the first local identifier list, deducting the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting 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 the remote UE; deducting the local identifiers in the second local identifier list, deducting the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting 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 the remote UE; deducting the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting 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. The local identifier allocated to the remote UE and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication is deducted 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 based on the first intersection; 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 are taken to obtain a second intersection. The first U2U relay UE deducts the local identifier that the first U2U relay UE has 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 is allowed to allocate to the remote UE based on the fifth local identifier list.

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

[0254] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: obtaining, in the pre-configuration information, a list of sixth local identities that the first U2U relay UE is allowed to allocate to the remote UE as the first information.

[0255] In one embodiment, when the computer program is executed by the processor, the following steps are further implemented: determining, according to the sixth local identifier list, a local identifier that the first U2U relay UE is allowed to allocate to the remote UE.

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

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

[0258] 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:

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

[0260] 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; and a message related to PC5-RRC reconfiguration.

[0261] 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 the direct communication interface discovery process.

[0262] In one embodiment, the first information carried by the target message includes one of the following: a first local identifier list, 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 local identifier set that the second U2U relay UE has allocated to the remote UE; a second local identifier list, the second local identifier list includes the local identifier set 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, 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 allocated to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

[0263] 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 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: the 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.

[0264] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and 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-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).

[0265] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, 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, they should be considered to be within the scope of this specification.

[0266] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.

Claims

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

2. The method according to claim 1, wherein: 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 UE is one or more; The first U2U relay UE obtains the first information according to pre-configuration information.

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

4. The method according to claim 2, wherein: 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, wherein: 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 allocated to a remote UE; 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, wherein 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 to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

6. The method according to claim 5, wherein: The remote UE that uses the second U2U relay UE to perform U2U communication includes: a remote UE that uses the second U2U relay UE to perform 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 to perform U2U communication includes: a remote UE that does not use the first U2U relay UE to perform U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

7. The method according to claim 5, wherein: The first user equipment to user equipment U2U relay UE determines, according to the first information, a local identifier that the first U2U relay UE is allowed to allocate to the remote UE, including: 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 local identifier that the first U2U relay UE has allocated to the remote UE, and / or the local identifier of the remote UE that uses the first U2U relay UE for U2U communication.

8. The method according to claim 7, wherein: The first U2U relay UE determines, according to the first information, a local identifier that the first U2U relay UE has allocated to the remote UE, and / or a local identifier of the remote UE that uses the first U2U relay UE for U2U communication, a local identifier that the first U2U relay UE is allowed to allocate to the remote UE, including at least one of the following: The first U2U relay UE deducts the local identifier in the first local identifier list from the local identifier list corresponding to the first U2U relay UE, deducts the local identifier that the first U2U relay UE has 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, so as to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE; The first U2U relay UE deducts the local identifier in the second local identifier list from the local identifier list corresponding to the first U2U relay UE, deducts the local identifier that the first U2U relay UE has 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, so as to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE; The first U2U relay UE deducts the local identifier that has been allocated by the first U2U relay UE 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 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, according to the first intersection, the local identifier that the first U2U relay UE is allowed to allocate to the remote UE; 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, and the first U2U relay UE deducts the local identifier that the first U2U relay UE has 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 based on the fifth local identifier list.

9. The method according to claim 8, wherein: The local identification 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 the pre-configuration information, including: The first U2U relay UE obtains, in the pre-configuration information, a list of sixth local identifiers that the first U2U relay UE is allowed to allocate to the remote UE as the first information.

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

12. The method according to any one of claims 1 to 11, wherein: The method further comprises: 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 allowed by the first U2U relay UE to be allocated to remote UEs.

13. The method according to claim 12, wherein: The first U2U relay UE allocates a 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 the 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 identifier allowed by the first U2U relay UE to be allocated to the 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 identifier allowed by the first U2U relay UE to be allocated to the remote UE.

14. A method for allocating a local identifier, wherein: The method comprises: The second U2U relay UE sends a target message to the first U2U relay UE through the direct communication interface, where the target message carries first information, wherein the first information at least includes a local identification list of remote UEs.

15. The method according to claim 14, wherein: The target message includes at least one of the following messages: Messages related to relay discovery; Messages related to PC5-S connection establishment; Messages related to PC5-RRC reconfiguration.

16. The method according to claim 14, 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 a direct communication interface discovery process.

17. The method according to claim 14, wherein: 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 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 a remote UE; 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, wherein 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 to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

18. The method according to claim 17, wherein: The remote UE that uses the second U2U relay UE to perform U2U communication includes: a remote UE that uses the second U2U relay UE to perform 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 to perform U2U communication includes: a remote UE that does not use the first U2U relay UE to perform U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

19. A local identification allocation device, wherein: For a first U2U relay UE, the apparatus comprises: a determining unit, 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; The first information at least includes a local identifier list of the remote UE.

20. A local identifier allocation device, wherein: For a second U2U relay UE, the apparatus comprises: A sending unit is used to send a target message to a first U2U relay UE through a direct communication interface, where the target message carries first information, wherein the first information at least includes a local identification list of a remote UE.

21. A first U2U relay UE, wherein: Including memory, transceiver, processor: Memory for storing computer programs; a transceiver, configured to transmit and receive data under the control of the processor; and a processor, configured to read the computer program in the memory and perform the following operations: Determine, according to the first information, a local identifier that the first U2U relay UE is allowed to allocate to the remote UE; The first information at least includes a local identifier list of the remote UE.

22. The first U2U relay UE according to claim 21, wherein: The processor is further configured 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, where the target message carries the first information, and the number of the second U2U relay UE is one or more; The first information is acquired according to the pre-configuration information.

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

24. The first U2U relay UE according to claim 22, wherein: 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, wherein: 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 allocated to a remote UE; 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, wherein 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 to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

26. The first U2U relay UE according to claim 25, wherein: The remote UE that uses the second U2U relay UE to perform U2U communication includes: a remote UE that uses the second U2U relay UE to perform 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 to perform U2U communication includes: a remote UE that does not use the first U2U relay UE to perform U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

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 the remote UE based on the first information, the local identifier that the first U2U relay UE has allocated to the 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: Deducting the local identifier in the first local identifier list, deducting the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting 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, so as to obtain the local identifier that the first U2U relay UE is allowed to allocate to the remote UE; Deducting the local identifier in the second local identifier list from the local identifier list corresponding to the first U2U relay UE, deducting the local identifier that the first U2U relay UE has allocated to the remote UE, and / or deducting 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; deducting the local identifier that the first U2U relay UE has allocated to the remote UE and / or deducting 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 taking 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 determining, according to the first intersection, the local identifier that the first U2U relay UE is allowed to allocate to the remote UE; A second intersection is taken for 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 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 based on the fifth local identifier list.

29. The first U2U relay UE according to claim 28, wherein: The local identification 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: The sixth local identifier list that the first U2U relay UE is allowed to allocate to the remote UE in the pre-configuration information is obtained 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: According to the sixth local identifier list, determine the local identifier that the first U2U relay UE is allowed to allocate to the remote UE.

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 the first target remote UE and the second target remote UE establish a U2U connection through the first U2U relay UE, local identifiers are allocated to the first target remote UE and the second target remote UE according to the local identifiers allowed by the first U2U relay UE to be allocated to 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 to the first target remote UE and the second target remote UE according to the local identifier allowed to be allocated to the remote UE by the first U2U relay UE; or, The same local identifier is allocated to the first target remote UE and the second target remote UE according to the local identifier allowed to be allocated to the remote UE by the first U2U relay UE.

34. A second U2U relay UE, wherein: Including memory, transceiver, processor: Memory for storing computer programs; a transceiver, configured to transmit and receive data under the control of the processor; and a processor, configured to read the computer program in the memory and perform the following operations: The transceiver is controlled to send a target message to the first U2U relay UE through the direct communication interface, where the target message carries first information, wherein the first information at least includes a local identification list of the remote UE.

35. The second U2U relay UE according to claim 34, wherein: The target message includes at least one of the following messages: Messages related to relay discovery; Messages related to PC5-S connection establishment; 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 a 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, 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 allocated to a remote UE; 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, wherein 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 to the remote UE by the second U2U relay UE, and the local identifier list corresponding to the second U2U relay UE includes one or more local identifiers that can be used to allocate to the remote UE.

38. The second U2U relay UE according to claim 37, wherein: The remote UE that uses the second U2U relay UE to perform U2U communication includes: a remote UE that uses the second U2U relay UE to perform 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 to perform U2U communication includes: a remote UE that does not use the first U2U relay UE to perform U2U communication through a single-hop U2U relay method and / or a multi-hop U2U relay method.

39. A processor-readable storage medium, wherein: The processor-readable storage medium stores a program, and the program is used to enable a 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 enable the processor to execute the method according to any one of claims 14 to 18.

Images