Configuration method and terminal in secondary link relay architecture

Abstract

The embodiment of the present application discloses a configuration method and terminal in a secondary link relay architecture, which can solve the problem that a remote terminal cannot obtain the secondary link configuration in the secondary link relay architecture. The method can be applied to a remote terminal, comprising: determining the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; a system message received from a resident cell or a serving cell; first configuration information from a relay terminal; and second configuration information from a network side device.

Description

Technical Field

[0001] The present application belongs to the field of communication technology, and specifically relates to a configuration method and a terminal in a secondary link relay architecture. Background Art

[0002] The Long Term Evolution (LTE) system has supported sidelink since its 12th release, which is used for direct data transmission between terminal devices without going through network devices.

[0003] With the development of sidelink, the sidelink relay architecture has been proposed in related technologies. In a typical sidelink relay architecture, the remote terminal (remote UE) is connected to the relay terminal (relay UE) through a sidelink link (or relay link), and the relay terminal forwards its data to the network device. In this sidelink relay architecture, the remote terminal can transmit data to the network device, and the relay terminal plays the role of data transfer.

[0004] Since a relay terminal is introduced into the sidelink relay architecture, how the remote terminal obtains the sidelink configuration in the sidelink relay architecture so that the message can be transmitted normally is a technical problem that needs to be solved urgently in the relevant technologies. Summary of the invention

[0005] The purpose of the embodiments of the present application is to provide a configuration method and terminal in a secondary link relay architecture, which can solve the problem that a remote terminal cannot obtain the secondary link configuration in the secondary link relay architecture.

[0006] In order to solve the above technical problems, this application is implemented as follows:

[0007] In a first aspect, a configuration method in a sub-link relay architecture is provided, which is applied to a remote terminal, and the method includes: determining the sub-link configuration in the sub-link relay architecture according to at least one of the following: pre-configuration information; a system message received from a resident cell or a service cell; first configuration information from a relay terminal; and second configuration information from a network side device.

[0008] According to a second aspect, a remote terminal is provided, comprising: a determination module for determining a sub-link configuration in a sub-link relay architecture according to at least one of the following: pre-configuration information; a system message received from a resident cell or a service cell; first configuration information from a relay terminal; and second configuration information from a network side device.

[0009] In a third aspect, a terminal is provided, comprising a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the method described in the first aspect.

[0010] In a fourth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the method described in the first aspect is implemented.

[0011] In a fifth aspect, a computer program product is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the method described in the first aspect.

[0012] In a sixth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run a program or instruction to implement the method described in the first aspect.

[0013] In the embodiment of the present application, the remote terminal can determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; system message received from the resident cell or the serving cell; first configuration information from the relay terminal; second configuration information from the network side device. The embodiment of the present application facilitates the consistency of understanding between the remote terminal, the relay terminal and the network side, thereby improving the effectiveness of communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] Figure 1 is a block diagram of a wireless communication system according to an embodiment of the present application;

[0015] Figure 2 is a schematic flow chart of a configuration method in a secondary link relay architecture according to an embodiment of the present application;

[0016] Figure 3 is a schematic diagram of a relay architecture according to an embodiment of the present application;

[0017] Figure 4 is a schematic diagram of the structure of a remote terminal according to an embodiment of the present application;

[0018] Figure 5 is a schematic structural diagram of a communication device according to an embodiment of the present application;

[0019] Figure 6 It is a schematic diagram of the structure of a terminal according to an embodiment of the present application. DETAILED DESCRIPTION

[0020] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0021] The terms "first", "second", etc. in the specification and claims of this application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.

[0022] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. However, the following description describes a New Radio (NR) system for illustrative purposes, and the NR terminology is used in most of the following descriptions, although these technologies can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.

[0023] Figure 1A block diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal side devices, and the wearable device includes: a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 can be a base station or a core network, wherein the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a next generation node B (gNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0024] like Figure 2 As shown, an embodiment of the present application provides a configuration method 200 in a secondary link relay architecture, which can be executed by a remote terminal. In other words, the method can be executed by software or hardware installed in the remote terminal, and the method includes the following steps.

[0025] S202: Determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; a system message received from a resident cell or a serving cell; first configuration information from a relay terminal; second configuration information from a network side device.

[0026] The secondary link relay architecture mentioned in the embodiments of the present application can be found in Figure 3 In this secondary link relay architecture, the remote terminal (remote UE) can transmit data with the network device, and the relay terminal (relay UE) plays the role of data transfer; at the same time, the remote UE can also perform traditional secondary link transmission with the relay UE, which does not pass through the network device.

[0027] The relevant configurations of the sub-link transmission mentioned in each embodiment of the present application may include the relevant configurations required to establish a sub-link relay architecture between the remote terminal and the relay terminal, and may also include the relevant configurations required for data transmission between the remote terminal and the relay terminal after the sub-link relay architecture is established.

[0028] In the embodiment of the present application, the remote terminal can determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; system message received from the resident cell or the serving cell; first configuration information from the relay terminal; second configuration information from the network side device. The embodiment of the present application facilitates the consistency of understanding between the remote terminal, the relay terminal and the network side, thereby improving the effectiveness of communication.

[0029] To explain in detail the configuration method in the secondary link relay architecture provided by this embodiment, several cases are described in detail below.

[0030] Case 1: Off-network remote UE L3 relay architecture

[0031] In this case 1, the remote UE is in an offline state before establishing the L3 relay architecture with the relay UE. When the remote UE is in an offline state, it cannot obtain any system messages and configuration information related to the sidelink / sidelink relay. In this way, S202 can be: the remote UE determines the secondary link configuration in the secondary link relay architecture according to the pre-configuration information, and the remote UE is also used to establish the L3 relay architecture with the relay UE according to the pre-configuration information. For example, the remote UE uses the pre-configured sidelink / sidelink relay parameters to perform a discovery process with the relay UE, and then establishes the L3 relay architecture.

[0032] In the L3 relay architecture operation, there are two ways to obtain the secondary link configuration in the remote UE secondary link relay architecture:

[0033] The first one is to continue to use the above pre-configuration information to determine the sidelink configuration in the sidelink relay architecture, for example, continue to use the pre-configured sidelink / sidelink relay parameters.

[0034] The second method is to determine the sidelink configuration in the sidelink relay architecture by receiving the first configuration information from the relay terminal through the PC5 Radio Resource Control (RRC) process. For example, the relay UE sends the relevant sidelink / sidelink relay parameters to the remote UE through the PC5RRC process for the remote UE to use in the relay operation. The relay UE's own parameter information comes from the network side device. The first configuration information sent by the relay UE to the remote UE can be determined by itself or refer to the configuration information from the network side device.

[0035] Case 2: Remote UE L3 relay architecture in the network

[0036] In case 2, the remote UE and the relay UE are in an idle state or a connected state before establishing the L3 relay architecture.

[0037] When the remote UE is in a normal cell resident state, it can obtain the system information configuration related to the sidelink / sidelink relay. At this time, the remote UE can determine the sidelink configuration in the sidelink relay architecture based on the system message received from the cell. The remote UE can also establish an L3 relay architecture with the relay terminal based on the above system message.

[0038] Alternatively, the remote UE is in a normal RRC connection state and can obtain the dedicated configuration related to the sidelink / sidelink relay from its serving cell. At this time, the remote UE can determine the secondary link configuration in the secondary link relay architecture according to the second configuration information (which may refer to the above-mentioned dedicated configuration) from the network side device, and the remote UE can also establish an L3 relay architecture with the relay terminal according to the second configuration information.

[0039] When the remote UE meets the conditions for L3 relay operation and needs to perform L3 relay operation, there are two ways to obtain the configuration information of the remote UE:

[0040] The first one is that in the L3 relay architecture, the system message or the second configuration information is continued to be used to determine the sidelink configuration in the sidelink relay architecture. For example, the remote UE continues to use the sidelink / sidelink relay parameters in the currently obtained system information.

[0041] The second method is to determine the sidelink configuration in the sidelink relay architecture by receiving the first configuration information from the relay terminal through the PC5 RRC process. For example, the relay UE sends the relevant sidelink / sidelinkrelay parameters to the remote UE through the PC5 RRC process for the remote UE to use in the relay operation. The parameter information used by the relay UE itself comes from the network side. The first configuration information sent by the relay UE to the remote UE can be determined by itself or refer to the configuration information from the network side device.

[0042] Optionally, before the L3 relay architecture is established, the remote UE is in a connected state, wherein, in the L3 relay architecture, the remote UE can also release the RRC connection (such as releasing a dedicated configuration) and use the received system message to determine the sub-link configuration in the sub-link relay architecture; or, determine the sub-link configuration in the sub-link relay architecture by receiving the first configuration information from the relay terminal through the PC5 RRC process.

[0043] Optionally, in the above situation 1 or situation 2, the remote UE may also send first information to the relay UE during the PC5 RRC process with the relay UE, such as the discovery process, and the first information includes at least one of the following of the remote terminal: resident cell information, sidelink system information acquisition status, and network disconnection status; wherein the relay terminal is also used to send the first information to the network side device. In this way, the network side device can configure a sidelink configuration that is more suitable for the remote UE and the relay UE for the remote UE based on the first information.

[0044] For example, the network side device may send the secondary link configuration parameters to the relay UE according to the first information, and the relay UE processes the received secondary link configuration parameters and sends them to the remote UE (such as the first configuration information sent as described above).

[0045] Optionally, in the above-mentioned cases 1 and 2, after the remote UE determines the secondary link configuration in the secondary link relay architecture, the method further includes: receiving third configuration information, wherein the third configuration information is the configuration that the remote UE re-obtains in the new cell when the relay UE moves out of the current cell, wherein, in the current cell, the remote UE and the relay UE have established an L3 relay architecture.

[0046] This embodiment may be a configuration that the remote UE reacquires in a new cell when the remote UE and the relay UE move out of the current cell together. In this embodiment, the remote UE may obtain the third configuration information through a system message (such as SIB) or through PC5RRC. Optionally, the third configuration information may also include a dedicated configuration of the remote UE.

[0047] For example, in this embodiment, the remote UE and the relay UE move out of the current cell and move to the new cell, and the remote UE obtains the third configuration information by reading the system message of the new cell. For another example, the remote UE and the relay UE move out of the current cell and move to the new cell, and the relay UE reads the system message of the new cell, and then sends the third configuration information to the remote UE through PC5 RRC based on the system message.

[0048] Case 3: Off-network remote UE L2 architecture

[0049] In this case 3, the remote UE is in an offline state before establishing the L2 relay architecture with the relay UE. The remote UE is in an offline state, that is, it cannot obtain any system messages and configuration information related to the sidelink / sidelink relay. In this case, the remote UE can determine the secondary link configuration in the secondary link relay architecture based on the pre-configured information, and the remote UE is also used to establish the L2 relay architecture with the relay terminal based on the pre-configured information. For example, the remote UE can use the pre-configured sidelink / sidelink relay parameters to perform a discovery process with the relay UE, and then establish the L2 relay architecture.

[0050] In L2 relay architecture operation, there are two ways to obtain the configuration information of the remote UE:

[0051] The first method is to determine the secondary link configuration in the secondary link relay architecture by receiving second configuration information from a network side device through an RRC process.

[0052] The second method is to receive first configuration information from the relay terminal through the PC5 RRC process to determine the secondary link configuration in the secondary link relay architecture.

[0053] Optionally, in the L2 relay architecture, the remote UE determines the sidelink radio bearer (SLRB) configuration, service data adaptation protocol (SDAP) configuration and packet data convergence protocol (PDCP) configuration of the sidelink transmission according to the second configuration information received in the RRC process. For example, the layer 3 related parameters such as SLRB, SDAP, PDCP, etc. are obtained by the remote UE from the network side through its own RRC process.

[0054] Optionally, in the L2 relay architecture, the remote UE determines the radio link control (RLC) bearer configuration of the secondary link transmission according to the second configuration information or the first configuration information. For example, for layer 2 related parameters such as RLC bearer, the remote UE can obtain them from the network side device through the RRC process, or from the relay UE through PC5 RRC.

[0055] In case 3, since the remote UE does not have any resident / serving cell before entering the relay operation, optionally, after the remote UE establishes an RRC connection with the network side device through the relay UE, the serving cell selected for the remote UE is the primary cell of the relay UE; or the serving cell selected for the remote UE belongs to the same network side device as the primary cell of the relayUE. For example, the serving cell of the remote UE is preferably a cell consistent with the primary cell (Pcell) of the relayUE, or it can be another cell under the same base station as the Pcell.

[0056] Case 4: Remote UE L2 architecture in the network

[0057] In case 4, the remote UE and the relay UE are in an idle state or a connected state before establishing the L2 relay architecture.

[0058] When the remote UE is in a normal cell resident state, it can obtain the system information configuration related to the sidelink / sidelink relay. In this case, the remote UE determines the sidelink configuration in the sidelink relay architecture according to the system message received from the resident cell or the serving cell, and the remote UE is also used to establish the L2 relay architecture with the relay UE according to the system message.

[0059] Or the remote UE is in a connected state and has obtained the dedicated configuration related to the sidelink / sidelink relay from its serving cell. In this case, the remote UE determines the secondary link configuration in the secondary link relay architecture according to the second configuration information (which may refer to the above-mentioned dedicated configuration) from the network side device, and the remote terminal is also used to establish the L2 relay architecture with the relay terminal according to the second configuration information.

[0060] When the remote UE meets the conditions for L2 relay operation and needs to perform L2 relay operation, there are two ways to obtain its configuration information:

[0061] First, in the L2 relay architecture, the remote UE continues to use the system message to determine the sidelink configuration in the sidelink relay architecture, for example, the remote UE continues to use the sidelink / sidelink relay parameters in the currently obtained system information.

[0062] The second type is that in the L2 relay architecture, the remote UE receives the second configuration information from the network side device through the RRC process to determine the sidelink configuration in the sidelink relay architecture. For example, the remote UE's own RRC process obtains relevant sidelink / sidelink relay parameters from the new service cell for use by the remote UE in the relay operation. In this example, if the remote UE has a dedicated configuration before the L2 relay architecture is established (that is, the remote UE is in a connected state before the L2 relay architecture is established), the remote UE can also decide whether to release the above dedicated configuration based on whether the service cell changes. For example, the above dedicated configuration is released when the service cell changes, and the second configuration information is obtained from the new service cell; when the service cell does not change, the above dedicated configuration can continue to be used.

[0063] In case 4, optionally, when the remote UE establishes an RRC connection with the network side device, the remote UE may also carry the remote UE's belonging information; wherein the belonging information includes at least one of the following of the remote terminal: resident cell information, sidelink system information acquisition status, and network disconnection status. In this way, the network side device can configure a secondary link configuration that is more suitable for the remote UE and the relay UE for the remote UE based on the remote UE's belonging information.

[0064] In case 4, optionally, the remote UE can also determine whether the system message or the second configuration information used in the first service cell is applicable to the second service cell; wherein the first service cell is the service cell before the remote terminal establishes the RRC connection, the second service cell is the service cell after the RRC connection, and the first service cell is the same as or different from the second service cell.

[0065] In situation 4, optionally, the remote UE may also send the service characteristics transmitted between the remote terminal and the relay terminal to the network side device, and the service characteristics are used by the network side device to configure wireless bearer information for the remote terminal; the remote UE may also receive the wireless bearer information and establish a wireless bearer based on the wireless bearer information, and the wireless bearer is used for the remote terminal to communicate with the relay terminal.

[0066] In situation 4, optionally, the remote UE may also send to the network side device the service characteristics transmitted between the remote terminal and the relay terminal, and the service characteristics are used by the network side device to configure dedicated resource information for the remote terminal; the remote UE may also receive the dedicated resource information and communicate with the relay terminal according to the dedicated resources indicated by the dedicated resource information.

[0067] Case 5: Dual-Connectivity (DC) / Carrier Aggregation (CA) Operation in L3 Relay Architecture

[0068] In the L3 relay architecture, the relay UE can be configured with CA and / or DC operation, while the remote UE only has a PC5 interface to communicate with the relay UE and there is no direct connection link with the network.

[0069] When the relay UE is configured for CA or DC operation, if the data radio bearer (DRB) / logical channel of the relay UE's Uu interface used to carry the remote UE data is not restricted by the network side configuration and cannot use CA operation, the DRB / logical channel of the remote UE's corresponding data can be transmitted in CA according to the existing principles and scheduling and logical channel priority rules.

[0070] If the DRB / logical channel of the Uu interface of the relay UE used to carry the remote UE data is configured as a main cell group (MCG) bearer or a secondary cell group (SCG) bearer or a split bearer, the DRB / logical channel of the corresponding data of the remote UE can perform relevant DC transmission operations according to existing principles.

[0071] In the PC5 interface, the transmission between the remote UE and the relay UE may also use multi-carrier transmission, which complies with the multi-carrier transmission rules of the PC5 interface and is independent of the CA / DC operation of the Uu interface of the relay UE.

[0072] Case 6: DC / CA operation in L2 relay architecture

[0073] In the L2 relay architecture, the relay UE can be configured with CA and / or DC operation. Since the remote UE has a logical L3 connection with the network and the PDCP anchor node is on the network side, the configuration of the DC's MCG / SCG will affect the security operation of the remote UE bearer.

[0074] When the relay UE is configured for CA or DC operation, if the RLC bearer of the Uu interface of the relay UE used to carry the remote UE data is not restricted by the network side configuration to not use CA operation, the RLC bearer of the corresponding data of the remote UE can perform CA transmission according to the existing principles and scheduling and logical channel priority rules.

[0075] If the RLC bearer of the Uu interface of the relay UE used to carry the remote UE data is configured as an MCG bearer, an SCG bearer, or a split bearer, the RLC bearer of the corresponding data of the remote UE can perform relevant DC transmission operations according to existing principles.

[0076] The CA operation of the Uu interface of the relay UE does not affect the remote UE, because there is only one service node and only one set of PDCP security keys is used. However, when the Uu interface of the relay UE is configured with DC operation, if the RLC bearer used by the Uu interface of the relay UE to carry the remote UE data is configured as an MCG bearer, SCG bearer or splitbearer, the PDCP entity corresponding to the remote UE uses different keys, MCG key or SCG key, depending on the final data anchor point.

[0077] Based on the introduction of the above situation 5 and situation 6, optionally, each of the above embodiments may further include the following steps: performing multi-carrier sublink transmission with the relay terminal (PC5 interface). Optionally, the Uu interface between the relay terminal and the network side device is configured with carrier aggregation CA or dual connection DC.

[0078] Optionally, the remote UE may also perform CA duplication transmission on a target service between the remote UE and the relay terminal, wherein the CA duplication transmission on the target service is:

[0079] 1) Directly configured for the remote terminal. For example, in an L2 relay architecture, the remote UE reports the service demand to the network, and the network configures the bearer and directly instructs the bearer to perform CA repeated transmission.

[0080] 2) When the remote terminal reports the quality of service (QoS) of the target service, the network side device configures the secondary link radio bearer SLRB corresponding to the target service. For example, the remote UE reports its own service QoS, the network side configures the mapping relationship between SLRB and QoS flow, and configures whether the SLRB is Duplication. Of course, in this example, the SLRB corresponding to the target service is configured with repeated transmission.

[0081] 3) The QoS profile used by the target service has the CA retransmission function enabled. For example, the network-side device configures QoS profile 1 to not enable the CA retransmission function; QoS profile 2 to enable the CA retransmission function; QoS profile 2 to enable the CA retransmission function, etc. For example, the service QoS profile of the remote UE is QoS Profile 2, and the CA retransmission function is enabled for the service according to the network-side configuration. In this example, the QoS profile used by the target service has the CA retransmission function enabled.

[0082] 4) The QoS feature configuration of the target service enables the CA duplication function. For example, if the packet delay budget (PDB) of the service configured on the network side is less than X and the block error rate (BLER) is less than Y, the CA duplication function is enabled. In this example, the PDB of the target service is less than X and the BLER is less than Y.

[0083] Optionally, at the PC5 interface, multiple RLC bearers used by the remote UE to transmit repeated data are respectively configured with different component carrier (CC) subsets (Component Carrier).

[0084] Optionally, when dual connection is configured on the Uu interface between the relay terminal and the network side device:

[0085] 1) The remote terminal uses a set of security parameters, and multiple data radio bearers (DRBs) of the remote terminal correspond to one network device; or

[0086] 2) The multiple DRBs of the remote terminal use multiple sets of security parameters.

[0087] To explain in detail the configuration method in the secondary link relay architecture provided in the embodiment of the present application, several specific embodiments will be described below.

[0088] Embodiment 1 of the present invention: Configuration acquisition of L3 architecture remote UE

[0089] In the L3 architecture, there is no direct logical connection between the remote UE and the network side device (hereinafter referred to as the network), that is, the PC5 interface and the Uu interface are relatively independent. The remote UE performs relay operations smoothly and does not affect the remote UE's resident status or serving cell.

[0090] In the L3 architecture, the remote UE obtains the configuration related to the relay operation mainly from the following channels:

[0091] First, pre-configuration information;

[0092] The second is the system message read by the remote UE from the camping cell or serving cell;

[0093] Third, the remote UE receives configuration information from the relay UE through PC5 RRC.

[0094] In an example, if the remote UE is in an offline state, that is, it cannot obtain any relevant system information about the sidelink / sidelink relay, then the remote UE performs sidelink or sidelink relay operations, such as the discovery process, and various types of (unicast / multicast / broadcast / relay operations) reception and transmission, all of which use pre-configuration information. The pre-configuration information generally includes general configurations, or configuration information that is valid based on a certain location area.

[0095] The remote UE can use the above pre-configuration information in the discovery process and the subsequent relay communication process, which does not introduce additional signaling overhead. However, considering the lack of configuration negotiation between the remote UE and the relay UE, for example, it is impossible to know exactly what resources or parameters the other party uses, and only blind detection can be performed within a large range, and the communication efficiency is not high.

[0096] Optionally, when the remote UE completes the discovery process with the relay UE using pre-configured information, the remote UE can inform the relay UE of its own resident cell / sidelink system information acquisition status / offline information during the discovery process. The relay UE requests relevant configuration of the relay operation from its own serving cell. The requested information may also carry information such as the resident cell / sidelink system information acquisition status / offline information of the remote UE. For example, the sidelink / relay system information configuration or offline status can be obtained from cell1.

[0097] The purpose of carrying the above additional information in the request information is to enable the network side to configure a configuration that better matches the existing configuration of the remote UE, to perform dedicated configuration for the relay UE, and optionally to be used for the network side to send configuration to the remote UE. The relay UE forwards these configurations to the remote UE through the PC5 RRC, for example, it can be a dedicated resource for the remote UE. In other implementations, the above additional information may not be carried on the Uu interface of the relay UE, and the relayUE directly sends the sidelink / relay information in the SIB that it can receive to the remote UE through the PC5 RRC, or organizes new configuration information to the remote UE based on the sidelink-related configuration it has received, so as to facilitate communication between the two. Specifically, for example, if the network side configures dedicated resources for the relay UE, such as a dedicated resource pool or periodic dedicated resources, or a multi-carrier configuration, the relay UE can notify the remote UE on the PC5 interface, so that the remote UE can receive these resources more efficiently.

[0098] In another example, if the remote UE is in an idle state, it can obtain configuration information about the sidelink / sidelink relay from the system message, and use this information to perform a discovery process with the relay UE. In the subsequent relay communication process, the remote UE can also continue to use this public configuration information.

[0099] Optionally, during the discovery process, the remote UE may inform the relay UE of the status of obtaining its own resident cell / sidelink system information. The relay UE requests relevant configurations about the relay operation from its own serving cell. The requested information may also carry the status of obtaining the remote UE's resident cell / sidelink system information, for example, the sidelink / relay system information configuration or configuration information identifier can be obtained from cell1.

[0100] The purpose of carrying the above additional information in the request information is to enable the network side to configure a configuration that is more compatible with the existing configuration of the remote UE, to perform a dedicated configuration for the relay UE, and optionally to enable the network side to send a dedicated configuration to the remote UE. The relay UE forwards these configurations to the remote UE through the PC5 RRC, for example, it can be a dedicated resource for the remote UE. In other implementations, the above additional information may not be carried on the Uu interface of the relay UE, and the relay UE organizes the PC5 configuration information to the remote UE based on the sidelink-related configuration it receives, so as to facilitate communication between the two.

[0101] In another example, if the remote UE is in a connected state, then regardless of whether the core network uses the non-3GPP interworking function (N3IWF), the remote UE in the L3 architecture does not have an RRC connection for access network nodes, such as CU (central unit) or gNB. Therefore, when the remote UE is in a connected state and needs to continue data transmission in the relay architecture, it is equivalent to the remote UE first releasing the existing connection, entering the idle state, and then establishing a relay connection. That is, the remote UE first releases the existing sidelink dedicated configuration, and then, as described above, establishes a relay connection from the idle state.

[0102] It should be noted that in the L3 relay architecture, since the remote UE has no connection to the network side, there is no concept of a remote UE connected service cell. If the remote UE receives a dedicated configuration forwarded by the relay UE, it is also a dedicated configuration allocated by the network side for the PC5 link between the remote UE and the relay UE in order to bind the remote UE and the relay UE. These dedicated configurations become invalid once the relay UE moves out of the current cell, and need to be reconfigured in the new cell, or the configuration of the source cell is carried in the handover request message between the source node and the target node interface, and the target cell reconsiders the configuration under itself and sends it to the relay UE through a handover command, and then forwards it to the remote UE.

[0103] Embodiment 2 of the present invention: L2 architecture remote UE configuration acquisition

[0104] In the L2 architecture, there is a direct logical connection between the remote UE and the network. The RRC / SDAP / PDCP entity counterpart of the remote UE is located on the network side, such as a base station or CU. Data transmission from the remote UE to the network is transmitted through two RLC bearers, PC5 and Uu. The remote UE needs a connected serving cell for relay operations.

[0105] In the L2 architecture, the remote UE obtains the configuration related to the relay operation mainly from the following channels:

[0106] The first is pre-configuration information (mainly used before relay connection);

[0107] The second is the system message read by the remote UE from the camping cell or serving cell;

[0108] Third, the remote UE receives configuration information from the network side through Uu RRC.

[0109] For the remote UE in the L2 relay architecture, there are mainly two stages: the first stage is before the RRC connection is established between the relay UE and the network side; the second stage is after the RRC connection is established between the relay UE and the network side.

[0110] In the first stage, the remote UE needs some basic configurations for sidelink relay operation, such as explicit indication of support for L2 relay architecture, conditions for L2 relay operation (such as RSRP thresholds or service requirements), and basic sidelink configurations, such as common resource pools and common PC5 configurations. These configurations can be obtained as follows:

[0111] 1. For a remote UE that is offline, the above two types of information are obtained through a pre-configuration message;

[0112] 2. For the remote UE in idle state, the above two types of information are obtained by reading the SIB message;

[0113] 3. For the remote UE in the connected state, the common information part of the above two types of information can be obtained through the SIB message, or the network side can further configure some dedicated configurations, such as a dedicated RSRP threshold.

[0114] The Remote UE uses these two types of basic configuration information. Based on this information, when it determines that it meets the conditions for relay operation, it initiates a discovery process to the relay UE and then establishes a relay connection.

[0115] In the second stage, after the remote UE establishes an RRC connection with the network side through the relay UE, the remote UE is equivalent to entering the RRC connection state. After entering the RRC connection state, the following process is performed through the RRC process of the remote UE.

[0116] For example, the Remote UE can report the service characteristics transmitted between itself and the relay UE, such as QoS profile, to the serving cell; the serving cell configures SLRB and RLC bearer for the remote UE based on the service information; the Remote UE receives the SLRB and RLC bearer from the serving cell, establishes the corresponding bearer, and conducts PC5 communication with the relay UE.

[0117] For another example, the Remote UE may also report the characteristics of the service, such as period and transmission size; the serving cell configures dedicated periodic resources for the remote UE based on this information, such as configured grant type 1 resources, and / or configured grant type 2 resources, or other types of dedicated resources, such as a dedicated resource pool; the Remote UE receives the dedicated resources and configuration from the serving cell, and uses the relevant resources and configuration to communicate with the PC5 of the relay UE.

[0118] In addition, the serving cell of the remote UE after the RRC connection is established with the network side through the relay UE may be different from the serving cell before the RRC connection is established with the network side through the relay UE.

[0119] For example, before the remote UE establishes the relay connection, it resides in cell1 under gNB1 in idle state. Since the service cell of the relay UE is cell2 under the same gNB1, for the convenience of management, the service cell of the remote UE after the relay connection is established is also determined to be cell2 under gNB1. At this time, the remote UE has the sidelink / sidelink relay public configuration in the SIB message of cell1, but not the sidelink / sidelink relay public configuration in the SIB message of cell2. This will cause the remote UE to use wrong configuration information for relay operation under cell2, unless the configuration is coordinated in advance between the cells to ensure that the system configuration under cell1 can also work in cell2. If cell2 is a cell under gNB2 across base stations, the probability of using wrong configuration information is even greater.

[0120] For another example, before establishing the relay connection, the remote UE is in an offline state and has only the pre-configured sidelink / sidelink relay public configuration information. Since the serving cell of the relay UE is cell2 under gNB1, for the convenience of management, the serving cell of the remote UE after the relay connection is established is also determined to be cell2 under gNB1. At this time, the remote UE has the sidelink / sidelink relay public configuration in the pre-configuration message, but not the sidelink / sidelink relay public configuration in the SIB message of cell2. This will cause the remote UE to use incorrect configuration information for relay operations under cell2, unless configuration coordination is performed in advance to ensure that the pre-configured system configuration can also work in cell2.

[0121] The methods to solve the above-mentioned use of incorrect configuration information are as follows:

[0122] Method 1: When the remote UE establishes an RRC connection to the base station, it carries its own belonging information, such as the offline status, the previous resident cell information, or the cell information of the sidelink / sidelink relay SIB message previously read, or even the identifier or version information of the specific sidelink / sidelink relay message. The belonging information can be carried in the RRC connection establishment request or completion message, or in a special message.

[0123] When the network side receives the relevant attribution information, it can know whether the sidelink / relay public information currently used by the remote UE is applicable to this relay operation. If not, new sidelink / relay configuration information is sent to the remote UE through the RRC message, and this configuration information will overwrite the original configuration information of the remote UE.

[0124] If the cell where the remote UE resides and the new cell after the relay connection is established are the same cell, the network side does not need to send common configuration information, and the remote UE can continue to use the previous configuration information.

[0125] Method 2: The network side uses a dedicated configuration or identifier to inform the remote UE which configuration information can be used universally and which cannot be used universally.

[0126] For example, in the pre-configuration information previously obtained by the remote UE or the SIB information of cell1, it can be clearly indicated whether it is universal. If it is universal, the remote UE does not need to request sidelink / relay configuration when establishing a connection with the network side through the relay UE. If it is not universal, the remote UE needs to re-request the configuration. The request information can be carried in the RRC connection establishment request or completion message, or a special message.

[0127] In particular, before the remote UE establishes the relay connection, it is in the connected state, and after the relay connection is established, it is also in the connected state. This process is similar to the terminal handover process. When the previous serving cell and the relay UE serving cell are the same cell, it is similar to intra cell handover, and the sidelink / relay public and dedicated configuration information can continue to be used; when the previous serving cell and the relay UE serving cell are different cells under the same base station, it is similar to intercell intra-gNB / CU handover, and the sidelink / relay public and dedicated configuration information can be reconfigured or continued to be used; when the previous serving cell and the relay UE serving cell are different cells under different base stations, it is similar to inter-gNB / CU handover, and the sidelink / relay public and dedicated configuration information need to be reconfigured. The source configuration information and the target configuration information are carried in the handover request message and the handover response message of the interface negotiation process between base stations, respectively.

[0128] Embodiment 3 of the present invention: DC / CA operation in L3 architecture

[0129] In the L3 architecture, the protocol stack entities corresponding to the remote UE are terminated at the relay UE, and there is no logical connection or entity between the remote UE and the gNB. Therefore, the DC / CA operation of the relay UE has little impact on it.

[0130] From the perspective of the Uu interface of the relay UE, the DRB bearer of the Uu interface of the relay UE can be divided into two categories: one is the relay UE's own data, and the other is the remote UE's data. These two types of data can be carried by different DRBs / RLC bearers / logical channels to facilitate data retransmission and state transfer in various switching scenarios. For example, the relay UE's own data is carried in DRBs 0-7, and DRBs 8-15 are the bearers of the remote UE data on the Uu interface of the relay UE. Among them, the data bearers of different remote UEs connected to the same relay UE can be independent DRBs or multiplexed DRBs.

[0131] If the relay UE is configured with CA operation, that is, the relay UE is on the Uu interface, multiple carriers can be used for transmission. In the case of multiple carriers, optional carrier restriction can be configured, that is, the set of CCs that a specific logical channel / RLC bearer can use. This carrier restriction is generally used when the duplication function is enabled. When logical channel 1 and logical channel 2 are two duplicated logical channels corresponding to a DRB, in order to ensure the duplication effect and avoid duplicate data transmission on the same CC and lose duplication gain, logical channel 1 can be restricted to upload on CC1 and CC2, and logical channel 2 can be restricted to upload on CC3, CC4 and CC5.

[0132] Similarly, similar carrier restrictions can also be used to restrict the transmission of the logical channel corresponding to the remote UE data, to avoid the Uu interface data rate being too fast and the PC5 interface rate being too slow, resulting in rate mismatch, packet loss and resource waste. Of course, no restrictions need to be configured, which is equivalent to the logical channel corresponding to the remote UE data being able to use the current CC at will.

[0133] If the relay UE is configured for DC operation, each bearer of the Uu interface of the relay UE can be individually configured as MCG bearer / SCG bearer / split bearer. The bearer of the relay UE corresponding to the remote UE data can also be configured in the same way and a bearer type can be selected.

[0134] In particular, if a data type of a remote UE has very high QoS requirements, such as extremely low latency and / or extremely high reliability requirements, you can consider configuring duplication transmission for this service on the Uu interface and performing CA or DC duplication transmission.

[0135] From the perspective of the PC5 interface between the relay UE and the remote UE: Since the PC5 interface and the Uu interface are relatively independent, the CA / DC configured on the Uu interface has basically no effect on the PC5. However, from the perspective of rate matching, once the Uu interface is configured with CA / DC, the data rate of the remote UE is increased on the Uu interface. In order to match the PC5 interface and avoid timeout packet loss and resource waste, multi-carrier sidelink transmission can also be performed on the PC5 interface.

[0136] When a service type of the remote UE has very high QoS requirements, such as very low latency and / or very high reliability requirements, you can consider configuring duplication transmission for this service on the PC5 interface and performing CA duplication transmission. The CA duplication configuration of the PC5 interface can be configured together with the CA / DC duplication mechanism of the Uu interface, or the two can be configured separately.

[0137] Embodiment 4 of the present invention: L2 architecture DC / CA operation

[0138] In the L2 architecture, the L2 protocol stack entity corresponding to the remote UE is terminated in the relay UE, while the peer entities of the L3 protocol are all located in the gNB / CU. Therefore, the CA / DC of the Uu interface of the relay UE has a certain impact on the remote UE.

[0139] The RLC bearer of the Uu interface of the relay UE can be divided into two categories: one is the relay UE's own data, and the other is the remote UE's data. Generally speaking, these two types of data need to be carried by different RLC bearers / logical channels to facilitate data retransmission and status transfer in various switching scenarios. For example, the relay UE's own data is carried in RLCbearer / LCID 0-7, and RLC bearer / LCID 8-15 is the bearer of the remote UE data on the Uu interface of the relay UE. Among them, the data bearers of different remote UEs connected to the same relay UE can be independent RLC bearers / LCIDs, or multiplexed RLC bearers / LCIDs.

[0140] When the relay UE is configured with CA: for the RLC bearer / LCID corresponding to the remote UE data, it is possible to configure whether these RLC bearers / LCIDs are allowed to be transmitted on all CCs or only on some CCs, that is, a CC subset can be configured to limit the RLC bearer / LCID corresponding to the remote UE data. If the restriction information does not exist, it means that any CC can be used to transmit the remote UE data.

[0141] On the PC5 interface, the corresponding RLC bearer can also perform multi-carrier transmission to achieve the effect of rate matching. For example, if the same bearer is transmitted in CA mode on the Uu interface, the rate can reach 100Mbps, but only single-carrier transmission on the PC5 interface has a rate of only 20Mbps, which will cause downlink data to accumulate in the relay UE and then be deleted, wasting Uu interface transmission resources. At this time, if the PC5 interface also supports multi-carrier transmission and the rate reaches 100Mbps, it can perform rate matching well and improve transmission efficiency.

[0142] In particular, when the remote UE service QoS requirements are high, such as very high latency requirements and / or very high reliability requirements, one or more of the following configurations can be performed:

[0143] On the Uu interface, the CA duplication function is configured for the RLC bearer of the remote UE, that is, the two RLC bearers transmitting duplicate data are configured with different CC subsets for duplication transmission. The same data is transmitted simultaneously on CCsubset1 and CC subset2 to obtain higher reliability and latency indicators. The CA duplication of the Uu interface is configured and controlled by the base station.

[0144] On the PC5 interface, the CA duplication function is configured for the RLC bearer of the remote UE, that is, the two RLC bearers transmitting duplicate data are configured with different CC subsets for duplication transmission. The same data is transmitted simultaneously on CCsubset1 and CC subset2 to obtain higher reliability and latency indicators. The CA duplication of the PC5 interface is controlled by the PC5 RRC configuration and PC5 MAC. The controlling node can be the relay UE or the transmitting UE of the PC5 interface.

[0145] In the case where the relay UE is configured with DC: the biggest impact of the DC operation on the remote UE is the difference in security parameters. If the remote UE's DRB is terminated at MCG, the DRB needs to use MCG security parameters, such as key and / or security algorithm, etc. If the remote UE's DRB is terminated at SCG, the DRB needs to use SCG security parameters. This embodiment can process security parameters in the following manner:

[0146] First, all DRBs of the remote UE can only be terminated at one node, MCG or SCG, so that the remote UE only needs to obtain a set of security parameters; and different remote UEs connected to a relay UE can be distinguished, some terminated at MCG and others terminated at SCG, which also plays a role in data diversion and has less impact on the remote UE.

[0147] Second, the remote UE can use two or more sets of security parameters (such as dual connections or multi-connections) and explicitly configure the security parameters used by each DRB of the remote UE, MCG or SCG, so that the remote UE uses different security parameters for different DRBs. However, the remote PC5 interface does not have multi-link operation at the bottom layer, that is, it is still a MAC entity, and the existing signaling configuration needs to be enhanced.

[0148] For the Uu interface, the Uu RLC bearer of the relay UE corresponding to the remote UE data can choose different paths: one is the MCG bearer, which is equivalent to the RLC bearer directly transmitting from the relay UE to the MCG; the second is the SCGbearer, which is equivalent to the RLC bearer directly transmitting from the relay UE to the SCG; the third is the split bearer, which is equivalent to the RLC bearer being transmitted from the relay UE to both the MCG and the SCG, which is equivalent to both legs being used, and the transmission rate is higher; the split RLC bearer will also select a node for data aggregation, reorder the data transmitted by the two legs according to the SN order, and submit them to the core network in sequence. The data aggregation node is configurable. When the data aggregation node is MCG, the bearer uses the MCG security parameters, and when the data aggregation node is SCG, the bearer uses the SCG security parameters.

[0149] Similarly, when the relay UE is configured with DC, the Uu interface can also be configured with the DC duplication mechanism, that is, in the split bearer configuration, duplicate data can be transmitted on the two legs to achieve high reliability and low latency requirements. DC duplication can be configured and activated for the remote UE data on the Uu interface. Correspondingly, on the PC5 interface, CA duplication can be configured and enabled to meet this requirement. The two legs can be configured independently or together.

[0150] In addition, when DC split transmission is performed on the Uu interface, because the data rates of the two nodes are increased, CA transmission can also be enabled on the PC5 interface for the purpose of rate matching.

[0151] Figure 4 is a schematic diagram of the structure of a remote terminal according to an embodiment of the present application, such as Figure 4 As shown, the remote terminal 400 includes:

[0152] The determination module 402 can be used to determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; system message received from the resident cell or the serving cell; first configuration information from the relay terminal; second configuration information from the network side device.

[0153] In the embodiment of the present application, the remote terminal can determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; system message received from the resident cell or the serving cell; first configuration information from the relay terminal; second configuration information from the network side device. The embodiment of the present application facilitates the consistency of understanding between the remote terminal, the relay terminal and the network side, thereby improving the effectiveness of communication.

[0154] Optionally, as an embodiment, before determining the secondary link configuration in the secondary link relay architecture, the remote terminal is in an offline state, wherein the determining module 402 is used to:

[0155] Determine the secondary link configuration in the secondary link relay architecture according to the pre-configuration information, and the remote terminal is further used to establish an L3 relay architecture with the relay terminal according to the pre-configuration information;

[0156] In the L3 relay architecture, continue to use the pre-configuration information to determine the secondary link configuration in the secondary link relay architecture; or, receive the first configuration information from the relay terminal through the PC5 radio resource control RRC process to determine the secondary link configuration in the secondary link relay architecture.

[0157] Optionally, as an embodiment, before determining the secondary link configuration in the secondary link relay architecture, the remote terminal is in an idle state or a connected state, wherein the determining module 402 is used to:

[0158] Determine the secondary link configuration in the secondary link relay architecture according to the system message or the second configuration information from the network side device, and the remote terminal is further used to establish an L3 relay architecture with the relay terminal according to the system message or the second configuration information;

[0159] In the L3 relay architecture, continue to use the system message or the second configuration information to determine the secondary link configuration in the secondary link relay architecture; or, receive the first configuration information from the relay terminal through the PC5 RRC process to determine the secondary link configuration in the secondary link relay architecture.

[0160] Optionally, as an embodiment, before determining the secondary link configuration in the secondary link relay architecture, the remote terminal is in an offline state, wherein the determining module 402 is used to:

[0161] Determine the secondary link configuration in the secondary link relay architecture according to the pre-configuration information, and the remote terminal is further configured to establish an L2 relay architecture with the relay terminal according to the pre-configuration information;

[0162] In the L2 relay architecture, the sub-link configuration in the sub-link relay architecture is determined by receiving the second configuration information from the network side device through the RRC process; or, the sub-link configuration in the sub-link relay architecture is determined by receiving the first configuration information from the relay terminal through the PC5 RRC process.

[0163] Optionally, as an embodiment, before determining the secondary link configuration in the secondary link relay architecture, the remote terminal is in an idle state or a connected state, wherein the determining module 402 is used to:

[0164] Determine the secondary link configuration in the secondary link relay architecture according to the system message or the second configuration information from the network side device, and the remote terminal is further used to establish an L2 relay architecture with the relay terminal according to the system message or the second configuration information;

[0165] In the L2 relay architecture, continue to use the system message to determine the secondary link configuration in the secondary link relay architecture; or, receive the second configuration information from the network side device through the RRC process to determine the secondary link configuration in the secondary link relay architecture.

[0166] Optionally, as an embodiment, the remote terminal 400 further includes:

[0167] A sending module, used for sending the service characteristics transmitted between the remote terminal and the relay terminal to the network side device, wherein the service characteristics are used by the network side device to configure radio bearer information for the remote terminal;

[0168] The receiving module is used to receive the radio bearer information and establish a radio bearer according to the radio bearer information, wherein the radio bearer is used for the remote terminal to communicate with the relay terminal.

[0169] Optionally, as an embodiment, the remote terminal 400 further includes:

[0170] A sending module, used for sending the service characteristics transmitted between the remote terminal and the relay terminal to the network side device, wherein the service characteristics are used by the network side device to configure dedicated resource information for the remote terminal;

[0171] The receiving module is used to receive the dedicated resource information and communicate with the relay terminal according to the dedicated resources indicated by the dedicated resource information.

[0172] Optionally, as an embodiment, the remote terminal 400 performs multi-carrier sub-link transmission with the relay terminal.

[0173] Optionally, as an embodiment, the Uu interface between the relay terminal and the network side device is configured with carrier aggregation CA or dual connection DC.

[0174] Optionally, as an embodiment, the target service between the remote terminal and the relay terminal performs CA duplication transmission, wherein the target service performs CA duplication transmission:

[0175] Directly configured for the remote terminal;

[0176] In the case where the remote terminal reports the quality of service QoS of the target service, the network side device configures the SLRB corresponding to the target service;

[0177] The QoS configuration used by the target service has the CA repeated transmission function enabled;

[0178] The QoS feature configuration of the target service enables the CA repeated transmission function.

[0179] Optionally, as an embodiment, the remote terminal configures different carrier component CC subsets for each of the multiple RLC bearers used to transmit repeated data.

[0180] Optionally, as an embodiment, when a dual connection is configured on a Uu interface between the relay terminal and the network side device:

[0181] The remote terminal uses a set of security parameters, and multiple data radio bearers (DRBs) of the remote terminal correspond to one network device; or

[0182] The multiple DRBs of the remote terminal use multiple sets of security parameters.

[0183] According to the embodiment of the present application, the remote terminal 400 can refer to the process of the method 200 corresponding to the embodiment of the present application, and the various units / modules in the remote terminal 400 and the above-mentioned other operations and / or functions are respectively for implementing the corresponding processes in the method 200, and can achieve the same or equivalent technical effects. For the sake of brevity, they will not be repeated here.

[0184] The remote terminal in the embodiment of the present application may be a terminal, or a component, integrated circuit, or chip in the terminal. The device may be a mobile terminal or a non-mobile terminal. For example, the mobile terminal may include but is not limited to the types of terminals 11 listed above, and the non-mobile terminal may be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which are not specifically limited in the embodiment of the present application.

[0185] The remote terminal in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0186] The remote terminal provided in the embodiment of the present application can achieve Figure 2 The various processes implemented by the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0187] Optional, such as Figure 5 As shown, an embodiment of the present application also provides a communication device 500, including a processor 501, a memory 502, and a program or instruction stored in the memory 502 and executable on the processor 501. For example, when the communication device 500 is a remote terminal, the program or instruction is executed by the processor 501 to implement the various processes of the configuration method embodiment in the above-mentioned sub-link relay architecture, and can achieve the same technical effect.

[0188] Figure 6 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0189] The terminal 600 includes but is not limited to: a radio frequency unit 601, a network module 602, an audio output unit 603, an input unit 604, a sensor 605, a display unit 606, a user input unit 607, an interface unit 608, a memory 609, and a processor 610.

[0190] Those skilled in the art will appreciate that the terminal 600 may also include a power source (such as a battery) for supplying power to various components, and the power source may be logically connected to the processor 610 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Figure 6 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0191] It should be understood that in the embodiment of the present application, the input unit 604 may include a graphics processor (Graphics Processing Unit, GPU) 6041 and a microphone 6042, and the graphics processor 6041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 606 may include a display panel 6061, and the display panel 6061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 607 includes a touch panel 6071 and other input devices 6072. The touch panel 6071 is also called a touch screen. The touch panel 6071 may include two parts: a touch detection device and a touch controller. Other input devices 6072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0192] In the embodiment of the present application, the radio frequency unit 601 receives downlink data from the network side device and sends it to the processor 610 for processing; in addition, the uplink data is sent to the network side device. Generally, the radio frequency unit 601 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0193] The memory 609 can be used to store software programs or instructions and various data. The memory 609 can mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 609 can include a high-speed random access memory, and can also include a non-volatile memory, wherein the non-volatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage devices.

[0194] The processor 610 may include one or more processing units; optionally, the processor 610 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, etc., and the modem processor mainly processes wireless communications, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 610.

[0195] Among them, the processor 610 is used to determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; system message received from the resident cell or the serving cell; first configuration information from the relay terminal; second configuration information from the network side device.

[0196] In the embodiment of the present application, the remote terminal (such as terminal 600) can determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; system message received from the resident cell or the serving cell; first configuration information from the relay terminal; second configuration information from the network side device. The embodiment of the present application facilitates the consistency of understanding between the remote terminal, the relay terminal and the network side, thereby improving the effectiveness of communication.

[0197] The terminal provided in the embodiment of the present application implements each process of the configuration method embodiment in the above-mentioned secondary link relay architecture when executed, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0198] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the configuration method embodiment in the above-mentioned sub-link relay architecture is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0199] The processor may be a processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0200] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the various processes of the configuration method embodiment in the above-mentioned sub-link relay architecture, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0201] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0202] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0203] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0204] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A configuration method in a secondary link relay architecture, applied to a remote terminal, characterized in that: The method comprises: Determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; a system message received from a resident cell or a serving cell; first configuration information from a relay terminal; second configuration information from a network side device; Before determining the sub-link configuration in the sub-link relay architecture, the remote terminal is in an offline state, wherein determining the sub-link configuration in the sub-link relay architecture according to at least one of the following includes: determining the sub-link configuration in the sub-link relay architecture according to the pre-configuration information, and the remote terminal is also used to establish an L3 relay architecture with the relay terminal according to the pre-configuration information; in the L3 relay architecture, continuing to use the pre-configuration information to determine the sub-link configuration in the sub-link relay architecture; or, receiving the first configuration information from the relay terminal through the PC5 wireless resource control RRC process to determine the sub-link configuration in the sub-link relay architecture; or, Before determining the sub-link configuration in the sub-link relay architecture, the remote terminal is in an idle state or a connected state, wherein determining the sub-link configuration in the sub-link relay architecture according to at least one of the following includes: determining the sub-link configuration in the sub-link relay architecture according to the system message or the second configuration information from the network side device, and the remote terminal is also used to establish an L3 relay architecture with the relay terminal according to the system message or the second configuration information; in the L3 relay architecture, continue to use the system message or the second configuration information to determine the sub-link configuration in the sub-link relay architecture; or, receive the first configuration information from the relay terminal through the PC5 RRC process to determine the sub-link configuration in the sub-link relay architecture; or, Before determining the sub-link configuration in the sub-link relay architecture, the remote terminal is in an offline state, wherein determining the sub-link configuration in the sub-link relay architecture according to at least one of the following includes: determining the sub-link configuration in the sub-link relay architecture according to the pre-configuration information, and the remote terminal is also used to establish an L2 relay architecture with the relay terminal according to the pre-configuration information; in the L2 relay architecture, receiving the second configuration information from the network side device through the RRC process to determine the sub-link configuration in the sub-link relay architecture; or, receiving the first configuration information from the relay terminal through the PC5 RRC process to determine the sub-link configuration in the sub-link relay architecture; or, Before determining the sub-link configuration in the sub-link relay architecture, the remote terminal is in an idle state or a connected state, wherein determining the sub-link configuration in the sub-link relay architecture according to at least one of the following includes: determining the sub-link configuration in the sub-link relay architecture according to the system message or the second configuration information from the network side device, and the remote terminal is also used to establish an L2 relay architecture with the relay terminal according to the system message or the second configuration information; in the L2 relay architecture, continue to use the system message to determine the sub-link configuration in the sub-link relay architecture; or, determine the sub-link configuration in the sub-link relay architecture by receiving the second configuration information from the network side device through the RRC process.

2. The method according to claim 1, characterized in that Before determining the secondary link configuration in the secondary link relay architecture, the remote terminal is in a connected state, wherein: In the L3 relay architecture, the remote terminal releases the RRC connection and uses the system message to determine the secondary link configuration in the secondary link relay architecture; or, receives the first configuration information from the relay terminal through the PC5 RRC process to determine the secondary link configuration in the secondary link relay architecture.

3. The method according to claim 1, characterized in that The method further comprises: During the discovery process with the relay terminal, first information is sent to the relay terminal, wherein the first information includes at least one of the following of the remote terminal: resident cell information, sidelink system information acquisition status, and network disconnection status; wherein the relay terminal is also used to send the first information to a network side device.

4. The method according to claim 1, characterized in that After determining the secondary link configuration in the secondary link relay architecture, the method further includes: Receive third configuration information, wherein the third configuration information is a configuration that the remote terminal re-obtains in a new cell when the relay terminal moves out of the current cell.

5. The method according to claim 1, characterized in that In the L2 relay architecture, The remote terminal determines, according to the second configuration information, a secondary link radio bearer SLRB configuration, a service data adaptation protocol SDAP configuration, and a packet data convergence protocol PDCP configuration of the secondary link transmission; The remote terminal determines the radio link control RLC bearer configuration of the secondary link transmission according to the second configuration information or the first configuration information.

6. The method according to claim 1, characterized in that After the remote terminal establishes an RRC connection with the network side device through the relay terminal, The serving cell selected for the remote terminal is a primary cell of the relay terminal; or The serving cell selected for the remote terminal and the primary cell of the relay terminal belong to the same network side device.

7. The method according to claim 1, characterized in that When the remote terminal establishes an RRC connection with the network side device, the remote terminal carries the attribution information of the remote terminal; wherein the attribution information includes at least one of the following of the remote terminal: resident cell information, sidelink system information acquisition status, and network disconnection status.

8. The method according to claim 1, characterized in that The method further comprises: Determine whether the system message or the second configuration information used in the first serving cell is applicable to the second serving cell; The first service cell is a service cell before the remote terminal establishes an RRC connection, the second service cell is a service cell after the RRC connection, and the first service cell is the same as or different from the second service cell.

9. The method according to claim 1, characterized in that: The method further comprises: Sending to the network side device a service characteristic transmitted between the remote terminal and the relay terminal, the service characteristic being used by the network side device to configure radio bearer information for the remote terminal; The radio bearer information is received, and a radio bearer is established according to the radio bearer information, where the radio bearer is used for the remote terminal to communicate with the relay terminal.

10. The method according to claim 1, characterized in that The method further comprises: Sending to the network side device service characteristics transmitted between the remote terminal and the relay terminal, the service characteristics being used by the network side device to configure dedicated resource information for the remote terminal; The dedicated resource information is received, and communication is performed with the relay terminal according to the dedicated resource indicated by the dedicated resource information.

11. The method according to claim 1, characterized in that: The method further comprises: Perform multi-carrier sublink transmission with the relay terminal.

12. The method according to claim 1 or 11, characterized in that: The Uu interface between the relay terminal and the network side device is configured with carrier aggregation CA or dual connection DC.

13. The method according to claim 1, characterized in that The method further comprises: Perform CA duplication transmission on the target service between the relay terminal, wherein the CA duplication transmission on the target service is: Directly configured for the remote terminal; In the case where the remote terminal reports the quality of service QoS of the target service, the network side device configures the SLRB corresponding to the target service; The QoS configuration used by the target service has the CA repeated transmission function enabled; The QoS feature configuration of the target service enables the CA repeated transmission function.

14. The method according to claim 1, characterized in that The multiple RLC bearers used by the remote terminal to transmit repeated data are respectively configured with different carrier component CC subsets.

15. The method according to claim 1, characterized in that When dual connection is configured on the Uu interface between the relay terminal and the network-side device: The remote terminal uses a set of security parameters, and multiple data radio bearers (DRBs) of the remote terminal correspond to one network device; or The multiple DRBs of the remote terminal use multiple sets of security parameters.

16. A remote terminal, characterized in that: include: A determination module, configured to determine a secondary link configuration in a secondary link relay architecture according to at least one of the following: pre-configuration information; A system message received from a resident cell or a serving cell; first configuration information from a relay terminal; and second configuration information from a network side device; Before determining the sub-link configuration in the sub-link relay architecture, the remote terminal is in an offline state, wherein the determination module is used to: determine the sub-link configuration in the sub-link relay architecture according to the pre-configuration information, and the remote terminal is also used to establish an L3 relay architecture with the relay terminal according to the pre-configuration information; in the L3 relay architecture, continue to use the pre-configuration information to determine the sub-link configuration in the sub-link relay architecture; or, receive the first configuration information from the relay terminal through the PC5 wireless resource control RRC process to determine the sub-link configuration in the sub-link relay architecture; or, Before determining the sub-link configuration in the sub-link relay architecture, the remote terminal is in an idle state or a connected state, wherein the determination module is used to: determine the sub-link configuration in the sub-link relay architecture according to the system message or the second configuration information from the network side device, and the remote terminal is also used to establish an L3 relay architecture with the relay terminal according to the system message or the second configuration information; in the L3 relay architecture, continue to use the system message or the second configuration information to determine the sub-link configuration in the sub-link relay architecture; or, receive the first configuration information from the relay terminal through the PC5 RRC process to determine the sub-link configuration in the sub-link relay architecture; or, Before determining the sub-link configuration in the sub-link relay architecture, the remote terminal is in an offline state, wherein the determination module is used to: determine the sub-link configuration in the sub-link relay architecture according to the pre-configuration information, and the remote terminal is also used to establish an L2 relay architecture with the relay terminal according to the pre-configuration information; in the L2 relay architecture, receive the second configuration information from the network side device through the RRC process to determine the sub-link configuration in the sub-link relay architecture; or, receive the first configuration information from the relay terminal through the PC5RRC process to determine the sub-link configuration in the sub-link relay architecture; or, Before determining the sub-link configuration in the sub-link relay architecture, the remote terminal is in an idle state or a connected state, wherein the determination module is used to: determine the sub-link configuration in the sub-link relay architecture according to the system message or the second configuration information from the network side device, and the remote terminal is also used to establish an L2 relay architecture with the relay terminal according to the system message or the second configuration information; in the L2 relay architecture, continue to use the system message to determine the sub-link configuration in the sub-link relay architecture; or, receive the second configuration information from the network side device through the RRC process to determine the sub-link configuration in the sub-link relay architecture.

17. The remote terminal according to claim 16, characterized in that: Also includes: A sending module, used for sending the service characteristics transmitted between the remote terminal and the relay terminal to the network side device, wherein the service characteristics are used by the network side device to configure radio bearer information for the remote terminal; The receiving module is used to receive the radio bearer information and establish a radio bearer according to the radio bearer information, wherein the radio bearer is used for the remote terminal to communicate with the relay terminal.

18. The remote terminal according to claim 16, characterized in that: Also includes: A sending module, used for sending the service characteristics transmitted between the remote terminal and the relay terminal to the network side device, wherein the service characteristics are used by the network side device to configure dedicated resource information for the remote terminal; The receiving module is used to receive the dedicated resource information and communicate with the relay terminal according to the dedicated resources indicated by the dedicated resource information.

19. The remote terminal according to claim 16, characterized in that: The remote terminal performs multi-carrier sub-link transmission with the relay terminal.

20. The remote terminal according to claim 16 or 19, characterized in that: The Uu interface between the relay terminal and the network side device is configured with carrier aggregation CA or dual connection DC.

21. The remote terminal according to claim 16, characterized in that: The target service between the remote terminal and the relay terminal performs CA duplication transmission, wherein the target service performs CA duplication transmission: Directly configured for the remote terminal; In the case where the remote terminal reports the quality of service QoS of the target service, the network side device configures the SLRB corresponding to the target service; The QoS configuration used by the target service has the CA repeated transmission function enabled; The QoS feature configuration of the target service enables the CA repeated transmission function.

22. The remote terminal according to claim 16, characterized in that: The multiple RLC bearers used by the remote terminal to transmit repeated data are respectively configured with different carrier component CC subsets.

23. The remote terminal according to claim 16, characterized in that: When dual connection is configured on the Uu interface between the relay terminal and the network-side device: The remote terminal uses a set of security parameters, and multiple data radio bearers (DRBs) of the remote terminal correspond to one network device; or The multiple DRBs of the remote terminal use multiple sets of security parameters.

24. A remote terminal, characterized in that: It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the configuration method in the secondary link relay architecture as described in any one of claims 1 to 15.

25. A readable storage medium, characterized in that: The readable storage medium stores a program or an instruction, and when the program or the instruction is executed by the processor, the configuration method in the secondary link relay architecture as described in any one of claims 1 to 15 is implemented.

Images