IP Library Granted Patent US 12,414,032
Granted Patent B2
US 12,414,032 · App. 17/890,276 · Granted Sep 9, 2025

Relay method, routing table generation method and apparatus, terminal, and storage medium

Inventor: Qianxi Lu (Guangdong, CN)
Assignee: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.
H04W40/248H04W76/14H04W80/02H04W92/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,414,032
App. No.
17/890,276
Granted
Sep 9, 2025
Kind
B2
Abstract

The application discloses a relay method, a routing table generation method and apparatus, a terminal and a storage medium. The relay method is applied to a relay UE. The relay UE comprises a relay protocol stack, the relay protocol stack being located between a PDCP layer and a layer 2 protocol stack of a PC5 interface, or the relay protocol stack being a MAC layer protocol stack, and the relay protocol stack comprising a relay receiving entity and a relay sending entity. The relay method comprises: the relay receiving entity receiving a relay protocol data unit (PDU) sent by a last hop node, and forwarding the relay PDU to the relay sending entity; and the relay sending entity sending the relay PDU to a next hop node according to a protocol header of the relay PDU, the relay PDU being a PDU sent between at least two remote UEs.

Claims (76)

1. A relay UE, comprising a relay protocol stack, the relay protocol stack being located between a packet data convergence protocol (PDCP) layer and a layer 2 protocol stack of a PC5 interface, and the relay protocol stack comprising a relay receiving entity and a relay sending entity;

wherein the relay UE comprises method comprising:

a processor; and

memory for storing executable instructions for the processor;

wherein the processor is configured to execute the instructions stored in the memory to cause the relay UE to perform:

receiving a relay protocol data unit (PDU) sent by a last hop node through the relay receiving entity; and forwarding the relay PDU to the relay sending entity;

sending the relay PDU to a next hop node through the relay sending entity according to a protocol header of the relay PDU;

wherein the relay PDU is a PDU sent between at least two remote UEs;

wherein the relay PDU comprises a first relay PDU; and the first relay PDU is a PDU sent by a first remote UE to a second remote UE;

wherein a protocol header of the first relay PDU comprises a first source ID and a first destination ID; the first source ID comprises a UE ID of the first remote UE; and the first destination ID comprises a UE ID of the second remote UE;

wherein the processor is further configured to execute the instructions stored in the memory to cause the relay UE to perform:

when a first routing relationship corresponding to the first destination ID is included in a relay routing table, sending the first relay PDU to the next hop node through the relay sending entity according to the first routing relationship;

wherein the first routing relationship comprises the UE ID of the second remote UE and a node ID of the next hop node, and the first routing relationship is a routing relationship when the UE ID of the second remote UE is used as the destination ID.

2. The relay UE according to claim 1 , wherein the processor is further configured to execute the instructions stored in the memory to cause the relay UE to perform:

when no first routing relationship corresponding to the first destination ID is included in the relay routing table, sending the first relay PDU to a default next hop node through the relay sending entity, wherein a number of the default next hop node is at least one.

3. The relay UE according to claim 1 , wherein the processor is further configured to execute the instructions stored in the memory to cause the relay UE to perform:

establishing a second routing relationship in the relay routing table through the relay receiving entity when no routing relationship corresponding to the first source ID is included in the relay routing table;

wherein the second routing relationship comprises the UE ID of the first remote UE and the node ID of the last hop node; the second routing relationship is a routing relationship when the UE ID of the first remote UE is used as the destination ID.

4. The relay UE according to claim 1 , wherein the first relay PDU further comprises the first PDCP PDU;

wherein the first PDCP PDU comprises at least one of a first signaling and a first data packet, the first signaling is a signaling related to the first remote UE as a sender, and the first data packet is a data packet related to the first remote UE as a sender.

5. The relay UE according to claim 1 , wherein

when the relay protocol stack is located between the PDCP layer and the layer 2 protocol stack of the PC5 interface, the relay PDU further comprises a first radio bearer identifier.

6. The relay UE according to claim 1 , wherein an end-to-end protocol stack between the at least two remote UEs comprises:

the PDCP layer protocol stack of the PC 5 interface and other protocol layers located above the PDCP protocol layer.

7. The relay UE according to claim 1 , wherein a point-to-point protocol stack between the relay UE and the last hop node comprises:

the layer 2 protocol stack and a layer 1 protocol stack of the PC5 interface, wherein the layer 2 protocol stack comprises a radio link control (RLC) layer protocol stack and a MAC layer protocol stack, and the layer 1 protocol stack comprises a physical (PHY) layer protocol stack.

8. A first remote UE, comprising a relay protocol stack, the relay protocol stack being located between a packet data convergence protocol (PDCP) layer and a layer 2 protocol stack of a PC5 interface, and the relay protocol stack comprising a relay sending entity;

wherein the first remote UE comprises:

a processor; and

memory for storing executable instructions for the processor;

wherein the processor is configured to execute the instructions stored in the memory to cause the first remote UE to perform:

receiving a PDCP protocol data unit (PDU) transmitted by the PDCP layer protocol stack, generating a relay protocol data unit (PDU) according to the PDCP PDU, and sending the relay PDU to a next hop node through the relay sending entity;

wherein the relay PDU is a PDU sent between at least two remote UEs;

wherein the relay PDU comprises a first relay PDU, and the first relay PDU is a PDU sent by the first remote UE to a second remote UE;

wherein a protocol header of the first relay PDU comprises a first source ID and a first destination ID; the first source ID comprises a UE ID of the first remote UE; and the first destination ID comprises a UE ID of the second remote UE;

wherein the processor is further configured to execute the instructions stored in the memory to cause the first remote UE to perform:

when a first routing relationship corresponding to the first destination ID is included in a relay routing table, sending the first relay PDU to the next hop node through the relay sending entity according to the first routing relationship;

wherein the first routing relationship comprises the UE ID of the second remote UE and a node ID of the next hop node, and the first routing relationship is a routing relationship when the UE ID of the second remote UE is used as the destination ID.

9. The first remote UE according to claim 8 , wherein the relay protocol stack further comprises a relay receiving entity, and the processor is further configured to execute the instructions stored in the memory to cause the first remote UE to perform:

receiving a second relay PDU through the relay receiving entity, wherein the second relay PDU is a PDU sent by the second remote UE to the first remote UE, and the second source ID of the second relay PDU comprises the UE ID of the second remote UE;

establishing the first routing relationship in the relay routing table through the relay receiving entity when no routing relationship corresponding to the second source ID is included in the relay routing table.

10. The first remote UE according to claim 8 , wherein the processor is further configured to execute the instructions stored in the memory to cause the first remote UE to perform:

when a sidelink exists between the first remote UE and the second remote UE, sending the relay PDU to the second remote UE through the sidelink.

11. The first remote UE according to claim 8 , wherein the first relay PDU further comprises a first PDCP PDU;

wherein the first PDCP PDU comprises at least one of a first signaling and a first data packet, the first signaling is a signaling related to the first remote UE as a sender, and the first data packet is a data packet related to the first remote UE as a sender.

12. The first remote UE according to claim 8 , wherein

when the relay protocol stack is located between the PDCP layer and the layer 2 protocol stack of the PC5 interface, the relay PDU further comprises a first radio bearer identifier.

13. The first remote UE according to claim 8 , wherein an end-to-end protocol stack between the at least two remote UEs comprises:

the PDCP layer protocol stack of the PC5 interface and other protocol layers located above the PDCP protocol layer.

14. The first remote UE according to claim 8 , wherein a point-to-point protocol stack between the first remote UE and the next hop node comprises:

the layer 2 protocol stack and a layer 1 protocol stack of the PC5 interface, wherein the layer 2 protocol stack comprises a radio link control (RLC) layer protocol stack and a MAC layer protocol stack, and the layer 1 protocol stack comprises a physical (PHY) layer protocol stack.

15. The first remote UE according to claim 8 , wherein the relay protocol stack further comprises a relay receiving entity, and the processor is further configured to execute the instructions stored in the memory to cause the first remote UE to perform:

receiving a second relay PDU through the relay receiving entity, wherein the second relay PDU is a relay PDU sent by the second remote UE to the first remote UE.

16. The first remote UE according to claim 15 , wherein the second relay PDU comprises a second PDCP PDU;

wherein the relay receiving entity transmits the second PDCP PDU to an upper layer protocol.

17. The first remote UE according to claim 15 , wherein

when the relay protocol stack is located between the PDCP layer and the layer 2 protocol stack of the PC5 interface, the second relay PDU further comprises a second radio bearer identifier, and the relay receiving entity transmits the second radio bearer identifier to the PDCP layer protocol stack.

18. A second remote UE, comprising a relay protocol stack, the relay protocol stack being located between a packet data convergence protocol (PDCP) layer and a layer 2 protocol stack of a PC5 interface, the relay protocol stack comprising a relay receiving entity and a relay sending entity;

wherein the second remote UE comprises:

a processor; and

memory for storing executable instructions for the processor;

wherein the processor is configured to execute the instructions stored in the memory to cause the second remote UE to perform:

receiving a relay protocol data unit (PDU) from a last hop node through the relay receiving entity and transmitting a first PDCP PDU in the relay PDU to the PDCP layer;

wherein the relay PDU is a PDU sent between at least two remote UEs;

wherein the relay PDU comprises a first relay PDU; and the first relay PDU is a PDU sent by a first remote UE to the second remote UE;

wherein a protocol header of the first relay PDU comprises a first source ID and a first destination ID; the first source ID comprises a UE ID of the first remote UE; and the first destination ID comprises a UE ID of the second remote UE;

wherein the first relay PDU is received from the last hop node through the relay sending entity according to a first routing relationship when the first routing relationship corresponding to the first destination ID is included in a relay routing table;

wherein the first routing relationship comprises the UE ID of the second remote UE and a node ID of a next hop node, and the first routing relationship is a routing relationship when the UE ID of the second remote UE is used as the destination ID.

19. The second remote UE according to claim 18 , the processor is further configured to execute the instructions stored in the memory to cause the second remote UE to perform:

when the first destination ID in the first relay PDU is the same as the UE ID of the second remote UE, transmitting the first PDCP PDU to the PDCP layer through the relay receiving entity;

wherein the first PDCP PDU comprises at least one of a first signaling and a first data packet, the first signaling is a signaling related to the first remote UE as a sender, and the first data packet is a data packet related to the first remote UE as a sender;

wherein the processor is further configured to execute the instructions stored in the memory to cause the second remote UE to perform:

receiving the PDCP PDU sent by the PDCP layer, generating a second relay PDU according to the PDCP PDU, and sending the second relay PDU to the next hop node through the relay sending entity, wherein the second relay PDU is a relay PDU sent by the second remote UE to the first remote UE.

20. The second remote UE according to claim 18 , wherein the processor is further configured to execute the instructions stored in the memory to cause the second remote UE to perform:

establishing a second routing relationship in the relay routing table through the relay receiving entity when no routing relationship corresponding to the first source ID is included in the relay routing table;

wherein the second routing relationship comprises the UE ID of the first remote UE and the node ID of the last hop node; and the second routing relationship is a routing relationship when the UE ID of the first remote UE is used as the destination ID.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 30, 2022
From: LU, QIANXI
To: GUANGDONG OPPO MOBILE TELECOMMUNICATIONS CORP., LTD.
Reel/Frame 060933/0590 →
Continuity (2)
Continuation PCTCN2020076485 · Feb 24, 2020
Related Publication 20220408344A1 · Dec 22, 2022
References Cited (21)
US 11375527B1 · Eyuboglu · 2022 [cited by examiner]
US 20130016651A1 · Zhang · 2013 [cited by examiner]
US 20180116007A1 · Yasukawa · 2018 [cited by examiner]
US 20190021123A1 · Ma · 2019 [cited by examiner]
US 20190373652A1 · Hong · 2019 [cited by examiner]
US 20210160956A1 · Wang · 2021 [cited by examiner]
US 20220361267A1 · Wang · 2022 [cited by examiner]
US 20230063139A1 · Du · 2023 [cited by examiner]
US 20230073469A1 · Wang · 2023 [cited by examiner]
CN 105657838 · 2016 [cited by applicant]
CN 105992273 · 2016 [cited by applicant]
WO 2018175817 · 2018 [cited by applicant]
WO WO2021139771A1 · 2021 [cited by examiner]
Huawei et al. “Layer 2 architecture for UE-to-Network Relay” 3GPP TSG RAN WG2 Meeting #95 R2-165464, Aug. 2016, pp. 1-6. [cited by applicant]
“International Search Report (Form PCT/ISA/210) of PCT/CN2020/076485,” mailed on Nov. 26, 2020, with English translation thereof, pp. 1-4. [cited by applicant]
“Written Opinion of the International Searching Authority (Form PCT/ISA/237) of PCT/CN2020/076485,” mailed on Nov. 26, 2020, with English translation thereof, pp. 1-6. [cited by applicant]
ZTE, “Consideration on Routing in IAB Architecture 1a and 1b”, 3GPP TSG-RAN WG2 #103 R2-1812469, Aug. 2018, pp. 1-4. [cited by applicant]
ZTE, “Discussion on layer 2 ProSe UE-to-network relay for feD2D”, 3GPP TSG-RAN WG2 Meeting #95bis R2-166815, Oct. 2016, pp. 1-7. [cited by applicant]
OPPO, “TP on Layer-2 Relay Data Identification”, 3GPP TSG-RAN2 Meeting #98 R2-1704097, May 2017, pp. 1-6. [cited by applicant]
Coolpad, “Discussion on Signaling Radio Bearer Modelling for L2 Relay UE”, 3GPP TSG RAN WG2 Meeting #98 R2-1704553, May 2017, pp. 1-4. [cited by applicant]
“Search Report of Europe Counterpart Application No. 20915870.8”, issued on Mar. 20, 2023, pp. 1-10. [cited by applicant]