IP Library › Granted Patent US 12,745,105
Granted Patent B2
US 12,745,105 · App. 18/152,936 · Granted Sep 22, 2026

Method for configuring sidelink relay architecture and terminal

Inventor: Jiamin Liu (Guangdong, CN)
Assignee: VIVO MOBILE COMMUNICATION CO., LTD.
H04W24/02H04W76/14H04W88/04H04W92/18
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,745,105
App. No.
18/152,936
Granted
Sep 22, 2026
Kind
B2
Abstract

Embodiments of this application disclose a method for configuring a sidelink relay architecture and a terminal, so as to resolve a problem that a remote terminal cannot obtain a sidelink configuration for the sidelink relay architecture. The method can be applied to a remote terminal, and includes: determining a sidelink configuration for the sidelink relay architecture based on at least one of the following: pre-configuration information; a system message received from a camping cell or serving cell; first configuration information from a relay terminal; and second configuration information from a network-side device.

Claims (53)

1 . A method for configuring a sidelink relay architecture, applied to a remote terminal, wherein the method comprises:

determining a sidelink configuration for the sidelink relay architecture based on at least one of first configuration information from a relay terminal and second configuration information from a network-side device;

wherein the determining a sidelink configuration for the sidelink relay architecture comprises:

in a layer 2 (L2) relay architecture, determining the sidelink configuration for the sidelink relay architecture based on the second configuration information from the network-side device received in a radio resource control (RRC) procedure or determining the sidelink configuration for the sidelink relay architecture based on the first configuration information from the relay terminal received in a PC5 RRC procedure;

wherein in the L2 relay architecture, the remote terminal determines, for sidelink transmission based on the second configuration information, a sidelink radio bearer (SLRB) configuration, a service data adaptation protocol (SDAP) configuration, and a packet data convergence protocol (PDCP) configuration; and

the remote terminal determines, based on the second configuration information or the first configuration information, a radio link control (RLC) bearer configuration for sidelink transmission;

wherein the method further comprises performing carrier aggregation (CA) duplication transmission for a target service with a relay terminal, wherein the CA duplication transmission for the target service is:

configured by the network-side device for a sidelink radio bearer (SLRB) corresponding to the target service in a case that the remote terminal reports quality of service (QoS) of the target service;

enabling a CA duplication transmission function in a QoS profile used for the target service; or

enabling a CA duplication transmission function in a QoS feature profile of the target service.

2 . The method according to claim 1 , wherein the method further comprises:

performing multi-carrier sidelink transmission with the relay terminal.

3 . The method according to claim 1 , wherein carrier aggregation (CA) or dual connectivity (DC) is configured for a Uu interface between the relay terminal and the network-side device.

4 . The method according to claim 1 , wherein multiple RLC bearers used by the remote terminal to transmit duplicate data are configured to different component carrier (CC) subsets, respectively.

5 . The method according to claim 1 , wherein in a case that dual connectivity is configured for a Uu interface between the relay terminal and the network-side device:

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

multiple DRBs of the remote terminal use multiple sets of security parameters.

6 . A remote terminal, comprising a processor, a memory, and a program or instructions stored in the memory and capable of running on the processor, wherein when the program or instructions are executed by the processor, the following steps are implemented:

determining a sidelink configuration for the sidelink relay architecture based on at least one of first configuration information from a relay terminal and second configuration information from a network-side device;

wherein the determining a sidelink configuration for the sidelink relay architecture comprises:

in a layer 2 (L2) relay architecture, determining the sidelink configuration for the sidelink relay architecture based on the second configuration information from the network-side device received in a radio resource control (RRC) procedure or determining the sidelink configuration for the sidelink relay architecture based on the first configuration information from the relay terminal received in a PC5 RRC procedure;

wherein in the L2 relay architecture, the remote terminal determines, for sidelink transmission based on the second configuration information, a sidelink radio bearer (SLRB) configuration, a service data adaptation protocol (SDAP) configuration, and a packet data convergence protocol (PDCP) configuration; and

the remote terminal determines, based on the second configuration information or the first configuration information, a radio link control (RLC) bearer configuration for sidelink transmission;

wherein when the program or instructions are executed by the processor, the following steps are further implemented:

performing carrier aggregation (CA) duplication transmission for a target service with a relay terminal, wherein the CA duplication transmission for the target service is:

configured by the network-side device for a sidelink radio bearer (SLRB) corresponding to the target service in a case that the remote terminal reports quality of service (QoS) of the target service;

enabling a CA duplication transmission function in a QoS profile used for the target service; or

enabling a CA duplication transmission function in a QoS feature profile of the target service.

7 . The remote terminal according to claim 6 , wherein the following steps are further implemented:

performing multi-carrier sidelink transmission with the relay terminal.

8 . The remote terminal according to claim 6 , wherein carrier aggregation (CA) or dual connectivity (DC) is configured for a Uu interface between the relay terminal and the network-side device.

9 . The remote terminal according to claim 6 , wherein multiple RLC bearers used by the remote terminal to transmit duplicate data are configured to different component carrier (CC) subsets, respectively.

10 . The remote terminal according to claim 6 , wherein in a case that dual connectivity is configured for a Uu interface between the relay terminal and the network-side device:

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

multiple DRBs of the remote terminal use multiple sets of security parameters.

11 . A non-transitory readable storage medium, wherein the non-transitory readable storage medium stores a program or instructions, and when the program or instructions are executed by a processor, the following steps are implemented:

determining a sidelink configuration for the sidelink relay architecture based on at least one of first configuration information from a relay terminal and second configuration information from a network-side device;

wherein the determining a sidelink configuration for the sidelink relay architecture comprises:

in a layer 2 (L2) relay architecture, determining the sidelink configuration for the sidelink relay architecture based on the second configuration information from the network-side device received in a radio resource control (RRC) procedure or determining the sidelink configuration for the sidelink relay architecture based on the first configuration information from the relay terminal received in a PC5 RRC procedure;

wherein in the L2 relay architecture, determining, for sidelink transmission based on the second configuration information, a sidelink radio bearer (SLRB) configuration, a service data adaptation protocol (SDAP) configuration, and a packet data convergence protocol (PDCP) configuration; and

determining, based on the second configuration information or the first configuration information, a radio link control (RLC) bearer configuration for sidelink transmission-;

wherein when the program or instructions are executed by the processor, the following steps are further implemented:

performing carrier aggregation (CA) duplication transmission for a target service with a relay terminal, wherein the CA duplication transmission for the target service is:

configured by the network-side device for a sidelink radio bearer (SLRB) corresponding to the target service in a case that the remote terminal reports quality of service (QoS) of the target service;

enabling a CA duplication transmission function in a QoS profile used for the target service; or

enabling a CA duplication transmission function in a QoS feature profile of the target service.

12 . The non-transitory readable storage medium according to claim 11 , wherein the following steps are further implemented:

performing multi-carrier sidelink transmission with the relay terminal.

13 . The non-transitory readable storage medium according to claim 11 , wherein carrier aggregation (CA) or dual connectivity (DC) is configured for a Uu interface between the relay terminal and the network-side device.

14 . The non-transitory readable storage medium according to claim 11 , wherein multiple RLC bearers used by the remote terminal to transmit duplicate data are configured to different component carrier (CC) subsets, respectively.

15 . The non-transitory readable storage medium according to claim 11 , wherein in a case that dual connectivity is configured for a Uu interface between the relay terminal and the network-side device:

using a set of security parameters, and multiple data radio bearer (DRBs) of the remote terminal correspond to one network device; or

multiple DRBs of the remote terminal use multiple sets of security parameters.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 11, 2023
From: LIU, JIAMIN
To: VIVO MOBILE COMMUNICATION CO., LTD.
Reel/Frame 062342/0784 →
Priority Claims (1)
CN 202010753310.6 · Jul 30, 2020 · national
Continuity (2)
Continuation PCTCN2021108846 · Jul 28, 2021
Related Publication 20230144480A1 · May 11, 2023
References Cited (42)
US 20150092942A1 · Wager · 2015 [cited by examiner]
US 20160330781A1 · Kalhan et al. · 2016 [cited by applicant]
US 20180324842A1 · Gulati et al. · 2018 [cited by applicant]
US 20180343556A1 · Wang et al. · 2018 [cited by applicant]
US 20190215685A1 · Wang et al. · 2019 [cited by applicant]
US 20200092685A1 · Fehrenbach · 2020 [cited by examiner]
US 20200100088A1 · Kim et al. · 2020 [cited by applicant]
US 20200229194A1 · Belleschi · 2020 [cited by examiner]
US 20200389900A1 · Lee et al. · 2020 [cited by applicant]
US 20210144791A1 · Kang · 2021 [cited by examiner]
US 20210212050A1 · Lu et al. · 2021 [cited by applicant]
US 20210297899A1 · Baek · 2021 [cited by examiner]
US 20210314112A1 · Balasubramanian · 2021 [cited by examiner]
US 20220053517A1 · Kim · 2022 [cited by examiner]
US 20220109970A1 · Jeong · 2022 [cited by examiner]
US 20220303821A1 · Kang · 2022 [cited by examiner]
US 20220346162A1 · Van Phan · 2022 [cited by examiner]
US 20230066281A1 · Tseng · 2023 [cited by examiner]
US 20230073469A1 · Wang · 2023 [cited by examiner]
US 20230156839A1 · Bi · 2023 [cited by examiner]
US 20230269799A1 · Cai · 2023 [cited by examiner]
CN 110574476A · 2019 [cited by applicant]
CN 110677921A · 2020 [cited by applicant]
CN 110679190A · 2020 [cited by applicant]
CN 112771956A · 2021 [cited by applicant]
EP 3531723A1 · 2019 [cited by applicant]
EP 3579642A1 · 2019 [cited by applicant]
KR 20180112810A · 2018 [cited by applicant]
WO 2018208114A1 · 2018 [cited by applicant]
WO 2019061167A1 · 2019 [cited by applicant]
WO 2020037688A1 · 2020 [cited by applicant]
WO WO2020222595A1 · 2020 [cited by examiner]
MediaTek Inc., Scenarios and Assumptions on Sidelink Relay, Discussion and decision, 3GPP TSG-RAN WG2 Meeting #111 electronic, R2-2006570, Aug. 17-28, 2020, Online. [cited by applicant]
3rd Generation Partnership Project, Technical Specification Group Services and System Aspects; Study on system enhancement for Proximity based Services (ProSe) in the 5G System (5GS), (Release 17), 3GPP TR 23.752 V0.4.0… [cited by applicant]
Coolpad, Resource Allocation for IC and OOC Scenarios, 3GPP TSG-RAN WG2 #92, R2-156399, Nov. 16-20, 2015, Anaheim, USA. [cited by applicant]
Vivo, Protocol stack and service continuity for L2 and L3 relay, 3GPP TSG-RAN WG2 Meeting #111-e, R2-2007041, E-Meeting, Aug. 17-Aug. 28, 2020. [cited by applicant]
Apple, Lenovo, Motorola Mobility, Mediatek Inc., Philips, Fraunhofer IIS, Fraunhofer HHI, Interdigital, KPN, AT&T, Convida Wireless, Sony, R17 Sidelink Relay, 3GPP TSG RAN Meeting #86, RP-193106, Dec. 9-12, 2019, Sitges… [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Services and System Aspects; Proximity-based services (ProSe) Stage 2, (Release 16)”, 3GPP TS 23.303 V16.0.0, Jul. 2020, Valbonne, France. [cited by applicant]
3rd Generation Partnership Project, “Technical Specification Group Radio Access Network; NR; Radio Resource Control (RRC) protocol specification (Release 16)”, 3GPP TS 38.331 V16.1.0, Jul. 2020, Valbonne, France. [cited by applicant]
First Korean Office Action for Korean Patent Application No. 10-2023-7004643 mailed Sep. 23, 2025, 11 pages. [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 16)”, 3GPP TS 23.502 V16.5.0 (Jul. 2020), Valbonne—France. [cited by applicant]
Ericsson, “Signalling to support UE-NW relay and Service continuity”, 3GPP TSG-RAN WG2 #89bis Tdoc, R2-151148, Bratislava, Slovakia, Apr. 20-24, 2015. [cited by applicant]