IP Library › Granted Patent US 12,452,632
Granted Patent B2
US 12,452,632 · App. 17/866,832 · Granted Oct 21, 2025

Bearer establishment method, configuration method, terminal, and network side device

Inventor: Wei Bao (Dongguan, CN)
Assignee: VIVO MOBILE COMMUNICATION CO., LTD.
H04W4/06H04W76/10H04W76/40H04W80/02
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,452,632
App. No.
17/866,832
Granted
Oct 21, 2025
Kind
B2
Abstract

A bearer establishment method, a configuration method, a terminal, and a network side device are provided. The bearer establishment method includes: receiving first information; and establishing, according to a first Layer 2 (L2) configuration parameter of a first Multicast Broadcast Service (MBS), a bearer corresponding to the first MBS, where the first L2 configuration parameter is determined based on the first information.

Claims (95)

1. A bearer establishment method, performed by a terminal, the method comprising:

receiving first information, wherein the first information carries a part of configuration parameters of a Layer 2 (L2) configuration parameter; and

establishing, according to a first L2 configuration parameter of a first Multicast Broadcast Service (MBS), a bearer corresponding to the first MBS, wherein the first L2 configuration parameter is determined based on the part of configuration parameters of the L2 configuration parameter carried in the first information and a default L2 configuration parameter,

wherein the first L2 configuration parameter is used to indicate at least one of the following:

a parameter of a Packet Data Convergence Protocol (PDCP) entity on the bearer, wherein the parameter of the PDCP entity comprises at least one of the following: a header compression configuration, a security configuration, a reordering timer configuration, or a PDCP Sequence Number (SN) size; or

a parameter of a Radio Link Control (RLC) entity of the bearer, wherein the parameter of the RLC entity comprises at least one of the following: an RLC transmission mode, an RLC SN length, a reassembly timer length, or a related parameter of an AM status feedback.

2. The bearer establishment method according to claim 1 , wherein the first information is:

MBS configuration information; or

first signaling, wherein the first signaling corresponds to the first MBS or an MBS of a first type, and the MBS of the first type comprises the first MBS.

3. The bearer establishment method according to claim 2 , wherein when the first information is the first signaling,

the first L2 configuration parameter is determined according to at least the first information in a condition,

wherein:

the condition comprises: the first information is signaling of a second type, or the first information is signaling of a second format.

4. The bearer establishment method according to claim 1 , wherein the first information may be carried by using any one of the following: broadcast signaling, multicast signaling, unicast signaling, dedicated signaling, or system information.

5. The bearer establishment method according to claim 1 , wherein the first L2 configuration parameter is further used to indicate at least one of the following:

whether a Service Data Adaptation Protocol (SDAP) entity presents on the bearer;

a parameter of the SDAP entity on the bearer;

whether the PDCP entity presents on the bearer;

or

a parameter of a Medium Access Control (MAC) entity of the bearer.

6. The bearer establishment method according to claim 5 , wherein the first information is used to indicate at least one of the following:

whether an SDAP entity presents on the bearer;

first characteristic information of the first MBS, wherein there is a correspondence between the first characteristic information and whether an SDAP entity presents on the bearer;

a parameter of the SDAP entity on the bearer;

first identifier information, wherein there is a correspondence between the first identifier information and the parameter of the SDAP entity on the bearer;

second characteristic information of the first MBS, wherein there is a correspondence between the second characteristic information and the parameter of the SDAP entity on the bearer;

whether a PDCP entity presents on the bearer;

third characteristic information of the first MBS, wherein there is a correspondence between the third characteristic information and whether a PDCP entity presents on the bearer;

a parameter of the PDCP entity on the bearer;

second identifier information, wherein there is a correspondence between the second identifier information and the parameter of the PDCP entity on the bearer;

fourth characteristic information of the first MBS, wherein there is a correspondence between the fourth characteristic information and the parameter of the PDCP entity on the bearer;

a parameter of a RLC entity of the bearer;

third identifier information, wherein there is a correspondence between the third identifier information and the parameter of the RLC entity of the bearer;

fifth characteristic information of the first MBS, wherein there is a correspondence between the fifth characteristic information and the parameter of the RLC entity of the bearer;

a parameter of an MAC entity;

fourth identifier information, wherein there is a correspondence between the fourth identifier information and the parameter of the MAC entity of the bearer; or

sixth characteristic information corresponding to the first MBS, wherein there is a correspondence between the sixth characteristic information and the parameter of the MAC entity of the bearer.

7. A configuration method, performed by a network side device, the method comprising:

sending first information, wherein the first information carries a part of configuration parameters of a Layer 2 (L2) configuration parameter,

wherein the first information is used to determine a first L2 configuration parameter of a first Multicast Broadcast Service (MBS),

wherein the first L2 configuration parameter is determined based on the part of configuration parameters of the L2 configuration parameter carried in the first information and a default L2 configuration parameter,

wherein the first L2 configuration parameter is used to indicate at least one of the following:

a parameter of a Packet Data Convergence Protocol (PDCP) entity on the bearer, wherein the parameter of the PDCP entity comprises at least one of the following: a header compression configuration, a security configuration, a reordering timer configuration, or a PDCP Sequence Number (SN) size; or

a parameter of a Radio Link Control (RLC) entity of the bearer, wherein the parameter of the RLC entity comprises at least one of the following: an RLC transmission mode, an RLC SN length, a reassembly timer length, or a related parameter of an AM status feedback.

8. The configuration method according to claim 7 , wherein the first information is:

MBS configuration information; or

first signaling, wherein the first signaling corresponds to the first MBS or an MBS of a first type, and the MBS of the first type comprises the first MBS.

9. The configuration method according to claim 8 , wherein when the first information is the first signaling,

the first L2 configuration parameter is determined according to at least the first information in a condition,

wherein:

the condition comprises: the first information is signaling of a second type, or the first information is signaling of a second format.

10. The configuration method according to claim 7 , wherein the first information may be carried by using any one of the following: broadcast signaling, multicast signaling, unicast signaling, dedicated signaling, or system information.

11. The configuration method according to claim 7 , wherein the first L2 configuration parameter is further used to indicate at least one of the following:

whether a Service Data Adaptation Protocol (SDAP) entity presents on the bearer;

a parameter of the SDAP entity on the bearer;

whether the PDCP entity presents on the bearer;

or

a parameter of a Medium Access Control (MAC) entity of the bearer.

12. The configuration method according to claim 7 , wherein the first information is used to indicate at least one of the following:

whether an SDAP entity presents on the bearer;

first characteristic information of the first MBS, wherein there is a correspondence between the first characteristic information and whether an SDAP entity presents on the bearer;

a parameter of the SDAP entity on the bearer;

first identifier information, wherein there is a correspondence between the first identifier information and the parameter of the SDAP entity on the bearer;

second characteristic information of the first MBS, wherein there is a correspondence between the second characteristic information and the parameter of the SDAP entity on the bearer;

whether a PDCP entity presents on the bearer;

third characteristic information of the first MBS, wherein there is a correspondence between the third characteristic information and whether a PDCP entity presents on the bearer;

a parameter of the PDCP entity on the bearer;

second identifier information, wherein there is a correspondence between the second identifier information and the parameter of the PDCP entity on the bearer;

fourth characteristic information of the first MBS, wherein there is a correspondence between the fourth characteristic information and the parameter of the PDCP entity on the bearer;

a parameter of a RLC entity of the bearer;

third identifier information, wherein there is a correspondence between the third identifier information and the parameter of the RLC entity of the bearer;

fifth characteristic information of the first MBS, wherein there is a correspondence between the fifth characteristic information and the parameter of the RLC entity of the bearer;

a parameter of an MAC entity;

fourth identifier information, wherein there is a correspondence between the fourth identifier information and the parameter of the MAC entity of the bearer; or

sixth characteristic information corresponding to the first MBS, wherein there is a correspondence between the sixth characteristic information and the parameter of the MAC entity of the bearer.

13. A terminal, comprising a processor, a memory, and a computer program that is stored in the memory and that can be run on the processor, wherein the computer program, when executed by the processor, causes the processor to perform a bearer establishment method, the method comprising:

receiving first information, wherein the first information carries a part of configuration parameters of a Layer 2 (L2) configuration parameter; and

establishing, according to a first L2 configuration parameter of a first Multicast Broadcast Service (MBS), a bearer corresponding to the first MBS, wherein the first L2 configuration parameter is determined based on the part of configuration parameters of the L2 configuration parameter carried in the first information and a default L2 configuration parameter,

wherein the first L2 configuration parameter is used to indicate at least one of the following:

a parameter of a Packet Data Convergence Protocol (PDCP) entity on the bearer, wherein the parameter of the PDCP entity comprises at least one of the following: a header compression configuration, a security configuration, a reordering timer configuration, or a PDCP Sequence Number (SN) size; or

a parameter of a Radio Link Control (RLC) entity of the bearer, wherein the parameter of the RLC entity comprises at least one of the following: an RLC transmission mode, an RLC SN length, a reassembly timer length, or a related parameter of an AM status feedback.

14. The terminal according to claim 13 , wherein the first information is:

MBS configuration information; or

first signaling, wherein the first signaling corresponds to the first MBS or an MBS of a first type, and the MBS of the first type comprises the first MBS.

15. The terminal according to claim 14 , wherein when the first information is the first signaling,

the first L2 configuration parameter is determined according to at least the first information in a condition,

wherein:

the condition comprises: the first information is signaling of a second type, or the first information is signaling of a second format.

16. The terminal according to claim 13 , wherein the first information may be carried by using any one of the following: broadcast signaling, multicast signaling, unicast signaling, dedicated signaling, or system information.

17. The terminal according to claim 13 , wherein the first L2 configuration parameter is further used to indicate at least one of the following:

whether a Service Data Adaptation Protocol (SDAP) entity presents on the bearer;

a parameter of the SDAP entity on the bearer;

whether the PDCP entity presents on the bearer;

or

a parameter of a Medium Access Control (MAC) entity of the bearer.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 18, 2022
From: BAO, WEI
To: VIVO MOBILE COMMUNICATION CO., LTD.
Reel/Frame 060540/0069 →
Priority Claims (1)
CN 202010075718.2 · Jan 22, 2020 · national
Continuity (2)
Continuation PCTCN2021072086 · Jan 15, 2021
Related Publication 20220353643A1 · Nov 3, 2022
References Cited (27)
US 20050043050A1 · Lee · 2005 [cited by examiner]
US 20060256807A1 · Jung · 2006 [cited by examiner]
US 20090116418A1 · Lee · 2009 [cited by examiner]
US 20100058133A1 · Lee · 2010 [cited by examiner]
US 20100080159A1 · Hu et al. · 2010 [cited by applicant]
US 20230027089A1 · Pelletier · 2023 [cited by examiner]
CN 101166306A · 2008 [cited by applicant]
CN 101426231A · 2009 [cited by applicant]
CN 101998275A · 2011 [cited by applicant]
CN 109155902A · 2019 [cited by applicant]
CN 109714794A · 2019 [cited by applicant]
CN 110035398A · 2019 [cited by applicant]
CN 110326313A · 2019 [cited by applicant]
CN 110475210A · 2019 [cited by applicant]
KR 20060115257A · 2006 [cited by applicant]
WO 2016115669A1 · 2016 [cited by applicant]
WO 2016119634A1 · 2016 [cited by applicant]
WO 2019214733A1 · 2019 [cited by applicant]
International Search Report issued in corresponding International Application No. PCT/CN2021/072086, mailed Apr. 7, 2021, 4 pages. [cited by applicant]
First Office Action issued in related Chinese Application No. 202010075718.2, mailed Dec. 3, 2021, 8 pages. [cited by applicant]
Office Action issued in related European Application No. 21744655.8, mailed Aug. 22, 2023, 12 pages. [cited by applicant]
Huawei et al: “MBS Session Management”, 3GPP Draft; S2-2000489, Jan. 2020, 4 pages. [cited by applicant]
Office Action issued in related European Application No. 21744655.8, mailed Feb. 27, 2024, 14 pages. [cited by applicant]
The Extended European Search Report issued in related European Application No. 21744655.8, mailed Jan. 12, 2023, 9 pages. [cited by applicant]
Office Action issued in related Korean Application No. 10-2022-7028243, mailed Apr. 23, 2025, 13 pages. [cited by applicant]
3GPP TS 36.331 V15.8.0, Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource Control (RRC); Protocol specification (Release 15), Dec. 2019, 947 pages. [cited by applicant]
LG Electronics, “New MBS architecture and procedures”, SA WG2 Meeting #136AH, S2-2000350, Jan. 2020, 12 pages. [cited by applicant]