Method, apparatus and system for multi-path configuration

Abstract

This application provides a multipath configuration method, apparatus, and system for providing a process for a remote UE to establish multiple paths from a single path. The method includes: a first terminal device receiving a first message from a network device through a first path; wherein the first message instructs the first terminal device to establish a second path between the first terminal device and the network device, the second path being different from the first path; the first terminal device using the first message to establish the second path in a second cell; and the first terminal device maintaining a Media Access Control (MAC) entity, the MAC entity being used for communication between the first terminal device and the network device through a direct path in either the first or second path.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to multipath configuration methods, apparatus and systems. Background Technology

[0002] In carrier aggregation (CA) technology, multiple component carriers (CCs) can be aggregated for use by user equipment (UE) to increase communication bandwidth. The UE and base station have only one radio resource control (RRC) connection, but the base station can configure a primary cell (PCell) and one or more secondary cells (SCells) for the UE.

[0003] When a remote UE adds a path to the base station, for example, if the remote UE has already established an indirect path with the base station through a relay UE and needs to configure a direct path between the remote UE and the base station, if the existing CA configuration procedure is used to configure the PCell, then although the RRC message sent by the base station to the relay UE carries synchronization reconfiguration parameters, these synchronization reconfiguration parameters can only be used for the remote UE to perform cell handover. That is, these synchronization reconfiguration parameters can only be used for the remote UE to handover from the first cell accessed in the indirect path to the second cell to be accessed in the direct path, and cannot be used for the remote UE to access both the first and second cells at the same time. In other words, the remote UE cannot maintain both the indirect and direct paths with the base station at the same time. Summary of the Invention

[0004] This application provides a multipath configuration method, apparatus, and system for providing a process for a remote UE to establish multiple paths from a single path.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, a multipath configuration method is provided. The apparatus executing this multipath configuration method can be a first terminal device, or a module applied in the first terminal device, such as a chip or chip system. The following description uses the first terminal device as the executing entity. The first terminal device receives a first message from a network device through a first path; wherein the first message instructs the first terminal device to establish a second path between the first terminal device and the network device, the second path being different from the first path; the first terminal device uses the first message to establish the second path in a second cell; the first terminal device maintains a Media Access Control (MAC) entity, which is used for communication between the first terminal device and the network device through the first path or a directly connected path in the second path.

[0007] In this embodiment of the application, since the first message can instruct the first terminal device to establish a second path between the first terminal device and the network device, the first terminal device can also establish a second path different from the first path after the first path is established, so as to achieve the purpose of the first terminal device communicating with the network device through multiple paths, namely the first path and the second path.

[0008] In conjunction with the first aspect described above, in one possible implementation, the first message includes a second identifier of the first terminal device, which is the identifier of the first terminal device within the second cell to which the first terminal device is to access in the second path. Before the first terminal device receives the first message from the network device through the first path, the method further includes: the first terminal device receiving and storing the first identifier of the first terminal device from the network device through the first path, where the first identifier of the first terminal device is the identifier of the first terminal device within the first cell to which the first terminal device is accessed in the first path. After the first terminal device receives the first message from the network device through the first path, the method further includes: the first terminal device updating the stored first identifier of the first terminal device to the second identifier of the first terminal device; or, the first terminal device storing the second identifier of the first terminal device. In this scheme, the first terminal device only stores the most recently received second identifier of the first terminal device, which can effectively save the storage resources of the first terminal device. The first terminal device stores both a first identifier and a second identifier, so that the first identifier can be used when transmitting data via the first path and the second identifier can be used when transmitting data via the second path, making it easier to distinguish between them.

[0009] In conjunction with the first aspect described above, in one possible implementation, the first message includes a second identifier of the first terminal device and an identifier of the second cell to which the first terminal device is to access in the second path. The second identifier of the first terminal device is the identifier of the first terminal device within the second cell to which the first terminal device is to access in the second path. Before the first terminal device receives the first message from the network device through the first path, the method further includes: the first terminal device receiving and storing the first identifier of the first terminal device from the network device through the first path. The first identifier of the first terminal device is the identifier of the first terminal device within the first cell to which the first terminal device is accessed in the first path. After the first terminal device receives the first message from the network device through the first path, the method further includes: if the identifier of the second cell is the same as the identifier of the first cell, the first terminal device updates the stored first identifier of the first terminal device to the second identifier of the first terminal device; if the identifier of the second cell is different from the identifier of the first cell, the first terminal device stores the second identifier of the first terminal device. If the first cell and the second cell are the same cell, the first terminal device only stores the most recently received second identifier of the first terminal device, which can effectively save the storage resources of the first terminal device. If the first cell and the second cell are different cells, the first terminal device stores both the first identifier and the second identifier of the first terminal device, so that the first identifier is used when transmitting data through the first path and the second identifier is used when transmitting data through the second path, making it easier to distinguish.

[0010] In conjunction with the first aspect mentioned above, in one possible implementation, the first path is a non-directly connected path, and the second path is a directly connected path.

[0011] In conjunction with the first aspect described above, in one possible implementation, the first path is a direct path, and the second path is a non-direct path. The first message includes the identifier of the second terminal device, but does not include the second identifier of the first terminal device. The second identifier of the first terminal device is the identifier of the first terminal device within the second cell to which the first terminal device is to access in the second path. The second terminal device is a relay device between the first terminal device and the network device. The first terminal device uses the first message to establish the second path, including: the first terminal device uses the identifier of the second terminal device in the first message to establish a sidelink (SL) connection with the second terminal device. Since the first message does not include the second identifier of the first terminal device, the first terminal device only needs to store one identifier of the first terminal device, i.e., the first identifier of the first terminal device, to achieve the establishment of multiple paths.

[0012] In conjunction with the first aspect described above, in one possible implementation, after the first terminal device establishes the second path, the method further includes: the first terminal device determining the primary cell it accesses, wherein the primary cell is a special cell on the target path. In this scheme, the determined primary cell can be used by the first terminal device to uniquely identify the first terminal device within the primary cell, and this identifier can be used for RRC reconstruction or cell handover.

[0013] In conjunction with the first aspect above, in one possible implementation, the target path is the first path; the target path is a direct path between the first path and the second path; the target path is a non-direct path between the first path and the second path; or, the target path is a path randomly selected by the first terminal device from the first path and the second path.

[0014] In conjunction with the first aspect above, in one possible implementation, if the network device does not configure a separate SRB for the signaling radio bearer SRB, the target path is the path where the SRB is located.

[0015] In conjunction with the first aspect above, in one possible implementation, when the network device is configured to separate and replicate SRBs, the target path is the first path; the target path is a directly connected path between the first path and the second path; the target path is a non-directly connected path between the first path and the second path; or, the target path is a path randomly selected by the first terminal device from the first path and the second path.

[0016] In conjunction with the first aspect above, in one possible implementation, when the network device configures a separate SRB but not a replicated SRB, the target path is the path where the primary radio link control (RLC) entity is located.

[0017] In conjunction with the first aspect above, in one possible implementation, when the target path is the first path, the primary cell is the first cell; when the target path is the second path, the primary cell is the second cell.

[0018] In conjunction with the first aspect above, in one possible implementation, after the first terminal device establishes the second path, the method further includes: the first terminal device determining the main path.

[0019] In conjunction with the first aspect above, in one possible implementation, the main path is a first path; the main path is a directly connected path between the first path and the second path; the main path is a non-directly connected path between the first path and the second path; or, the main path is a path randomly selected by the first terminal device from the first path and the second path.

[0020] In conjunction with the first aspect above, in one possible implementation, if the network device does not configure a separate SRB for the SRB, the primary path is the path where the SRB is located.

[0021] In conjunction with the first aspect above, in one possible implementation, when the network device is configured to separate and replicate SRBs, the main path is the first path; the main path is a directly connected path between the first path and the second path; the main path is a non-directly connected path between the first path and the second path; or, the main path is a path randomly selected by the first terminal device from the first path and the second path.

[0022] In conjunction with the first aspect above, in one possible implementation, when the network device is configured to separate the SRB but not to replicate the SRB, the primary path is the path where the primary RLC entity resides.

[0023] Secondly, a first terminal device is provided for implementing the above-described method. This first terminal device includes modules, units, or means corresponding to the implementation of the above-described method. These modules, units, or means can be implemented in hardware, software, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-described functions.

[0024] In conjunction with the second aspect above, in one possible implementation, the first terminal device includes: a transceiver module and a processing module; the transceiver module is configured to receive a first message from a network device via a first path; wherein the first message is configured to instruct the first terminal device to establish a second path between the first terminal device and the network device, the second path being different from the first path; the transceiver module is further configured to use the first message to establish the second path in a second cell; the processing module is configured to maintain a Media Access Control (MAC) entity, the MAC entity being used for communication between the first terminal device and the network device via a direct path in the first path or the second path.

[0025] In conjunction with the second aspect described above, in one possible implementation, the first terminal device further includes a storage module; the first message includes a second identifier of the first terminal device, the second identifier of the first terminal device being the identifier of the first terminal device within the second cell to which the first terminal device is to be accessed in the second path; the transceiver module is further configured to receive a first identifier of the first terminal device from the network device through the first path, the first identifier of the first terminal device being the identifier of the first terminal device within the first cell to which the first terminal device is accessed in the first path; the storage module is configured to store the first identifier of the first terminal device; the processing module is further configured to update the first identifier of the first terminal device stored in the storage module to the second identifier of the first terminal device; or, the storage module is further configured to store the second identifier of the first terminal device.

[0026] In conjunction with the second aspect described above, in one possible implementation, the first terminal device further includes: a storage module; the first message includes a second identifier of the first terminal device and an identifier of a second cell to be accessed by the first terminal device in the second path, wherein the second identifier of the first terminal device is the identifier of the first terminal device within the second cell to be accessed by the first terminal device in the second path; the transceiver module is further configured to receive a first identifier of the first terminal device from the network device through the first path, wherein the first identifier of the first terminal device is the identifier of the first terminal device within the first cell to be accessed by the first terminal device in the first path; the storage module is configured to store the first identifier of the first terminal device; the processing module is further configured to update the stored first identifier of the first terminal device to the second identifier of the first terminal device if the identifier of the second cell is the same as the identifier of the first cell; the storage module is further configured to store the second identifier of the first terminal device if the identifier of the second cell is different from the identifier of the first cell.

[0027] In conjunction with the second aspect above, in one possible implementation, the first path is a non-directly connected path, and the second path is a directly connected path.

[0028] In conjunction with the second aspect above, in one possible implementation, the first path is a direct path, and the second path is a non-direct path; the first message includes the identifier of the second terminal device, but does not include the second identifier of the first terminal device, where the second identifier of the first terminal device is the identifier of the first terminal device within the second cell to which the first terminal device is to be accessed in the second path, and the second terminal device is a relay device between the first terminal device and the network device; the transceiver module is further configured to establish the second path in the second cell using the first message, including: using the identifier of the second terminal device in the first message to establish a sidelink (SL) connection with the second terminal device.

[0029] In conjunction with the second aspect above, in one possible implementation, the processing module is further configured to determine the primary cell accessed by the first terminal device, wherein the primary cell is a special cell on the target path.

[0030] In conjunction with the second aspect above, in one possible implementation, the target path is the first path; the target path is a direct path between the first path and the second path; the target path is a non-direct path between the first path and the second path; or, the target path is a path randomly selected by the first terminal device from the first path and the second path.

[0031] In conjunction with the second aspect above, in one possible implementation, if the network device does not configure a separate SRB for the signaling radio bearer SRB, the target path is the path where the SRB is located.

[0032] In conjunction with the second aspect above, in one possible implementation, when the network device is configured to separate and replicate SRBs, the target path is the first path; the target path is a directly connected path between the first path and the second path; the target path is a non-directly connected path between the first path and the second path; or, the target path is a path randomly selected by the first terminal device from the first path and the second path.

[0033] In conjunction with the second aspect above, in one possible implementation, when the network device configures a separate SRB but not a replicated SRB, the target path is the path where the primary radio link control (RLC) entity is located.

[0034] In conjunction with the second aspect above, in one possible implementation, when the target path is the first path, the primary cell is the first cell; when the target path is the second path, the primary cell is the second cell.

[0035] In conjunction with the second aspect mentioned above, in one possible implementation, the processing module is also used to determine the main path.

[0036] In conjunction with the second aspect above, in one possible implementation, the main path is a first path; the main path is a directly connected path between the first path and the second path; the main path is a non-directly connected path between the first path and the second path; or, the main path is a path randomly selected by the first terminal device from the first path and the second path.

[0037] In conjunction with the second aspect above, in one possible implementation, if the network device does not configure a separate SRB for the SRB, the primary path is the path where the SRB is located.

[0038] In conjunction with the second aspect above, in one possible implementation, when the network device is configured to separate and replicate SRBs, the main path is the first path; the main path is a directly connected path between the first path and the second path; the main path is a non-directly connected path between the first path and the second path; or, the main path is a path randomly selected by the first terminal device from the first path and the second path.

[0039] In conjunction with the second aspect above, in one possible implementation, when the network device is configured to separate the SRB but not to replicate the SRB, the primary path is the path where the primary RLC entity resides.

[0040] Thirdly, a communication device is provided, comprising: a processor; the processor being coupled to a memory and, after reading computer instructions stored in the memory, executing the method described in the first aspect above according to the instructions.

[0041] In conjunction with the third aspect above, in one possible implementation, the communication device further includes a memory for storing computer instructions.

[0042] In conjunction with the third aspect described above, in one possible implementation, the communication device further includes a communication interface; this communication interface is used for communication between the communication device and other devices. For example, the communication interface may be a transceiver, an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuitry, etc.

[0043] In conjunction with the third aspect described above, in one possible implementation, the communication device can be a chip or a chip system. When the communication device is a chip system, it can be composed of chips or may include chips and other discrete components.

[0044] In conjunction with the third aspect above, in one possible implementation, when the communication device is a chip or chip system, the aforementioned communication interface can be an input / output interface, interface circuit, output circuit, input circuit, pin, or related circuit on the chip or chip system. The aforementioned processor can also be embodied as a processing circuit or logic circuit.

[0045] Fourthly, a communication system is provided, comprising: a network device, a second terminal device, and a first terminal device for performing the method described in the first aspect; wherein the second terminal device is a relay device between the first terminal device and the network device.

[0046] Fifthly, a computer-readable storage medium is provided that stores instructions which, when executed on a computer, enable the computer to perform the method described in the first aspect.

[0047] The technical effects brought about by the second to fifth aspects can be seen in the technical effects brought about by the different implementation methods in the first aspect above, and will not be repeated here. Attached Figure Description

[0048] Figure 1 This is a schematic diagram of SL communication in the prior art;

[0049] Figure 2 This is a schematic diagram of a multipath relay communication scenario in existing technologies;

[0050] Figure 3A This is a schematic diagram of the protocol stack architecture for communication between a remote UE and a relay UE via SL in the existing technology.

[0051] Figure 3B This is a schematic diagram of the protocol stack architecture for communication between a remote UE and a relay UE via an ideal non-3GPP link in the existing technology.

[0052] Figure 4 This is a schematic diagram illustrating how a base station configures carrier aggregation for a UE in the existing technology.

[0053] Figure 5A This application provides a schematic diagram of the architecture of a communication system.

[0054] Figure 5B This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0055] Figure 6 Schematic diagram of the communication device provided in the embodiments of this application Figure 1 ;

[0056] Figure 7 A flowchart illustrating a multipath configuration method provided in an embodiment of this application;

[0057] Figure 8 A flowchart illustrating a specific example of a multipath configuration method provided in this application embodiment;

[0058] Figure 9 A flowchart illustrating another specific example of a multipath configuration method provided in this application embodiment;

[0059] Figure 10 A flowchart illustrating yet another specific example of a multipath configuration method provided in this application embodiment;

[0060] Figure 11 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 . Detailed Implementation

[0061] To facilitate understanding of the technical solutions of the embodiments of this application, a brief introduction to the relevant technologies or terms of this application is given below.

[0062] First, sidelink (SL) and SL communication.

[0063] In wireless communication systems, UEs can transmit data with each other via a base station, or they can transmit data directly between UEs without a base station. Similar to the Uu interface between a UE and a base station, the interface between UEs can be called a PC5 interface.

[0064] Typically, the link between UEs can be referred to as an SL. For example... Figure 1 As shown, UE 1 and UE 2 can transmit data via the PC5 interface through SL. A typical application scenario for SL communication is vehicle-to-everything (V2X). In V2X, each vehicle can be regarded as a UE, and UEs can transmit data directly with each other through SL without the need for a base station, thus effectively reducing communication latency.

[0065] SL supports broadcast, unicast, and multicast communication.

[0066] In broadcast communication, similar to base station broadcast system information, UE 1 can send unencrypted broadcast service data to other UEs. Any UE within the effective reception range, such as UE 2, can receive the broadcast service data if it is interested in the broadcast service.

[0067] In unicast communication, similar to how a UE and a base station first establish an RRC connection before data communication, UE 1 and UE 2 first establish a unicast connection and then transmit data based on a negotiated identifier. Data transmitted in unicast communication can be encrypted or unencrypted. Unlike broadcast communication, UE 1 and UE 2 can only communicate after a unicast connection has been established.

[0068] Multicast communication can be communication between all UEs within a communication group, where any UE can send or receive multicast service data.

[0069] This application primarily relates to unicast communication. A single unicast communication in an SL corresponds to a pair of source layer-2 identifiers (L2 IDs) and destination L2 IDs. These source and destination L2 IDs are included in the header of each SL media access control (MAC) layer protocol data unit (PDU) to ensure data can be transmitted from the sender to the correct receiver.

[0070] Second, radio bearer (RB).

[0071] The various protocol entities and related configurations allocated by the base station to the UE are collectively referred to as RBs. RBs are services provided by Layer 2 for transmitting user data between the UE and the base station. RBs include Packet Data Convergence Protocol (PDCP) entities, Radio Link Control (RLC) protocol entities, MAC protocol entities, and resources allocated to the physical (PHY) layer. Specifically, RBs can be divided into Data Radio Bearers (DRBs) for carrying data and Signalling Radio Bearers (SRBs) for carrying signaling messages.

[0072] In SL communication, UEs communicate with each other via SL RBs. SL RBs include SL DRBs and SL SRBs. In relevant protocols, RB configuration typically refers to the configuration of the PDCP layer and the Service Data Adaptation Protocol (SDAP) layer. Furthermore, protocol entities at the RLC layer and below can be referred to as RLC bearers, and their corresponding configurations are given in the RLC bearer configuration.

[0073] Third, communication scenarios involving multi-path relay.

[0074] As an evolution of the UE-to-network relay scheme in 3GPP Release R17, the multipath relay scheme was widely discussed in 3GPP R18. Figure 2A schematic diagram of a multi-path relay communication scenario is shown. In this scenario, the remote UE can communicate with the base station simultaneously via direct and non-direct paths. On the direct path, the remote UE and the base station can communicate directly via the Uu interface. On the non-direct path, the remote UE can communicate with the base station via a relay UE. The relay UE can communicate with the base station via the Uu interface, and the remote UE and the relay UE can communicate via either the SL (Single Link) or an ideal non-3GPP link. In a multi-path relay communication scenario, because the same or different data can be transmitted simultaneously on both the direct and non-direct paths (i.e., data packet 1 and data packet 2 can be transmitted simultaneously, and data packet 1 and data packet 2 can be the same or different), the throughput and reliability of data transmission can be improved.

[0075] Figure 3A This diagram illustrates the protocol stack architecture for communication between a remote UE and a relay UE via SL. On the remote UE side, besides PDCP, there are two protocol stacks. One stack communicates with the base station via the Uu interface and includes RLC, MAC, and PHY; the other stack communicates with the relay UE via the PC5 interface and includes an adaptation protocol, RLC, MAC, and PHY. On the relay UE side, there are two protocol stacks, one for communication with the remote UE via the PC5 interface and the other for communication with the base station via the Uu interface. Both stacks include an adaptation protocol, RLC, MAC, and PHY. On the base station side, besides PDCP, there are two protocol stacks. One stack communicates with the remote UE via the Uu interface and includes RLC, MAC, and PHY; the other stack communicates with the relay UE via the Uu interface and includes an adaptation protocol, RLC, MAC, and PHY. Typically, the adaptation protocol used when the remote UE and relay UE communicate via the PC5 interface can be SRAP.

[0076] Figure 3B This diagram illustrates the protocol stack architecture for communication between a remote UE and a relay UE via an ideal non-3GPP link. Figure 3A The difference lies in the protocol stack used for communication with the relay UE via an ideal non-3GPP link on the remote UE side, which includes an adaptation protocol and a PHY. On the relay UE side, the protocol stack used for communication with the remote UE via an ideal non-3GPP link includes an adaptation protocol and a PHY. Optionally, Figure 3B The adapter protocol may not be included.

[0077] Fourth, carrier aggregation.

[0078] A UE with carrier aggregation capability can transmit data simultaneously on one or more carrier interfaces (CCs). For example... Figure 4 As shown, the CC can be further divided into the primary component carrier (PCC) between the base station and the PCell, and the secondary component carrier (SCC) between the base station and the SCell. The PCell can provide non-access stratum (NAS) mobility information during the establishment, reconstruction, or handover of the RRC connection between the base station and the UE. The SCell can also provide security input during the reconstruction or handover of the RRC connection between the base station and the UE. One PCell and one or more SCells can form a set of serving cells; in other words, the UE's serving cell set consists of one PCell and one or more SCells.

[0079] When the base station configures carrier aggregation for the UE, the multi-carrier nature of the PHY layer only affects the MAC layer. In both uplink and downlink, each cell in the serving cell set has an independent hybrid automatic repeat request (HARQ) entity. Without spatial multiplexing, each cell in the serving cell set is allocated a transport block or granted a transport block. Each transport block and its potential HARQ retransmissions are mapped to a corresponding cell.

[0080] The reconfiguration, addition, and deletion of SCells can be performed by the base station via RRC connections. During cell handover within the new radio (NR) system or during the transition from RRC_INACTIVE to RRC_CONNECTED state, the base station can add, delete, retain, or reconfigure SCells for use with a target Pcell. When a new SCell is added, dedicated RRC signaling is used to transmit all the system information required for the SCell. That is, when the UE is in RRC_CONNECTED state, it does not need to directly obtain broadcast system information from the SCell.

[0081] Fifth, the existing carrier aggregation configuration process and its problems.

[0082] In multi-path relay communication scenarios, such as when a remote UE has established a non-direct path with the base station through a relay UE and needs to configure a direct path between the remote UE and the base station, if the existing carrier aggregation configuration process is used to configure SCell, the RRC message sent by the base station to the relay UE will not carry the synchronization reconfiguration parameters for the remote UE to randomly access the base station. This will result in the remote UE being unable to randomly access the base station and thus unable to establish a direct path.

[0083] As described in the background section, if the PCell is configured using the existing CA configuration process, the remote UE cannot simultaneously maintain both the non-directly connected path and the directly connected path with the base station. Furthermore, the base station can assign a first cell radio network temporary identifier (C-RNTI) to the remote UE. This first C-RNTI is the C-RNTI of the remote UE within the first cell accessed by the remote UE in the non-directly connected path, and is sent to the remote UE via the non-directly connected path. The synchronization reconfiguration parameters carried in the aforementioned RRC message may include a second C-RNTI, which is the C-RNTI of the remote UE within the second cell accessed by the remote UE in the directly connected path. Determining which C-RNTI to report when the remote UE triggers re-establishment after receiving both the first and second C-RNTIs is also a pressing technical problem that needs to be solved.

[0084] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Meanwhile, in the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a concrete manner for ease of understanding.

[0085] like Figure 5A The diagram illustrates a communication system 50 provided in an embodiment of this application. The communication system 50 includes a first terminal device 501, a second terminal device 502, and a network device 503. The path through which the first terminal device 501 communicates with the network device 503 via the second terminal device 502 is called the first path. The path through which the first terminal device 501 communicates directly with the network device 503 is called the second path. In other words, the first path is a non-direct connection path, and the second path is a direct connection path.

[0086] like Figure 5BThe diagram illustrates another communication system 51 provided in this application embodiment. This communication system 51 includes a first terminal device 501, a second terminal device 502, and a network device 503. The path through which the first terminal device 501 communicates directly with the network device 503 is the first path. The path through which the first terminal device 501 communicates with the network device 503 via the second terminal device 502 is the second path. In other words, the first path is a direct connection path, and the second path is a non-direct connection path.

[0087] In this embodiment of the application, one of the first path and the second path is a directly connected path and the other path is a non-directly connected path, which is used as an example for illustration. However, the first path and the second path can also be two different non-directly connected paths. This embodiment of the application does not limit this in any way.

[0088] exist Figure 5A and Figure 5B In this process, the first terminal device 501 receives a first message from the network device 503 through a first path; wherein the first message instructs the first terminal device 501 to establish a second path between the first terminal device 501 and the network device 503, the second path being different from the first path; the first terminal device 501 uses the first message to establish the second path in a second cell; the first terminal device 501 maintains a MAC entity, the MAC entity being used for communication between the first terminal device 501 and the network device 503 through a direct connection path in either the first path or the second path. The specific implementation and technical effects of this scheme will be described in detail in subsequent method embodiments, and will not be repeated here.

[0089] Optionally, the network device 503 in this embodiment is a device that connects a terminal device to a wireless network. It can be a base station, an evolved NodeB (eNodeB), a transmission reception point (TRP), a next-generation NodeB (gNB) in a 5G mobile communication system, a base station in a future mobile communication system, or an access node in a wireless-fidelity (Wi-Fi) system; it can also be a module or unit that performs some of the functions of a base station, for example, a central unit (CU) or a distributed unit (DU). The embodiments of this application do not limit the specific technology or device form used in the network device. In this application, unless otherwise specified, network device refers to wireless access network device.

[0090] Optionally, the first terminal device 501 or the second terminal device 502 in this embodiment can be a device for implementing wireless communication functions, such as a terminal or a chip that can be used in a terminal. The aforementioned terminal can be a UE, access terminal, terminal unit, terminal station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, terminal agent, or terminal device in a 5G network or a future evolved public land mobile network (PLMN). The access terminal can be a cellular phone, cordless phone, session initiation protocol (SIP) phone, wireless local loop (WLL) station, personal digital assistant (PDA), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, in-vehicle device or wearable device, virtual reality (VR) terminal device, augmented reality (AR) terminal device, wireless terminal in industrial control or self-driving, wireless terminal in remote medical care, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, wireless terminal in smart home, etc. The first terminal device 501 or the second terminal device 502 can be fixed in location or movable; this application embodiment does not specifically limit this.

[0091] Optionally, in this embodiment, the first terminal device 501 or the second terminal device 502 includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution subject of the method provided in the embodiments of this application may be a first terminal device 501 or a second terminal device 502, or a functional module in the first terminal device 501 or the second terminal device 502 that can call and execute a program; or, the execution subject of the method provided in the embodiments of this application may be a network device 503, or a functional module in the network device 503 that can call and execute a program.

[0092] Optionally, the relevant functions of the first terminal device, the second terminal device, or the network device in the embodiments of this application can be implemented by one device, or by multiple devices, or by one or more functional modules within a single device. The embodiments of this application do not specifically limit this. It is understood that the aforementioned functions can be network elements in hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0093] For example, the relevant functions of the first terminal device, the second terminal device, or the network device in the embodiments of this application can be achieved through... Figure 6 This is achieved through the communication device 600.

[0094] Figure 6 The diagram shown is a structural schematic of a communication device 600 provided in an embodiment of this application. The communication device 600 includes one or more processors 601, a communication line 602, and at least one communication interface. Figure 6 (This is merely an example illustration of a communication interface 604 and a processor 601; optionally, a memory 603 may also be included.)

[0095] The processor 601 may be a CPU, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of programs according to the present application.

[0096] The communication line 602 may include a path for connecting different components.

[0097] The communication interface 604 can be a transceiver module used to communicate with other devices or communication networks, such as Ethernet, RAN, WLAN, etc. For example, the transceiver module can be a transceiver or a similar device. Optionally, the communication interface 604 can also be a transceiver circuit located within the processor 601, used to implement the processor's signal input and signal output.

[0098] The memory 603 can be a device with storage functionality. For example, it can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; electrically erasable programmable read-only memory (EEPROM); compact disc read-only memory (CD-ROM) or other optical disc storage; optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.); magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory can exist independently and be connected to the processor via communication line 602. The memory can also be integrated with the processor.

[0099] The memory 603 stores computer execution instructions for implementing the scheme of this application, and its execution is controlled by the processor 601. The processor 601 executes the computer execution instructions stored in the memory 603, thereby implementing the multipath configuration method provided in the embodiments of this application.

[0100] Alternatively, in this embodiment, the processor 601 may execute the processing-related functions in the multipath configuration method provided in the following embodiments of this application, and the communication interface 604 may be responsible for communicating with other devices or communication networks. This embodiment does not specifically limit this.

[0101] The computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0102] In a specific implementation, as one embodiment, the processor 601 may include one or more CPUs, for example... Figure 6 CPU0 and CPU1 in the CPU.

[0103] In a specific implementation, as one example, the communication device 600 may include multiple processors, such as... Figure 6 Processors 601 and 607 are described herein. Each of these processors may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. A processor here may refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0104] In a specific implementation, as one embodiment, the communication device 600 may further include an output device 605 and an input device 606. The output device 605 communicates with the processor 601 and can display information in various ways.

[0105] The following will combine Figures 1 to 6 The multipath configuration method provided in the embodiments of this application will be described in detail.

[0106] like Figure 7 The image shows a multipath configuration method provided in an embodiment of this application. The multipath configuration method includes the following steps:

[0107] Step S701: The first terminal device receives a first message from the network device through a first path; wherein, the first message is used to instruct the first terminal device to establish a second path between the first terminal device and the network device, and the second path is different from the first path.

[0108] In combination with the above Figure 2 , Figure 3A and Figure 3B The first terminal device can be the above Figure 2 , Figure 3A or Figure 3B The remote UE in the middle; the second terminal device can be the above Figure 2 , Figure 3A or Figure 3B The relay UE in the network device can be one of the above. Figure 2 , Figure 3A or Figure 3B Base stations in the region.

[0109] In the embodiments of this application, unless otherwise specified, the first path can be a non-directly connected path or a directly connected path. When the first path is a non-directly connected path, the second path is a directly connected path; when the first path is a directly connected path, the second path is a non-directly connected path.

[0110] For example, the first message can be an RRC reconfiguration message.

[0111] Optionally, the first message includes a second identifier of the first terminal device, which is the identifier of the first terminal device in the second cell to which the first terminal device is to access in the second path. Before step S701, the multi-path configuration method provided in this application embodiment further includes: the first terminal device receiving and storing a first identifier of the first terminal device from the network device through the first path, where the first identifier of the first terminal device is the identifier of the first terminal device in the first cell to which a terminal device is accessed in the first path. After step S701, the multi-path configuration method provided in this application embodiment further includes: the first terminal device updating the stored first identifier of the first terminal device to the second identifier of the first terminal device; or, the first terminal device storing the second identifier of the first terminal device. In this scheme, the first terminal device only stores the most recently received second identifier of the first terminal device, which can effectively save the storage resources of the first terminal device. The first terminal device stores both the first identifier and the second identifier of the first terminal device so that the first identifier of the first terminal device can be used when transmitting data through the first path and the second identifier of the first terminal device can be used when transmitting data through the second path, making it easier to distinguish.

[0112] In this embodiment, the identifier of the first terminal device can be uniquely determined by the path and the cells on that path. This will be explained uniformly here and will not be repeated below. For example, the identifier of the first terminal device can be its C-RNTI. The second identifier of the first terminal device can be included in the synchronization reconfiguration parameters.

[0113] In this embodiment, the identifier of the first terminal device can be a parameter name, and the value of the first identifier or the second identifier of the first terminal device, i.e., the first value or the second value, can be a parameter value. The first terminal device updating the stored first identifier of the first terminal device to the second identifier of the first terminal device can also be described as: the first terminal device changing or replacing the value of the identifier of the first terminal device from the first value to the second value; or, the first terminal device replacing the first value with the second value as the value of the identifier of the first terminal device; or, the first terminal device setting the value of the identifier of the first terminal device to the second value.

[0114] Optionally, the first identifier of the first terminal device and the second identifier of the first terminal device may be the same or different.

[0115] For ease of reference and explanation, in the embodiments of this application, the above-mentioned scheme of "the first terminal device updates the first identifier of the first terminal device stored in the first terminal device to the second identifier of the first terminal device" is referred to as Scheme 1, and the above-mentioned scheme of "the first terminal device stores the first identifier of the first terminal device and the second identifier of the first terminal device" is referred to as Scheme 2.

[0116] Option 1 above can be used Figure 5A It can be executed in the scenario shown, or in Figure 5B This will be executed in the scenario shown. Similarly, the second solution above can be implemented in... Figure 5A It can be executed in the scenario shown, or in Figure 5B This will be executed in the scenario shown. This application does not impose any limitations on this embodiment.

[0117] Optionally, the first message includes a second identifier of the first terminal device and an identifier of the second cell to which the first terminal device is to access in the second path. The second identifier of the first terminal device is the identifier of the first terminal device within the second cell to which the first terminal device is to access in the second path. Before step S701, the multi-path configuration method provided in this application embodiment further includes: the first terminal device receiving and storing a first identifier of the first terminal device from the network device through the first path. The first identifier of the first terminal device is the identifier of the first terminal device within the first cell to which the first terminal device is accessed in the first path. After step S702, the multi-path configuration method provided in this application embodiment further includes: if the identifier of the second cell is the same as the identifier of the first cell, the first terminal device updates the stored first identifier of the first terminal device to the second identifier of the first terminal device; if the identifier of the second cell is different from the identifier of the first cell, the first terminal device stores the second identifier of the first terminal device. For ease of reference and explanation, in this application embodiment, this scheme is referred to as Scheme Three. Scheme Three can be... Figure 5A It can be executed in the scenario shown, or in Figure 5B Execute in the scenario shown.

[0118] In Scheme 3, if the first cell and the second cell are the same cell, the first terminal device only stores the most recently received second identifier of the first terminal device, which can effectively save the storage resources of the first terminal device. If the first cell and the second cell are different cells, the first terminal device stores both the first identifier and the second identifier of the first terminal device, so that the first identifier is used when transmitting data through the first path and the second identifier is used when transmitting data through the second path, making it easier to distinguish.

[0119] For example, the identifier of the first cell can be the physical cell identifier (PCI) and / or the cell global identifier (CGI) of the first cell. The identifier of the second cell can be the PCI and / or CGI of the second cell.

[0120] For example, the second identifier of the first terminal device and the identifier of the second cell can be included in the synchronization reconfiguration parameters.

[0121] Step S702: The first terminal device uses the first message to establish a second path in the second cell.

[0122] Optionally, the first path is a direct path, and the second path is a non-direct path; the first message includes the identifier of the second terminal device, but does not include the second identifier of the first terminal device. The second identifier of the first terminal device is the identifier of the first terminal device in the second cell to which the first terminal device is to access in the second path, and the second terminal device is a relay device between the first terminal device and the network device; step S702 includes: the first terminal device uses the identifier of the second terminal device in the first message to establish an SL connection with the second terminal device. For ease of reference and explanation, this scheme is referred to as Scheme Four in this embodiment. Scheme Four can only be used in... Figure 5B Execute in the scenario shown.

[0123] In Scheme 4, since the first message does not include the second identifier of the first terminal device, the first terminal device only needs to store one identifier of the first terminal device, that is, the first identifier of the first terminal device, to achieve the establishment of multiple paths.

[0124] exist Figure 5A and Figure 5B In the scenario shown, the same solution can be executed; for example, solution one, solution two, or solution three can all be executed. Figure 5A and Figure 5B In the scenario shown, different solutions can also be implemented, for example, in Figure 5A In the scenario shown, execute Option 1, Option 2, or Option 3. Figure 5B In the scenario shown, option four is executed. For example, in... Figure 5A In the scenario shown, execute plan one. Figure 5B In the scenario shown, execute option two; or, in Figure 5A In the scenario shown, execute plan two. Figure 5B In the scenario shown, execute option one; or, in Figure 5A In the scenario shown, execute plan one. Figure 5B In the scenario shown, execute option three; or, in Figure 5AIn the scenario shown, execute plan three. Figure 5B In the scenario shown, execute option one; or, in Figure 5A In the scenario shown, execute plan two. Figure 5B In the scenario shown, execute option three; or, in Figure 5A In the scenario shown, execute plan three. Figure 5B In the scenario shown, Scheme 2 is executed. This application does not impose any limitations on this embodiment.

[0125] Step S703: The first terminal device maintains a MAC entity, which is used for the first terminal device to communicate with the network device through a direct connection path in the first path or the second path.

[0126] In this application embodiment, the MAC entity can be a Uu MAC entity.

[0127] Unlike dual connectivity (DC), where the first terminal device needs to maintain two MAC entities, in this embodiment, the first terminal device only needs to maintain one MAC entity.

[0128] exist Figure 5A In the scenario shown, before step S703, the multipath configuration method provided in this application embodiment further includes: the first terminal device creating a MAC entity.

[0129] In this embodiment of the application, since the first message can instruct the first terminal device to establish a second path between the first terminal device and the network device, the first terminal device can also establish a second path different from the first path after the first path is established, so as to achieve the purpose of the first terminal device communicating with the network device through multiple paths, namely the first path and the second path.

[0130] For example, combined Figure 5A Taking the first terminal device as the remote UE, the second terminal device as the relay UE, the network device as the gNB, the first message as the RRC reconfiguration message, the first identifier of the first terminal device as the first C-RNTI, and the second identifier of the first terminal device as the second C-RNTI as an example. Figure 8 This paper illustrates a specific example of a multipath configuration method provided in an embodiment of this application, which includes the following steps:

[0131] Step S801: The remote UE and gNB can communicate via a non-direct connection path. Alternatively, the remote UE and gNB can communicate via a relay UE.

[0132] In this embodiment, on a non-directly connected path, the gNB can configure a special cell (SpCell) and one or more SCells for the relay UE. The definition of SpCell in this embodiment can be found in existing standards and will not be repeated here. Step S801 may include: the relay UE can send the identifier of the accessed SpCell to the remote UE. Correspondingly, the remote UE can receive the identifier of the accessed SpCell from the relay UE and use this SpCell as the cell accessed by the remote UE in the non-directly connected path, i.e., the first cell.

[0133] Step S801 may further include: the relay UE may forward the first C-RNTI configured by the gNB to the remote UE. Accordingly, the remote UE may receive the first C-RNTI from the relay UE.

[0134] In step S802, the gNB can send an RRC reconfiguration message to the remote UE via a non-direct connection path. The RRC reconfiguration message instructs the remote UE to establish a direct connection path. Correspondingly, the remote UE can receive the RRC reconfiguration message from the gNB via the non-direct connection path.

[0135] Optionally, the triggering condition for step S802 may be: gNB decides to configure multipath for the remote UE based on the measurement reporting results of the remote UE.

[0136] Optionally, the RRC reconfiguration message may include synchronization reconfiguration parameters, which may include the second C-RNTI and the identifier of the second cell. After the remote UE receives the second C-RNTI, how to store the second C-RNTI can be referred to Scheme 1, Scheme 2 and Scheme 3 in step S701 above, and will not be repeated here.

[0137] Optionally, the RRC reconfiguration message may also include a dedicated configuration for the random access channel (RACH). This dedicated configuration can be used for the remote UE's random access to the gNB in ​​step S804 below. The dedicated configuration may include time-domain and / or frequency-domain resources in the second cell for the UE's random access to the gNB, information supporting contention-based or non-contention-based random access, and information supporting two-step or four-step random access.

[0138] After step S802, the following step can be performed: the remote UE creates a Uu MAC entity for the direct path. This step can also be performed before step S801, and this embodiment of the application does not limit it in any way.

[0139] After the Uu MAC entity is created, the following steps can also be performed: the remote UE maintains the Uu MAC entity.

[0140] Step S803: The remote UE can send an RRC reconfiguration complete message to the gNB. Correspondingly, the gNB can receive the RRC reconfiguration complete message from the remote UE.

[0141] exist Figure 8 The diagram illustrates step S803 being performed on a non-directly connected path.

[0142] Step S804: The remote UE initiates a random access procedure, that is, the remote UE uses the RRC reconfiguration message to establish a direct connection path in the second cell.

[0143] In this embodiment, the remote UE can randomly access the gNB on the time-domain resources and / or frequency-domain resources of the second cell; or, the remote UE can randomly access the gNB on the time-domain resources and / or frequency-domain resources included in the RRC reconfiguration message; or, the remote UE can randomly access the gNB based on system messages. This embodiment does not impose any limitations on these aspects.

[0144] In this embodiment, step S803 can be executed first, followed by step S804; or step S804 can be executed first, followed by step S803; or steps S803 and S804 can be executed simultaneously. This embodiment does not impose any limitations on these steps. Before the remote UE successfully accesses the gNB, i.e., before the direct connection path is established, step S803 can be executed on the non-direct connection path. After the remote UE successfully accesses the gNB, i.e., after the direct connection path is established, step S803 can be executed on the non-direct connection path and / or the direct connection path.

[0145] After the direct connection path is established, the second cell can be regarded as the SpCell accessed by the remote UE on the direct connection path. In addition, the gNB can also configure one or more SCells for the remote UE on the direct connection path, and these one or more SCells and the second cell form the serving cell set of the remote UE on the direct connection path.

[0146] After the direct connection path is established, the second C-RNTI can be used by the gNB to allocate time-domain and / or frequency-domain resources for data transmission to the remote UE. In other words, the gNB can use the second C-RNTI when scheduling time-domain and / or frequency-domain resources for data transmission through the direct connection path.

[0147] Before a direct path is established, including during its configuration, the remote UE can maintain data transmission with the gNB via a non-direct path. After a direct path is established, the remote UE can transmit data with the gNB via the direct path and / or a non-direct path.

[0148] For example, combined Figure 5B Taking the first terminal device as the remote UE, the second terminal device as the relay UE, the network device as the gNB, the first message as the RRC reconfiguration message, the first identifier of the first terminal device as the first C-RNTI, and the second identifier of the first terminal device as the second C-RNTI as an example. Figure 9 This paper illustrates another specific example of the multipath configuration method provided in the embodiments of this application, which includes the following steps:

[0149] Step S901: The remote UE and gNB can communicate via a direct connection path. Alternatively, the remote UE and gNB can communicate directly.

[0150] In this embodiment, on the direct connection path, the gNB can configure a first cell and one or more SCells for the remote UE. The first cell is the SpCell of the remote UE on the direct connection path. Step S901 may include: the gNB can send the identifier of the first cell and the first C-RNTI to the remote UE. Correspondingly, the remote UE receives the identifier of the first cell and the first C-RNTI from the gNB.

[0151] Since the Uu MAC entity is already established when the direct path is established, the remote UE can maintain the Uu MAC entity.

[0152] In step S902, the gNB can send an RRC reconfiguration message to the relay UE. Correspondingly, the relay UE can receive the RRC reconfiguration message from the gNB.

[0153] Step S903: The relay UE can send an RRC reconfiguration complete message to the gNB. Correspondingly, the gNB can receive the RRC reconfiguration complete message from the relay UE.

[0154] After steps S902 and S903, the gNB can establish an RRC connection with the relay UE so that it can forward downlink data to the remote UE or assist the remote UE in sending uplink data to the gNB.

[0155] In step S904, the gNB can send an RRC reconfiguration message to the remote UE via a direct path. The RRC reconfiguration message instructs the remote UE to establish a non-direct path. Correspondingly, the remote UE can receive the RRC reconfiguration message from the gNB via a direct path.

[0156] Optionally, the triggering condition for step S904 may be: the gNB selects a suitable relay UE for the remote UE based on the measurement and reporting results of the remote UE.

[0157] In one possible implementation, the RRC reconfiguration message may include synchronization reconfiguration parameters, which may include the second C-RNTI and the identifier of the second cell. After the remote UE receives the second C-RNTI, how to store the second C-RNTI can be referred to Scheme 1, Scheme 2, and Scheme 3 in step S701 above, and will not be elaborated further here.

[0158] In another possible implementation, the RRC reconfiguration message may include synchronization reconfiguration parameters, which may include the identifier of the second cell and the identifier of the relay UE, but not the second C-RNTI. A description of this implementation can be found in Scheme 4 in step S702 above, and will not be repeated here.

[0159] Step S905: Establish SL connection between remote UE and relay UE.

[0160] The above steps S902 and S903 can be performed before or after steps S904 and S905. This application embodiment does not limit this in any way.

[0161] Step S906: The remote UE sends an RRC reconfiguration complete message to the gNB. Correspondingly, the gNB receives the RRC reconfiguration complete message from the remote UE.

[0162] Before a non-directly connected path is established, including during its configuration, the remote UE can maintain data transmission with the gNB via a direct path. After a non-directly connected path is established, the remote UE can transmit data with the gNB via a direct path and / or a non-directly connected path.

[0163] In this embodiment, step S905 can be executed first, followed by step S906; or step S906 can be executed first, followed by step S905; or steps S905 and S906 can be executed simultaneously. This embodiment does not impose any limitations on this. Before a non-directly connected path is established, step S906 can be executed on a directly connected path. After a non-directly connected path is established, step S906 can be executed on both the non-directly connected path and / or the directly connected path.

[0164] Optionally, after the first terminal device establishes the second path, the multi-path configuration method provided in this application embodiment further includes: the first terminal device determining the primary cell to which it accesses, wherein the primary cell is a special cell on the target path. In this scheme, the determined primary cell can be used by the first terminal device to uniquely identify the first terminal device within the primary cell, and the identifier can be used for RRC reconstruction or cell handover.

[0165] Combination Figure 8In the illustrated embodiment, after the direct connection path is established, the remote UE can simultaneously access the first cell on the non-direct connection path and the second cell on the direct connection path. On the direct connection path, the gNB can configure a serving cell set including the second cell for the remote UE. The first terminal device determines the primary cell to which it accesses; that is, the remote UE selects one cell from the first cell and the serving cell set including the second cell as the primary cell for access.

[0166] Combination Figure 9 In the illustrated embodiment, on the direct connection path, the gNB can configure a serving cell set including the first cell for the remote UE. After a non-direct connection path is established, the remote UE can simultaneously access the serving cell set including the first cell on the direct connection path and the second cell on the non-direct connection path. The first terminal device determines the primary cell to access, that is, the remote UE selects a cell from the serving cell set including the first cell and the second cell as the primary cell to access.

[0167] Optionally, the target path is a first path; the target path is a directly connected path between the first path and the second path; the target path is a non-directly connected path between the first path and the second path; or, the target path is a path randomly selected by the first terminal device from the first path and the second path.

[0168] Optionally, if the network device does not configure the SRB to split, the target path is the path where the SRB is located.

[0169] For example, the SRB in this application embodiment can be SRB1. To improve the reliability of multipath transmission, the network device can configure SRB1 to be split and replicated.

[0170] Optionally, when the network device is configured to split SRB and duplicat SRB for SRB, the target path is the first path; the target path is a directly connected path between the first path and the second path; the target path is a non-directly connected path between the first path and the second path; or, the target path is a path randomly selected by the first terminal device from the first path and the second path.

[0171] Optionally, if the network device is configured to separate the SRB but not to replicate the SRB, the target path is the path where the primary RLC entity is located.

[0172] For example, combined Figure 8 or Figure 9 , Figure 10 This paper illustrates another specific example of the multipath configuration method provided in the embodiments of this application. This example is used for remote UE to perform RRC reconstruction and includes the following steps:

[0173] Step S1001: The remote UE sends an RRC Reestablishment Request to the target gNB through the source gNB. Correspondingly, the target gNB receives the RRC Reestablishment Request from the remote UE through the source gNB.

[0174] In this embodiment, the triggering condition for step S1001 can refer to the triggering condition for rebuilding the RRC connection in the prior art, and will not be repeated here.

[0175] Figure 10 The source gNB in ​​the illustrated embodiment can be Figure 8 or Figure 9 gNB in ​​the middle.

[0176] In this embodiment, the RRC re-establishment request may include the primary cell accessed by the remote UE, and the C-RNTI of the remote UE within that primary cell. The scheme for determining the primary cell accessed by the remote UE can be found in the above embodiments and will not be repeated here.

[0177] Optionally, if the target path is the first path, the primary cell accessed by the remote UE is the first cell; if the target path is the second path, the primary cell accessed by the remote UE is the second cell.

[0178] Step S1002: The target gNB sends a UE context request to the source gNB. This UE context request includes the C-RNTI of the remote UE in the primary cell to which the remote UE is accessed. Correspondingly, the source gNB receives the UE context request from the target gNB.

[0179] Optionally, in this embodiment, the source gNB and the target gNB can be the same gNB or different gNBs. When the source gNB and the target gNB are the same gNB, the source gNB can obtain the context of the remote UE locally without needing to perform the interaction of step S1002 and the following step S1003.

[0180] Optionally, if the remote UE stores the first C-RNTI and the second C-RNTI, and the remote UE randomly selects one path from the first path and the second path as the target path, after executing step S1002 and before executing step S1003, the source gNB can perform integrity verification using two short MAC-Is. If the source gNB successfully verifies using at least one short MAC-I, then the following steps continue.

[0181] Step S1003: The source gNB sends a retrieve UE context response to the target gNB. This retrieval UE context request includes the context of the remote UE. Accordingly, the target gNB receives the retrieve UE context response from the source gNB.

[0182] Step S1004: The target gNB sends an RRC Reestablishment message to the remote UE through the source gNB. Correspondingly, the remote UE receives the RRC Reestablishment message from the target gNB through the source gNB.

[0183] Step S1005: The remote UE sends an RRC Reestablishment Complete message to the target gNB through the source gNB. Correspondingly, the target gNB receives the RRC Reestablishment message from the remote UE through the source gNB.

[0184] Step S1006: The target gNB sends an RRC reconfiguration message to the remote UE through the source gNB. Correspondingly, the remote UE receives the RRC reconfiguration message from the target gNB through the source gNB.

[0185] Step S1007: The remote UE sends an RRC reconfiguration complete message to the target gNB through the source gNB. Correspondingly, the target gNB receives the RRC reconfiguration complete message from the remote UE through the source gNB.

[0186] In this embodiment of the application, the target gNB can perform RRC reconfiguration to rebuild SRB2 and DRB.

[0187] Optionally, if the triggering condition for rebuilding the RRC connection is met on the target path, then execute... Figure 10 The steps in the illustrated embodiment are as follows: If the triggering conditions for re-establishing the RRC connection are met on a path other than the target path, the remote UE informs the source gNB via an RRC message, and the source gNB restores the RRC connection.

[0188] Apart from Figure 10 In the RRC reconstruction procedure shown, when the remote UE switches from the source gNB to the target gNB, if the target gNB is configured with multipath, then the target gNB can send the identifier of the primary cell accessed by the remote UE to the remote UE. The scheme for determining the primary cell accessed by the remote UE can be found in the above embodiments and will not be repeated here.

[0189] Optionally, after the first terminal device establishes the second path, the multi-path configuration method provided in this application embodiment further includes: the first terminal device determining the primary path;

[0190] Optionally, the main path is the first path; or, the main path is a directly connected path between the first path and the second path; or, the main path is a non-directly connected path between the first path and the second path; or, the main path is a path randomly selected by the first terminal device from the first path and the second path.

[0191] Optionally, if the network device does not configure a separate SRB for the SRB, the primary path is the path where the SRB is located.

[0192] Optionally, when the network device is configured to separate and replicate SRBs, the primary path is the first path; the primary path is a directly connected path between the first path and the second path; the primary path is a non-directly connected path between the first path and the second path; or, the primary path is a path randomly selected by the first terminal device from the first path and the second path.

[0193] Optionally, if the network device is configured to separate the SRB but not to replicate the SRB, the primary path is the path where the primary RLC entity is located.

[0194] In the embodiments of this application, the method for determining the main path can refer to the method for determining the target path, and will not be repeated here.

[0195] It is understood that, in the above embodiments, the methods and / or steps implemented by the first terminal device can also be implemented by components (e.g., chips or circuits) that can be used in the first terminal device; the methods and / or steps implemented by the second terminal device can also be implemented by components (e.g., chips or circuits) that can be used in the second terminal device; and the methods and / or steps implemented by the network device can also be implemented by components (e.g., chips or circuits) that can be used in the network device.

[0196] The above mainly describes the solutions provided by the embodiments of this application from the perspective of interaction between various network elements. Correspondingly, the embodiments of this application also provide a communication device for implementing the various methods described above. This communication device can be a first terminal device in the above method embodiments, or a device containing the first terminal device, or a component usable in the first terminal device; or, this communication device can be a second terminal device in the above method embodiments, or a device containing the second terminal device, or a component usable in the second terminal device; or, this communication device can be a network device in the above method embodiments, or a device containing the network device, or a component usable in the network device. It is understood that, in order to achieve the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, in conjunction with the units and algorithm steps of the various examples described in the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0197] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0198] Figure 11 A schematic diagram of a communication device 11 is shown. The communication device 11 includes a transceiver module 111. The transceiver module 111, also known as a transceiver unit, is used to implement transceiver functions, and may be, for example, a transceiver circuit, a transceiver, a transceiver device, or a communication interface.

[0199] Taking the communication device 11 as the first terminal device in the above method embodiment as an example, then:

[0200] The communication device 11 further includes a processing module 112; a transceiver module 111, configured to receive a first message from a network device via a first path; wherein the first message is configured to instruct the communication device 11 to establish a second path between the communication device 11 and the network device, the second path being different from the first path; the transceiver module 111 is also configured to establish a second path in a second cell using the first message; the processing module 112 is configured to maintain a Media Access Control (MAC) entity, the MAC entity being used for communication between the communication device 11 and the network device via a direct path in either the first path or the second path.

[0201] In one possible implementation, the communication device 11 further includes a storage module 113; the first message includes a second identifier of the communication device 11, which is the identifier of the communication device 11 in the second cell to be accessed by the communication device 11 in the second path; the transceiver module 111 is further configured to receive the first identifier of the communication device 11 from the network device through the first path, which is the identifier of the communication device 11 in the first cell to be accessed by the communication device 11 in the first path; the storage module 113 is configured to store the first identifier of the communication device 11; the processing module 112 is further configured to update the first identifier of the communication device 11 stored in the storage module 113 to the second identifier of the communication device 11; or, the storage module 113 is further configured to store the second identifier of the communication device 11.

[0202] In one possible implementation, the communication device 11 further includes: a storage module 113; a first message including a second identifier of the communication device 11 and an identifier of a second cell to be accessed by the communication device 11 in the second path, wherein the second identifier of the communication device 11 is the identifier of the communication device 11 in the second cell to be accessed by the communication device 11 in the second path; a transceiver module 111, further configured to receive the first identifier of the communication device 11 from a network device through a first path, wherein the first identifier of the communication device 11 is the identifier of the communication device 11 in the first cell accessed by the communication device 11 in the first path; a storage module 113, configured to store the first identifier of the communication device 11; a processing module 112, further configured to update the stored first identifier of the communication device 11 to the second identifier of the communication device 11 if the identifier of the second cell is the same as the identifier of the first cell; and a storage module 113, further configured to store the second identifier of the communication device 11 if the identifier of the second cell is different from the identifier of the first cell.

[0203] In one possible implementation, the first path is a direct path, and the second path is a non-direct path; the first message includes the identifier of the second terminal device, but does not include the second identifier of the communication device 11, the second identifier of the communication device 11 being the identifier of the communication device 11 in the second cell to which the communication device 11 is to be accessed in the second path, and the second terminal device is a relay device between the communication device 11 and the network device; the transceiver module 111 is further configured to establish a second path in the second cell using the first message, including: establishing an SL connection with the second terminal device using the identifier of the second terminal device in the first message.

[0204] In one possible implementation, the processing module 112 is further configured to determine the primary cell accessed by the communication device 11, wherein the primary cell is a special cell on the target path.

[0205] In one possible implementation, the processing module 112 is also used to determine the main path.

[0206] All relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0207] In this embodiment, the communication device 11 is presented in an integrated manner, divided into various functional modules. Here, "module" can refer to a specific ASIC, circuit, processor and memory executing one or more software or firmware programs, integrated logic circuit, and / or other devices that can provide the above-mentioned functions.

[0208] When the communication device 11 is the first terminal device in the above method embodiments, in a simple embodiment, those skilled in the art will realize that the communication device 11 can adopt... Figure 6 The communication device 600 shown is in the form of this device.

[0209] for example, Figure 6 The processor 601 or 607 in the communication device 600 shown can execute the multipath configuration method described in the above method embodiment by calling computer execution instructions stored in the memory 603. Specifically, Figure 11 The function / implementation process of the processing module 112 can be achieved through... Figure 6 The processor 601 or 607 in the communication device 600 shown calls computer execution instructions stored in memory 603 to implement the function. Figure 11 The function / implementation process of the transceiver module 111 can be achieved through... Figure 6 The communication module connected to the communication interface 604 in the middle is used to achieve this.

[0210] Since the communication device 11 provided in this embodiment can execute the above-described multipath configuration method, the technical effects it can achieve can be referred to the above-described method embodiments, and will not be repeated here.

[0211] It should be noted that one or more of the above modules or units can be implemented by software, hardware, or a combination of both. When any of the above modules or units are implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow. The processor can be built into a SoC (System-on-a-Chip) or ASIC, or it can be a separate semiconductor chip. In addition to the core that executes software instructions for computation or processing, the processor may further include necessary hardware accelerators, such as field-programmable gate arrays (FPGAs), PLDs (Programmable Logic Devices), or logic circuits that implement dedicated logic operations.

[0212] When the above modules or units are implemented in hardware, the hardware can be any one or any combination of a CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0213] Optionally, embodiments of this application also provide a chip system, including: at least one processor and an interface, wherein the at least one processor is coupled to a memory via the interface, and when the at least one processor executes a computer program or instructions in the memory, the method in any of the above method embodiments is executed. In one possible implementation, the communication device further includes a memory. Optionally, the chip system may be composed of chips, or may include chips and other discrete devices; embodiments of this application do not specifically limit this.

[0214] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device containing one or more servers, data centers, etc., that can be integrated with the medium. The available media can be magnetic media (e.g., floppy disks, hard disks, magnetic tapes), optical media (e.g., DVDs), or semiconductor media (e.g., solid-state disks, SSDs), etc.

[0215] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude a plurality. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0216] Although this application has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made thereto without departing from the spirit and scope of this application. Accordingly, this specification and drawings are merely exemplary illustrations of this application as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from the spirit and scope of this application. Thus, if such modifications and modifications of this application fall within the scope of the claims of this application and their equivalents, this application is also intended to include such modifications and modifications.

Claims

1. A method of configuring a multi-path, characterized by, include: The first terminal device receives and stores a first identifier of the first terminal device from the network device through a first path. The first identifier is the identifier of the first terminal device in the first cell accessed by the first terminal device in the first path. The first terminal device receives a first message from the network device through the first path; wherein, the first message is used to instruct the first terminal device to establish a second path between the first terminal device and the network device, the second path being different from the first path; the first message includes a second identifier of the first terminal device, the second identifier being the identifier of the first terminal device in the second cell to which the first terminal device is to access in the second path; The first terminal device updates the stored first identifier to the second identifier; or, the first terminal device stores the second identifier. The first terminal device uses the first message to establish the second path in the second cell; The first terminal device communicates with the network device through the first path and / or the second path.

2. The method of claim 1, wherein, The first message also includes the identifier of the second cell that the first terminal device needs to access in the second path; After the first terminal device receives the first message from the network device via the first path, the method further includes: If the identifier of the second cell is the same as the identifier of the first cell, the first terminal device will update the stored first identifier to the second identifier; If the identifier of the second cell is different from the identifier of the first cell, the first terminal device stores the second identifier.

3. The method according to claim 1 or 2, characterized in that, The first path is a non-directly connected path, and the second path is a directly connected path.

4. The method according to claim 1 or 2, characterized in that, After the first terminal device establishes the second path, the method further includes: The first terminal device determines the primary cell it accesses, wherein the primary cell is a special cell on the target path.

5. The method according to claim 4, characterized in that, The target path is the first path; The target path is a direct connection path between the first path and the second path; The target path is a non-directly connected path between the first path and the second path; or... The target path is a path randomly selected by the first terminal device from the first path and the second path.

6. The method of claim 4, wherein, If the network device does not configure a separate SRB for the signaling radio bearer SRB, the target path is the path where the SRB is located.

7. The method of claim 4, wherein, In the case where the network device is configured to split SRB and replicate SRB, The target path is the first path; The target path is a direct connection path between the first path and the second path; The target path is a non-directly connected path between the first path and the second path; or... The target path is a path randomly selected by the first terminal device from the first path and the second path.

8. The method of claim 4, wherein, When the network device is configured to separate the SRB but not to replicate the SRB, the target path is the path where the primary Radio Link Control (RLC) entity is located.

9. The method according to any one of claims 5-8, characterized in that, When the target path is the first path, the primary cell is the first cell; when the target path is the second path, the primary cell is the second cell.

10. The method according to any one of claims 1 or 2, 5-8, characterized in that, After the first terminal device establishes the second path, the method further includes: The first terminal device determines the main path.

11. The method according to claim 10, characterized in that, The main path is the first path; The main path is the direct path between the first path and the second path; The main path is a non-directly connected path between the first path and the second path; or, The main path is a path randomly selected by the first terminal device from the first path and the second path.

12. The method of claim 10, wherein, If the network device does not configure a separate SRB for the SRB, the primary path is the path where the SRB is located.

13. The method according to claim 10, characterized in that, In the case where the network device is configured to split SRB and replicate SRB, The main path is the first path; The main path is the direct connection path between the first path and the second path; The main path is a non-directly connected path between the first path and the second path; or, The main path is a path randomly selected by the first terminal device from the first path and the second path.

14. The method of claim 10, wherein, When the network device is configured to separate the SRB but not to replicate the SRB, the primary path is the path where the primary RLC entity is located.

15. A first terminal device, comprising: The first terminal device includes: a transceiver module, a processing module, and a storage module; The transceiver module is configured to receive a first identifier of the first terminal device from a network device via a first path, wherein the first identifier is the identifier of the first terminal device in the first cell accessed by the first terminal device in the first path. The storage module is used to store the first identifier; The transceiver module is configured to receive a first message from a network device via a first path; wherein the first message is configured to instruct the first terminal device to establish a second path between the first terminal device and the network device, the second path being different from the first path; the first message includes a second identifier of the first terminal device, the second identifier being the identifier of the first terminal device in the second cell to which the first terminal device is to access in the second path; The processing module is further configured to update the first identifier stored in the storage module to the second identifier; or, the storage module is further configured to store the second identifier. The transceiver module is further configured to use the first message to establish the second path in the second cell; The processing module is used for the first terminal device and the network device to communicate through the first path and / or the second path.

16. The first terminal device of claim 15, wherein, The first message also includes the identifier of the second cell that the first terminal device needs to access in the second path; The processing module is further configured to update the stored first identifier to the second identifier if the identifier of the second cell is the same as the identifier of the first cell; The storage module is further configured to store the second identifier if the identifier of the second cell is different from the identifier of the first cell.

17. The first terminal device according to claim 15 or 16, characterized by The first path is a non-directly connected path, and the second path is a directly connected path.

18. The first terminal device according to claim 15 or 16, characterized by, The processing module is further configured to determine the primary cell accessed by the first terminal device, wherein the primary cell is a special cell on the target path.

19. The first terminal device of claim 18, wherein, The target path is the first path; the target path is a directly connected path between the first path and the second path; the target path is a non-directly connected path between the first path and the second path; or, the target path is a path randomly selected by the first terminal device from the first path and the second path.

20. The first terminal device according to claim 18, characterized in that, If the network device does not configure a separate SRB for the signaling radio bearer SRB, the target path is the path where the SRB is located.

21. The first terminal device of claim 18, wherein, When the network device is configured to split SRB and replicate SRB, the target path is the first path; the target path is the directly connected path between the first path and the second path. The target path is a non-directly connected path between the first path and the second path; or, the target path is a path randomly selected by the first terminal device from the first path and the second path.

22. The first terminal device of claim 18, wherein, When the network device is configured to separate the SRB but not to replicate the SRB, the target path is the path where the primary Radio Link Control (RLC) entity is located.

23. The first terminal device according to any one of claims 19-22, characterized by, When the target path is the first path, the primary cell is the first cell; when the target path is the second path, the primary cell is the second cell.

24. A communications device, characterized by include: A memory and a processor coupled to the memory, the memory being used to store a program, and the processor being used to execute the program stored in the memory; when the communication device is running, the processor runs the program, causing the communication device to perform the multipath configuration method according to any one of claims 1-14.

25. A communication system, characterized by The communication system includes a network device, a second terminal device, and a first terminal device for performing the method as described in any one of claims 1-14; wherein the second terminal device is a relay device between the first terminal device and the network device.

26. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program or instructions that, when executed, implement the multipath configuration method as described in any one of claims 1-14.

Images