Method and apparatus for allocating local id, and storage medium

Abstract

The present disclosure provides a method and apparatus for allocating a local ID, and a storage medium. The method comprises: a first network device sends first information to a second network device, wherein the first information comprises a first local ID request indication and / or a first local ID allocated to a remote terminal by the first network device, and the first local ID request indication is used for requesting the second network device to allocate a local ID to the remote terminal. The remote terminal communicates with the first network device and / or the second network device by means of a relay terminal.

Description

Method, device and storage medium for allocating local identifiers

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to Chinese patent application No. 202311126285.9, filed on September 1, 2023, entitled “Method, device and storage medium for allocating local identifiers”, which is incorporated herein by reference in its entirety. Technical Field

[0003] The present disclosure relates to the field of wireless communication technologies, and in particular to a method, device, and storage medium for allocating local identifiers. Background Art

[0004] In order to improve the peak rate and / or reliability of the remote terminal (remote UE), a multi-path (i.e., multi-path transmission) mechanism can be considered. For scenarios using the multi-path transmission mechanism, there is no clear solution for how to assign the local ID of the remote terminal.

[0005] Summary of the Invention

[0006] The present disclosure provides a method, device and storage medium for allocating local identifiers, so as to solve the problem of how to allocate local identifiers of remote terminals.

[0007] In a first aspect, the present disclosure provides a method for allocating a local identifier, applied to a first network device, comprising:

[0008] Sending first information to the second network device, where the first information includes a first local identifier request indication and / or a first local identifier allocated by the first network device to the remote terminal; the first local identifier request indication is used to request the second network device to allocate a local identifier to the remote terminal;

[0009] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0010] In some embodiments, sending the first information to the second network device includes:

[0011] A local identifier is allocated to the remote terminal, and a first local identifier request indication is sent to the second network device.

[0012] In some embodiments, when the first information includes the first local identifier, the method further includes:

[0013] A first reply message sent by the second network device is received, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

[0014] In some embodiments, the method further comprises:

[0015] Based on the first reply message, a local identifier for identifying the remote terminal on the first network device side is determined.

[0016] In some embodiments, determining, based on the first reply message, a local identifier on the first network device side for identifying the remote terminal includes:

[0017] If the first network device side cannot use the second local identifier allocated by the second network device to the remote terminal, determining that the first network device side uses the first local identifier to identify the remote terminal;

[0018] If the first network device side can use the second local identifier allocated by the second network device to the remote terminal, it is determined that the first network device side uses the second local identifier to identify the remote terminal, or it is determined that the first network device side uses the first local identifier to identify the remote terminal.

[0019] In some embodiments, the method further comprises:

[0020] When it is determined that the first network device side uses the first local identifier to identify the remote terminal, first indication information is sent to the second network device, where the first indication information is used to instruct the first network device side not to use the second local identifier to identify the remote terminal.

[0021] In some embodiments, when the first information includes the first local identifier, the method further includes:

[0022] A second reply message sent by the second network device is received, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device to use the first local identifier to identify the remote terminal.

[0023] In some embodiments, sending the first information to the second network device includes:

[0024] Determining a first local identifier allocated to the remote terminal based on the operation management and maintenance (OAM) pre-configuration information;

[0025] The first local identifier is sent to the second network device.

[0026] In some embodiments, before sending the first information to the second network device, the method further includes:

[0027] A second local identity request indication sent by the second network device is received, where the second local identity request indication is used to request the first network device to allocate a local identity to the remote terminal.

[0028] In a second aspect, the present disclosure further provides a method for allocating a local identifier, applied to a second network device, comprising:

[0029] Receive first information, the first information including a first local identity request indication and / or a first local identity allocated by the first network device to the remote terminal; the first local identity request indication is used to request the second network device to allocate a local identity to the remote terminal;

[0030] allocating a local identifier to the remote terminal based on the first information;

[0031] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0032] In some embodiments, receiving the first information includes:

[0033] receiving first information sent by a first network device, where the first information includes a first local identity request indication and / or a first local identity; or,

[0034] First information sent by a remote terminal is received, where the first information includes a first local identity request indication.

[0035] In some embodiments, allocating a local identifier to the remote terminal based on the first information includes:

[0036] When the first information includes the first local identifier and it is determined that the first local identifier cannot be used on the second network device side, a second local identifier is allocated to the remote terminal.

[0037] In some embodiments, the method further comprises:

[0038] A first reply message is sent to the first network device, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

[0039] In some embodiments, allocating a local identifier to the remote terminal based on the first information includes:

[0040] When the first information includes the first local identifier and it is determined that the first local identifier can be used on the second network device side, it is determined that the second network device side uses the first local identifier to identify the remote terminal.

[0041] In some embodiments, the method further comprises:

[0042] A second reply message is sent to the first network device, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device to use the first local identifier to identify the remote terminal.

[0043] In some embodiments, before receiving the first information sent by the first network device, the method further includes:

[0044] A second local identity request indication is sent to the first network device, where the second local identity request indication is used to request the first network device to allocate a local identity to the remote terminal.

[0045] In a third aspect, the present disclosure further provides a method for allocating a local identifier, applied to a remote terminal, comprising:

[0046] Sending a first local identity request indication to the second network device, where the first local identity request indication is used to request the second network device to allocate a local identity to the remote terminal;

[0047] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0048] In a fourth aspect, the present disclosure further provides a first network device, comprising a memory, a transceiver, and a processor;

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

[0050] Sending first information to the second network device, where the first information includes a first local identifier request indication and / or a first local identifier allocated by the first network device to the remote terminal; the first local identifier request indication is used to request the second network device to allocate a local identifier to the remote terminal;

[0051] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0052] In some embodiments, sending the first information to the second network device includes:

[0053] A local identifier is allocated to the remote terminal, and a first local identifier request indication is sent to the second network device.

[0054] In some embodiments, when the first information includes the first local identifier, the operation further includes:

[0055] A first reply message sent by the second network device is received, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

[0056] In some embodiments, the operations further include:

[0057] Based on the first reply message, a local identifier for identifying the remote terminal on the first network device side is determined.

[0058] In some embodiments, determining, based on the first reply message, a local identifier on the first network device side for identifying the remote terminal includes:

[0059] If the first network device side cannot use the second local identifier allocated by the second network device to the remote terminal, determining that the first network device side uses the first local identifier to identify the remote terminal;

[0060] If the first network device side can use the second local identifier allocated by the second network device to the remote terminal, it is determined that the first network device side uses the second local identifier to identify the remote terminal, or it is determined that the first network device side uses the first local identifier to identify the remote terminal.

[0061] In some embodiments, the operations further include:

[0062] When it is determined that the first network device side uses the first local identifier to identify the remote terminal, first indication information is sent to the second network device, where the first indication information is used to instruct the first network device side not to use the second local identifier to identify the remote terminal.

[0063] In some embodiments, when the first information includes the first local identifier, the operation further includes:

[0064] A second reply message sent by the second network device is received, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device to use the first local identifier to identify the remote terminal.

[0065] In some embodiments, sending the first information to the second network device includes:

[0066] Determining a first local identifier allocated to the remote terminal based on the operation management and maintenance (OAM) pre-configuration information;

[0067] The first local identifier is sent to the second network device.

[0068] In some embodiments, before sending the first information to the second network device, the operation further includes:

[0069] A second local identity request indication sent by the second network device is received, where the second local identity request indication is used to request the first network device to allocate a local identity to the remote terminal.

[0070] In a fifth aspect, the present disclosure further provides a second network device, comprising a memory, a transceiver, and a processor;

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

[0072] Receive first information, the first information including a first local identity request indication and / or a first local identity allocated by the first network device to the remote terminal; the first local identity request indication is used to request the second network device to allocate a local identity to the remote terminal;

[0073] allocating a local identifier to the remote terminal based on the first information;

[0074] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0075] In some embodiments, receiving the first information includes:

[0076] receiving first information sent by a first network device, where the first information includes a first local identity request indication and / or a first local identity; or,

[0077] First information sent by a remote terminal is received, where the first information includes a first local identity request indication.

[0078] In some embodiments, allocating a local identifier to the remote terminal based on the first information includes:

[0079] When the first information includes the first local identifier and it is determined that the first local identifier cannot be used on the second network device side, a second local identifier is allocated to the remote terminal.

[0080] In some embodiments, the operations further include:

[0081] A first reply message is sent to the first network device, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

[0082] In some embodiments, allocating a local identifier to the remote terminal based on the first information includes:

[0083] When the first information includes the first local identifier and it is determined that the first local identifier can be used on the second network device side, it is determined that the second network device side uses the first local identifier to identify the remote terminal.

[0084] In some embodiments, the operations further include:

[0085] A second reply message is sent to the first network device, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device to use the first local identifier to identify the remote terminal.

[0086] In some embodiments, before receiving the first information sent by the first network device, the operation further includes:

[0087] A second local identity request indication is sent to the first network device, where the second local identity request indication is used to request the first network device to allocate a local identity to the remote terminal.

[0088] In a sixth aspect, the present disclosure further provides a remote terminal comprising a memory, a transceiver, and a processor;

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

[0090] Sending a first local identity request indication to the second network device, where the first local identity request indication is used to request the second network device to allocate a local identity to the remote terminal;

[0091] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0092] In a seventh aspect, the present disclosure further provides an apparatus for allocating a local identifier, comprising:

[0093] A first sending unit is configured to send first information to the second network device, where the first information includes a first local identifier request indication and / or a first local identifier allocated by the first network device to the remote terminal; the first local identifier request indication is used to request the second network device to allocate a local identifier to the remote terminal;

[0094] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0095] In some embodiments, sending the first information to the second network device includes:

[0096] A local identifier is allocated to the remote terminal, and a first local identifier request indication is sent to the second network device.

[0097] In some embodiments, the apparatus further comprises:

[0098] The first receiving unit is configured to receive a first reply message sent by the second network device when the first information includes the first local identifier, where the first reply message includes the second local identifier allocated by the second network device to the remote terminal.

[0099] In some embodiments, the apparatus further comprises:

[0100] The first determining unit is configured to determine, based on the first reply message, a local identifier on the first network device side for identifying the remote terminal.

[0101] In some embodiments, determining, based on the first reply message, a local identifier on the first network device side for identifying the remote terminal includes:

[0102] If the first network device side cannot use the second local identifier allocated by the second network device to the remote terminal, determining that the first network device side uses the first local identifier to identify the remote terminal;

[0103] If the first network device side can use the second local identifier allocated by the second network device to the remote terminal, it is determined that the first network device side uses the second local identifier to identify the remote terminal, or it is determined that the first network device side uses the first local identifier to identify the remote terminal.

[0104] In some embodiments, the first sending unit is further configured to:

[0105] When it is determined that the first network device side uses the first local identifier to identify the remote terminal, first indication information is sent to the second network device, where the first indication information is used to instruct the first network device side not to use the second local identifier to identify the remote terminal.

[0106] In some embodiments, the apparatus further comprises:

[0107] The second receiving unit is used to receive a second reply message sent by the second network device when the first information includes the first local identifier, and the second reply message includes second indication information, and the second indication information is used to instruct the second network device side to use the first local identifier to identify the remote terminal.

[0108] In some embodiments, sending the first information to the second network device includes:

[0109] Determining a first local identifier allocated to the remote terminal based on the operation management and maintenance (OAM) pre-configuration information;

[0110] The first local identifier is sent to the second network device.

[0111] In some embodiments, the apparatus further comprises:

[0112] The third receiving unit is configured to receive a second local identity request indication sent by the second network device before sending the first information to the second network device, where the second local identity request indication is used to request the first network device to allocate a local identity to the remote terminal.

[0113] In an eighth aspect, the present disclosure further provides an apparatus for allocating a local identifier, comprising:

[0114] a fourth receiving unit, configured to receive first information, the first information including a first local identity request indication and / or a first local identity allocated by the first network device to the remote terminal; the first local identity request indication is used to request the second network device to allocate a local identity to the remote terminal;

[0115] an allocating unit, configured to allocate a local identifier to the remote terminal based on the first information;

[0116] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0117] In some embodiments, receiving the first information includes:

[0118] receiving first information sent by a first network device, where the first information includes a first local identity request indication and / or a first local identity; or,

[0119] First information sent by a remote terminal is received, where the first information includes a first local identity request indication.

[0120] In some embodiments, allocating a local identifier to the remote terminal based on the first information includes:

[0121] When the first information includes the first local identifier and it is determined that the first local identifier cannot be used on the second network device side, a second local identifier is allocated to the remote terminal.

[0122] In some embodiments, the apparatus further comprises:

[0123] The second sending unit is configured to send a first reply message to the first network device, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

[0124] In some embodiments, allocating a local identifier to the remote terminal based on the first information includes:

[0125] When the first information includes the first local identifier and it is determined that the first local identifier can be used on the second network device side, it is determined that the second network device side uses the first local identifier to identify the remote terminal.

[0126] In some embodiments, the apparatus further comprises:

[0127] The third sending unit is used to send a second reply message to the first network device, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device to use the first local identifier to identify the remote terminal.

[0128] In some embodiments, the apparatus further comprises:

[0129] The fourth sending unit is configured to send a second local identifier request indication to the first network device before receiving the first information sent by the first network device, where the second local identifier request indication is used to request the first network device to allocate a local identifier to the remote terminal.

[0130] In a ninth aspect, the present disclosure further provides an apparatus for allocating a local identifier, comprising:

[0131] A fifth sending unit, configured to send a first local identity request indication to the second network device, where the first local identity request indication is used to request the second network device to allocate a local identity to the remote terminal;

[0132] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0133] In the tenth aspect, the present disclosure also provides a non-transitory readable storage medium, which stores a computer program, and the computer program is used to enable a processor to execute the method of allocating local identifiers as described in the first aspect, or execute the method of allocating local identifiers as described in the second aspect, or execute the method of allocating local identifiers as described in the third aspect.

[0134] In the eleventh aspect, the present disclosure also provides a communication device, in which a computer program is stored, and the computer program is used to enable the communication device to execute the method of allocating local identifiers as described in the first aspect, or execute the method of allocating local identifiers as described in the second aspect, or execute the method of allocating local identifiers as described in the third aspect.

[0135] In the twelfth aspect, the present disclosure also provides a processor-readable storage medium, which stores a computer program, and the computer program is used to enable the processor to execute the method of allocating local identifiers as described in the first aspect, or execute the method of allocating local identifiers as described in the second aspect, or execute the method of allocating local identifiers as described in the third aspect.

[0136] In the thirteenth aspect, the present disclosure also provides a chip product, in which a computer program is stored, and the computer program is used to enable the chip product to execute the method of allocating local identifiers as described in the first aspect, or execute the method of allocating local identifiers as described in the second aspect, or execute the method of allocating local identifiers as described in the third aspect.

[0137] The method, apparatus, and storage medium for allocating a local identifier provided by the present disclosure send first information to a second network device through a first network device, so that at least one of the first network device and the second network device allocates a local identifier to a remote terminal, thereby solving the problem of how to allocate a local identifier to a remote terminal in a multipath transmission scenario across base stations, and helping to improve the peak rate and / or reliability of the remote terminal through a multipath transmission mechanism. BRIEF DESCRIPTION OF THE DRAWINGS

[0138] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or related technologies, the following is a brief introduction to the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are some embodiments of the present disclosure. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0139] FIG1 is a schematic diagram of direct communication provided by related art;

[0140] FIG2 is a schematic diagram of a terminal-to-network relay scenario provided by related technologies;

[0141] FIG3 is a schematic diagram of three multipath transmission scenarios provided by related technologies;

[0142] FIG4 is a schematic diagram of an interaction interface between base stations provided by related art;

[0143] FIG5 is a flowchart of a method for allocating a local identifier according to an embodiment of the present disclosure;

[0144] FIG6 is a second flow chart of a method for allocating local identifiers provided in an embodiment of the present disclosure;

[0145] FIG7 is a third flow chart of a method for allocating local identifiers according to an embodiment of the present disclosure;

[0146] FIG8 is a signaling interaction diagram of Example 1 provided by an embodiment of the present disclosure;

[0147] FIG9 is a signaling interaction diagram of Example 2 provided in an embodiment of the present disclosure;

[0148] FIG10 is a signaling interaction diagram of Example 3 provided in an embodiment of the present disclosure;

[0149] FIG11 is a signaling interaction diagram of Example 4 provided in an embodiment of the present disclosure;

[0150] FIG12 is a signaling interaction diagram of Example 5 provided in an embodiment of the present disclosure;

[0151] FIG13 is a schematic structural diagram of a first network device provided in an embodiment of the present disclosure;

[0152] FIG14 is a schematic structural diagram of a second network device provided in an embodiment of the present disclosure;

[0153] FIG15 is a schematic diagram of the structure of a remote terminal provided in an embodiment of the present disclosure;

[0154] FIG16 is a schematic diagram of a structure of a device for allocating a local identifier according to an embodiment of the present disclosure;

[0155] FIG17 is a second structural diagram of the apparatus for allocating local identifiers provided in an embodiment of the present disclosure;

[0156] FIG18 is a third structural diagram of the apparatus for allocating local identifiers provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0157] In the embodiments of the present disclosure, the term "and / or" describes the association relationship between associated objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. The character " / " generally indicates that the associated objects are in an "or" relationship.

[0158] In the embodiments of the present disclosure, the term "plurality" refers to two or more than two, and other quantifiers are similar thereto.

[0159] In the embodiments of the present disclosure, the terms "first," "second," and the like are used to distinguish similar objects, and are not used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, so that the embodiments of the present disclosure can be implemented in an order other than that illustrated or described herein. Furthermore, the objects distinguished by "first" and "second" are generally of the same type, and do not limit the number of objects. For example, the first object can be one or more.

[0160] The following will be combined with the accompanying drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the embodiments described are only part of the embodiments of the present disclosure and not all of the embodiments. Based on the embodiments of the present disclosure, all other embodiments obtained by ordinary technicians in this field without making any creative efforts shall fall within the scope of protection of the present disclosure.

[0161] In order to facilitate a clearer understanding of the technical solutions of the various embodiments of the present disclosure, some technical contents related to the various embodiments of the present disclosure are first introduced.

[0162] (1)Direct communication

[0163] Figure 1 illustrates direct communication in related technologies. As shown in Figure 1, direct communication allows nearby terminals to transmit data over a short distance via a direct communication link (also known as a Sidelink or PC5 link). The wireless interface corresponding to the direct communication link is called a direct communication interface (also known as a Sidelink interface or PC5 interface).

[0164] (2) Layer 2 (L2) relay

[0165] To expand network coverage, it is possible to consider introducing an L2 relay, which can itself be a terminal with relay functionality. Figure 2 is a schematic diagram of a terminal-to-network relay scenario provided by related technologies. As shown in Figure 2, for the terminal-to-network relay (UE-to-Network Relay, U2N Relay) scenario, the interface between the L2 relay and the network uses a Uu interface, and the corresponding communication link is a Uu link. The interface between the L2 relay and the relayed terminal (which can be called a remote terminal) uses a direct communication interface, and the corresponding communication link is a direct communication link.

[0166] (3) Inter-gNB multipath

[0167] After the introduction of U2N Relay, in order to improve the peak rate and / or reliability of remote terminals, a multi-path mechanism can be considered. That is, the terminal can access the network device through the Uu interface and U2N Relay at the same time.

[0168] To facilitate the description of different paths in multipath transmission scenarios, the following terms are defined:

[0169] Direct path: refers to the transmission path used by the remote terminal to directly connect to the network device through the Uu interface.

[0170] Indirect path: refers to the transmission path used by the remote terminal to connect to the network device through the U2N Relay.

[0171] Figure 3 illustrates three multipath transmission scenarios provided by related technologies. As shown in Figure 3, (a) illustrates an inter-gNB direct-indirect multipath scenario, where a remote terminal is connected to two gNBs simultaneously. The transmission path between the remote terminal and the master node (MN) is a direct path, while the transmission path between the remote terminal and the slave node (SN) is an indirect path. (b) illustrates an inter-gNB indirect-indirect multipath scenario, where a remote terminal is connected to two gNBs simultaneously. The transmission path between the remote terminal and the master node (MN) is an indirect path, while the transmission path between the remote terminal and the slave node (SN) is an indirect path. (c) illustrates an inter-gNB indirect-direct multipath scenario, where a remote terminal is connected to two gNBs simultaneously. The transmission path between the remote terminal and the master node (MN) is an indirect path, while the transmission path between the remote terminal and the slave node (SN) is a direct path. In FIG3 , the F1 interface is the interface between the centralized unit (Gnb-CU) of the base station and the distributed unit (Gnb-DU) of the base station.

[0172] (4) Interaction interface between base stations

[0173] Figure 4 is a schematic diagram of the interaction interface between base stations provided by the relevant technology. As shown in Figure 4, base stations can interact with each other in two ways. (a) in Figure 4 indicates that base stations can directly interact with each other through the Xn interface, and (b) in Figure 4 indicates that base stations can interact with each other through the NG interface between the base station and the access and mobility management function (Access and Mobility Management Function, AMF). The interaction information between base stations is transferred through the AMF.

[0174] Currently, there is no clear solution to support cross-base station multi-path transmission. How to allocate local identifiers of remote terminals in cross-base station multi-path transmission scenarios is a problem that needs to be solved.

[0175] FIG5 is a flow chart of a method for allocating a local identifier according to an embodiment of the present disclosure. The method may be applied to a first network device. As shown in FIG5 , the method includes the following steps:

[0176] Step 500: Send first information to the second network device, where the first information includes a first local identity request indication and / or a first local identity allocated by the first network device to the remote terminal; the first local identity request indication is used to request the second network device to allocate a local identity to the remote terminal.

[0177] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0178] Specifically, the remote terminal is connected to the first network device and the second network device at the same time. The remote terminal can communicate with the first network device through the relay terminal, that is, the transmission path between the remote terminal and the first network device is a non-direct connection path, and the transmission path between the remote terminal and the second network device can be a direct connection path; or, the remote terminal can communicate with the second network device through the relay terminal, that is, the transmission path between the remote terminal and the second network device is a non-direct connection path, and the transmission path between the remote terminal and the first network device can be a direct connection path; or, the remote terminal can communicate with the first network device and the second network device through the relay terminal, that is, the transmission path between the remote terminal and the first network device is a non-direct connection path, and the transmission path between the remote terminal and the second network device is a non-direct connection path.

[0179] The first network device can be interpreted as a source network device (e.g., a source base station) or a master network device (e.g., a master base station, a master node, etc.), and the second network device can be correspondingly interpreted as a target network device (e.g., a target base station) or a slave network device (e.g., a slave base station, a slave node, etc.). Alternatively, the first network device can be interpreted as a target network device (e.g., a target base station) or a slave network device (e.g., a slave base station, a slave node, etc.), and the second network device can be correspondingly interpreted as a source network device (e.g., a source base station) or a master network device (e.g., a master base station, a master node, etc.).

[0180] In a scenario where the CU / DU of the network devices are separated, the first network device can be interpreted as the CU of the first network device, and the second network device can be interpreted as the CU of the second network device.

[0181] The first network device and the second network device may interact through the Xn interface between the first network device and the second network device, or may transfer the interaction information between the first network device and the second network device through the AMF, that is, interact through the NG interface.

[0182] In the embodiment of the present disclosure, at least one of the first network device and the second network device allocates the local identifier of the remote terminal.

[0183] In some embodiments, the first network device may send a first local identity request indication to the second network device, instructing the second network device to allocate a local identity to the remote terminal.

[0184] In some embodiments, the first network device may send a first local identifier to the second network device, where the first local identifier is assigned by the first network device. The second network device may use the first local identifier or refer to the first local identifier to assign a local identifier to the remote terminal.

[0185] In some embodiments, the first network device may allocate a first local identifier and send a first local identifier request indication and the first local identifier to the second network device. The second network device may use the first local identifier or refer to the first local identifier to allocate a local identifier for the remote terminal.

[0186] In some embodiments, the first information may be carried in a path addition request message, direct communication link terminal information (Sidelink UE Information, SUI), Xn interface signaling, NG interface signaling, etc., which is not specifically limited in this disclosure. The SUI may be carried in a path addition request message or other signaling message, which is not limited here.

[0187] The method for allocating a local identifier provided by the embodiment of the present disclosure sends first information to a second network device through a first network device, so that at least one of the first network device and the second network device allocates a local identifier for a remote terminal, thereby solving the problem of how to allocate a local identifier for a remote terminal in a multi-path transmission scenario across base stations, and helping to improve the peak rate and / or reliability of the remote terminal through a multi-path transmission mechanism.

[0188] In some embodiments, sending the first information to the second network device includes:

[0189] A local identifier is allocated to the remote terminal, and a first local identifier request indication is sent to the second network device.

[0190] Specifically, in the embodiment of the present disclosure, the first network device and the second network device may respectively allocate local identifiers to the remote terminal, and the first network device and the second network device may identify the remote terminal using their respective allocated local identifiers.

[0191] For example, a source network device can assign a local identifier to a remote terminal based on a request from a source relay terminal (i.e., a terminal that provides relay functionality between the remote terminal and the source network device). When the source network device decides to establish multipath transmission for the remote terminal, it can send a path add request message to the target network device. This path add request message can carry a SUI (Survey User Interface) containing a local identifier request indicator. The target network device can then assign a local identifier to the remote terminal based on the received path add request message.

[0192] In some embodiments, when the first information includes the first local identifier, the method further includes:

[0193] A first reply message sent by the second network device is received, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

[0194] Specifically, in the embodiment of the present disclosure, the first network device and the second network device may negotiate to allocate a local identifier of the remote terminal, and the first network device may send the first local identifier allocated by the first network device to the remote terminal to the second network device.

[0195] After the second network device receives the first local identifier, if it determines that the first local identifier cannot be used (for example, the first local identifier conflicts with the local identifier already allocated to other terminals on the second network device side), or the second network device determines not to use the first local identifier, the second network device can allocate a second local identifier to the remote terminal and send a first reply message to the first network device, where the first reply message includes the second local identifier.

[0196] For example, the source network device may allocate local identifier 1 to the remote terminal based on the request instruction of the source relay terminal. When the source network device decides to establish multipath transmission for the remote terminal, the source network device may send a path addition request message to the target network device. The path addition request message may carry the SUI, which includes local identifier 1. After receiving local identifier 1, if the target network device determines that local identifier 1 cannot be used, it may allocate local identifier 2 to the remote terminal and reply to the source network device.

[0197] For another example, when the source network device decides to establish multi-path transmission for the remote terminal, the source network device can send a path addition request message to the target network device. After receiving the path addition request message, the target network device can allocate a local identifier 3 for the remote terminal and send the local identifier 3 to the source network device through interface signaling (Xn interface signaling or NG interface signaling). After receiving the local identifier 3, if the source network device determines that the local identifier 3 cannot be used, it can allocate a local identifier 4 for the remote terminal and reply to the target network device.

[0198] In some embodiments, the method further comprises:

[0199] Based on the first reply message, a local identifier for identifying the remote terminal on the first network device side is determined.

[0200] Specifically, after receiving the first reply message, the first network device may determine, based on the second local identifier carried in the message, the local identifier used by the first network device to identify the remote terminal. For example, based on the first reply message, the first network device may determine whether to use the second local identifier on the first network device side to identify the remote terminal, or to continue to use the first local identifier to identify the remote terminal.

[0201] In some embodiments, determining, based on the first reply message, a local identifier on the first network device side for identifying the remote terminal includes:

[0202] If the first network device side cannot use the second local identifier allocated by the second network device to the remote terminal, determining that the first network device side uses the first local identifier to identify the remote terminal;

[0203] If the first network device side can use the second local identifier allocated by the second network device to the remote terminal, it is determined that the first network device side uses the second local identifier to identify the remote terminal, or it is determined that the first network device side uses the first local identifier to identify the remote terminal.

[0204] Specifically, if the first network device determines that the second local identifier cannot be used (for example, the second local identifier conflicts with a local identifier already allocated to other terminals on the first network device side), the first network device may still use the first local identifier to identify the remote terminal.

[0205] If the first network device determines that the second local identifier can be used (for example, the second local identifier does not conflict with a local identifier already assigned to another terminal on the first network device side), the first network device may use the second local identifier to identify the remote terminal, or the first network device may continue to use the first local identifier to identify the remote terminal. The specific details may depend on the implementation of the first network device.

[0206] In some embodiments, the method further comprises:

[0207] When it is determined that the first network device side uses the first local identifier to identify the remote terminal, first indication information is sent to the second network device, where the first indication information is used to instruct the first network device side not to use the second local identifier to identify the remote terminal.

[0208] Specifically, if the first network device determines that the first local identifier is still used (i.e., the second local identifier is not used), the first network device may send first instruction information to the second network device, instructing the first network device not to use the second local identifier to identify the remote terminal. The first network device and the second network device respectively use different local identifiers to identify the remote terminal.

[0209] In some embodiments, when the first information includes the first local identifier, the method further includes:

[0210] A second reply message sent by the second network device is received, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device to use the first local identifier to identify the remote terminal.

[0211] Specifically, in the embodiment of the present disclosure, the first network device and the second network device may negotiate to allocate a local identifier of the remote terminal, and the first network device may send the first local identifier allocated by the first network device to the remote terminal to the second network device.

[0212] After receiving the first local identifier, if the second network device determines that the first local identifier can be used (for example, the first local identifier does not conflict with a local identifier already assigned to another terminal on the second network device side), the second network device may send a second reply message to the first network device. The second reply message includes second instruction information instructing the second network device to use the first local identifier to identify the remote terminal. The first network device and the second network device use the same local identifier to identify the remote terminal.

[0213] For example, the source network device may allocate local identifier 1 to the remote terminal based on the request instruction of the source relay terminal. When the source network device decides to establish multipath transmission for the remote terminal, the source network device may send a path addition request message to the target network device. The path addition request message may carry a SUI, and the SUI includes local identifier 1. After receiving local identifier 1, if the target network device determines that local identifier 1 can be used, it will reply to the source network device with the second indication information.

[0214] For another example, when the source network device decides to establish multi-path transmission for the remote terminal, the source network device can send a path addition request message to the target network device. After receiving the path addition request message, the target network device can allocate a local identifier 3 for the remote terminal and send the local identifier 3 to the source network device through interface signaling (Xn interface signaling or NG interface signaling). After receiving the local identifier 3, if the source network device determines that the local identifier 3 can be used, it will reply to the target network device with a second indication message.

[0215] In some embodiments, sending the first information to the second network device includes:

[0216] Determining a first local identifier allocated to the remote terminal based on the operation management and maintenance (OAM) pre-configuration information;

[0217] The first local identifier is sent to the second network device.

[0218] Specifically, in the embodiment of the present disclosure, the first network device may allocate a local identifier of the remote terminal based on Operation Administration and Maintenance (OAM) preconfiguration information and then send the identifier to the second network device. The second network device may use the first local identifier allocated by the first network device.

[0219] In some embodiments, the OAM pre-configuration information may pre-configure a value range of the local identifier, and the first network device may select the local identifier of the remote terminal from the value range.

[0220] For example, when the source network device decides to establish multipath transmission for a remote terminal, it can assign a local identifier 5 to the remote terminal based on the OAM preconfiguration information. The source network device can send a path addition request message to the target network device. The path addition request message can carry a SUI (SUI) containing the local identifier 5. After receiving the local identifier 5, the target network device can use the local identifier 5 to identify the remote terminal.

[0221] For another example, when the source network device decides to establish multi-path transmission for the remote terminal, the source network device can send a path addition request message to the target network device. After receiving the path addition request message, the target network device can allocate a local identifier 6 for the remote terminal according to the OAM pre-configuration information, and send the local identifier 6 to the source network device through interface signaling (Xn interface signaling or NG interface signaling). After receiving the local identifier 6, the source network device can use the local identifier 6 to identify the remote terminal.

[0222] In some embodiments, before sending the first information to the second network device, the method further includes:

[0223] A second local identity request indication sent by the second network device is received, where the second local identity request indication is used to request the first network device to allocate a local identity to the remote terminal.

[0224] Specifically, the first network device allocates the local identifier of the remote terminal based on the OAM pre-configuration information, which may be triggered by a second local identifier request indication sent by the second network device. After the second network device sends the second local identifier request indication to the first network device, the first network device allocates the local identifier of the remote terminal based on the OAM pre-configuration information, and then sends it to the second network device.

[0225] For example, when the source network device decides to establish multi-path transmission for the remote terminal, the source network device can send a path addition request message to the target network device. The path addition request message carries the SUI, and the SUI includes a second local identifier request indication. After receiving the path addition request message, the target network device can allocate a local identifier 6 for the remote terminal according to the OAM pre-configuration information, and send the local identifier 6 to the source network device through interface signaling (which can be a path addition request confirmation message). After receiving the local identifier 6, the source network device can use the local identifier 6 to identify the remote terminal.

[0226] FIG6 is a second flow chart of a method for allocating a local identifier according to an embodiment of the present disclosure. The method may be applied to a second network device. As shown in FIG6 , the method includes the following steps:

[0227] Step 600: Receive first information, the first information including a first local identity request indication and / or a first local identity allocated by a first network device to a remote terminal; the first local identity request indication is used to request a second network device to allocate a local identity to the remote terminal.

[0228] Step 601: Allocate a local identifier for a remote terminal based on first information.

[0229] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0230] Specifically, the remote terminal is connected to the first network device and the second network device at the same time. The remote terminal can communicate with the first network device through the relay terminal, that is, the transmission path between the remote terminal and the first network device is a non-direct connection path, and the transmission path between the remote terminal and the second network device can be a direct connection path; or, the remote terminal can communicate with the second network device through the relay terminal, that is, the transmission path between the remote terminal and the second network device is a non-direct connection path, and the transmission path between the remote terminal and the first network device can be a direct connection path; or, the remote terminal can communicate with the first network device and the second network device through the relay terminal, that is, the transmission path between the remote terminal and the first network device is a non-direct connection path, and the transmission path between the remote terminal and the second network device is a non-direct connection path.

[0231] The first network device can be interpreted as a source network device (e.g., a source base station) or a master network device (e.g., a master base station, a master node, etc.), and the second network device can be correspondingly interpreted as a target network device (e.g., a target base station) or a slave network device (e.g., a slave base station, a slave node, etc.). Alternatively, the first network device can be interpreted as a target network device (e.g., a target base station) or a slave network device (e.g., a slave base station, a slave node, etc.), and the second network device can be correspondingly interpreted as a source network device (e.g., a source base station) or a master network device (e.g., a master base station, a master node, etc.).

[0232] In a scenario where the CU / DU of the network devices are separated, the first network device can be interpreted as the CU of the first network device, and the second network device can be interpreted as the CU of the second network device.

[0233] In the embodiment of the present disclosure, at least one of the first network device and the second network device allocates the local identifier of the remote terminal.

[0234] In some embodiments, receiving the first information includes:

[0235] receiving first information sent by a first network device, where the first information includes a first local identity request indication and / or a first local identity; or,

[0236] First information sent by a remote terminal is received, where the first information includes a first local identity request indication.

[0237] For example, the first network device may send a first local identity request indication to the second network device, instructing the second network device to allocate a local identity to the remote terminal.

[0238] For example, the first network device may send a first local identifier to the second network device, where the first local identifier is allocated by the first network device. The second network device may use the first local identifier or allocate a local identifier to the remote terminal with reference to the first local identifier.

[0239] For example, the first network device may allocate a first local identifier and send a first local identifier request indication and the first local identifier to the second network device. The second network device may use the first local identifier or refer to the first local identifier to allocate a local identifier for the remote terminal.

[0240] For example, the remote terminal may send a first local identity request indication to the second network device, instructing the second network device to allocate a local identity to the remote terminal.

[0241] In some embodiments, the first information may be carried in a path addition request message, direct communication link terminal information (Sidelink UE Information, SUI), Xn interface signaling, NG interface signaling, Radio Resource Control (Radio Resource Control, RRC) message, etc., which is not specifically limited in this disclosure. The SUI may be carried in a path addition request message, an RRC message, or other signaling message, which is not limited here.

[0242] The method for allocating a local identifier provided by the embodiment of the present disclosure, by sending a first message to a second network device, enables at least one of the first network device and the second network device to allocate a local identifier of a remote terminal, thereby solving the problem of how to allocate a local identifier to a remote terminal in a multipath transmission scenario across base stations, and helps to improve the peak rate and / or reliability of the remote terminal through a multipath transmission mechanism.

[0243] In some embodiments, allocating a local identifier to the remote terminal based on the first information includes:

[0244] When the first information includes the first local identifier and it is determined that the first local identifier cannot be used on the second network device side, a second local identifier is allocated to the remote terminal.

[0245] Specifically, after the second network device receives the first local identifier sent by the first network device, if it determines that the first local identifier cannot be used (for example, the first local identifier conflicts with the local identifier allocated to other terminals on the second network device side), or the second network device determines not to use the first local identifier, the second network device can allocate a second local identifier to the remote terminal.

[0246] In some embodiments, the method further comprises:

[0247] A first reply message is sent to the first network device, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

[0248] For example, the source network device can assign local identifier 1 to the remote terminal based on the request instruction of the source relay terminal. When the source network device decides to establish multipath transmission for the remote terminal, it can send a path addition request message to the destination network device. The path addition request message can carry the SUI, which includes local identifier 1. After receiving local identifier 1, if the destination network device determines that local identifier 1 cannot be used, it can assign local identifier 2 to the remote terminal and reply to the source network device.

[0249] For another example, when the source network device decides to establish multi-path transmission for the remote terminal, the source network device can send a path addition request message to the target network device. After receiving the path addition request message, the target network device can allocate a local identifier 3 for the remote terminal and send the local identifier 3 to the source network device through interface signaling (Xn interface signaling or NG interface signaling). After receiving the local identifier 3, if the source network device determines that the local identifier 3 cannot be used, it can allocate a local identifier 4 for the remote terminal and reply to the target network device.

[0250] In some embodiments, allocating a local identifier to the remote terminal based on the first information includes:

[0251] When the first information includes the first local identifier and it is determined that the first local identifier can be used on the second network device side, it is determined that the second network device side uses the first local identifier to identify the remote terminal.

[0252] Specifically, after the second network device receives the first local identifier sent by the first network device, if it is determined that the first local identifier can be used (for example, the first local identifier does not conflict with the local identifier allocated to other terminals on the second network device side), the second network device can use the first local identifier to identify the remote terminal.

[0253] In some embodiments, the method further comprises:

[0254] A second reply message is sent to the first network device, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device to use the first local identifier to identify the remote terminal.

[0255] For example, the source network device may allocate local identifier 1 to the remote terminal based on the request instruction of the source relay terminal. When the source network device decides to establish multipath transmission for the remote terminal, the source network device may send a path addition request message to the target network device. The path addition request message may carry a SUI, and the SUI includes local identifier 1. After receiving local identifier 1, if the target network device determines that local identifier 1 can be used, it will reply to the source network device with the second indication information.

[0256] For another example, when the source network device decides to establish multi-path transmission for the remote terminal, the source network device can send a path addition request message to the target network device. After receiving the path addition request message, the target network device can allocate a local identifier 3 for the remote terminal and send the local identifier 3 to the source network device through interface signaling (Xn interface signaling or NG interface signaling). After receiving the local identifier 3, if the source network device determines that the local identifier 3 can be used, it will reply to the target network device with a second indication message.

[0257] In some embodiments, before receiving the first information sent by the first network device, the method further includes:

[0258] A second local identity request indication is sent to the first network device, where the second local identity request indication is used to request the first network device to allocate a local identity to the remote terminal.

[0259] Specifically, the first network device allocates the local identifier of the remote terminal, which can be triggered by the second local identifier request indication sent by the second network device. After the second network device sends the second local identifier request indication to the first network device, the first network device allocates the local identifier of the remote terminal and then sends it to the second network device.

[0260] For example, when the source network device decides to establish multi-path transmission for the remote terminal, the source network device can send a path addition request message to the target network device. The path addition request message carries the SUI, and the SUI includes a second local identifier request indication. After receiving the path addition request message, the target network device can allocate a local identifier 6 for the remote terminal according to the OAM pre-configuration information, and send the local identifier 6 to the source network device through interface signaling (which can be a path addition request confirmation message). After receiving the local identifier 6, the source network device can use the local identifier 6 to identify the remote terminal.

[0261] FIG7 is a third flow chart of a method for allocating a local identifier according to an embodiment of the present disclosure. The method may be applied to a remote terminal. As shown in FIG7 , the method includes the following steps:

[0262] Step 700: Send a first local identity request indication to a second network device, where the first local identity request indication is used to request the second network device to allocate a local identity to a remote terminal.

[0263] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0264] Specifically, the remote terminal is connected to the first network device and the second network device at the same time. The remote terminal can communicate with the first network device through the relay terminal, that is, the transmission path between the remote terminal and the first network device is a non-direct connection path, and the transmission path between the remote terminal and the second network device can be a direct connection path; or, the remote terminal can communicate with the second network device through the relay terminal, that is, the transmission path between the remote terminal and the second network device is a non-direct connection path, and the transmission path between the remote terminal and the first network device can be a direct connection path; or, the remote terminal can communicate with the first network device and the second network device through the relay terminal, that is, the transmission path between the remote terminal and the first network device is a non-direct connection path, and the transmission path between the remote terminal and the second network device is a non-direct connection path.

[0265] The first network device can be interpreted as a source network device (e.g., a source base station) or a master network device (e.g., a master base station, a master node, etc.), and the second network device can be correspondingly interpreted as a target network device (e.g., a target base station) or a slave network device (e.g., a slave base station, a slave node, etc.). Alternatively, the first network device can be interpreted as a target network device (e.g., a target base station) or a slave network device (e.g., a slave base station, a slave node, etc.), and the second network device can be correspondingly interpreted as a source network device (e.g., a source base station) or a master network device (e.g., a master base station, a master node, etc.).

[0266] In a scenario where the CU / DU of the network devices are separated, the first network device can be interpreted as the CU of the first network device, and the second network device can be interpreted as the CU of the second network device.

[0267] In the embodiment of the present disclosure, at least one of the first network device and the second network device allocates the local identifier of the remote terminal.

[0268] The allocation of a local identifier by the second network device to the remote terminal may be triggered by the remote terminal, and the remote terminal may send a first local identifier request indication to the second network device, instructing the second network device to allocate a local identifier to the remote terminal.

[0269] For example, the source network device may allocate a local identifier for the remote terminal based on a request indication from a source relay terminal (i.e., a terminal providing a relay function between the remote terminal and the source network device). When the source network device decides to establish multipath transmission for the remote terminal, it may send a path addition request message to the target network device. The target network device may, based on the path addition request message, allocate the relevant configuration for the remote terminal to access the target network device and send it to the remote terminal. The remote terminal then sends an SUI to the target network device. The SUI includes a first local identifier request indication, requesting the target network device to allocate a local identifier for the remote terminal.

[0270] The method for allocating local identifiers provided in the embodiments of the present disclosure can trigger the second network device to allocate the local identifier of the remote terminal by the remote terminal, thereby solving the problem of how to allocate local identifiers to remote terminals in a multi-path transmission scenario across base stations, and helping to improve the peak rate and / or reliability of the remote terminal through the multi-path transmission mechanism.

[0271] The methods provided in the various embodiments of the present disclosure are based on the same application concept, so the implementation of each method can refer to each other, and the repeated parts will not be repeated.

[0272] The following describes the methods provided in the above embodiments of the present disclosure through examples of specific application scenarios.

[0273] Example 1 (option 1a): Two base stations (or base station CUs) respectively allocate local identifiers to the remote terminal, and allocation of the local identifier by the second base station is triggered by the first base station.

[0274] FIG8 is a signaling interaction diagram of Example 1 provided by an embodiment of the present disclosure. As shown in FIG8 , the main process includes:

[0275] Step 1: A PC5 connection is established between the remote terminal and the first relay terminal.

[0276] Step 2: The first relay terminal sends an SUI to the first base station. The SUI includes request information, and the request information is used to request the first base station to allocate a local identifier for the remote terminal.

[0277] Step 3: The first base station allocates a local identifier a to the remote terminal and generates relevant configurations for the remote terminal to access the first base station, including PC5 configuration, mapping configuration, etc.

[0278] Step 4: The first base station sends an RRC reconfiguration message to the remote terminal, which includes the local identifier a and the configuration related to the remote terminal accessing the first base station.

[0279] Step 5: The first base station decides to establish an inter-gNB indirect-indirect multi-path for the remote terminal and sends a path addition request message to the second base station, carrying the SUI. The SUI includes a first local identity request indication, requesting the second base station to allocate a local identity for the remote terminal.

[0280] Step 6: The second base station allocates a local identifier b to the remote terminal and generates relevant configurations for the remote terminal to access the second base station, including PC5 configuration, mapping configuration, etc.

[0281] Step 7: The second base station sends an RRC reconfiguration message to the remote terminal, which includes the local identifier b and the configuration related to the remote terminal accessing the second base station.

[0282] Note: Local identifier a and local identifier b can be the same or different.

[0283] Example 2 (option 1b): Two base stations (or base station CUs) respectively allocate local identifiers to the remote terminal, and allocation of the local identifier by the second base station is triggered by the remote terminal.

[0284] FIG9 is a signaling interaction diagram of Example 2 provided in an embodiment of the present disclosure. As shown in FIG9 , the main process includes:

[0285] Step 1: A PC5 connection is established between the remote terminal and the first relay terminal.

[0286] Step 2: The first relay terminal sends an SUI to the first base station. The SUI includes request information, and the request information is used to request the first base station to allocate a local identifier for the remote terminal.

[0287] Step 3: The first base station allocates a local identifier a to the remote terminal and generates relevant configurations for the remote terminal to access the first base station, including PC5 configuration, mapping configuration, etc.

[0288] Step 4: The first base station sends an RRC reconfiguration message to the remote terminal, which includes the local identifier a and the configuration related to the remote terminal accessing the first base station.

[0289] Step 5: The first base station decides to establish an inter-gNB indirect-indirect multi-path for the remote terminal and sends a path addition request message to the second base station.

[0290] Step 6: The second base station generates relevant configurations for the remote terminal to access the second base station, including PC5 configuration, mapping configuration, etc.

[0291] Step 7: The second base station sends an RRC reconfiguration message, which includes relevant configurations for the remote terminal to access the second base station.

[0292] Step 8: The remote terminal sends an SUI to the second base station, including a first local identity request indication, requesting the second base station to allocate a local identity to it.

[0293] Step 9: The second base station allocates a local identifier b and configures it to the remote terminal through an RRC message.

[0294] Note: Local identifier a and local identifier b can be the same or different.

[0295] Example 3 (option 2): Two base stations (or base station CUs) negotiate to allocate a local identifier to a remote terminal.

[0296] FIG10 is a signaling interaction diagram of Example 3 provided in an embodiment of the present disclosure. As shown in FIG10 , the main process includes:

[0297] Step 1: A PC5 connection is established between the remote terminal and the first relay terminal.

[0298] Step 2: The first relay terminal sends an SUI to the first base station. The SUI includes request information, and the request information is used to request the first base station to allocate a local identifier for the remote terminal.

[0299] Step 3: The first base station allocates a local identifier a to the remote terminal and generates relevant configurations for the remote terminal to access the first base station, including PC5 configuration, mapping configuration, etc.

[0300] Step 4: The first base station sends an RRC reconfiguration message to the remote terminal, which includes the local identifier a and the configuration related to the remote terminal accessing the first base station.

[0301] Step 5: The first base station sends an Xn signaling to the second base station, which may indicate a path addition request. The signaling includes a local identifier a and may optionally include a local identifier request indication.

[0302] Step 6: The second base station determines whether the local identifier allocated by the first base station can be used on the second base station side (whether it conflicts with the existing local identifier on the second base station side).

[0303] Step 7a1: The second base station determines that the local identifier a can be used on the second base station side, and the two base stations use the same local identifier for the remote terminal.

[0304] Step 7a2: Optionally, the second base station replies to the first base station, indicating that the second base station can use the local identifier a.

[0305] or,

[0306] Step 7b1: The second base station determines that the local identifier a cannot be used.

[0307] Step 7b2: The second base station allocates a new local identifier b.

[0308] Step 7b3: Optionally, the second base station replies the local identifier b to the first base station.

[0309] Step 7b4: The first base station determines whether the local identifier b allocated by the second base station can be used.

[0310] Step 7b5c1: If the first base station cannot use the local identifier assigned by the second base station, fall back to Option 1a, that is, the first base station and the second base station use different local identifiers. Optionally, the first base station notifies the second base station through interface signaling that the first base station and the second base station cannot use the same local identifier.

[0311] Step 7b5c2: If the first base station can use the local identifier allocated by the second base station, that is, the local identifier allocated by the second base station does not conflict with the local identifier already owned by the first base station, the first base station can choose to use the local identifier allocated by the second base station, or it can choose to fall back to option 1a, that is, allocate local identifiers separately, which depends on the implementation of the first base station.

[0312] Step 8: The second base station configures the remote terminal with relevant configurations for accessing the second base station, including PC5 configuration, mapping configuration, etc. Optionally, the configuration includes a local identifier b allocated by the second base station.

[0313] Example 4 (option 3a): The base station (or base station CU) allocates the local identifier of the remote terminal based on OAM. The first base station obtains the local identifier through OAM.

[0314] FIG11 is a signaling interaction diagram of Example 4 provided in an embodiment of the present disclosure. As shown in FIG11 , the main process includes:

[0315] Step 1: A PC5 connection is established between the remote terminal and the first relay terminal.

[0316] Step 2: The first relay terminal sends an SUI to the first base station. The SUI includes request information, and the request information is used to request the first base station to allocate a local identifier for the remote terminal.

[0317] Step 3: The first base station allocates a local identifier a to the remote terminal and generates relevant configurations for the remote terminal to access the first base station, including PC5 configuration, mapping configuration, etc.

[0318] Step 4: The first base station sends an RRC reconfiguration message to the remote terminal, which includes the local identifier a and the configuration related to the remote terminal accessing the first base station.

[0319] Step 5: The first eNB decides to establish an inter-gNB indirect-indirect multi-path for the remote terminal. The first eNB selects a local identifier c based on the OAM preconfiguration information. Note: Local identifier c can be the same as local identifier a.

[0320] Step 6: The first base station sends a path addition request message carrying the local identifier c.

[0321] Step 7: Optionally, the first base station configures the local identifier c to the remote terminal.

[0322] Step 8: The second base station generates relevant configurations for the remote terminal to access the second base station, including PC5 configuration and mapping-related configurations.

[0323] Step 9: The second base station sends an RRC reconfiguration message, carrying the configuration related to the remote terminal accessing the target base station. If there is no step 7, this step carries the local identifier c configured to the remote terminal.

[0324] Example 5 (option 3b): The base station (or base station CU) allocates the local identifier of the remote terminal based on OAM. The second base station obtains the local identifier through OAM.

[0325] FIG12 is a signaling interaction diagram of Example 5 provided in an embodiment of the present disclosure. As shown in FIG12 , the main process includes:

[0326] Step 1: A PC5 connection is established between the remote terminal and the first relay terminal.

[0327] Step 2: The first relay terminal sends an SUI to the first base station. The SUI includes request information, and the request information is used to request the first base station to allocate a local identifier for the remote terminal.

[0328] Step 3: The first base station allocates a local identifier a to the remote terminal and generates relevant configurations for the remote terminal to access the first base station, including PC5 configuration, mapping configuration, etc.

[0329] Step 4: The first base station sends an RRC reconfiguration message to the remote terminal, which includes the local identifier a and the configuration related to the remote terminal accessing the first base station.

[0330] Step 5: The first base station decides to establish an inter-gNB indirect-indirect multi-path for the remote terminal.

[0331] Step 6: The first base station sends a path addition request message to the second base station.

[0332] Step 7: The second base station generates the relevant configuration for the remote terminal to access the second base station, including the PC5 configuration and mapping-related configuration. It also selects the local identifier c based on the OAM pre-configuration information and sends it back to the first base station in a path addition confirmation message. Note: The local identifier c can be the same as the local identifier a.

[0333] Step 8: The second base station sends an RRC reconfiguration message, carrying relevant configurations for the remote terminal to access the second base station and the local identifier c to the remote terminal.

[0334] The methods and devices provided in the various embodiments of the present disclosure are based on the same application concept. Since the methods and devices solve problems based on similar principles, the implementation of the devices and methods can refer to each other, and the repeated parts will not be repeated.

[0335] FIG13 is a schematic structural diagram of a first network device provided in an embodiment of the present disclosure. As shown in FIG13 , the first network device includes a memory 1320 , a transceiver 1310 , and a processor 1300 ; wherein the processor 1300 and the memory 1320 may also be physically arranged separately.

[0336] The memory 1320 is used to store computer programs; the transceiver 1310 is used to send and receive data under the control of the processor 1300.

[0337] Specifically, the transceiver 1310 is configured to receive and send data under the control of the processor 1300 .

[0338] In FIG13 , the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1300 and memory represented by memory 1320. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, all of which are well known in the art and, therefore, are not further described in this disclosure. The bus interface provides an interface. The transceiver 1310 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or the like.

[0339] The processor 1300 is responsible for managing the bus architecture and general processing, and the memory 1320 can store data used by the processor 1300 when performing operations.

[0340] The processor 1300 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0341] The processor 1300 calls the computer program stored in the memory 1320 to execute any of the methods provided in the embodiments of the present disclosure according to the obtained executable instructions, for example: sending first information to the second network device, the first information including a first local identifier request indication and / or a first local identifier allocated by the first network device to the remote terminal; the first local identifier request indication is used to request the second network device to allocate a local identifier to the remote terminal; wherein the remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0342] In some embodiments, sending the first information to the second network device includes:

[0343] A local identifier is allocated to the remote terminal, and a first local identifier request indication is sent to the second network device.

[0344] In some embodiments, when the first information includes the first local identifier, the method further includes:

[0345] A first reply message sent by the second network device is received, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

[0346] In some embodiments, the method further comprises:

[0347] Based on the first reply message, a local identifier for identifying the remote terminal on the first network device side is determined.

[0348] In some embodiments, determining, based on the first reply message, a local identifier on the first network device side for identifying the remote terminal includes:

[0349] If the first network device side cannot use the second local identifier allocated by the second network device to the remote terminal, determining that the first network device side uses the first local identifier to identify the remote terminal;

[0350] If the first network device side can use the second local identifier allocated by the second network device to the remote terminal, it is determined that the first network device side uses the second local identifier to identify the remote terminal, or it is determined that the first network device side uses the first local identifier to identify the remote terminal.

[0351] In some embodiments, the method further comprises:

[0352] When it is determined that the first network device side uses the first local identifier to identify the remote terminal, first indication information is sent to the second network device, where the first indication information is used to instruct the first network device side not to use the second local identifier to identify the remote terminal.

[0353] In some embodiments, when the first information includes the first local identifier, the method further includes:

[0354] A second reply message sent by the second network device is received, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device to use the first local identifier to identify the remote terminal.

[0355] In some embodiments, sending the first information to the second network device includes:

[0356] Determining a first local identifier allocated to the remote terminal based on the operation management and maintenance (OAM) pre-configuration information;

[0357] The first local identifier is sent to the second network device.

[0358] In some embodiments, before sending the first information to the second network device, the method further includes:

[0359] A second local identity request indication sent by the second network device is received, where the second local identity request indication is used to request the first network device to allocate a local identity to the remote terminal.

[0360] FIG14 is a schematic structural diagram of a second network device provided in an embodiment of the present disclosure. As shown in FIG14 , the second network device includes a memory 1420 , a transceiver 1410 , and a processor 1400 ; wherein the processor 1400 and the memory 1420 may also be physically arranged separately.

[0361] The memory 1420 is used to store computer programs; the transceiver 1410 is used to send and receive data under the control of the processor 1400.

[0362] Specifically, the transceiver 1410 is used to receive and send data under the control of the processor 1400 .

[0363] In FIG14 , the bus architecture may include any number of interconnected buses and bridges, specifically linking together various circuits of one or more processors represented by processor 1400 and memory represented by memory 1420. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described in this disclosure. The bus interface provides an interface. The transceiver 1410 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices over a transmission medium, such as a wireless channel, a wired channel, an optical cable, or the like.

[0364] The processor 1400 is responsible for managing the bus architecture and general processing, and the memory 1420 can store data used by the processor 1400 when performing operations.

[0365] The processor 1400 may be a CPU, an ASIC, an FPGA, or a CPLD, and the processor may also adopt a multi-core architecture.

[0366] The processor 1400 calls the computer program stored in the memory 1420 to execute any of the methods provided in the embodiments of the present disclosure according to the obtained executable instructions, for example: receiving first information, the first information including a first local identifier request indication and / or a first local identifier allocated by the first network device to the remote terminal; the first local identifier request indication is used to request the second network device to allocate a local identifier to the remote terminal; based on the first information, a local identifier is allocated to the remote terminal; wherein the remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0367] In some embodiments, receiving the first information includes:

[0368] receiving first information sent by a first network device, where the first information includes a first local identity request indication and / or a first local identity; or,

[0369] First information sent by a remote terminal is received, where the first information includes a first local identity request indication.

[0370] In some embodiments, allocating a local identifier to the remote terminal based on the first information includes:

[0371] When the first information includes the first local identifier and it is determined that the first local identifier cannot be used on the second network device side, a second local identifier is allocated to the remote terminal.

[0372] In some embodiments, the method further comprises:

[0373] A first reply message is sent to the first network device, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

[0374] In some embodiments, allocating a local identifier to the remote terminal based on the first information includes:

[0375] When the first information includes the first local identifier and it is determined that the first local identifier can be used on the second network device side, it is determined that the second network device side uses the first local identifier to identify the remote terminal.

[0376] In some embodiments, the method further comprises:

[0377] A second reply message is sent to the first network device, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device to use the first local identifier to identify the remote terminal.

[0378] In some embodiments, before receiving the first information sent by the first network device, the method further includes:

[0379] A second local identity request indication is sent to the first network device, where the second local identity request indication is used to request the first network device to allocate a local identity to the remote terminal.

[0380] FIG15 is a schematic structural diagram of a remote terminal provided in an embodiment of the present disclosure. As shown in FIG15 , the remote terminal includes a memory 1520 , a transceiver 1510 , and a processor 1500 ; wherein the processor 1500 and the memory 1520 may also be physically arranged separately.

[0381] The memory 1520 is used to store computer programs; the transceiver 1510 is used to send and receive data under the control of the processor 1500.

[0382] Specifically, the transceiver 1510 is used to receive and send data under the control of the processor 1500 .

[0383] In FIG15 , the bus architecture may include any number of interconnected buses and bridges, specifically various circuits of one or more processors represented by processor 1500 and memory represented by memory 1520. The bus architecture may also link together various other circuits such as peripheral devices, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described in this disclosure. The bus interface provides an interface. The transceiver 1510 may be a plurality of components, i.e., a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, such as a wireless channel, a wired channel, an optical cable, and the like. For different user devices, the user interface 1530 may also be an interface capable of connecting external or internal devices as required, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0384] The processor 1500 is responsible for managing the bus architecture and general processing, and the memory 1520 can store data used by the processor 1500 when performing operations.

[0385] The processor 1500 may be a CPU, an ASIC, an FPGA, or a CPLD, and the processor may also adopt a multi-core architecture.

[0386] The processor 1500 calls the computer program stored in the memory 1520 to execute any of the methods provided in the embodiments of the present disclosure according to the obtained executable instructions, for example: sending a first local identification request indication to the second network device, where the first local identification request indication is used to request the second network device to assign a local identification to the remote terminal; wherein the remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0387] It should be noted here that the above-mentioned first network device, second network device and remote terminal provided in the embodiment of the present disclosure 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.

[0388] FIG16 is a schematic diagram of a structure of a device for allocating a local identifier according to an embodiment of the present disclosure. As shown in FIG16 , the device includes:

[0389] The first sending unit 1600 is configured to send first information to the second network device, where the first information includes a first local identity request indication and / or a first local identity allocated by the first network device to the remote terminal; the first local identity request indication is used to request the second network device to allocate a local identity to the remote terminal;

[0390] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0391] In some embodiments, sending the first information to the second network device includes:

[0392] A local identifier is allocated to the remote terminal, and a first local identifier request indication is sent to the second network device.

[0393] In some embodiments, the apparatus further comprises:

[0394] The first receiving unit is configured to receive a first reply message sent by the second network device when the first information includes the first local identifier, where the first reply message includes the second local identifier allocated by the second network device to the remote terminal.

[0395] In some embodiments, the apparatus further comprises:

[0396] The first determining unit is configured to determine, based on the first reply message, a local identifier on the first network device side for identifying the remote terminal.

[0397] In some embodiments, determining, based on the first reply message, a local identifier on the first network device side for identifying the remote terminal includes:

[0398] If the first network device side cannot use the second local identifier allocated by the second network device to the remote terminal, determining that the first network device side uses the first local identifier to identify the remote terminal;

[0399] If the first network device side can use the second local identifier allocated by the second network device to the remote terminal, it is determined that the first network device side uses the second local identifier to identify the remote terminal, or it is determined that the first network device side uses the first local identifier to identify the remote terminal.

[0400] In some embodiments, the first sending unit 1600 is further configured to:

[0401] When it is determined that the first network device side uses the first local identifier to identify the remote terminal, first indication information is sent to the second network device, where the first indication information is used to instruct the first network device side not to use the second local identifier to identify the remote terminal.

[0402] In some embodiments, the apparatus further comprises:

[0403] The second receiving unit is used to receive a second reply message sent by the second network device when the first information includes the first local identifier, and the second reply message includes second indication information, and the second indication information is used to instruct the second network device side to use the first local identifier to identify the remote terminal.

[0404] In some embodiments, sending the first information to the second network device includes:

[0405] Determining a first local identifier allocated to the remote terminal based on the operation management and maintenance (OAM) pre-configuration information;

[0406] The first local identifier is sent to the second network device.

[0407] In some embodiments, the apparatus further comprises:

[0408] The third receiving unit is configured to receive a second local identity request indication sent by the second network device before sending the first information to the second network device, where the second local identity request indication is used to request the first network device to allocate a local identity to the remote terminal.

[0409] FIG17 is a second structural diagram of an apparatus for allocating a local identifier according to an embodiment of the present disclosure. As shown in FIG17 , the apparatus includes:

[0410] The fourth receiving unit 1700 is configured to receive first information, where the first information includes a first local identity request indication and / or a first local identity allocated by the first network device to the remote terminal; the first local identity request indication is used to request the second network device to allocate a local identity to the remote terminal;

[0411] The allocating unit 1710 is configured to allocate a local identifier to the remote terminal based on the first information;

[0412] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0413] In some embodiments, receiving the first information includes:

[0414] receiving first information sent by a first network device, where the first information includes a first local identity request indication and / or a first local identity; or,

[0415] First information sent by a remote terminal is received, where the first information includes a first local identity request indication.

[0416] In some embodiments, allocating a local identifier to the remote terminal based on the first information includes:

[0417] When the first information includes the first local identifier and it is determined that the first local identifier cannot be used on the second network device side, a second local identifier is allocated to the remote terminal.

[0418] In some embodiments, the apparatus further comprises:

[0419] The second sending unit is configured to send a first reply message to the first network device, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

[0420] In some embodiments, allocating a local identifier to the remote terminal based on the first information includes:

[0421] When the first information includes the first local identifier and it is determined that the first local identifier can be used on the second network device side, it is determined that the second network device side uses the first local identifier to identify the remote terminal.

[0422] In some embodiments, the apparatus further comprises:

[0423] The third sending unit is used to send a second reply message to the first network device, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device to use the first local identifier to identify the remote terminal.

[0424] In some embodiments, the apparatus further comprises:

[0425] The fourth sending unit is configured to send a second local identifier request indication to the first network device before receiving the first information sent by the first network device, where the second local identifier request indication is used to request the first network device to allocate a local identifier to the remote terminal.

[0426] FIG18 is a third structural diagram of an apparatus for allocating a local identifier according to an embodiment of the present disclosure. As shown in FIG18 , the apparatus includes:

[0427] The fifth sending unit 1800 is configured to send a first local identity request indication to the second network device, where the first local identity request indication is used to request the second network device to allocate a local identity to the remote terminal;

[0428] The remote terminal communicates with the first network device and / or the second network device through the relay terminal.

[0429] It should be noted that the division of units in the embodiments of the present disclosure 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 disclosure 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.

[0430] 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 disclosure is essentially 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, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present disclosure. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0431] It should be noted here that the above-mentioned device provided in the embodiment of the present disclosure 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.

[0432] On the other hand, an embodiment of the present disclosure further provides a non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a computer program, and the computer program is used to enable a processor to execute the method for allocating a local identifier provided by the above embodiments.

[0433] It should be noted here that the non-transitory readable storage medium provided in the embodiment of the present disclosure 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.

[0434] The non-transitory readable storage medium can be any available medium or data storage device that can be accessed by a computer, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid-state drives (SSDs)), etc.

[0435] The technical solution provided by the embodiment of the present disclosure can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new air interface (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

[0436] The terminal involved in the embodiments of the present disclosure may be a device that provides voice and / or data connectivity to a user, a handheld device with wireless connection function, or other processing devices connected to a wireless modem. In different systems, the name of the terminal may also be different. For example, in a 5G system, the terminal may be called User Equipment (UE). A wireless terminal device can communicate with one or more core networks (CN) via a radio access network (RAN). The wireless terminal device may be a mobile terminal device, such as a mobile phone (or "cellular" phone) and a computer with a mobile terminal device. For example, it may be a portable, pocket-sized, handheld, computer-built-in or vehicle-mounted mobile device that exchanges voice and / or data with a radio access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), and other devices. The wireless terminal device may also be referred to as a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, a remote terminal device, an access terminal device, a user terminal device, a user agent, or a user device, but is not limited in the embodiments of the present disclosure.

[0437] The network device involved in the embodiments of the present disclosure may be a base station, which may include multiple cells providing services to terminals. Depending on the specific application scenario, the base station may also be called an access point, or may be a device in an access network that communicates with a wireless terminal device through one or more sectors on an air interface, or may be called another name. The network device may be used to interchange received air frames with Internet Protocol (IP) packets, acting as a router between the wireless terminal device and the rest of the access network, wherein the rest of the access network may include an Internet Protocol (IP) communication network. The network device may also coordinate the attribute management of the air interface. For example, the network device involved in the embodiments of the present disclosure may be a base transceiver station (BTS) in the Global System for Mobile communications (GSM) or code division multiple access (CDMA), a network device (NodeB) in wide-band code division multiple access (WCDMA), an evolutionary Node B (eNB or e-NodeB) in the long term evolution (LTE) system, a 5G base station (gNB) in the 5G network architecture (next generation system), a home evolved Node B (HeNB), a relay node, a femto, a pico, etc., and is not limited in the embodiments of the present disclosure. In some network structures, the network device may include a centralized unit (CU) node and a distributed unit (DU) node, and the centralized unit and the distributed unit may also be geographically separated.

[0438] Network devices and terminals can each use one or more antennas for Multiple Input Multiple Output (MIMO) transmission. MIMO transmission can be single-user MIMO (SU-MIMO) or multi-user MIMO (MU-MIMO). Depending on the configuration and number of antenna combinations, MIMO transmission can be 2D-MIMO, 3D-MIMO, FD-MIMO, or massive-MIMO. It can also use diversity transmission, precoding transmission, or beamforming transmission.

[0439] Those skilled in the art will appreciate that the embodiments of the present disclosure may be provided as methods, systems, or computer program products. Therefore, the present disclosure may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Furthermore, the present disclosure may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage and optical storage, etc.) containing computer-usable program code.

[0440] The present disclosure is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present disclosure. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer-executable instructions. These computer-executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0441] These processor-executable instructions may also be stored in a processor-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0442] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0443] Obviously, those skilled in the art may make various changes and modifications to the present disclosure without departing from the spirit and scope of the present disclosure. Thus, if these modifications and variations of the present disclosure fall within the scope of the claims of the present disclosure and their equivalents, the present disclosure is intended to include such modifications and variations.

Claims

1. A method for allocating a local identifier, applied to a first network device, comprising: Sending first information to a second network device, wherein the first information includes a first local identifier request indication and / or a first local identifier allocated by the first network device to a remote terminal; the first local identifier request indication is used to request the second network device to allocate a local identifier to the remote terminal; Wherein, the remote terminal communicates with the first network device and / or the second network device through a relay terminal.

2. The method for allocating a local identifier according to claim 1, wherein: The sending the first information to the second network device includes: A local identifier is allocated to the remote terminal, and the first local identifier request indication is sent to the second network device.

3. The method for allocating a local identifier according to claim 1, wherein: In the case where the first information includes the first local identifier, the method further includes: A first reply message sent by the second network device is received, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

4. The method for allocating a local identifier according to claim 3, wherein: The method further comprises: Based on the first reply message, a local identifier for identifying the remote terminal on the first network device side is determined.

5. The method for allocating a local identifier according to claim 4, wherein: The determining, based on the first reply message, a local identifier for identifying the remote terminal on the first network device side includes: If the first network device side cannot use the second local identifier assigned by the second network device to the remote terminal, determining that the first network device side uses the first local identifier to identify the remote terminal; If the first network device side can use the second local identifier assigned to the remote terminal by the second network device, it is determined that the first network device side uses the second local identifier to identify the remote terminal, or it is determined that the first network device side uses the first local identifier to identify the remote terminal.

6. The method for allocating a local identifier according to claim 4 or 5, wherein: The method further comprises: When it is determined that the first network device side uses the first local identifier to identify the remote terminal, first indication information is sent to the second network device, where the first indication information is used to instruct the first network device side not to use the second local identifier to identify the remote terminal.

7. The method for allocating a local identifier according to claim 1, wherein: In the case where the first information includes the first local identifier, the method further includes: A second reply message sent by the second network device is received, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device side to use the first local identifier to identify the remote terminal.

8. The method for allocating a local identifier according to claim 1, wherein: The sending the first information to the second network device includes: Determine a first local identifier assigned to the remote terminal based on the operation management and maintenance (OAM) pre-configuration information; The first local identifier is sent to the second network device.

9. The method for allocating a local identifier according to claim 8, wherein: Before sending the first information to the second network device, the method further includes: A second local identifier request indication sent by the second network device is received, where the second local identifier request indication is used to request the first network device to allocate a local identifier to the remote terminal.

10. A method for allocating a local identifier, applied to a second network device, comprising: Receive first information, wherein the first information includes a first local identifier request indication and / or a first local identifier allocated by the first network device to the remote terminal; The first local identifier request indication is used to request the second network device to allocate a local identifier to the remote terminal; Based on the first information, assigning a local identifier to the remote terminal; Wherein, the remote terminal communicates with the first network device and / or the second network device through a relay terminal.

11. The method for allocating a local identifier according to claim 10, wherein: The receiving of the first information comprises: Receive first information sent by the first network device, the first information including the first local identification request indication and / or the first local identification; or, Receive first information sent by the remote terminal, where the first information includes the first local identity request indication.

12. The method for allocating a local identifier according to claim 10 or 11, wherein: The allocating a local identifier to the remote terminal based on the first information includes: When the first information includes the first local identifier and it is determined that the first local identifier cannot be used on the second network device side, a second local identifier is allocated to the remote terminal.

13. The method for allocating a local identifier according to claim 12, wherein: The method further comprises: A first reply message is sent to the first network device, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

14. The method for allocating a local identifier according to claim 10 or 11, wherein: The allocating a local identifier to the remote terminal based on the first information includes: When the first information includes the first local identifier and it is determined that the first local identifier can be used on the second network device side, it is determined that the second network device side uses the first local identifier to identify the remote terminal.

15. The method for allocating a local identifier according to claim 14, wherein: The method further comprises: A second reply message is sent to the first network device, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device side to use the first local identifier to identify the remote terminal.

16. The method for allocating a local identifier according to claim 11, wherein: Before receiving the first information sent by the first network device, the method further includes: A second local identifier request indication is sent to the first network device, where the second local identifier request indication is used to request the first network device to allocate a local identifier to the remote terminal.

17. A first network device, comprising a memory, a transceiver, and a 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: Sending first information to a second network device, wherein the first information includes a first local identifier request indication and / or a first local identifier allocated by the first network device to a remote terminal; the first local identifier request indication is used to request the second network device to allocate a local identifier to the remote terminal; Wherein, the remote terminal communicates with the first network device and / or the second network device through a relay terminal.

18. The first network device according to claim 17, wherein: The sending the first information to the second network device includes: A local identifier is allocated to the remote terminal, and the first local identifier request indication is sent to the second network device.

19. The first network device according to claim 17, wherein: In a case where the first information includes the first local identifier, the operation further includes: A first reply message sent by the second network device is received, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

20. The first network device according to claim 19, wherein: The operations also include: Based on the first reply message, a local identifier for identifying the remote terminal on the first network device side is determined.

21. The first network device according to claim 20, wherein: The determining, based on the first reply message, a local identifier for identifying the remote terminal on the first network device side includes: If the first network device side cannot use the second local identifier assigned by the second network device to the remote terminal, determining that the first network device side uses the first local identifier to identify the remote terminal; If the first network device side can use the second local identifier assigned to the remote terminal by the second network device, it is determined that the first network device side uses the second local identifier to identify the remote terminal, or it is determined that the first network device side uses the first local identifier to identify the remote terminal.

22. The first network device according to claim 20 or 21, wherein: The operations also include: In determining that the first network device uses the first local identifier to identify the remote terminal In this case, first indication information is sent to the second network device, where the first indication information is used to instruct the first network device side not to use the second local identifier to identify the remote terminal.

23. The first network device according to claim 17, wherein: In a case where the first information includes the first local identifier, the operation further includes: A second reply message sent by the second network device is received, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device side to use the first local identifier to identify the remote terminal.

24. The first network device according to claim 17, wherein: The sending the first information to the second network device includes: Determine a first local identifier assigned to the remote terminal based on the operation management and maintenance (OAM) pre-configuration information; The first local identifier is sent to the second network device.

25. The first network device according to claim 24, wherein: Before sending the first information to the second network device, the operation further includes: A second local identifier request indication sent by the second network device is received, where the second local identifier request indication is used to request the first network device to allocate a local identifier to the remote terminal.

26. A second network device comprising a memory, a transceiver, and a processor; Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is configured to read the computer program in the memory and perform the following operations: Receive first information, wherein the first information includes a first local identifier request indication and / or a first local identifier allocated by the first network device to the remote terminal; the first local identifier request indication is used to request the second network device to allocate a local identifier to the remote terminal; Based on the first information, assigning a local identifier to the remote terminal; Wherein, the remote terminal communicates with the first network device and / or the second network device through a relay terminal.

27. The second network device according to claim 26, wherein: The receiving of the first information comprises: Receive first information sent by the first network device, the first information including the first local identification request indication and / or the first local identification; or, Receive first information sent by the remote terminal, where the first information includes the first local identity request indication.

28. The second network device according to claim 26 or 27, wherein: The allocating a local identifier to the remote terminal based on the first information includes: When the first information includes the first local identifier and it is determined that the first local identifier cannot be used on the second network device side, a second local identifier is allocated to the remote terminal.

29. The second network device according to claim 28, wherein: The operations also include: A first reply message is sent to the first network device, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

30. The second network device according to claim 26 or 27, wherein: The allocating a local identifier to the remote terminal based on the first information includes: When the first information includes the first local identifier and it is determined that the first local identifier can be used on the second network device side, it is determined that the second network device side uses the first local identifier to identify the remote terminal.

31. The second network device according to claim 30, wherein: The operations also include: A second reply message is sent to the first network device, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device side to use the first local identifier to identify the remote terminal.

32. The second network device according to claim 27, wherein: Before receiving the first information sent by the first network device, the operation further includes: A second local identifier request indication is sent to the first network device, where the second local identifier request indication is used to request the first network device to allocate a local identifier to the remote terminal.

33. A device for allocating a local identifier, comprising: A first sending unit, configured to send first information to a second network device, wherein the first information includes a first local identifier request indication and / or a first local identifier allocated by the first network device to a remote terminal; the first local identifier request indication is used to request the second network device to allocate a local identifier to the remote terminal; Wherein, the remote terminal communicates with the first network device and / or the second network device through a relay terminal.

34. The apparatus for allocating a local identifier according to claim 33, wherein: The sending the first information to the second network device includes: A local identifier is allocated to the remote terminal, and the first local identifier request indication is sent to the second network device.

35. The apparatus for allocating a local identifier according to claim 33, wherein: The device also includes: The first receiving unit is configured to receive a first reply message sent by the second network device when the first information includes the first local identifier, wherein the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

36. The apparatus for allocating a local identifier according to claim 35, wherein: The device also includes: The first determining unit is used to determine, based on the first reply message, a local identifier on the first network device side for identifying the remote terminal.

37. The apparatus for allocating a local identifier according to claim 36, wherein: The determining, based on the first reply message, a local identifier for identifying the remote terminal on the first network device side includes: If the first network device side cannot use the second local identifier assigned by the second network device to the remote terminal, determining that the first network device side uses the first local identifier to identify the remote terminal; If the first network device side can use the second local identifier assigned to the remote terminal by the second network device, it is determined that the first network device side uses the second local identifier to identify the remote terminal, or it is determined that the first network device side uses the first local identifier to identify the remote terminal.

38. The apparatus for allocating a local identifier according to claim 36 or 37, wherein: The first sending unit is further used for: In determining that the first network device uses the first local identifier to identify the remote terminal In this case, first indication information is sent to the second network device, where the first indication information is used to instruct the first network device side not to use the second local identifier to identify the remote terminal.

39. The apparatus for allocating a local identifier according to claim 33, wherein: The device also includes: A second receiving unit is used to receive a second reply message sent by the second network device when the first information includes the first local identifier, and the second reply message includes second indication information, and the second indication information is used to instruct the second network device side to use the first local identifier to identify the remote terminal.

40. The apparatus for allocating a local identifier according to claim 33, wherein: The sending the first information to the second network device includes: Determine a first local identifier assigned to the remote terminal based on the operation management and maintenance (OAM) pre-configuration information; The first local identifier is sent to the second network device.

41. The apparatus for allocating a local identifier according to claim 40, wherein: The device also includes: The third receiving unit is used to receive a second local identifier request indication sent by the second network device before sending the first information to the second network device, where the second local identifier request indication is used to request the first network device to allocate a local identifier for the remote terminal.

42. An apparatus for allocating a local identifier, comprising: A fourth receiving unit, configured to receive first information, wherein the first information includes a first local identifier request indication and / or a first local identifier allocated by the first network device to the remote terminal; the first local identifier request indication is used to request the second network device to allocate a local identifier to the remote terminal; an allocating unit, configured to allocate a local identifier to the remote terminal based on the first information; Wherein, the remote terminal communicates with the first network device and / or the second network device through a relay terminal.

43. The apparatus for allocating a local identifier according to claim 42, wherein: The receiving of the first information comprises: Receive first information sent by the first network device, the first information including the first local identification request indication and / or the first local identification; or, Receive first information sent by the remote terminal, where the first information includes the first local identity request indication.

44. The apparatus for allocating a local identifier according to claim 42 or 43, wherein: The allocating a local identifier to the remote terminal based on the first information includes: When the first information includes the first local identifier and it is determined that the first local identifier cannot be used on the second network device side, a second local identifier is allocated to the remote terminal.

45. The apparatus for allocating a local identifier according to claim 44, wherein: The device also includes: The second sending unit is used to send a first reply message to the first network device, where the first reply message includes a second local identifier allocated by the second network device to the remote terminal.

46. ​​The apparatus for allocating a local identifier according to claim 42 or 43, wherein: The allocating a local identifier to the remote terminal based on the first information includes: When the first information includes the first local identifier and it is determined that the first local identifier can be used on the second network device side, it is determined that the second network device side uses the first local identifier to identify the remote terminal.

47. The apparatus for allocating a local identifier according to claim 46, wherein: The device also includes: The third sending unit is used to send a second reply message to the first network device, where the second reply message includes second indication information, and the second indication information is used to instruct the second network device side to use the first local identifier to identify the remote terminal.

48. The apparatus for allocating a local identifier according to claim 43, wherein: The device also includes: The fourth sending unit is used to send a second local identifier request indication to the first network device before receiving the first information sent by the first network device, wherein the second local identifier request indication is used to request the first network device to allocate a local identifier to the remote terminal.

49. A non-transitory readable storage medium storing a computer program, wherein the computer program is used to cause a processor to execute the method according to any one of claims 1 to 9, or to execute the method according to any one of claims 10 to 16.

Images