WO2022022550A1 - 副链路中继架构中的配置方法和终端 - Google Patents

副链路中继架构中的配置方法和终端 Download PDF

Info

Publication number
WO2022022550A1
WO2022022550A1 PCT/CN2021/108846 CN2021108846W WO2022022550A1 WO 2022022550 A1 WO2022022550 A1 WO 2022022550A1 CN 2021108846 W CN2021108846 W CN 2021108846W WO 2022022550 A1 WO2022022550 A1 WO 2022022550A1
Authority
WO
WIPO (PCT)
Prior art keywords
relay
secondary link
configuration
remote terminal
information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2021/108846
Other languages
English (en)
French (fr)
Inventor
刘佳敏
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vivo Mobile Communication Co Ltd
Original Assignee
Vivo Mobile Communication Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Vivo Mobile Communication Co Ltd filed Critical Vivo Mobile Communication Co Ltd
Priority to KR1020237004643A priority Critical patent/KR20230037611A/ko
Priority to PH1/2023/550104A priority patent/PH12023550104A1/en
Priority to JP2023504039A priority patent/JP7635362B2/ja
Priority to EP21850631.9A priority patent/EP4192073A4/en
Publication of WO2022022550A1 publication Critical patent/WO2022022550A1/zh
Priority to US18/152,936 priority patent/US20230144480A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/155—Ground-based stations
    • H04B7/15528—Control of operation parameters of a relay station to exploit the physical medium
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/02—Communication route or path selection, e.g. power-based or shortest path routing
    • H04W40/22—Communication route or path selection, e.g. power-based or shortest path routing using selective relaying for reaching a BTS [Base Transceiver Station] or an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W40/00—Communication routing or communication path finding
    • H04W40/24—Connectivity information management, e.g. connectivity discovery or connectivity update
    • H04W40/246—Connectivity information discovery
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W48/00—Access restriction; Network selection; Access point selection
    • H04W48/16—Discovering, processing access restriction or access information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/14—Direct-mode setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/04—Terminal devices adapted for relaying to or from another terminal or user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/18—Interfaces between hierarchically similar devices between terminal devices

Definitions

  • the present application belongs to the field of communication technologies, and in particular relates to a configuration method and a terminal in a secondary link relay architecture.
  • the Long Term Evolution (Long Term Evolution, LTE) system has supported a side link (sidelink) since the 12th release, which is used for direct data transmission between terminal devices without going through a network device.
  • sidelink side link
  • a sidelink relay architecture is proposed in related technologies.
  • the remote terminal sends its data to the network through the sidelink link (or relay link) between the remote terminal (remote UE) and the relay terminal (relay UE). device forwards.
  • the remote terminal can perform data transmission with the network device, and the relay terminal plays the role of data relay.
  • the purpose of the embodiments of the present application is to provide a configuration method and terminal in the secondary link relay architecture, which can solve the problem that the remote terminal cannot obtain the secondary link configuration in the secondary link relay architecture.
  • a first aspect provides a configuration method in a secondary link relay architecture, applied to a remote terminal, the method includes: determining a secondary link configuration in the secondary link relay architecture according to at least one of the following: Pre-configuration information; system messages received from the camping cell or serving cell; first configuration information from the relay terminal; second configuration information from the network side device.
  • a remote terminal including: 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 slave cell or a serving cell The received system message; the first configuration information from the relay terminal; the second configuration information from the network side device.
  • a terminal in a third aspect, includes a processor, a memory, and a program or instruction stored on the memory and executable on the processor, when the program or instruction is executed by the processor A method as described in the first aspect is implemented.
  • a readable storage medium is provided, and a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the method according to the first aspect is implemented.
  • a computer program product comprising a processor, a memory, and a program or instruction stored on the memory and executable on the processor, the program or instruction being executed by the The method as described in the first aspect is implemented when the processor executes.
  • a chip in a sixth aspect, includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is configured to run a program or an instruction to implement the method according to the first aspect .
  • the remote terminal may determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; system messages received from the camping cell or serving cell; The first configuration information of the relay terminal; the second configuration information from the network side device.
  • FIG. 1 is a block diagram of a wireless communication system according to an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a configuration method in a secondary link relay architecture according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of a relay architecture according to an embodiment of the present application.
  • FIG. 4 is a schematic structural diagram of a remote terminal according to an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a communication device according to an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of a terminal according to an embodiment of the present application.
  • first, second and the like in the description and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It is to be understood that the data so used are interchangeable under appropriate circumstances so that the embodiments of the present application can be practiced in sequences other than those illustrated or described herein, and "first”, “second” distinguishes Usually it is a class, and the number of objects is not limited.
  • the first object may be one or multiple.
  • “and/or” in the description and claims indicates at least one of the connected objects, and the character “/" generally indicates that the associated objects are in an "or” relationship.
  • LTE Long Term Evolution
  • LTE-Advanced LTE-Advanced
  • LTE-A Long Term Evolution-Advanced
  • CDMA Code Division Multiple Access
  • TDMA Time Division Multiple Access
  • FDMA Frequency Division Multiple Access
  • OFDMA Orthogonal Frequency Division Multiple Access
  • SC-FDMA Single-carrier Frequency-Division Multiple Access
  • system and “network” in the embodiments of the present application are often used interchangeably, and the described technology can be used not only for the above-mentioned systems and radio technologies, but also for other systems and radio technologies.
  • NR New Radio
  • the following description describes a New Radio (NR) system for example purposes, and uses NR terminology in most of the description below, although these techniques are also applicable to applications other than NR system applications, such as 6th generation (6 th Generation, 6G) communication system.
  • 6th generation 6 th Generation, 6G
  • FIG. 1 shows a block diagram of a wireless communication system to which the embodiments of the present application can be applied.
  • the wireless communication system includes a terminal 11 and a network-side device 12 .
  • the terminal 11 may also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 may be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital computer Assistant (Personal Digital Assistant, PDA), handheld computer, netbook, ultra-mobile personal computer (ultra-mobile personal computer, UMPC), mobile Internet device (Mobile Internet Device, MID), wearable device (Wearable Device) or vehicle-mounted device (VUE), pedestrian terminal (PUE) and other terminal-side devices, wearable devices include: bracelets, headphones, glasses, etc.
  • PDA Personal Digital Assistant
  • the network side device 12 may be a base station or a core network, wherein the base station may be referred to as a Node B, an evolved Node B, an access point, a Base Transceiver Station (BTS), a radio base station, a radio transceiver, a basic service Set (Basic Service Set, BSS), Extended Service Set (Extended Service Set, ESS), Node B, Evolved Node B (eNB), Next Generation Node B (gNB), Home Node B, Home Evolved Node B, WLAN Access point, WiFi node, 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 specific technical vocabulary. In the application embodiments, only the base station in the NR system is used as an example, but the specific type of the base station is not limited.
  • 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 implemented by software installed in the remote terminal or The hardware is implemented, and the method includes the following steps.
  • S202 Determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; system messages received from the residing cell or serving cell; first configuration information from the relay terminal; The second configuration information from the network side device.
  • data transmission can be performed between a remote terminal (remote UE) and a network device, and the relay terminal ( relay UE) plays the role of data relay; at the same time, the remote UE can also perform traditional secondary link transmission with the relay UE, and the transmission does not pass through the network equipment.
  • relay UE remote terminal
  • relay UE relay terminal
  • the relevant configuration of the secondary link transmission mentioned in the various embodiments of this application may include the relevant configuration required for establishing the secondary link relay architecture between the remote terminal and the relay terminal, and may also include the establishment of the secondary link relay architecture. After completion, the relevant configuration required for data transmission between the remote terminal and the relay terminal.
  • the remote terminal may determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; system messages received from the camping cell or serving cell; The first configuration information of the relay terminal; the second configuration information from the network side device.
  • the remote UE is offline before establishing the L3 relay architecture with the relay UE.
  • the remote UE cannot obtain any system messages and configuration information related to the sidelink/sidelink relay.
  • S202 can be :
  • the remote UE determines the secondary link configuration in the secondary link relay architecture according to the preconfigured information, and the remote UE is also used to establish an L3 relay architecture with the relay UE according to the preconfigured information.
  • 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.
  • the secondary link configuration in the secondary link relay architecture is determined by receiving the first configuration information from the relay terminal through the PC5 Radio Resource Control (RRC) process.
  • RRC Radio Resource Control
  • the relay UE sends the relevant sidelink/sidelink relay parameters to the remote UE through the PC5 RRC process for the remote UE to use in the relay operation.
  • the relay UE's own parameter information comes from the network side device, and the relayUE sends the first configuration to the remote UE.
  • the information can be determined by itself or can refer to the configuration information from the network side device.
  • the remote UE and the relay UE are in idle state or connected state before establishing the L3 relay architecture.
  • the remote UE When the remote UE is in the normal cell camping state, it can obtain the system information configuration related to the sidelink/sidelink relay. At this time, the remote UE can determine the secondary link configuration in the secondary link relay architecture according to the system information received from the cell. , the remote UE can also establish an L3 relay architecture with the relay terminal according to the above system message.
  • the remote UE is in the normal RRC connection state, and can obtain the dedicated configuration related to the sidelink/sidelink relay from its serving cell.
  • the remote UE may 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 may also be based on the second configuration information and The relay terminal establishes an L3 relay architecture.
  • the remote UE continues to use the sidelink/sidelink relay parameter in the currently obtained system information.
  • the secondary link configuration in the secondary link relay architecture is determined by receiving the first configuration information from the relay terminal through the PC5RRC process.
  • the relay UE sends the relevant sidelink/sidelink relay 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, and the relayUE sends the first configuration to the remote UE.
  • the information can be determined by itself or can refer to the configuration information from the network side device. .
  • the remote UE 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 (for example, release the dedicated configuration), and use the received system message to determine the secondary chain.
  • the secondary link configuration in the secondary link relay architecture is determined; or, the secondary link configuration in the secondary link relay architecture is determined by receiving the first configuration information from the relay terminal through the PC5RRC process.
  • the remote UE may also send first information to the relay UE during the PC5RRC process with the relay UE, for example, during the discovery process, where the first information includes at least one of the following: 1: The information about the camped-on cell, the information obtained by the sidelink system, and the situation of being disconnected from the network; wherein, the relay terminal is further configured to send the first information to the network side device.
  • the network side device can configure the remote UE with a secondary link configuration that is more suitable for the remote UE and the relay UE.
  • 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). ).
  • the method further includes: receiving third configuration information, wherein the third configuration The information is the configuration obtained by the remote UE 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.
  • This embodiment may be a configuration obtained by the remote UE in the new cell when the remote UE and the relay UE jointly move out of the current cell.
  • the remote UE can obtain the above-mentioned third configuration information through a system message (such as SIB) or through PC5 RRC.
  • the above-mentioned third configuration information can also include the dedicated configuration of the remote UE.
  • the remote UE and the relay UE jointly move out of the current cell and move to the new cell, and the remote UE obtains the above-mentioned third configuration information by reading the system message in the new cell.
  • the remote UE and the relay UE jointly move out of the current cell and move to the new cell, and the relay UE reads the system message under the new cell, and then sends the third configuration information to the remote UE through the PC5 RRC based on the above-mentioned system message.
  • the remote UE is offline before establishing the L2 relay architecture with the relay UE.
  • the remote UE is in an offline state, that is, it cannot obtain any sidelink/sidelink relay related system messages and configuration information.
  • the remote UE can determine the secondary link configuration in the secondary link relay architecture according to the pre-configured information.
  • the remote UE is also used to establish an L2 relay architecture with the relay terminal according to the pre-configuration information. For example, the remote UE can use the pre-configured sidelink/sidelink relay parameters to carry out the discovery process with the relay UE, and then establish the L2 relay architecture.
  • the secondary link configuration in the secondary link relay architecture is determined by receiving the second configuration information from the network side device through the RRC process.
  • the second is to determine the secondary link configuration in the secondary link relay architecture by receiving the first configuration information from the relay terminal through the PC5 RRC process.
  • the remote UE determines the secondary link radio bearer (Sidelink Radio Bearer, SLRB) configuration, service data adaptation protocol ( Service Data Adaptation Protocol (SDAP) configuration and Packet Data Convergence Protocol (PDCP) configuration.
  • SLRB Secondary Link Radio Bearer
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • the parameters related to layer 3 such as SLRB, SDAP, PDCP, etc., the remote UE obtains from the network side through its own RRC process.
  • the remote UE determines a radio link control (Radio Link Control, RLC) bearer (bearer) configuration for secondary link transmission according to the second configuration information or the first configuration information.
  • RLC Radio Link Control
  • the remote UE can be obtained from the network side device through the RRC process, or can be obtained from the relay UE through PC5 RRC.
  • the remote UE since the remote UE does not have any camping/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 remote UE selects the service
  • the cell is the primary cell of the relay UE; or the serving cell selected for the remote UE, and belongs to the same network side device as the primary cell of the relay UE.
  • the serving cell of the remote UE is preferably a cell consistent with the primary cell (Pcell) of the relay UE, or may be another cell under the same base station as the Pcell.
  • the remote UE and the relay UE are in idle state or connected state before establishing the L2 relay architecture.
  • the remote UE When the remote UE is in the normal cell camping state, the system information configuration related to the sidelink/sidelink relay can be obtained.
  • the remote UE determines the secondary link configuration in the secondary link relay architecture according to the system message received from the camping cell or the serving cell, and the remote UE is also used to establish L2 with the relay UE according to the system message. relay architecture.
  • the remote UE is in the connected state and has obtained the dedicated configuration related to sidelink/sidelink relay from its serving cell.
  • 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 for The second configuration information establishes an L2 relay architecture with the relay terminal.
  • the remote UE When the remote UE meets the conditions of L2 relay operation and needs to perform L2 relay operation, its configuration information can be obtained in two ways:
  • the remote UE continues to use the system message to determine the secondary link configuration in the secondary link relay architecture. For example, the remote UE continues to use the sidelink/sidelink/sidelink in the currently obtained system information. sidelink relay parameter.
  • the remote UE receives 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.
  • the relevant sidelink/sidelink relay parameters are obtained from the new serving cell by the RRC process of the remote UE itself, for the remote UE to use in the relay operation.
  • the remote UE can also decide whether to release the dedicated configuration according to whether the serving cell changes, for example , when the serving cell changes, the above-mentioned dedicated configuration is released, and the second configuration information is obtained from the new serving cell; when the serving cell does not change, the above-mentioned dedicated configuration can be continued to be used.
  • the remote UE when it establishes an RRC connection with the network side device, it may also carry the attribution information of the remote UE; wherein the attribution information includes at least one of the following of the remote terminal : Information about the camped cell, information about the sidelink system, and status of disconnection.
  • the network side device can configure the secondary link configuration more suitable for the remote UE and the relay UE for the remote UE based on the attribution information of the remote UE.
  • the remote UE may further determine whether the system message or the second configuration information used in the first serving cell is applicable to the second serving cell; wherein the first serving cell is the The serving cell before the remote terminal establishes the RRC connection, the second serving cell is the serving cell after the RRC connection, and the first serving cell and the second serving cell are the same or different.
  • the remote UE may also send the service characteristics transmitted between the remote terminal and the relay terminal to the network side equipment, where the service characteristics are used for the network side equipment to be
  • the remote terminal configures radio bearer information; the remote UE can also receive the radio bearer information, and establish a radio bearer according to the radio bearer information, and the radio bearer is used for the remote terminal and the relay terminal to perform communication. communication.
  • the remote UE may also send the service characteristics transmitted between the remote terminal and the relay terminal to the network side equipment, where the service characteristics are used for the network side equipment to be
  • the remote terminal configures dedicated resource information; the remote UE may also receive the dedicated resource information, and communicate with the relay terminal according to the dedicated resource indicated by the dedicated resource information.
  • the relay UE can be configured with CA and/or DC operations, while the remote UE only has the PC5 interface to communicate with the relay UE, and there is no direct link with the network.
  • the relay UE When the relay UE is configured for CA or DC operation, if the Uu interface of the relay UE is used to carry the data radio bearer (DRB)/logical channel of the data of the remote UE
  • DRB data radio bearer
  • the DRB/logical channel of the corresponding data can perform CA transmission according to the existing principle, according to the scheduling and logical channel priority rules.
  • the DRB/logical channel of the Uu interface of the relay UE used to carry the data of the remote UE is configured as a primary cell group (MCG) bearer or a secondary cell group (SCG) bearer or a split bearer, in the DRB/logical channel of the corresponding data of the remote UE
  • MCG primary cell group
  • SCG secondary cell group
  • split bearer in the DRB/logical channel of the corresponding data of the remote UE
  • the logical channel may perform related DC transmission operations according to existing principles.
  • the transmission between the remote UE and the relay UE can also use multi-carrier transmission.
  • the multi-carrier transmission follows 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.
  • the relay UE can be configured with CA and/or DC operations, while the remote UE has a logical L3 connection with the network, and the PDCP anchor node (anchor) is on the network side, so the DC MCG/SCG configuration Will affect the security operation of the remote UE bearer.
  • the relay UE When the relay UE is configured for CA or DC operation, if the RLC bearer of the relay UE's Uu interface used to carry the data of the remote UE is not restricted by the network side configuration and cannot use the CA operation, the RLC bearer of the data corresponding to the remote UE can follow the Existing principles, CA transmission is performed according to scheduling and logical channel priority rules.
  • the RLC bearer used to carry the data of the remote UE on the Uu interface of the relay UE is configured as an MCG bearer, an SCG bearer or a split bearer
  • the RLC bearer corresponding to the data of the remote UE can perform related DC transmission operations according to the existing principles.
  • the CA operation of the Uu interface of the relay UE will not affect the remote UE, because there is only one service node and only one set of PDCP security keys.
  • the DC operation is configured on the Uu interface of the relay UE, if the RLC bearer used to carry the remote UE data on the Uu interface of the relay UE is configured as MCG bearer, SCG bearer or split bearer, then according to the final data anchor point, the remote UE corresponds to The PDCP entity uses a different key, either the MCG key or the SCG key.
  • each of the foregoing embodiments may further include the following steps: performing multi-carrier sub-link transmission with the relay terminal (PC5 interface).
  • the Uu interface between the relay terminal and the network side device is configured with carrier aggregation CA or dual-connection DC.
  • the remote UE can also perform CA duplication transmission with the target service between the relay terminals, wherein the CA duplication transmission of the target service is:
  • the remote UE reports the service requirements to the network, and the network configures the bearer and directly instructs the bearer to perform CA repeated transmission.
  • the network side device When the remote terminal reports the quality of service (QoS) of the target service, the network side device is configured for the secondary link radio bearer SLRB corresponding to the target service. For example, when the remote UE reports its own service QoS, the network side configures the mapping relationship between SLRB and QoS flow, and also configures whether the SLRB is Duplication. Of course, in this example, the SLRB corresponding to the target service is configured with repeated transmission.
  • QoS quality of service
  • the QoS profile used by the target service enables the CA repeat transmission function.
  • the network side device configures QoS profile 1 to disable the CA repeat transmission function; QoS profile 2 to enable the CA repeat transmission function; QoS profile 2 to enable the CA repeat transmission function, etc.
  • the service QoS profile of the remoteUE is QoSProfile2, and the CA repeat transmission function is enabled for the service according to the configuration on the network side.
  • the QoS profile used by the target service enables the CA repeat transmission function
  • the QoS feature configuration of the target service enables the CA repeated transmission 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 activated. In this example, the PDB of the target service is less than X and the BLER is less than Y.
  • PDB packet delay budget
  • BLER block error rate
  • the multiple RLC bearers used by the remote UE to transmit duplicate data are respectively configured with different carrier component (CC) subsets (ComponentCarriers).
  • CC carrier component subsets
  • the Uu interface between the relay terminal and the network side device is configured with dual connections: 1) the remote terminal uses a set of security parameters, and multiple data radios of the remote terminal bear DRB; Corresponding to one network device; or 2) multiple DRBs of the remote terminal use multiple sets of security parameters.
  • Embodiment 1 of the present invention L3 architecture remote UE configuration acquisition
  • the remote UE performs relay operations, and smooth operation does not affect the remote UE. stay status or serving cell.
  • the remote UE obtains the relevant configuration of the relay operation mainly from the following ways: 1. Pre-configured information; 2. System messages read by the remote UE from the camping cell or serving cell; 3. The remote UE passes the PC5 RRC Receive configuration information from relay UE.
  • the remote UE performs sidelink or sidelink relay operations, such as the discovery process, various types (unicast/sidelink relay) Multicast/broadcast/relay operations) are received and sent using pre-configuration information.
  • the pre-configuration information generally includes general configuration, or configuration information valid based on a certain location area.
  • the remote UE can use the above pre-configured information in both the discovery process and the subsequent relay communication process, which will not introduce additional signaling overhead, but considering the lack of configuration negotiation between the remote UE and the relay UE, for example, it is impossible to determine the exact configuration Knowing what kind of resources or parameters the other party uses, blind detection can only be performed within a large range, and the communication efficiency is not high.
  • the remote UE when the remote UE uses the pre-configured information to complete the discovery process with the relay UE, the remote UE can inform the relay UE of its own camping cell/sidelink system information acquisition/disconnection and other information during the discovery process, and the relay UE sends the information to the relay UE.
  • Its own serving cell has requested the relevant configuration of the relay operation. In the requested information, it can also carry information such as the remote UE's camping cell/sidelink system information acquisition status/disconnection and other information, for example, sidelink/relay can be obtained from cell1 System information configuration or offline status.
  • the purpose of carrying the above additional information in the requested information is that the network side can configure the configuration more closely matching the existing configuration of the remote UE, perform dedicated configuration for the relay UE, and optionally use the network side to deliver the configuration to the remote UE, relay
  • the UE forwards these configurations to the remote UE through PC5 RRC, for example, it can be a dedicated resource for the remote UE.
  • the above-mentioned additional information may not be carried on the Uu interface of the relay UE, but the relay UE directly sends the sidelink/relay information in the SIB that it can receive to the remote UE through PC5 RRC, or according to its own reception
  • the received sidelink-related configuration organizes new configuration information to the remote UE to facilitate communication between the two.
  • the relay UE can notify the remote UE on the PC5 interface, so that the remote UE can use these resources more efficiently. to receive.
  • the configuration information about the sidelink/sidelink relay can be obtained from the system message, so as to use the information to perform the discovery process with the relay UE. And in the subsequent relay communication process, the remote UE can also continue to use these public configuration information.
  • the remote UE may inform the relay UE of the information about its own camped cell/sidelink system, and the relay UE has requested the relevant configuration of the relay operation from its own serving cell.
  • the requested information It can also carry the information obtained from the camped cell/sidelink system information of the remote UE, for example, the sidelink/relay system information configuration or the configuration information identifier can be obtained from cell1.
  • the purpose of carrying the above additional information in the requested information is that the network side can configure the configuration more closely matching the existing configuration of the remote UE, perform dedicated configuration for the relay UE, and optionally use the network side to deliver the dedicated configuration to the remote UE,
  • the relay UE forwards these configurations to the remote UE through PC5 RRC, for example, it can be a dedicated resource for the remote UE.
  • the above-mentioned additional information may not be carried on the Uu interface of the relay UE, but the relay UE organizes the configuration information of PC5 to the remote UE according to the sidelink related configuration received by itself, so as to facilitate the communication between the two.
  • the remote UE if the remote UE is in the online connection state, no matter whether the core network uses the non-3GPP interworking function (Non-3GPP interworking function, N3IWF), the access network node, such as CU (central unit) or gNB, It is said that the remote UE does not have an RRC connection in the L3 architecture. Therefore, when the remote UE is in the 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 the relay connection. That is, the remote UE first releases the existing sidelink dedicated configuration, and then, as described above, establishes the relay connection from the idle state.
  • N3IWF non-3GPP interworking function
  • the remote UE since the remote UE is not connected to the network side, there is no concept of a remote UE connected state serving cell. If the remote UE receives the dedicated configuration forwarded by the relay UE, it is also the network side that Remote UE and relay UE binding consideration, dedicated configuration allocated for PC5 link (link) between remote UE and relay UE. These dedicated configurations become invalid once the relay UE moves out of the current cell, and needs to be reconfigured in a new cell, or the configuration in 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 , sent to the relay UE through the handover command, and then relayed to the remote UE.
  • Embodiment 2 of the present invention L2 architecture remote UE configuration acquisition
  • the remote UE's RRC/SDAP/PDCP entity peer is located on the network side, such as a base station or a CU.
  • the data transmission from the Remote UE to the network is transmitted through the PC5 and Uu two-segment RLC bearers (bearers).
  • the remote UE performs the relay operation and requires a connected serving cell.
  • the remote UE obtains the relevant configuration of the relay operation mainly from the following ways: 1. Pre-configured information (mainly used before the relay connection); 2. The remote UE reads the system message from the camping cell or the serving cell 3. The remote UE receives the configuration information from the network side through Uu RRC.
  • the remote UE in the L2 relay architecture there are mainly two stages: the first stage is before the RRC connection is established with the network side through the relay UE; the second stage is after the RRC connection is established with the network side through the relay UE .
  • the remote UE needs is some basic configuration of sidelink relay operation, for example, the explicit instructions to support L2 relay architecture, the conditions for L2 relay operation (such as RSRP threshold, or service requirements, etc.), and the necessary It is the basic configuration of the sidelink, such as the public resource pool, the public PC5 configuration, etc.
  • These configurations can be obtained in the following ways: 1. For the off-network remote UE, the above two kinds of information are obtained through the pre-configuration message; 2. For the idle state For the remote UE of the remote UE, the above two kinds of information are obtained by reading the SIB message; 3. For the remote UE in the connected state, the common information part of the above two kinds of information can be obtained through the SIB message, or can be further configured by the network side.
  • Dedicated configuration for example, dedicated RSRP thresholds, etc.
  • the Remote UE will initiate a discovery process to the relay UE and then establish a relay connection when it judges that it meets the conditions for relay operation.
  • the remote UE 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 at this time. After entering the RRC connection state, the following processes are performed through the RRC process of the remote UE.
  • the Remote UE can report the service characteristics transmitted between itself and the relay UE, such as QoS profile, etc., to the serving cell; the serving cell configures SLRB and RLC bearer for the remote UE according to the service information; the Remote UE receives the data from the serving cell.
  • SLRB and RLC bearer, etc. establish the corresponding bearer and carry out PC5 communication with the relay UE.
  • the Remote UE can also report the characteristics of the service, such as the period and transmission size, etc.; the serving cell configures dedicated period resources for the remote UE according to the information, such as configuring scheduling type 1 (configured grant type 1) resources, and/or, Configure scheduling type 2 (configured grant type 2) resources, or other types of dedicated resources, such as dedicated resource pools, etc.; Remote UE receives dedicated resources and configurations from the serving cell, and uses relevant resources and configurations to communicate with relay UE PC5.
  • the characteristics of the service such as the period and transmission size, etc.
  • the serving cell configures dedicated period resources for the remote UE according to the information, such as configuring scheduling type 1 (configured grant type 1) resources, and/or, Configure scheduling type 2 (configured grant type 2) resources, or other types of dedicated resources, such as dedicated resource pools, etc.
  • Remote UE receives dedicated resources and configurations from the serving cell, and uses relevant resources and configurations to communicate with relay UE PC5.
  • the serving cell of the remote UE after establishing the RRC connection with the network side through the relay UE may be inconsistent with the serving cell before establishing the RRC connection with the network side through the relay UE.
  • the idle state resides in cell1 under gNB1, and because the serving cell of the relay UE is cell2 under the same gNB1, for the convenience of management, the serving cell of the remote UE after the relay connection is established is also It is determined to be cell2 under gNB1.
  • the remote UE has the public configuration of sidelink/sidelink relay in the SIB message of cell1, but there is no public configuration of sidelink/sidelink relay in the SIB message of cell2, which will cause the remote UE to be in cell2.
  • the relay operation is performed under the following conditions, the wrong configuration information is used, unless the configuration coordination between the cells is performed in advance, it is guaranteed that the system configuration under the cell1 can also work in the cell2. If cell2 is a cell under the cross-base station gNB2, the probability of using wrong configuration information is greater
  • the remote UE Before the remote UE establishes the relay connection, it is in an offline state, and only has the pre-configured sidelink/sidelink relay public configuration information. Since the serving cell of the relay UE is cell2 under gNB1, in order to facilitate management, after the relay connection is established, The serving cell of the remote UE is also determined to be cell2 under gNB1. At this time, it is equivalent that the remote UE has the sidelink/sidelink relay public configuration in the pre-configuration message, but does not have the sidelink/sidelink relay public configuration in the SIB message of cell2. It will cause the remote UE to use the wrong configuration information for the relay operation under cell2. Unless the configuration coordination is performed in advance, it is guaranteed that the pre-configured system configuration can also work in cell2.
  • Method 1 When the remote UE establishes an RRC connection to the base station, it carries its own attribution information, such as the off-network status, the information of the previously camped cell, or the cell information of the sidelink/sidelink relay SIB message previously read, or even the specific sidelink.
  • the identifier or version information of the /sidelink relay message, and the attribution information can be carried in the RRC connection establishment request or completion message, or in a special message.
  • the network side When the network side receives the relevant attribution information, it can know whether the public sidelink/relay information currently used by the remote UE is applicable to this relay operation. If it cannot be used, it will send the new sidelink/relay configuration information to the remote UE through an RRC message. , these configuration information will cover the original configuration information of the remote UE.
  • the network side does not need to send the public configuration information, and the remote UE can continue to use the previous configuration information.
  • Method 2 The network side uses a special configuration or identifier to inform the remote UE which configuration information is universal and which cannot be 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 common, the remote UE needs to re-request the configuration, and the request information can be carried in the RRC connection establishment request or completion message, or a special message.
  • both the remote UE when the remote UE is in the connected state before the relay connection is established, it is also in the connected state after the relay connection is established.
  • This process is similar to the terminal handover process.
  • both 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 under the same base station
  • both the sidelink/relay public and dedicated configuration information can be reconfigured or continue to be used; when the previous serving cell and the relay UE serving cell are different cells under different base stations, similar to For inter-gNB/CU handover, the public and dedicated configuration information of sidelink/relay needs to be reconfigured.
  • the handover request message and the handover response message in the interface negotiation process between base stations carry source configuration information and target configuration information respectively.
  • Embodiment 3 of the present invention L3 architecture DC/CA operation
  • the protocol stack entities corresponding to the remote UE are all terminated at the relay UE, and there is no logical connection and entity with the gNB, so the DC/CA operation of the relay UE has little impact on it.
  • the DRB bearer of the Uu interface of the relay UE can be divided into two categories: one is the data of the relay UE itself, and the other is the data of the remote UE. These two types of data can be carried by different DRB/RLC bearer/logical channels, which is convenient for data retransmission and state transfer in various switching scenarios.
  • the relay UE's own data is carried in DRB0-7, and DRB8-15 is remote
  • the UE data is carried on the Uu interface of the relay UE.
  • the data bearers of different remote UEs connected to the same relay UE can be independent DRBs or multiplexed DRBs.
  • Component carrier restriction can be configured, that is, the set of CCs that can be used by a specific logical channel/RLC bearer. This carrier restriction is generally used when the duplication function is enabled, when logical channel 1 and When logical channel 2 is two duplicated logical channels corresponding to one DRB, in order to ensure the duplication effect, avoid duplicate data transmission on the same CC, and lose the duplication gain, logical channel 1 can be limited to CC1 and CC2 for uploading, and logical channel 2 is limited Upload at CC3, CC4 and CC5.
  • Similar carrier limitation can also be used to limit the transmission of the logical channel corresponding to the remote UE data, so as to prevent the data rate of the Uu interface from being too fast, while the rate of the PC5 interface is slow, resulting in rate mismatch, packet loss and resource waste.
  • the logical channel corresponding to the remote UE data can use the current CC arbitrarily.
  • each bearer of the Uu interface of the relay UE can be individually configured as the bearer of the relay UE corresponding to the MCG bearer/SCG bearer/split bearer, and the remote UE data can also be configured in the same way. , select a bearer type.
  • a data type of a remote UE has high QoS requirements, such as extremely low latency and/or extremely high reliability requirements, you can consider configuring the duplication transmission on the Uu interface for this service. Carry out CA or DC duplication transmission.
  • the CA/DC configured on the Uu interface basically has no effect on the PC5.
  • the data rate of the remote UE will be increased on the Uu interface.
  • the data rate of the remote UE will be increased on the PC5 interface. Multi-carrier sidelink transmission is also possible.
  • 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.
  • Embodiment 4 of the present invention L2 architecture DC/CA operation
  • the L2 protocol stack entity corresponding to the remote UE is terminated at the relay UE, and the peer entities of the L3 protocol are 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.
  • the RLC bearer of the Uu interface of the relay UE can be divided into two categories: one is the data of the relay UE itself, and the other is the data of the remote UE. Generally speaking, these two types of data need to be carried by different RLC bearer/logical channels, which is convenient for data retransmission and status transfer in various switching scenarios.
  • relay UE's own data is carried in RLC bearer/LCID0-7
  • RLC bearer/LCID8-15 is the bearer of the remote UE data on the Uu interface of the relay UE, wherein the data bearer of different remote UEs connected to the same relay UE can be an independent RLC bearer/LCID, or RLC bearer/LCID can be multiplexed.
  • the relay UE When the relay UE is configured with CA: for the RLC bearer/LCID corresponding to the remote UE data, you can configure whether these RLC bearer/LCID are allowed to be transmitted on all CCs or only on some CCs, that is, the CC can be configured Subset, used 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 remote UE data.
  • the corresponding RLC bearer can also perform multi-carrier transmission to meet the rate matching effect. For example, if the same bearer is transmitted in CA mode on the Uu interface, the rate of 100Mbps can be achieved, 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 be deleted. , which wastes Uu interface transmission resources. At this time, if the PC5 interface also supports multi-carrier transmission and the rate reaches 100Mbps, the rate matching can be performed well and the transmission efficiency can be improved.
  • the service QoS requirements of the remote UE are relatively high, for example, the latency requirements are very high, and/or the reliability requirements are very high, one or more of the following configurations can be performed:
  • CA duplication function for the RLC bearer of the remote UE, that is, the two RLC bearers that transmit duplicate data are configured with different CC subsets for duplication transmission, and the same data is transmitted simultaneously on CC subset1 and CC subset2 to obtain High reliability and delay indicators; CA duplication of Uu interface is configured and controlled by the base station.
  • the CA duplication function on the RLC bearer of the remote UE configures the CA duplication function on the RLC bearer of the remote UE, that is, the two RLC bearers that transmit duplicate data are configured with different CC subsets for duplication transmission, and the same data is transmitted simultaneously on CC subset1 and CC subset2 to obtain High reliability and delay indicators;
  • the CA duplication of the PC5 interface is configured by the PC5 RRC and controlled by the PC5 MAC.
  • the controlled node can be the relay UE or the sender UE of the PC5 interface.
  • the biggest impact of the DC operation on the remote UE is the difference in security parameters. If the DRB of the remote UE is terminated in the MCG, the DRB needs to use the MCG security parameters, such as key and or security algorithm, etc., If the DRB of the remote UE terminates in the SCG, the DRB needs to use the SCG security parameter.
  • This embodiment may handle security parameters in the following manner:
  • All the DRBs of the remote UE can only be terminated in 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, and some are terminated in the MCG, Others are terminated in SCG, which also plays the role of data offloading and has less impact on the remote UE.
  • the remote UE can use two or more sets of security parameters (such as dual connections or multiple 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 DRBs.
  • security parameters such as dual connections or multiple connections
  • 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 being transmitted directly from the relay UE to the MCG; the other is the SCG bearer, which One is equivalent to the RLC bearer being transmitted directly from the relay UE to the SCG; the third is the split bearer, which is equivalent to the RLC bearer being transmitted by the relay UE to both the MCG and the SCG, which is equivalent to both legs can be used, The transmission rate is high; 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 order.
  • the data aggregation node can be configured. When the data aggregation node is MCG , the bearer uses the MCG security parameter, and when the data aggregation node is the SCG, the bearer uses the SCG security parameter.
  • the Uu interface can also be configured with the DC duplication mechanism, that is, in the case of split bearer configuration, duplicate data can be transmitted between two legs to meet the requirements of high reliability and low latency.
  • Uu interface configure and activate DC duplication for remote UE data.
  • CA duplication can be configured and enabled according to this requirement, and the two sections can be configured independently or together.
  • CA transmission can also be enabled on the PC5 interface.
  • FIG. 4 is a schematic structural diagram of a remote terminal according to an embodiment of the present application.
  • the remote terminal 400 includes: a determination module 402, which can be configured to determine the secondary link relay architecture according to at least one of the following Secondary link configuration: pre-configuration information; system messages received from the camping cell or serving cell; the first configuration information from the relay terminal; the second configuration information from the network side device.
  • the remote terminal may determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; system messages received from the camping cell or serving cell; The first configuration information of the relay terminal; the second configuration information from the network side device.
  • the remote terminal before the determining of the secondary link configuration in the secondary link relay architecture, the remote terminal is in an offline state, wherein the determining module 402 is configured to: according to the Pre-configuration information to determine the secondary link configuration in the secondary link relay architecture, and the remote terminal is further configured 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 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 relay Secondary link configuration in the fabric.
  • the remote terminal 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 configured to: according to The system message or the second configuration information from the network side device determines the secondary link configuration in the secondary link relay architecture, and the remote terminal is further configured to determine the secondary link configuration according to the system message or the second configuration information establish an L3 relay architecture with the relay terminal; 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, through PC5RRC The process determines the secondary link configuration in the secondary link relay architecture by receiving the first configuration information from the relay terminal.
  • the remote terminal before the determining of the secondary link configuration in the secondary link relay architecture, the remote terminal is in an offline state, wherein the determining module 402 is configured to: according to the Pre-configuration information to determine the secondary link configuration in the secondary link relay architecture, and the remote terminal is further configured to establish an L2 relay architecture with the relay terminal according to the pre-configuration information; in the L2 relay architecture , determine the secondary link configuration in the secondary link relay architecture by receiving the second configuration information from the network side device through the RRC process; or, receive the first configuration information from the relay terminal through the PC5 RRC process Determine the secondary link configuration in the secondary link relay architecture.
  • the remote terminal 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 configured to: according to The system message or the second configuration information from the network side device determines the secondary link configuration in the secondary link relay architecture, and the remote terminal is further configured to determine the secondary link configuration according to the system message or the second configuration information establishing an L2 relay architecture with the relay terminal; 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 data from the network through an RRC process The second configuration information of the side device determines the secondary link configuration in the secondary link relay architecture.
  • the remote terminal 400 further includes: a sending module, configured to send, to the network side device, the service characteristics transmitted between the remote terminal and the relay terminal, the service characteristics for the network side device to configure radio bearer information for the remote terminal; a receiving module, configured to receive the radio bearer information, and establish a radio bearer according to the radio bearer information, and the radio bearer is used for the remote terminal.
  • the end terminal communicates with the relay terminal.
  • the remote terminal 400 further includes: a sending module, configured to send, to the network side device, the service characteristics transmitted between the remote terminal and the relay terminal, the service characteristics
  • the network side device configures dedicated resource information for the remote terminal;
  • the receiving module is configured to receive the dedicated resource information, and communicate with the relay terminal according to the dedicated resource indicated by the dedicated resource information.
  • the remote terminal 400 and the relay terminal perform multi-carrier sub-link transmission.
  • the Uu interface between the relay terminal and the network side device is configured with carrier aggregation CA or dual-connection DC.
  • the target service between the remote terminal and the relay terminal performs CA repeated duplication transmission, wherein the CA repeated transmission of the target service is: directly configured for the remote terminal ; Under the situation that the quality of service QoS of the target service is reported by the remote terminal, the network side equipment is configured for the SLRB corresponding to the target service; the QoS configuration used by the target service has enabled the CA repeat transmission function; Configure the QoS feature of the target service to enable the CA repeat transmission function.
  • the multiple RLC bearers used by the remote terminal to transmit duplicate data are respectively configured with different carrier component CC subsets.
  • the remote terminal uses a set of security parameters, and multiple data of the remote terminal are used.
  • the radio bearer DRB corresponds to one network device; or multiple DRBs of the remote terminal use multiple sets of security parameters.
  • the remote terminal 400 may refer to the process of the method 200 corresponding to the embodiment of the present application, and each unit/module and the above-mentioned other operations and/or functions in the remote terminal 400 are for the purpose of implementing the method 200 respectively. and can achieve the same or equivalent technical effects. For brevity, no further description is given here.
  • the remote terminal in this embodiment of the present application may be a terminal, or may be a component, an integrated circuit, or a chip in the terminal.
  • the device may be a mobile terminal or a non-mobile terminal.
  • 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 (NAS), a personal computer (personal computer, PC), a television ( television, TV), teller machine, or self-service machine, etc., which are not specifically limited in the embodiments of the present application.
  • the remote terminal in this embodiment of the present application may be a device having an operating system.
  • the operating system may be an Android (Android) operating system, an ios operating system, or other possible operating systems, which are not specifically limited in the embodiments of the present application.
  • the remote terminal provided by the embodiment of the present application can implement each process implemented by the method embodiment of FIG. 2, and achieve the same technical effect. To avoid repetition, details are not repeated here.
  • an embodiment of the present application further provides a communication device 500, including a processor 501, a memory 502, a program or instruction stored in the memory 502 and executable on the processor 501,
  • a communication device 500 including a processor 501, a memory 502, a program or instruction stored in the memory 502 and executable on the processor 501,
  • the communication device 500 is a remote terminal
  • the program or instruction is executed by the processor 501, each process of the foregoing configuration method embodiment in the secondary link relay architecture can be achieved, and the same technical effect can be achieved.
  • FIG. 6 is a schematic diagram of a hardware structure of a terminal implementing an embodiment of the present application.
  • 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, a processor 610 and other components .
  • 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, so as to manage charging, discharging, and power consumption through the power management system management and other functions.
  • a power source such as a battery
  • the terminal structure shown in FIG. 6 does not constitute a limitation on the terminal, and the terminal may include more or less components than shown, or combine some components, or arrange different components, which will not be repeated here.
  • the input unit 604 may include a graphics processor (Graphics Processing Unit, GPU) 6041 and a microphone 6042. Such as camera) to obtain still pictures or video image data for processing.
  • the display unit 606 may include a display panel 6061, which may be configured in the form of a liquid crystal display, an organic light emitting diode, or the like.
  • 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, physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, and joysticks, which are not described herein again.
  • the radio frequency unit 601 receives the downlink data from the network side device, and then processes it to the processor 610; in addition, sends the uplink data to the network side device.
  • 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, and the like.
  • Memory 609 may be used to store software programs or instructions as well as various data.
  • the memory 609 may mainly include a stored program or instruction area and a storage data area, wherein the stored program or instruction area may 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.) and the like.
  • the memory 609 may include a high-speed random access memory, and may also include a non-volatile memory, wherein the non-volatile memory may be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM) ), erasable programmable read-only memory (ErasablePROM, EPROM), electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or flash memory.
  • ROM Read-Only Memory
  • PROM programmable read-only memory
  • ErasablePROM ErasablePROM
  • EPROM electrically erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • flash memory for example at least one magnetic disk storage device, flash memory device, or other non-volatile solid state storage device.
  • 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 the operating system, user interface, and application programs or instructions, etc. Modem processors mainly deal with wireless communications, such as baseband processors. It can be understood that, the above-mentioned modulation and demodulation processor may not be integrated into the processor 610.
  • the processor 610 is configured to determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; system messages received from the camping cell or serving cell; from the relay terminal The first configuration information of ; the second configuration information from the network side device.
  • a remote terminal (such as terminal 600) may determine the secondary link configuration in the secondary link relay architecture according to at least one of the following: pre-configuration information; System message; first configuration information from the relay terminal; second configuration information from the network side device.
  • the terminal provided by the embodiment of the present application implements each process of the above-mentioned configuration method embodiment in the secondary link relay architecture when executed, and can achieve the same technical effect. To avoid repetition, details are not described here.
  • An embodiment of the present application further provides a readable storage medium, where a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the above-mentioned configuration method embodiment of the secondary link relay architecture is implemented.
  • a program or an instruction is stored on the readable storage medium, and when the program or instruction is executed by a processor, the above-mentioned configuration method embodiment of the secondary link relay architecture is implemented.
  • Each process can achieve the same technical effect. In order to avoid repetition, it will not be repeated here.
  • the processor may be the processor in the terminal described in the foregoing embodiment.
  • the readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (Read-Only Memory, ROM), a random access memory (Random Access Memory, RAM), a magnetic disk or an optical disk, and the like.
  • An embodiment of the present application further provides a chip, where the chip includes a processor and a communication interface, the communication interface is coupled to the processor, and the processor is used to run a program or an instruction to implement the above-mentioned secondary link relay architecture
  • the chip mentioned in the embodiments of the present application may also be referred to as a system-on-chip, a system-on-chip, a system-on-chip, or a system-on-a-chip, or the like.
  • An embodiment of the present application further provides a computer program product, where the computer program product is stored in a non-volatile memory, and the computer program product is executed by at least one processor to implement the configuration in the secondary link relay architecture.
  • Each process of the method embodiment can achieve the same technical effect, and in order to avoid repetition, it will not be repeated here.
  • the embodiment of the present application further provides a communication device, which is configured to perform each process of the above-mentioned embodiment of the configuration method in the secondary link relay architecture, and can achieve the same technical effect. To avoid repetition, it is not repeated here. Repeat.
  • the method of the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course can also be implemented by hardware, but in many cases the former is better implementation.
  • the technical solution of the present application can be embodied in the form of a software product in essence or in a part that contributes to the prior art, and the computer software product is stored in a storage medium (such as ROM/RAM, magnetic disk, CD-ROM), including several instructions to make a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) execute the methods described in the various embodiments of this application.
  • a storage medium such as ROM/RAM, magnetic disk, CD-ROM

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephonic Communication Services (AREA)
  • Databases & Information Systems (AREA)

Abstract

本申请实施例公开了一种副链路中继架构中的配置方法和终端，能够解决远端终端无法获得副链路中继架构中的副链路配置的问题。该方法可以应用于远端终端，包括：根据如下至少之一，确定副链路中继架构中的副链路配置：预配置信息；从驻留小区或服务小区接收到的系统消息；来自于中继终端的第一配置信息；来自于网络侧设备的第二配置信息。

Description

副链路中继架构中的配置方法和终端
交叉引用
本申请要求在2020年7月30日在中国提交的申请号为202010753310.6、发明名称为“副链路中继架构中的配置方法和终端”的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请属于通信技术领域，具体涉及一种副链路中继架构中的配置方法和终端。
背景技术
长期演进(Long Term Evolution，LTE)系统从第12个发布版本开始支持副链路(sidelink)，用于终端设备之间不通过网络设备进行直接数据传输。
随着sidelink的发展，相关技术中提出了sidelink中继(relay)架构。在典型的sidelink中继架构中，远端终端(remote UE)通过和中继终端(relay UE)之间的sidelink链路(或称中继链路)，由中继终端将它的数据向网络设备进行转发。在该sidelink中继架构中，远端终端可以和网络设备之间进行数据传输，中继终端起到数据中转作用。
由于在sidelink中继架构中引入了中继终端，远端终端如何获得副链路中继架构中的副链路配置，使得消息能够正常传输，是相关技术中亟需解决的技术问题。
发明内容
本申请实施例的目的是提供一种副链路中继架构中的配置方法和终端，能够解决远端终端无法获得副链路中继架构中的副链路配置的问题。
为了解决上述技术问题，本申请是这样实现的：
第一方面，提供了一种副链路中继架构中的配置方法，应用于远端终端，所述方法包括：根据如下至少之一，确定副链路中继架构中的副链路配置：预配置信息；从驻留小区或服务小区接收到的系统消息；来自于中继终端的第一配置信息；来自于网络侧设备的第二配置信息。
第二方面，提供了一种远端终端，包括：确定模块，用于根据如下至少之一，确定副链路中继架构中的副链路配置：预配置信息；从驻留小区或服务小区接收到的系统消息；来自于中继终端的第一配置信息；来自于网络侧设备的第二配置信息。
第三方面，提供了一种终端，该终端包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法。
第四方面，提供了一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被处理器执行时实现如第一方面所述的方法。
第五方面，提供了一种计算机程序产品，该计算机程序产品包括处理器、存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如第一方面所述的方法。
第六方面，提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如第一方面所述的方法。
在本申请实施例中，远端终端可以根据如下至少之一，确定副链路中继架构中的副链路配置：预配置信息；从驻留小区或服务小区接收到的系统消息；来自于中继终端的第一配置信息；来自于网络侧设备的第二配置信息。本申请实施例便于使远端终端、中继终端和网络侧的理解保持一致，提高通信有效性。
附图说明
图1是根据本申请的一个实施例的无线通信系统的框图；
图2是根据本申请的一个实施例的副链路中继架构中的配置方法的示意性流程图；
图3是根据本申请的一个实施例的中继架构示意图；
图4是根据本申请的一个实施例的远端终端的结构示意图；
图5是根据本申请的一个实施例的通信设备的结构示意图；
图6是根据本申请的一个实施例的终端的结构示意图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有作出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
本申请的说明书和权利要求书中的术语“第一”、“第二”等是用于区别类似的对象，而不用于描述特定的顺序或先后次序。应该理解这样使用的数据在适当情况下可以互换，以便本申请的实施例能够以除了在这里图示或描述的那些以外的顺序实施，且“第一”、“第二”所区别的对象通常为一类，并不限定对象的个数，例如第一对象可以是一个，也可以是多个。此外，说明书以及权利要求中“和/或”表示所连接对象的至少其中之一，字符“/”一般表示前后关联对象是一种“或”的关系。
值得指出的是，本申请实施例所描述的技术不限于长期演进型(Long Term Evolution，LTE)/LTE的演进(LTE-Advanced，LTE-A)系统，还可用于其他无线通信系统，诸如码分多址(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)和其他系统。本申请实施例 中的术语“系统”和“网络”常被可互换地使用，所描述的技术既可用于以上提及的系统和无线电技术，也可用于其他系统和无线电技术。然而，以下描述出于示例目的描述了新空口(NewRadio，NR)系统，并且在以下大部分描述中使用NR术语，尽管这些技术也可应用于NR系统应用以外的应用，如第6代(6 thGeneration，6G)通信系统。
图1示出本申请实施例可应用的一种无线通信系统的框图。无线通信系统包括终端11和网络侧设备12。其中，终端11也可以称作终端设备或者用户终端(User Equipment，UE)，终端11可以是手机、平板电脑(Tablet Personal Computer)、膝上型电脑(Laptop Computer)或称为笔记本电脑、个人数字助理(Personal Digital Assistant，PDA)、掌上电脑、上网本、超级移动个人计算机(ultra-mobile personal computer，UMPC)、移动上网装置(Mobile Internet Device，MID)、可穿戴式设备(Wearable Device)或车载设备(VUE)、行人终端(PUE)等终端侧设备，可穿戴式设备包括：手环、耳机、眼镜等。需要说明的是，在本申请实施例并不限定终端11的具体类型。网络侧设备12可以是基站或核心网，其中，基站可被称为节点B、演进节点B、接入点、基收发机站(Base Transceiver Station，BTS)、无线电基站、无线电收发机、基本服务集(Basic Service Set，BSS)、扩展服务集(Extended Service Set，ESS)、B节点、演进型B节点(eNB)、下一代节点B(gNB)、家用B节点、家用演进型B节点、WLAN接入点、WiFi节点、发送接收点(TransmittingReceivingPoint，TRP)或所述领域中其他某个合适的术语，只要达到相同的技术效果，所述基站不限于特定技术词汇，需要说明的是，在本申请实施例中仅以NR系统中的基站为例，但是并不限定基站的具体类型。
如图2所示，本申请的一个实施例提供一种副链路中继架构中的配置方法200，该方法可以由远端终端执行，换言之，该方法可以由安装在远端终端的软件或硬件来执行，该方法包括如下步骤。
S202：根据如下至少之一，确定副链路中继架构中的副链路配置：预配置信息；从驻留小区或服务小区接收到的系统消息；来自于中继终端的第一 配置信息；来自于网络侧设备的第二配置信息。
本申请实施例提到的副链路中继架构可以参见图3，在该副链路中继架构中，远端终端(remote UE)可以和网络设备之间可以进行数据传输，中继终端(relay UE)起到数据中转作用；同时，remote UE还可以跟relay UE进行传统副链路传输，该传输不经过网络设备。
本申请各个实施例提到的副链路传输的相关配置，可以包括远端终端和中继终端之间建立副链路中继架构所需的相关配置，还可以包括副链路中继架构建立完成之后，远端终端和中继终端之间的数据传输所需的相关配置。
在本申请实施例中，远端终端可以根据如下至少之一，确定副链路中继架构中的副链路配置：预配置信息；从驻留小区或服务小区接收到的系统消息；来自于中继终端的第一配置信息；来自于网络侧设备的第二配置信息。本申请实施例便于使远端终端、中继终端和网络侧的理解保持一致，提高通信有效性。
为详细说明该实施例提供的副链路中继架构中的配置方法，以下将分几种情况进行详细说明。
情况1：脱网remote UEL3中继架构
该情况1中，remote UE在和relay UE建立L3 relay架构之前处于脱网状态，当remote UE处于脱网状态，即无法获得任何sidelink/sidelink relay相关的系统消息和配置信息，这样，S202可以是：remote UE根据预配置信息，确定副链路中继架构中的副链路配置，remote UE还用于根据所述预配置信息与relay UE建立L3中继架构。具体例如，remote UE使用预配置的sidelink/sidelink relay参数，与relay UE进行发现过程，之后建立L3 relay架构。
在L3 relay架构操作中，remote UE副链路中继架构中的副链路配置的获得有两种方式：
第一种，继续使用上述预配置信息确定副链路中继架构中的副链路配置，例如，继续使用预配置的sidelink/sidelink relay参数。
第二种，通过PC5无线资源控制(Radio Resource Control，RRC)过程接收来自于中继终端的第一配置信息确定副链路中继架构中的副链路配置。例如，由relay UE通过PC5 RRC过程发送相关的sidelink/sidelink relay参数给remote UE，供remote UE在relay操作中使用，relay UE自己的参数信息自于网络侧设备，relayUE发送给remoteUE的第一配置信息可以自行决定也可以参考来自于网络侧设备的配置信息。
情况2：在网remote UE L3中继架构
该情况2中，remote UE和relay UE在建立L3 relay架构之前处于空闲态或连接态。
当remote UE处于正常小区驻留状态时，可以获取sidelink/sidelink relay相关的系统信息配置，此时，remote UE可以根据从小区接收到的系统消息确定副链路中继架构中的副链路配置，remote UE可以还可以根据上述系统消息与中继终端建立L3中继架构。
或者，remote UE处于正常的RRC连接态，可以从它的服务小区获得了sidelink/sidelink relay相关的专用配置。此时，remote UE可以根据来自于网络侧设备的第二配置信息(可以是指上述专用配置)确定副链路中继架构中的副链路配置，remote UE可以还可以根据第二配置信息与中继终端建立L3中继架构。
当remote UE满足L3 relay操作的条件，需要进行L3 relay操作时，remote UE的配置信息获取有两种方式：
第一种，在L3中继架构中，继续使用所述系统消息或所述第二配置信息确定副链路中继架构中的副链路配置。例如，remote UE继续使用当前获得的系统信息中的sidelink/sidelink relay参数。
第二种，通过PC5RRC过程接收来自于中继终端的第一配置信息确定副链路中继架构中的副链路配置。例如，由relay UE通过PC5 RRC过程发送相关的sidelink/sidelink relay参数给remote UE，供remote UE在relay操作中使用，relay UE自己使用的参数信息来自于网络侧，relayUE发送给remoteUE 的第一配置信息可以自行决定也可以参考来自于网络侧设备的配置信息。。
可选地，在L3中继架构建立之前，remote UE处于连接态，其中，在L3中继架构中，remote UE还可以释放RRC连接(如释放专用配置)，使用接收到的系统消息确定副链路中继架构中的副链路配置；或者，通过PC5RRC过程接收来自于中继终端的第一配置信息确定副链路中继架构中的副链路配置。
可选地，在上述情况1或情况2中，remote UE在和relay UE的PC5RRC过程，例如发现过程中，还可以向relay UE发送第一信息，该第一信息包括远端终端的如下至少之一：驻留小区信息、sidelink系统信息获得情况、脱网情况；其中，所述中继终端还用于将所述第一信息发送给网络侧设备。这样，网络侧设备可以基于第一信息，为remote UE配置更适合于remote UE和relay UE的副链路配置。
具体例如，网络侧设备可以根据第一信息向relay UE发送副链路配置参数，relay UE将接收到的副链路配置参数进行处理后发送给remote UE(如前文介绍的发送的第一配置信息)。
可选地，在上述情况1和情况2中，remote UE在确定副链路中继架构中的副链路配置之后，所述方法还包括：接收第三配置信息，其中，所述第三配置信息是所述relay UE在移出当前小区的情况下，所述remote UE在新小区重新获得的配置，其中，在当前小区下，remote UE和relay UE已经建立了L3中继架构。
该实施例可以是remote UE和relay UE共同移出当前小区的情况下，remote UE在新小区重新获得的配置。该实施例中，remote UE可以通过系统消息(如SIB)或者通过PC5 RRC获得上述第三配置信息，可选地，上述第三配置信息还可以包括有remote UE的专用配置。
该实施例例如，remote UE和relay UE共同移出当前小区并移动到新小区，remote UE通过读取新小区下的系统消息得到上述第三配置信息。又例如，remote UE和relay UE共同移出当前小区并移动到新小区，relay UE通过 读取新小区下的系统消息，进而基于上述系统消息通过PC5 RRC向remote UE发送第三配置信息。
情况3：脱网remote UE L2架构
该情况3中，remote UE在和relay UE建立L2 relay架构之前处于脱网状态。remote UE处于脱网状态，即无法获得任何sidelink/sidelink relay相关的系统消息和配置信息，这种情况下，remote UE可以根据预配置信息，确定副链路中继架构中的副链路配置，remote UE还用于根据该预配置信息与中继终端建立L2中继架构。例如，remote UE可以使用预配置的sidelink/sidelink relay参数，与relay UE进行发现过程，之后建立L2 relay架构。
在L2 relay架构操作中，remote UE的配置信息获得有两种途径：
第一种，通过RRC过程接收来自于网络侧设备的第二配置信息确定副链路中继架构中的副链路配置。
第二种，通过PC5 RRC过程接收来自于中继终端的第一配置信息确定副链路中继架构中的副链路配置。
可选地，在L2中继架构中，remote UE根据RRC过程接收到的第二配置信息，确定副链路传输的副链路无线承载(Sidelink Radio Bearer，SLRB)配置、服务数据适配协议(Service Data Adaptation Protocol，SDAP)配置和分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)配置。具体例如，SLRB，SDAP，PDCP等layer 3相关的参数，remote UE通过自己的RRC过程由网络侧获得。
可选地，在L2中继架构中，remote UE根据第二配置信息或所述第一配置信息，确定副链路传输的无线链路控制(Radio Link Control，RLC)承载(bearer)配置。例如，对于RLC bearer等layer 2相关的参数，remote UE可以通过RRC过程由网络侧设备处获得，也可以通过PC5 RRC由relay UE处获得。
在情况3下，由于remote UE在进入relay操作之前没有任何的驻留/服务小区，可选地，remote UE通过relay UE与所述网络侧设备建立RRC连接 之后，为所述remote UE选择的服务小区，是所述relay UE的主小区；或为所述remote UE选择的服务小区，与所述relay UE的主小区属于同一个所述网络侧设备。具体例如，remote UE的服务小区优选为与relay UE的主小区(Pcell)一致的小区，也可以是与该Pcell同一个基站下的其它小区。
情况4：在网remote UE L2架构
在情况4中，remote UE和relay UE在建立L2 relay架构之前处于空闲态或连接态。
当remote UE处于正常小区驻留状态，可以获取sidelink/sidelink relay相关的系统信息配置。这种情况下，remote UE根据从驻留小区或服务小区接收到的系统消息，确定副链路中继架构中的副链路配置，remote UE还用于根据所述系统消息与relay UE建立L2中继架构。
或者remote UE处于连接态，已经从它的服务小区获得了sidelink/sidelink relay相关的专用配置。这种情况下，remote UE根据来自于网络侧设备的第二配置信息(可以是指上述专用配置)，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述第二配置信息与中继终端建立L2中继架构。
当remote UE满足L2 relay操作的条件，需要进行L2 relay操作时，它的配置信息获取有两种方式：
第一种，在所述L2中继架构中，remote UE继续使用所述系统消息确定副链路中继架构中的副链路配置，例如，remote UE继续使用当前获得的系统信息中的sidelink/sidelink relay参数。
第二种，在所述L2中继架构中，remote UE通过RRC过程接收来自于网络侧设备的第二配置信息确定副链路中继架构中的副链路配置。例如，由remote UE自身的RRC过程过程从新的服务小区获得相关的sidelink/sidelink relay参数，供remote UE在relay操作中使用。该例子中，如果L2中继架构建立之前remote UE具有专用配置(即L2中继架构建立之前remote UE处于连接态)，则remote UE还可以根据服务小区是否变化来决定是否释放上述专用配置，例如，在服务小区变化时释放上述专用配置，从新的服务小区获得 第二配置信息；在服务小区未变化时还可以继续使用上述专用配置。
在情况4中，可选地，remote UE在与网络侧设备建立RRC连接时，还可以携带有所述remote UE的归属信息；其中，所述归属信息包括所述远端终端的如下至少之一：驻留小区信息、sidelink系统信息获得情况、脱网情况。这样，网络侧设备可以基于remote UE的归属信息，为remote UE配置更适合于remote UE和relay UE的副链路配置。
在情况4中，可选地，remote UE还可以确定在第一服务小区使用的所述系统消息或所述第二配置信息是否适用于第二服务小区；其中，所述第一服务小区是所述远端终端建立RRC连接之前的服务小区，所述第二服务小区是所述RRC连接之后的服务小区，所述第一服务小区与所述第二服务小区相同或不同。
在情况4中，可选地，remote UE还可以向所述网络侧设备发送所述远端终端与所述中继终端之间传输的业务特性，所述业务特性用于所述网络侧设备为所述远端终端配置无线承载信息；remote UE还可以接收所述无线承载信息，并根据所述无线承载信息建立无线承载，所述无线承载用于所述远端终端与所述中继终端进行通信。
在情况4中，可选地，remote UE还可以向所述网络侧设备发送所述远端终端与所述中继终端之间传输的业务特性，所述业务特性用于所述网络侧设备为所述远端终端配置专用资源信息；remote UE还可以接收所述专用资源信息，并根据所述专用资源信息指示的专用资源与所述中继终端进行通信。
情况5：L3 relay架构的双连接(Dual-Connectivity，DC)/载波聚合(Carrier Aggregation，CA)操作
在L3 relay架构中，relay UE可以被配置CA和/或DC操作，而remote UE只有PC5接口与relay UE进行通信，并不存在与网络之间直接连接的链路。
当relay UE被配置为CA或者DC操作时，如果relay UE的Uu接口用于承载remote UE数据的数据无线承载(DRB)/逻辑信道并没有被网络侧配置限制不能使用CA操作时，在remote UE对应数据的DRB/逻辑信道可以依 照现有原则，根据调度和逻辑信道优先级规则进行CA传输。
如果relay UE的Uu接口用于承载remote UE数据的DRB/逻辑信道被配置为主小区组(MCG)bearer或者辅小区组(SCG)bearer或者分离(split)bearer，在remote UE对应数据的DRB/逻辑信道可以依照现有原则，进行相关DC传输操作。
在PC5接口，remote UE和relay UE之间的传输，也可以使用多载波传输，该多载波传输遵照PC5接口的多载波传输规则，与relay UE的Uu接口的CA/DC操作各自独立。
情况6：L2 relay架构的DC/CA操作
在L2 relay架构中，relay UE可以被配置CA和/或DC操作，而remote UE由于和网络之间存在逻辑上L3连接，PDCP锚节点(anchor)在网络侧，因此DC的MCG/SCG的配置将影响remote UE承载的安全操作。
当relay UE被配置为CA或者DC操作时，如果relay UE的Uu接口用于承载remote UE数据的RLC bearer并没有被网络侧配置限制不能使用CA操作时，在remote UE对应数据的RLC bearer可以依照现有原则，根据调度和逻辑信道优先级规则进行CA传输。
如果relay UE的Uu接口用于承载remote UE数据的RLC bearer被配置为MCG bearer或者SCG bearer或者split bearer，在remote UE对应数据的RLC bearer可以依照现有原则，进行相关DC传输操作。
Relay UE的Uu接口的CA操作并不会影响remote UE，因为服务节点只有一个，PDCP security key只用一套。但当relay UE的Uu接口配置了DC操作，如果relay UE的Uu接口用于承载remote UE数据的RLC bearer被配置为MCG bearer或者SCG bearer或者split bearer，则根据最终数据锚点不同，remote UE对应的PDCP entity使用不同的key，MCG key或者SCG key。
基于上述情况5和情况6的介绍，可选地，前文各个实施例还可以包括如下步骤：与中继终端之间(PC5接口)进行多载波副链路传输。可选地，所述中继终端与网络侧设备之间的Uu接口配置了载波聚合CA或双连接DC。
可选地，remote UE还可以与中继终端之间的目标业务进行CA重复duplication传输，其中，所述目标业务进行CA重复(duplication)传输是：
1)直接为所述远端终端配置的。例如L2中继架构下，remote UE将业务需求上报给网络，网络配置承载，直接指示该承载进行CA重复传输。
2)在所述远端终端上报所述目标业务的服务质量(QoS)的情况下，网络侧设备为所述目标业务对应的副链路无线承载SLRB配置的。具体例如，remote UE上报自己的业务QoS，网络侧配置了SLRB和QoS flow的映射关系，同时配置了该SLRB是否Duplication，当然，该例子中目标业务对应的SLRB是配置了重复传输。
3)所述目标业务使用的QoS配置(profile)开启了CA重复传输功能。例如，网络侧设备配置QoS profile 1不开CA重复传输功能；QoS profile 2开启CA重复传输功能；QoS profile 2开启CA重复传输功能等。例如remoteUE的业务QoSprofile为QoSProfile2，按照网络侧配置为该业务开启CA重复传输功能。该例子中，目标业务使用的QoS profile开启了CA重复传输功能
4)所述目标业务的QoS特征配置开启了CA重复传输功能。例如，网络侧配置业务的分组延迟预算(PDB)小于X且误块率(BLER)小于Y，则启动CA duplication功能，该例子中的目标业务的PDB小于X且BLER小于Y。
可选地，在PC5接口，remote UE用于传输重复数据的多个RLC承载分别配置不同的载波单元(CC)子集(ComponentCarrier)。
可选地，在中继终端与网络侧设备之间的Uu接口配置了双连接的情况下：1)所述远端终端使用一组安全参数，所述远端终端的多个数据无线承载DRB对应于一个网络设备；或2)所述远端终端的多个DRB使用多组安全参数。
为详细说明本申请实施例提供的副链路中继架构中的配置方法，以下将结合几个具体的实施例进行说明。
本发明实施例一：L3架构remote UE的配置获取
在L3架构中，remote UE和网络侧设备(后续简称网络)之间没有直接 的逻辑连接，也即PC5接口和Uu接口之间相对独立，remote UE进行relay操作，通畅并不影响remote UE的驻留状态或者服务小区。
在L3架构中，remote UE获得relay操作的相关配置，主要来自于以下途径：一、预配置信息；二、remote UE从驻留小区或者服务小区读取的系统消息；三、remote UE通过PC5 RRC接收来自于relay UE的配置信息。
在一个例子中，如果remote UE处于脱网状态，即无法获得任何关于sidelink/sidelink relay的相关系统信息，则此时remote UE进行sidelink或者sidelink relay操作，例如发现过程，各种类型(单播/组播/广播/relay操作)的接收和发送，都是采用预配置信息，预配置信息一般包含通用的配置，或者基于一定位置区域有效的配置信息。
Remote UE可以在发现过程和后续relay通信过程中，均使用上述预配置信息，这样不会引入额外的信令开销，但考虑到remote UE和relay UE之间缺乏对于配置的协商，例如，无法确切知道对方使用什么样的资源或者参数，只能在很大范围之内进行盲检，通信效率不高。
可选地，当remote UE使用预配置信息与relay UE完成了发现过程，remote UE在发现过程中，可以告知relay UE自己的驻留小区/sidelink系统信息获得情况/脱网等信息，relay UE向它自己的服务小区请求了关于relay操作的相关配置，在请求的信息中，也可以携带remote UE的驻留小区/sidelink系统信息获得情况/脱网等信息，例如，能从cell1获得sidelink/relay系统信息配置或者脱网状态。
在请求的信息中携带上述额外信息的目的，是为了网络侧可以配置更匹配于remote UE现有配置、为relay UE进行专用配置，以及可选的用于网络侧下发配置给remote UE，relay UE通过PC5 RRC将这些配置转发给remote UE，例如，可以是给remote UE的专用资源。在其他的实施方式中，也可以不在relay UE的Uu接口携带上述额外信息，而由relay UE直接将它能接收到的SIB中的sidelink/relay信息通过PC5 RRC发送给remote UE，或者根据自己接收到的sidelink相关配置，组织新的配置信息给remote UE，便于二者 通信。具体例如，如果网络侧为relay UE配置了专用资源，例如专用资源池或者周期性专用资源，或者多载波配置，relay UE都可以在PC5接口通知remote UE，便于remote UE能够更高效的在这些资源去接收。
在另一个例子中，如果remote UE处于在网空闲(idle)状态，则可以从系统消息中获得关于sidelink/sidelink relay的配置信息，从而利用这些信息进行和relay UE之间的发现过程。以及在后续的relay通信过程，remote UE也可以继续使用这些公共的配置信息。
可选地，remote UE在发现过程中，可以告知relay UE自己的驻留小区/sidelink系统信息获得情况，relay UE向它自己的服务小区请求了关于relay操作的相关配置，在请求的信息中，也可以携带remote UE的驻留小区/sidelink系统信息获得情况，例如能从cell1获得sidelink/relay系统信息配置或者配置信息标识。
在请求的信息中携带上述额外信息的目的，是为了网络侧可以配置更匹配于remote UE现有配置、为relay UE进行专用配置，以及可选的用于网络侧下发专用配置给remote UE，relay UE通过PC5 RRC将这些配置转发给remote UE，例如，可以是给remote UE的专用资源。在其他的实施方式中，也可以不在relay UE的Uu接口携带上述额外信息，而由relay UE根据自己接收到的sidelink相关配置，组织PC5的配置信息给remote UE，便于二者通信。
在再一个例子中，如果remote UE处于在网连接态，那么无论核心网是否使用非3GPP互通功能(Non-3GPP interworking function，N3IWF)，对接入网节点，例如CU(central unit)或者gNB来说，L3架构里remote UE不具有RRC连接。因此当remote UE处于连接态，需要到relay架构中继续进行数据传输时，相当于remote UE先释放现有连接，进入idle态，再建立relay连接。即remote UE先释放现有的sidelink专用配置，然后如上面所述，从idle状态，进行relay连接建立。
需要说明的是，在L3 relay架构中，由于remote UE没有到网络侧的连 接，因此没有remote UE连接态服务小区的概念，如果remote UE接收到relay UE转发的专用配置，也是网络侧出于将remote UE和relay UE绑定考虑，为remote UE和relay UE之间的PC5链路(link)分配的专用配置。这些专用配置一旦relay UE移出当前小区则失效，需要新小区重新配置，或者在源节点和目标节点接口之间的切换请求消息里携带在源小区的配置，由目标小区重新考虑在自己下面的配置，通过切换命令发送给relay UE，进而再中转给remote UE。
本发明实施方式二：L2架构remote UE配置获取
在L2架构中，remote UE和网络之间有直接的逻辑连接，remote UE的RRC/SDAP/PDCP实体对端位于网络侧，如基站或者CU。Remote UE到网络的数据传输，通过PC5和Uu两段RLC承载(bearer)进行传输，remote UE进行relay操作，需要有连接态服务小区。
在L2架构中，remote UE获得relay操作的相关配置，主要来自于以下途径：一、预配置信息(主要用于relay连接之前)；二、remote UE从驻留小区或者服务小区读取的系统消息；三、remote UE通过Uu RRC接收来自网络侧的配置信息。
对于L2 relay架构中的remote UE来说，主要有两个阶段：第一个阶段，是通过relay UE与网络侧建立RRC连接之前；第二个阶段，是通过relay UE与网络侧建立RRC连接之后。
在第一个阶段，remote UE需要的是sidelink relay操作的一些基本配置，例如，支持L2 relay架构的明确指示，进行L2 relay操作的条件(如，RSRP门限，或业务需求等)，还需要的是sidelink的基本配置，例如公共资源池，公共PC5配置等，这些配置可以通过如下方式获得：1、对于脱网的remote UE，上述两种信息都是通过预配置消息获得；2、对于空闲态的remote UE，上述两种信息都是通过读取SIB消息获得；3、对于连接态态的remote UE，上述两种信息的公共信息部分，可以通过SIB消息获得，也可以由网络侧进一步配置一些专用的配置，例如，专用的RSRP门限等。
Remote UE通过这两类基本的配置信息，则根据这些信息，当判断自己满足relay操作的条件时，则向relay UE发起发现过程，进而建立relay连接。
在第二个阶段，当remote UE通过relay UE与网络侧建立RRC连接之后，remote UE相当于此时进入了RRC连接状态，进入RRC连接态之后，以下过程通过remote UE的RRC过程进行。
例如，Remtoe UE可以上报自己与relay UE之间传输的业务特性，例如QoS profile等，给服务小区；服务小区根据这些业务信息，为remote UE配置SLRB和RLC bearer等；Remote UE接收来自服务小区的SLRB和RLC bearer等，建立相应承载，进行与relay UE的PC5通信。
再例如，Remote UE也可以上报业务的特性，例如周期和传输大小等；服务小区根据这些信息，为remote UE配置专用的周期资源，例如配置调度类型1(configured grant type1)资源，和/或，配置调度类型2(configured grant type 2)资源，或者其它类型的专用资源，例如专用资源池等；Remote UE接收来自服务小区的专用资源和配置，使用相关资源和配置进行与relay UE的PC5通信。
额外的，由于remote UE在通过relay UE与网络侧建立RRC连接之后的服务小区，与通过relay UE与网络侧建立RRC连接之前的服务小区有可能不一致。
例如，remote UE在建立relay连接之前，Idle态驻留在gNB1下的cell1，而由于relay UE的服务小区为相同gNB1下的cell2，为了便于管理，将建立relay连接之后的remote UE的服务小区也确定为gNB1下的cell2，此时相当于remote UE具有的是cell1的SIB消息中的sidelink/sidelink relay公共配置，而没有cell2的SIB消息里的sidelink/sidelink relay公共配置，会导致remote UE在cell2下进行relay操作使用错误的配置信息，除非小区之间提前进行配置协调，保证使用cell1下的系统配置在cell2也可以工作。如果cell2是跨基站gNB2下的小区，则使用错误配置信息的概率就更大
再例如，remote UE在建立relay连接之前，属于脱网状态，只有预配置 的sidelink/sidelink relay公共配置信息，而由于relay UE的服务小区为gNB1下的cell2，为了便于管理，将建立relay连接之后的remote UE的服务小区也确定为gNB1下的cell2，此时相当于remote UE具有的是预配置消息中的sidelink/sidelink relay公共配置，而没有cell2的SIB消息里的sidelink/sidelink relay公共配置，会导致remote UE在cell2下进行relay操作使用错误的配置信息，除非提前进行配置协调，保证使用预配置的系统配置在cell2也可以工作。
解决上述使用错误配置信息的方法如下：
方法1：remote UE在向基站进行连接RRC建立时，携带自己的归属信息，例如脱网状态，之前驻留小区信息，或者之前读取sidelink/sidelink relay SIB消息的小区信息，甚至时具体的sidelink/sidelink relay消息的标识或者版本信息，归属信息可以在RRC连接建立请求或者完成消息，或者专门的消息里携带。
网络侧收到相关的归属信息，就可以知道remote UE当前使用的sidelink/relay公共信息是否可以适用于本次relay操作，如果不能用，则通过RRC消息向remote UE发送新的sidelink/relay配置信息，这些配置信息将覆盖remote UE原有的配置信息。
如果remote UE驻留的小区和建立relay连接之后的新小区是同一个小区，则网络侧不需要发送公共配置信息，remote UE继续使用之前的配置信息即可。
方法2：网络侧使用专门的配置或者标识，以告知remote UE哪些配置信息是可以通用的，哪些是不能通用的。
例如，在remote UE先前获得的预配置信息或者cell1的SIB信息中，可以明确指示是否通用，如果通用，则remote UE在通过relay UE与网络侧建立连接时，不需要请求sidelink/relay配置，如果不通用，则remote UE需要重新请求配置，请求信息可以在RRC连接建立请求或者完成消息，或者专门的消息里携带。
特别的，当remote UE在建立relay连接之前，处于连接态，建立relay连接之后，也是连接态，该过程类似于终端切换过程。当之前服务小区与relay UE服务小区为同一个小区时，类似于进行intra cell handover，sidelink/relay公共和专用配置信息都可以继续使用；当之前服务小区与relay UE服务小区为同一个基站下不同小区时，类似于进行inter cell intra-gNB/CU handover，sidelink/relay公共和专用配置信息都可以重新配置或者继续使用；当之前服务小区与relay UE服务小区为不同基站下不同小区时，类似于进行inter-gNB/CU handover，sidelink/relay公共和专用配置信息都需要重新配置，在基站之间接口协商过程的切换请求消息中和切换响应消息中，分别携带源配置信息和目标配置信息。
本发明实施例三：L3架构DC/CA操作
在L3架构中，remote UE对应的协议栈实体均在relay UE就中止了，并没有和gNB之间有逻辑连接和实体，因此relay UE的DC/CA操作对它影响较小。
从relay UE的Uu接口来看，Relay UE的Uu接口的DRB承载，可以分为两类：一类是relay UE自己的数据，另一类是remote UE的数据。这两类数据可以采取不同的DRB/RLC bearer/逻辑信道进行承载，便于各种切换的场景进行数据重传和状态传递，例如，relay UE自己的数据承载在DRB0-7，DRB8-15为remote UE数据在relay UE的Uu接口的承载。其中，连接同一个relay UE的不同remote UE的数据承载可以是独立的DRB，也可以复用DRB。
如果relay UE被配置了CA操作，即relay UE在Uu接口上，可以使用多个载波进行传输。在多载波的情况下，可选的，可以配置载波限制(Component carrierrestriction)，即特定的逻辑信道/RLC bearer可以使用的CC集合，该载波限制一般用于duplication功能开启时，当逻辑信道1和逻辑信道2是一个DRB对应的两个duplicated逻辑信道时，为了确保duplication效果，避免重复数据在相同的CC上传输，失去duplication增益，可以将逻 辑信道1限制在CC1和CC2上传，逻辑信道2限制在CC3，CC4和CC5上传。
同样的，类似的载波限制也可以用于对remote UE数据对应的逻辑信道进行传输限制，避免Uu接口数据速率太快，而PC5接口速率慢，造成速率失调引起丢包和资源浪费。当然，也可以不用配置任何限制，相当于remote UE数据对应的逻辑信道可以任意使用当前的CC。
如果relay UE被配置了DC操作，则针对relay UE的Uu接口每一个承载，都可以单独配置它是MCG bearer/SCG bearer/split bearer，remote UE数据对应的relay UE的承载，也可以照此配置，选择一种bearer类型。
特别的，如果某个remote UE的一个数据类型具有很高的QoS需求，例如时延特低，和/或，可靠性要求特高，此时可以考虑为这个业务在Uu接口进行duplication传输配置，进行CA或者DC duplication传输。
从relay UE和remote UE之间的PC5接口来看：由于PC5接口和Uu接口相对独立，因此Uu接口配置的CA/DC基本对PC5没有影响。但是从速率匹配角度考虑，Uu接口一旦配置了CA/DC，则remote UE的数据速率在Uu接口被提升，为了使得PC5接口也能够匹配起来，避免超时丢包和资源浪费，此时在PC5接口也可以进行多载波sidelink传输。
当remote UE的一个业务类型具有很高的QoS需求，例如时延特低，和/或，可靠性要求特高，此时可以考虑为这个业务在PC5接口进行duplication传输配置，进行CA duplication传输。PC5接口的CA duplication配置可以和Uu接口的CA/DC duplication机制一起配置，也可以二者单独配置。
本发明实施例四：L2架构DC/CA操作
L2架构中，remote UE对应的L2协议栈实体在relay UE中止，而L3协议的对等端实体均位于gNB/CU，因此relay UE的Uu接口的CA/DC对remote UE有一定的影响。
Relay UE的Uu接口的RLC承载，可以分为两类：一类是relay UE自己的数据，另一类是remote UE的数据。一般来说这两类数据需要采取不同的 RLC bearer/逻辑信道进行承载，便于各种切换的场景进行数据重传和状态传递，例如，relay UE自己的数据承载在RLC bearer/LCID0-7，RLC bearer/LCID8-15为remote UE数据在relay UE的Uu接口的承载，其中，连接同一个relay UE的不同remote UE的数据承载可以是独立的RLC bearer/LCID，也可以复用RLC bearer/LCID。
当relay UE配置了CA：则对于remote UE数据对应的RLC bearer/LCID来说，可以配置这些RLC bearer/LCID是否允许在所有的CC上传输，还是仅允许在部分CC上传输，即可以配置CC子集(subset)，用于限制remote UE数据对应的RLC bearer/LCID。如果限制信息不存在，则意味着可以使用任意CC进行传输remote UE数据。
在PC5接口，对应的RLC bearer也可以进行多载波传输，以满足速率匹配的效果。例如，如果对于一个相同的承载，在Uu接口上以CA方式传输，可以达到100Mbps速率，而在PC5接口仅单载波传输，仅有20Mbps速率，就会造成下行数据在relay UE堆积，进而被删除，浪费了Uu接口传输资源。而此时如果PC5接口也支持多载波传输，速率也达到100Mbps，则可以很好的进行速率匹配，提升传输效率。
特别的，当remote UE的业务QoS要求较高，例如时延要求非常高，和/或，可靠性要求特高的情况下，可以进行下述一种或者多种配置：
在Uu接口，对remote UE的RLC bearer配置CA duplication功能，即传输重复数据的两个RLC bearer配置不同的CC subset，以进行duplication传输，相同的数据在CC subset1和CC subset2上同时传输，以获得较高的可靠性和时延指标；Uu接口的CA duplication由基站配置和控制。
在PC5接口，对remote UE的RLC bearer配置CA duplication功能，即传输重复数据的两个RLC bearer配置不同的CC subset，以进行duplication传输，相同的数据在CC subset1和CC subset2上同时传输，以获得较高的可靠性和时延指标；PC5接口的CA duplication由PC5 RRC配置和PC5 MAC控制，控制的节点可以是relay UE，也可以是PC5接口的发送端UE。
在relay UE配置了DC的情况下：DC操作对remote UE影响最大的是安全参数的不同，如果remote UE的DRB终结于MCG，则该DRB需要使用MCG安全参数，例如key和或安全算法等，如果remote UE的DRB终结于SCG，则该DRB需要使用SCG安全参数。该实施例可以采用如下方式处理安全参数：
一、使remote UE的全部DRB只能终结于一个节点，MCG or SCG，这样remote UE只需要获得一组安全参数；而连接于一个relay UE的不同remote UE可以区分开来，一些终结于MCG，另一些终结于SCG，这样也起到了数据分流的作用，对remote UE影响较小。
二、remote UE可以使用两组或更多安全参数(例如双连接或者多连接)，显式的配置remote UE的每个DRB使用的安全参数，MCG or SCG，这样remote UE对不同的DRB使用不同的安全参数，但remote PC5接口底层并没有多链接操作，即还是一个MAC实体(entity)，需要对现有信令配置进行增强。
对Uu接口来说，remote UE数据对应的relay UE的Uu RLC bearer可以选择不同的路径：一是MCG bearer，这种相当于该RLC bearer直接由relay UE到MCG进行传输；二是SCG bearer，这种相当于该RLC bearer直接由relay UE到SCG进行传输；三是split bearer，这种相当于该RLC bearer由relay UE既可以到MCG也可以到SCG进行传输，相当于两条leg都可以使用，传输速率较高；split RLC bearer也会选择一个节点进行数据聚合，将两条腿分别传输的数据进行按照SN顺序重排序，顺序递交核心网，数据汇聚的节点可配置，当数据汇聚节点为MCG时，该承载使用MCG安全参数，当数据汇聚节点为SCG时，该承载使用SCG安全参数。
同样的，relay UE配置了DC的情况下，Uu接口也可以配置DC duplication机制，即在split bearer配置情况，可以在两条leg传输重复数据，以获得高可靠性低时延的需求，可以在Uu接口，为remote UE的数据配置和激活DC duplication。相应的，在PC5接口，可以配合这种需求，配置和开启CA  duplication，两段可以独立配置也可以一起配置。
另外，对于在Uu接口进行了DC split传输的情况下，因为两个节点数据速率提升，为了速率匹配的目的，也可以在PC5接口开启CA传输。
图4是根据本申请实施例的远端终端的结构示意图，如图4所示，远端终端400包括：确定模块402，可以用于根据如下至少之一，确定副链路中继架构中的副链路配置：预配置信息；从驻留小区或服务小区接收到的系统消息；来自于中继终端的第一配置信息；来自于网络侧设备的第二配置信息。
在本申请实施例中，远端终端可以根据如下至少之一，确定副链路中继架构中的副链路配置：预配置信息；从驻留小区或服务小区接收到的系统消息；来自于中继终端的第一配置信息；来自于网络侧设备的第二配置信息。本申请实施例便于使远端终端、中继终端和网络侧的理解保持一致，提高通信有效性。
可选地，作为一个实施例，所述确定副链路中继架构中的副链路配置之前，所述远端终端处于脱网状态，其中，所述确定模块402，用于：根据所述预配置信息，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述预配置信息与中继终端建立L3中继架构；在所述L3中继架构中，继续使用所述预配置信息确定副链路中继架构中的副链路配置；或者，通过PC5无线资源控制RRC过程接收来自于所述中继终端的第一配置信息确定副链路中继架构中的副链路配置。
可选地，作为一个实施例，所述确定副链路中继架构中的副链路配置之前，所述远端终端处于空闲态或连接态，其中，所述确定模块402，用于：根据所述系统消息或来自于网络侧设备的第二配置信息，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述系统消息或所述第二配置信息与中继终端建立L3中继架构；在所述L3中继架构中，继续使用所述系统消息或所述第二配置信息确定副链路中继架构中的副链路配置；或者，通过PC5RRC过程接收来自于所述中继终端的第一配置信息确定副链路中继架构中的副链路配置。
可选地，作为一个实施例，所述确定副链路中继架构中的副链路配置之前，所述远端终端处于脱网状态，其中，所述确定模块402，用于：根据所述预配置信息，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述预配置信息与中继终端建立L2中继架构；在所述L2中继架构中，通过RRC过程接收来自于所述网络侧设备的第二配置信息确定副链路中继架构中的副链路配置；或者，通过PC5 RRC过程接收来自于所述中继终端的第一配置信息确定副链路中继架构中的副链路配置。
可选地，作为一个实施例，所述确定副链路中继架构中的副链路配置之前，所述远端终端处于空闲态或连接态，其中，所述确定模块402，用于：根据所述系统消息或来自于网络侧设备的第二配置信息，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述系统消息或所述第二配置信息与中继终端建立L2中继架构；在所述L2中继架构中，继续使用所述系统消息确定副链路中继架构中的副链路配置；或者，通过RRC过程接收来自于所述网络侧设备的第二配置信息确定副链路中继架构中的副链路配置。
可选地，作为一个实施例，远端终端400还包括：发送模块，用于向所述网络侧设备发送所述远端终端与所述中继终端之间传输的业务特性，所述业务特性用于所述网络侧设备为所述远端终端配置无线承载信息；接收模块，用于接收所述无线承载信息，并根据所述无线承载信息建立无线承载，所述无线承载用于所述远端终端与所述中继终端进行通信。
可选地，作为一个实施例，远端终端400还包括：发送模块，用于向所述网络侧设备发送所述远端终端与所述中继终端之间传输的业务特性，所述业务特性用于所述网络侧设备为所述远端终端配置专用资源信息；接收模块，用于接收所述专用资源信息，并根据所述专用资源信息指示的专用资源与所述中继终端进行通信。
可选地，作为一个实施例，远端终端400与中继终端进行多载波副链路传输。
可选地，作为一个实施例，所述中继终端与网络侧设备之间的Uu接口 配置了载波聚合CA或双连接DC。
可选地，作为一个实施例，所述远端终端与中继终端之间的目标业务进行CA重复duplication传输，其中，所述目标业务进行CA重复传输是：直接为所述远端终端配置的；在所述远端终端上报所述目标业务的服务质量QoS的情况下，网络侧设备为所述目标业务对应的SLRB配置的；所述目标业务使用的QoS配置开启了CA重复传输功能；所述目标业务的QoS特征配置开启CA重复传输功能。
可选地，作为一个实施例，所述远端终端用于传输重复数据的多个RLC承载分别配置不同的载波单元CC子集。
可选地，作为一个实施例，在中继终端与网络侧设备之间的Uu接口配置了双连接的情况下：所述远端终端使用一组安全参数，所述远端终端的多个数据无线承载DRB对应于一个网络设备；或所述远端终端的多个DRB使用多组安全参数。
根据本申请实施例的远端终端400可以参照对应本申请实施例的方法200的流程，并且，该远端终端400中的各个单元/模块和上述其他操作和/或功能分别为了实现方法200中的相应流程，并且能够达到相同或等同的技术效果，为了简洁，在此不再赘述。
本申请实施例中的远端终端可以是终端，也可以是终端中的部件、集成电路、或芯片。该装置可以是移动终端，也可以为非移动终端。示例性的，移动终端可以包括但不限于上述所列举的终端11的类型，非移动终端可以为服务器、网络附属存储器(Network Attached Storage，NAS)、个人计算机(personal computer，PC)、电视机(television，TV)、柜员机或者自助机等，本申请实施例不作具体限定。
本申请实施例中的远端终端可以为具有操作系统的装置。该操作系统可以为安卓(Android)操作系统，可以为ios操作系统，还可以为其他可能的操作系统，本申请实施例不作具体限定。
本申请实施例提供的远端终端能够实现图2的方法实施例实现的各个过 程，并达到相同的技术效果，为避免重复，这里不再赘述。
可选的，如图5所示，本申请实施例还提供一种通信设备500，包括处理器501，存储器502，存储在存储器502上并可在所述处理器501上运行的程序或指令，例如，该通信设备500为远端终端时，该程序或指令被处理器501执行时实现上述副链路中继架构中的配置方法实施例的各个过程，且能达到相同的技术效果。
图6为实现本申请实施例的一种终端的硬件结构示意图。
该终端600包括但不限于：射频单元601、网络模块602、音频输出单元603、输入单元604、传感器605、显示单元606、用户输入单元607、接口单元608、存储器609、以及处理器610等部件。
本领域技术人员可以理解，终端600还可以包括给各个部件供电的电源(比如电池)，电源可以通过电源管理系统与处理器610逻辑相连，从而通过电源管理系统实现管理充电、放电、以及功耗管理等功能。图6中示出的终端结构并不构成对终端的限定，终端可以包括比图示更多或更少的部件，或者组合某些部件，或者不同的部件布置，在此不再赘述。
应理解的是，本申请实施例中，输入单元604可以包括图形处理器(Graphics Processing Unit，GPU)6041和麦克风6042，图形处理器6041对在视频捕获模式或图像捕获模式中由图像捕获装置(如摄像头)获得的静态图片或视频的图像数据进行处理。显示单元606可包括显示面板6061，可以采用液晶显示器、有机发光二极管等形式来配置显示面板6061。用户输入单元607包括触控面板6071以及其他输入设备6072。触控面板6071，也称为触摸屏。触控面板6071可包括触摸检测装置和触摸控制器两个部分。其他输入设备6072可以包括但不限于物理键盘、功能键(比如音量控制按键、开关按键等)、轨迹球、鼠标、操作杆，在此不再赘述。
本申请实施例中，射频单元601将来自网络侧设备的下行数据接收后，给处理器610处理；另外，将上行的数据发送给网络侧设备。通常，射频单元601包括但不限于天线、至少一个放大器、收发信机、耦合器、低噪声放 大器、双工器等。
存储器609可用于存储软件程序或指令以及各种数据。存储器609可主要包括存储程序或指令区和存储数据区，其中，存储程序或指令区可存储操作系统、至少一个功能所需的应用程序或指令(比如声音播放功能、图像播放功能等)等。此外，存储器609可以包括高速随机存取存储器，还可以包括非易失性存储器，其中，非易失性存储器可以是只读存储器(Read-OnlyMemory，ROM)、可编程只读存储器(ProgrammableROM，PROM)、可擦除可编程只读存储器(ErasablePROM，EPROM)、电可擦除可编程只读存储器(ElectricallyEPROM，EEPROM)或闪存。例如至少一个磁盘存储器件、闪存器件、或其他非易失性固态存储器件。
处理器610可包括一个或多个处理单元；可选的，处理器610可集成应用处理器和调制解调处理器，其中，应用处理器主要处理操作系统、用户界面和应用程序或指令等，调制解调处理器主要处理无线通信，如基带处理器。可以理解的是，上述调制解调处理器也可以不集成到处理器610中。
其中，处理器610，用于根据如下至少之一，确定副链路中继架构中的副链路配置：预配置信息；从驻留小区或服务小区接收到的系统消息；来自于中继终端的第一配置信息；来自于网络侧设备的第二配置信息。
在本申请实施例中，远端终端(如终端600)可以根据如下至少之一，确定副链路中继架构中的副链路配置：预配置信息；从驻留小区或服务小区接收到的系统消息；来自于中继终端的第一配置信息；来自于网络侧设备的第二配置信息。本申请实施例便于使远端终端、中继终端和网络侧的理解保持一致，提高通信有效性。
本申请实施例提供的终端执行时实现上述副链路中继架构中的配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例还提供一种可读存储介质，所述可读存储介质上存储有程序或指令，该程序或指令被处理器执行时实现上述副链路中继架构中的配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再 赘述。
其中，所述处理器可以为上述实施例中所述的终端中的处理器。所述可读存储介质，包括计算机可读存储介质，如计算机只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等。
本申请实施例另提供了一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现上述副链路中继架构中的配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
应理解，本申请实施例提到的芯片还可以称为系统级芯片，系统芯片，芯片系统或片上系统芯片等。
本申请实施例另提供了一种计算机程序产品，所述计算机程序产品存储于非易失性的存储器，所述计算机程序产品被至少一个处理器执行以实现上述副链路中继架构中的配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
本申请实施例另提供了一种通信设备，被配置成用于执行上述副链路中继架构中的配置方法实施例的各个过程，且能达到相同的技术效果，为避免重复，这里不再赘述。
需要说明的是，在本文中，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、物品或者装置不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、物品或者装置所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括该要素的过程、方法、物品或者装置中还存在另外的相同要素。此外，需要指出的是，本申请实施方式中的方法和装置的范围不限按示出或讨论的顺序来执行功能，还可包括根据所涉及的功能按基本同时的方式或按相反的顺序来执行功能，例如，可以按不同于所描述的次序来执行所描述的方法，并且还可以添加、省去、或组合各种步骤。另外，参照某些示例所描述的特征可在其他示例中被 组合。
通过以上的实施方式的描述，本领域的技术人员可以清楚地了解到上述实施例方法可借助软件加必需的通用硬件平台的方式来实现，当然也可以通过硬件，但很多情况下前者是更佳的实施方式。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质(如ROM/RAM、磁碟、光盘)中，包括若干指令用以使得一台终端(可以是手机，计算机，服务器，空调器，或者网络设备等)执行本申请各个实施例所述的方法。
上面结合附图对本申请的实施例进行了描述，但是本申请并不局限于上述的具体实施方式，上述的具体实施方式仅仅是示意性的，而不是限制性的，本领域的普通技术人员在本申请的启示下，在不脱离本申请宗旨和权利要求所保护的范围情况下，还可做出很多形式，均属于本申请的保护之内。

Claims (36)

  1. 一种副链路中继架构中的配置方法，应用于远端终端，所述方法包括：
    根据如下至少之一，确定副链路中继架构中的副链路配置：预配置信息；从驻留小区或服务小区接收到的系统消息；来自于中继终端的第一配置信息；来自于网络侧设备的第二配置信息。
  2. 根据权利要求1所述的方法，其中，所述确定副链路中继架构中的副链路配置之前，所述远端终端处于脱网状态，其中，所述根据如下至少之一，确定副链路中继架构中的副链路配置包括：
    根据所述预配置信息，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述预配置信息与中继终端建立L3中继架构；
    在所述L3中继架构中，继续使用所述预配置信息确定副链路中继架构中的副链路配置；或者，通过PC5无线资源控制RRC过程接收来自于所述中继终端的第一配置信息确定副链路中继架构中的副链路配置。
  3. 根据权利要求1所述的方法，其中，所述确定副链路中继架构中的副链路配置之前，所述远端终端处于空闲态或连接态，其中，所述根据如下至少之一，确定副链路中继架构中的副链路配置包括：
    根据所述系统消息或来自于网络侧设备的第二配置信息，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述系统消息或所述第二配置信息与中继终端建立L3中继架构；
    在所述L3中继架构中，继续使用所述系统消息或所述第二配置信息确定副链路中继架构中的副链路配置；或者，通过PC5RRC过程接收来自于所述中继终端的第一配置信息确定副链路中继架构中的副链路配置。
  4. 根据权利要求3所述的方法，其中，所述确定副链路中继架构中的副链路配置之前，所述远端终端处于连接态，其中，
    在所述L3中继架构中，所述远端终端释放RRC连接，使用所述系统消息确定副链路中继架构中的副链路配置；或者，通过PC5RRC过程接收来自于所述中继终端的第一配置信息确定副链路中继架构中的副链路配置。
  5. 根据权利要求2或3所述的方法，其中，所述方法还包括：
    在和所述中继终端的发现过程中，向所述中继终端发送第一信息，所述第一信息包括所述远端终端的如下至少之一：驻留小区信息、sidelink系统信息获得情况、脱网情况；其中，所述中继终端还用于将所述第一信息发送给网络侧设备。
  6. 根据权利要求2或3所述的方法，其中，所述确定副链路中继架构中的副链路配置之后，所述方法还包括：
    接收第三配置信息，其中，所述第三配置信息是所述中继终端在移出当前小区的情况下，所述远端终端在新小区重新获得的配置。
  7. 根据权利要求1所述的方法，其中，所述确定副链路中继架构中的副链路配置之前，所述远端终端处于脱网状态，其中，所述根据如下至少之一，确定副链路中继架构中的副链路配置包括：
    根据所述预配置信息，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述预配置信息与中继终端建立L2中继架构；
    在所述L2中继架构中，通过RRC过程接收来自于所述网络侧设备的第二配置信息确定副链路中继架构中的副链路配置；或者，通过PC5 RRC过程接收来自于所述中继终端的第一配置信息确定副链路中继架构中的副链路配置。
  8. 根据权利要求7所述的方法，其中，在所述L2中继架构中，
    所述远端终端根据所述第二配置信息，确定副链路传输的副链路无线承载SLRB配置、服务数据适配协议SDAP配置和分组数据汇聚协议PDCP配置；
    所述远端终端根据所述第二配置信息或所述第一配置信息，确定副链路传输的无线链路控制RLC承载配置。
  9. 根据权利要求7所述的方法，其中，所述远端终端通过所述中继终端与所述网络侧设备建立RRC连接之后，
    为所述远端终端选择的服务小区，是所述中继终端的主小区；或
    为所述远端终端选择的服务小区，与所述中继终端的主小区属于同一个网络侧设备。
  10. 根据权利要求1所述的方法，其中，所述确定副链路中继架构中的副链路配置之前，所述远端终端处于空闲态或连接态，其中，所述根据如下至少之一，确定副链路中继架构中的副链路配置包括：
    根据所述系统消息或来自于网络侧设备的第二配置信息，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述系统消息或所述第二配置信息与中继终端建立L2中继架构；
    在所述L2中继架构中，继续使用所述系统消息确定副链路中继架构中的副链路配置；或者，通过RRC过程接收来自于所述网络侧设备的第二配置信息确定副链路中继架构中的副链路配置。
  11. 根据权利要求10所述的方法，其中，
    所述远端终端在与所述网络侧设备建立RRC连接时，携带有所述远端终端的归属信息；其中，所述归属信息包括所述远端终端的如下至少之一：驻留小区信息、sidelink系统信息获得情况、脱网情况。
  12. 根据权利要求10所述的方法，其中，所述方法还包括：
    确定在第一服务小区使用的所述系统消息或所述第二配置信息是否适用于第二服务小区；
    其中，所述第一服务小区是所述远端终端建立RRC连接之前的服务小区，所述第二服务小区是所述RRC连接之后的服务小区，所述第一服务小区与所述第二服务小区相同或不同。
  13. 根据权利要求10所述的方法，其中，所述方法还包括：
    向所述网络侧设备发送所述远端终端与所述中继终端之间传输的业务特性，所述业务特性用于所述网络侧设备为所述远端终端配置无线承载信息；
    接收所述无线承载信息，并根据所述无线承载信息建立无线承载，所述无线承载用于所述远端终端与所述中继终端进行通信。
  14. 根据权利要求10所述的方法，其中，所述方法还包括：
    向所述网络侧设备发送所述远端终端与所述中继终端之间传输的业务特性，所述业务特性用于所述网络侧设备为所述远端终端配置专用资源信息；
    接收所述专用资源信息，并根据所述专用资源信息指示的专用资源与所述中继终端进行通信。
  15. 根据权利要求1所述的方法，其中，所述方法还包括：
    与中继终端进行多载波副链路传输。
  16. 根据权利要求1或15所述的方法，其中，所述中继终端与网络侧设备之间的Uu接口配置了载波聚合CA或双连接DC。
  17. 根据权利要求1所述的方法，其中，所述方法还包括：
    与中继终端之间的目标业务进行CA重复duplication传输，其中，所述目标业务进行CA重复传输是：
    直接为所述远端终端配置的；
    在所述远端终端上报所述目标业务的服务质量QoS的情况下，网络侧设备为所述目标业务对应的SLRB配置的；
    所述目标业务使用的QoS配置开启了CA重复传输功能；
    所述目标业务的QoS特征配置开启CA重复传输功能。
  18. 根据权利要求1所述的方法，其中，所述远端终端用于传输重复数据的多个RLC承载分别配置不同的载波单元CC子集。
  19. 根据权利要求1所述的方法，其中，在中继终端与网络侧设备之间的Uu接口配置了双连接的情况下：
    所述远端终端使用一组安全参数，所述远端终端的多个数据无线承载DRB对应于一个网络设备；或
    所述远端终端的多个DRB使用多组安全参数。
  20. 一种远端终端，包括：
    确定模块，用于根据如下至少之一，确定副链路中继架构中的副链路配置：预配置信息；从驻留小区或服务小区接收到的系统消息；来自于中继终端的第一配置信息；来自于网络侧设备的第二配置信息。
  21. 根据权利要求20所述的远端终端，其中，所述确定副链路中继架构中的副链路配置之前，所述远端终端处于脱网状态，其中，所述确定模块，用于：
    根据所述预配置信息，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述预配置信息与中继终端建立L3中继架构；
    在所述L3中继架构中，继续使用所述预配置信息确定副链路中继架构中的副链路配置；或者，通过PC5无线资源控制RRC过程接收来自于所述中继终端的第一配置信息确定副链路中继架构中的副链路配置。
  22. 根据权利要求20所述的远端终端，其中，所述确定副链路中继架构中的副链路配置之前，所述远端终端处于空闲态或连接态，其中，所述确定模块，用于：
    根据所述系统消息或来自于网络侧设备的第二配置信息，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述系统消息或所述第二配置信息与中继终端建立L3中继架构；
    在所述L3中继架构中，继续使用所述系统消息或所述第二配置信息确定副链路中继架构中的副链路配置；或者，通过PC5RRC过程接收来自于所述中继终端的第一配置信息确定副链路中继架构中的副链路配置。
  23. 根据权利要求20所述的远端终端，其中，所述确定副链路中继架构中的副链路配置之前，所述远端终端处于脱网状态，其中，所述确定模块，用于：
    根据所述预配置信息，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述预配置信息与中继终端建立L2中继架构；
    在所述L2中继架构中，通过RRC过程接收来自于所述网络侧设备的第二配置信息确定副链路中继架构中的副链路配置；或者，通过PC5 RRC过程接收来自于所述中继终端的第一配置信息确定副链路中继架构中的副链路配置。
  24. 根据权利要求20所述的远端终端，其中，所述确定副链路中继架构 中的副链路配置之前，所述远端终端处于空闲态或连接态，其中，所述确定模块，用于：
    根据所述系统消息或来自于网络侧设备的第二配置信息，确定副链路中继架构中的副链路配置，所述远端终端还用于根据所述系统消息或所述第二配置信息与中继终端建立L2中继架构；
    在所述L2中继架构中，继续使用所述系统消息确定副链路中继架构中的副链路配置；或者，通过RRC过程接收来自于所述网络侧设备的第二配置信息确定副链路中继架构中的副链路配置。
  25. 根据权利要求24所述的远端终端，其中，还包括：
    发送模块，用于向所述网络侧设备发送所述远端终端与所述中继终端之间传输的业务特性，所述业务特性用于所述网络侧设备为所述远端终端配置无线承载信息；
    接收模块，用于接收所述无线承载信息，并根据所述无线承载信息建立无线承载，所述无线承载用于所述远端终端与所述中继终端进行通信。
  26. 根据权利要求24所述的远端终端，其中，还包括：
    发送模块，用于向所述网络侧设备发送所述远端终端与所述中继终端之间传输的业务特性，所述业务特性用于所述网络侧设备为所述远端终端配置专用资源信息；
    接收模块，用于接收所述专用资源信息，并根据所述专用资源信息指示的专用资源与所述中继终端进行通信。
  27. 根据权利要求20所述的远端终端，其中，所述远端终端与中继终端进行多载波副链路传输。
  28. 根据权利要求20或27所述的远端终端，其中，所述中继终端与网络侧设备之间的Uu接口配置了载波聚合CA或双连接DC。
  29. 根据权利要求20所述的远端终端，其中，所述远端终端与中继终端之间的目标业务进行CA重复duplication传输，其中，所述目标业务进行CA重复传输是：
    直接为所述远端终端配置的；
    在所述远端终端上报所述目标业务的服务质量QoS的情况下，网络侧设备为所述目标业务对应的SLRB配置的；
    所述目标业务使用的QoS配置开启了CA重复传输功能；
    所述目标业务的QoS特征配置开启CA重复传输功能。
  30. 根据权利要求20所述的远端终端，其中，所述远端终端用于传输重复数据的多个RLC承载分别配置不同的载波单元CC子集。
  31. 根据权利要求20所述的远端终端，其中，在中继终端与网络侧设备之间的Uu接口配置了双连接的情况下：
    所述远端终端使用一组安全参数，所述远端终端的多个数据无线承载DRB对应于一个网络设备；或
    所述远端终端的多个DRB使用多组安全参数。
  32. 一种远端终端，包括处理器，存储器及存储在所述存储器上并可在所述处理器上运行的程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至19任一项所述的副链路中继架构中的配置方法。
  33. 一种可读存储介质，所述可读存储介质上存储程序或指令，所述程序或指令被所述处理器执行时实现如权利要求1至19任一项所述的副链路中继架构中的配置方法。
  34. 一种芯片，所述芯片包括处理器和通信接口，所述通信接口和所述处理器耦合，所述处理器用于运行程序或指令，实现如权利要求1至19任一项所述的副链路中继架构中的配置方法。
  35. 一种计算机程序产品，所述计算机程序产品存储于非易失性的存储器，所述计算机程序产品被至少一个处理器执行以实现如权利要求1至19中任一项所述的副链路中继架构中的配置方法。
  36. 一种通信设备，被配置成用于执行如权利要求1至19中任一项所述的副链路中继架构中的配置方法的步骤。
PCT/CN2021/108846 2020-07-30 2021-07-28 副链路中继架构中的配置方法和终端 Ceased WO2022022550A1 (zh)

Priority Applications (5)

Application Number Priority Date Filing Date Title
KR1020237004643A KR20230037611A (ko) 2020-07-30 2021-07-28 사이드링크 릴레이 아키텍쳐에서의 구성 방법 및 단말
PH1/2023/550104A PH12023550104A1 (en) 2020-07-30 2021-07-28 Configuration method in sidelink relay architecture and terminal
JP2023504039A JP7635362B2 (ja) 2020-07-30 2021-07-28 サイドリンク中継アーキテクチャにおける配置方法と端末
EP21850631.9A EP4192073A4 (en) 2020-07-30 2021-07-28 CONFIGURATION PROCEDURE IN SIDELINK RELAY ARCHITECTURE AND TERMINAL DEVICE
US18/152,936 US20230144480A1 (en) 2020-07-30 2023-01-11 Method for configuring sidelink relay architecture and terminal

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010753310.6A CN114071490B (zh) 2020-07-30 2020-07-30 副链路中继架构中的配置方法和终端
CN202010753310.6 2020-07-30

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/152,936 Continuation US20230144480A1 (en) 2020-07-30 2023-01-11 Method for configuring sidelink relay architecture and terminal

Publications (1)

Publication Number Publication Date
WO2022022550A1 true WO2022022550A1 (zh) 2022-02-03

Family

ID=80037177

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/108846 Ceased WO2022022550A1 (zh) 2020-07-30 2021-07-28 副链路中继架构中的配置方法和终端

Country Status (7)

Country Link
US (1) US20230144480A1 (zh)
EP (1) EP4192073A4 (zh)
JP (1) JP7635362B2 (zh)
KR (1) KR20230037611A (zh)
CN (1) CN114071490B (zh)
PH (1) PH12023550104A1 (zh)
WO (1) WO2022022550A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023050084A1 (zh) * 2021-09-28 2023-04-06 Oppo广东移动通信有限公司 无线通信方法、终端设备及网络设备
WO2023231503A1 (zh) * 2022-05-30 2023-12-07 华为技术有限公司 通信的方法和装置
WO2024010750A1 (en) * 2022-07-06 2024-01-11 Interdigital Patent Holdings, Inc. Methods, architectures, apparatuses and systems for congestion control in multipath sidelink relaying
WO2024163745A1 (en) * 2023-02-01 2024-08-08 Interdigital Patent Holdings, Inc. Carrier selection and restriction for duplication in multipath relaying for new radio (nr) relays
WO2024163755A1 (en) * 2023-02-01 2024-08-08 Interdigital Patent Holdings, Inc. Carrier selection and restriction for duplication in multipath relaying for different data for new radio (nr) relays

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP4152888A4 (en) * 2020-08-07 2023-06-21 Guangdong Oppo Mobile Telecommunications Corp., Ltd. METHOD AND APPARATUS FOR OBTAINING MESSAGE FROM SYSTEM, TERMINAL DEVICE, AND NETWORK DEVICE
JPWO2023002987A1 (zh) * 2021-07-19 2023-01-26
US12317307B2 (en) * 2021-08-30 2025-05-27 Qualcomm Incorporated Signaling for network coding of sidelink communications
CN116097867A (zh) * 2022-09-26 2023-05-09 北京小米移动软件有限公司 资源选择方法、装置、用户设备、基站、存储介质与芯片
CN115918166B (zh) * 2022-09-26 2026-04-17 北京小米移动软件有限公司 控制中继设备信息发送的方法及其装置
CN115734313A (zh) * 2022-10-17 2023-03-03 华为技术有限公司 多路径配置方法、装置及系统
CN118158768A (zh) * 2022-12-05 2024-06-07 维沃移动通信有限公司 中继传输处理方法、装置、终端及网络侧设备
CN118524461A (zh) * 2023-02-17 2024-08-20 华为技术有限公司 侧行链路通信方法和装置
EP4694502A1 (en) * 2023-04-03 2026-02-11 LG Electronics Inc. Method and device for transmitting pc5 rrc message, of multi-carrier-supporting terminal

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110574476A (zh) * 2017-05-05 2019-12-13 高通股份有限公司 设备到设备通信系统中的中继
CN110679190A (zh) * 2017-05-11 2020-01-10 Lg电子株式会社 用于在无线通信系统中使用中继ue来分配侧链路资源的方法和装置
CN110677921A (zh) * 2019-09-26 2020-01-10 展讯半导体(南京)有限公司 侧链路无线承载的配置方法、装置
WO2020037688A1 (en) * 2018-08-24 2020-02-27 Nec Corporation A method, device and computer readable media for sidelink configuration transmission and reception
CN112771956A (zh) * 2018-09-28 2021-05-07 中兴通讯股份有限公司 用于配置和调度侧链路资源的方法和装置

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017014716A1 (en) * 2015-07-23 2017-01-26 Intel IP Corporation Layer 2 relay protocols and mobility relay method
US10924912B2 (en) 2017-01-06 2021-02-16 Lg Electronics Inc. Method for transmitting and receiving data through relay in wireless communication system and apparatus therefor
CN108391285B (zh) * 2017-02-03 2023-05-05 中兴通讯股份有限公司 一种设备直通系统的通信方法、数据转发方法及装置
US11109434B2 (en) * 2017-02-06 2021-08-31 Lg Electronics Inc. Method for handling of a RRC connection request message of a remote UE by a relay UE in wireless communication system and a device therefor
WO2019059638A1 (ko) * 2017-09-22 2019-03-28 주식회사 케이티 릴레이 노드의 데이터 처리 방법 및 그 장치
CN111279768B (zh) * 2017-09-28 2023-11-14 联想(北京)有限公司 用于侧链路上的探测参考信号传输的方法和装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110574476A (zh) * 2017-05-05 2019-12-13 高通股份有限公司 设备到设备通信系统中的中继
CN110679190A (zh) * 2017-05-11 2020-01-10 Lg电子株式会社 用于在无线通信系统中使用中继ue来分配侧链路资源的方法和装置
WO2020037688A1 (en) * 2018-08-24 2020-02-27 Nec Corporation A method, device and computer readable media for sidelink configuration transmission and reception
CN112771956A (zh) * 2018-09-28 2021-05-07 中兴通讯股份有限公司 用于配置和调度侧链路资源的方法和装置
CN110677921A (zh) * 2019-09-26 2020-01-10 展讯半导体(南京)有限公司 侧链路无线承载的配置方法、装置

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
MEDIATEK INC.: "Scenarios and Assumptions on Sidelink Relay", 3GPP DRAFT; R2-2006570, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. electronic; 20200817 - 20200828, 7 August 2020 (2020-08-07), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051911513 *
See also references of EP4192073A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023050084A1 (zh) * 2021-09-28 2023-04-06 Oppo广东移动通信有限公司 无线通信方法、终端设备及网络设备
WO2023231503A1 (zh) * 2022-05-30 2023-12-07 华为技术有限公司 通信的方法和装置
WO2024010750A1 (en) * 2022-07-06 2024-01-11 Interdigital Patent Holdings, Inc. Methods, architectures, apparatuses and systems for congestion control in multipath sidelink relaying
WO2024163745A1 (en) * 2023-02-01 2024-08-08 Interdigital Patent Holdings, Inc. Carrier selection and restriction for duplication in multipath relaying for new radio (nr) relays
WO2024163755A1 (en) * 2023-02-01 2024-08-08 Interdigital Patent Holdings, Inc. Carrier selection and restriction for duplication in multipath relaying for different data for new radio (nr) relays

Also Published As

Publication number Publication date
CN114071490A (zh) 2022-02-18
JP2023537241A (ja) 2023-08-31
US20230144480A1 (en) 2023-05-11
CN114071490B (zh) 2025-02-25
JP7635362B2 (ja) 2025-02-25
EP4192073A1 (en) 2023-06-07
KR20230037611A (ko) 2023-03-16
EP4192073A4 (en) 2024-01-03
PH12023550104A1 (en) 2024-03-18

Similar Documents

Publication Publication Date Title
WO2022022550A1 (zh) 副链路中继架构中的配置方法和终端
US11284468B2 (en) Suspending/resuming measurements in RRC inactive state
CN113905397B (zh) 中继确定方法、配置方法、装置、终端及网络侧设备
CN102843302B (zh) 终端接入方法及设备
JP2024039629A (ja) マルチアクセスポイント関連付け
WO2022068714A1 (zh) 传输配置的方法、装置和设备
CN115623451B (zh) 条件切换方法和设备
CN116711371A (zh) 用于mbs的无线通信的装置和方法
WO2022022736A1 (zh) 接入控制方法及装置
WO2022078394A1 (zh) 多播业务的传输方法、装置及通信设备
WO2021019701A1 (ja) 端末及び通信ノード
WO2023000334A1 (zh) Pdcch监听方法、装置、设备及存储介质
US20230180046A1 (en) Sl and wlan interworking method and apparatus and communication device
CN104735703B (zh) 一种主基站、用户终端和通信系统
WO2022057892A1 (zh) 业务数据传输方法及装置、终端和基站
WO2022012526A1 (zh) 处理方法、发送方法及相关设备
KR20250099337A (ko) 무선 통신 시스템에서 셀 상태에 기반한 모빌리티 제어
WO2023001172A1 (zh) 推荐比特率确定方法、装置及相关设备
WO2022188771A1 (zh) 副链路的非连续接收配置方法、装置、设备及可读存储介质
WO2022228437A1 (zh) 切换方法、装置、设备及可读存储介质
WO2022083545A1 (zh) 中继的配置方法、装置及用户设备
JP7699218B2 (ja) サービスデータ処理方法、装置及び機器
KR20200023842A (ko) 단말 연결 해제 방법 및 이를 운용하는 기지국
WO2025051113A1 (zh) 网络连接的处理方法、终端及网络侧设备
CN120075939A (zh) 数据转发方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21850631

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 202327002925

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2023504039

Country of ref document: JP

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 20237004643

Country of ref document: KR

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2021850631

Country of ref document: EP

ENP Entry into the national phase

Ref document number: 2021850631

Country of ref document: EP

Effective date: 20230228

NENP Non-entry into the national phase

Ref country code: DE

WWG Wipo information: grant in national office

Ref document number: 202327002925

Country of ref document: IN