IP Library Granted Patent US 12,484,111
Granted Patent B2
US 12,484,111 · App. 17/921,938 · Granted Nov 25, 2025

Bearer configuration method and device

Inventors: Hao Zhu (Shenzhen, CN); Lin Chen (Shenzhen, CN); Tao Qi (Shenzhen, CN); Zijiang Ma (Shenzhen, CN); Feng Xie (Shenzhen, CN); Ying Huang (Shenzhen, CN); Kun Cao (Shenzhen, CN); Liping Wang (Shenzhen, CN)
Assignee: ZTE CORPORATION
H04W76/40
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,484,111
App. No.
17/921,938
Granted
Nov 25, 2025
Kind
B2
Abstract

Provided are a bearer configuration method and apparatus, a context message management method and apparatus, a releasing method and apparatus, a device, and a storage medium. The bearer configuration method includes receiving first information and configuring a radio bearer of an MBS based on the first information. The radio bearer includes a point-to-point (PTP) bearer and/or a point-to-multipoint (PTM) bearer.

Claims (54)

1 . A bearer configuration method, the method being applied to a first communication node and comprising:

receiving first information; and

configuring a radio bearer of a multicast broadcast service (MBS) based on the first information, wherein the radio bearer comprises at least one of a point-to-point (PTP) bearer or a point-to-multipoint (PTM) bearer;

wherein the first information comprises PTP bearer configuration information; and wherein configuring the radio bearer of the MBS based on the first information comprises: configuring the PTP bearer based on the PTP bearer configuration information, wherein the PTP bearer configuration information comprises: a PTP radio bearer identifier, MBS identifier information, and packet data convergence protocol (PDCP) configuration information; or

the first information comprises second information; and wherein configuring the radio bearer of the MBS based on the first information comprises: configuring the PTM bearer based on the second information, wherein the second information comprises second bearer configuration and the second bearer configuration comprises: a PTM radio bearer identifier, MBS identifier information, a logical channel identifier, and PDCP configuration information.

2 . The method according to claim 1 , wherein

the PTP bearer configuration information further comprises at least one of following pieces of information: service data adaptation protocol (SDAP) configuration information, or radio link control (RLC) bearer configuration information.

3 . The method according to claim 2 , wherein the SDAP configuration information comprises at least one of the following:

an indication indicating whether the radio bearer is a default radio bearer;

an indication indicating whether downlink data on the radio bearer has an SDAP header;

an indication indicating whether uplink data on the radio bearer has an SDAP header;

the MBS identifier information;

an uplink quality of service (QOS) flow list, in an MBS session, that is to be mapped to the radio bearer and to be added; or

a to-be-released QoS flow list, in an MBS session, that has been mapped to the radio bearer;

wherein the MBS identifier information comprises at least one of the following: an MBS session identifier, a temporary mobile group identity (TMGI) of the MBS, an MBS identifier, or a protocol data unit (PDU) session identifier indicating the MBS session;

wherein in a case where the PTP bearer configuration information carries the SDAP configuration information, at least one of following operations is performed:

establishing a first SDAP entity;

configuring the first SDAP entity based on the carried SDAP configuration information; or

establishing an association between the first SDAP entity and a radio bearer corresponding to the PTP radio bearer identifier,

wherein the first SDAP entity is configured to map a QoS flow in the MBS identifier information to a PTP radio bearer.

4 . The method according to claim 2 , wherein in a case where the PTP bearer configuration information comprises the SDAP configuration information, or PTM bearer configuration information comprises SDAP configuration information, at least one of following operations is performed:

establishing a third SDAP entity;

configuring the third SDAP entity based on the SDAP configuration information; or

establishing an association between the third SDAP entity and a radio bearer corresponding to the PTP radio bearer identifier or a radio bearer corresponding to the PTM radio bearer identifier,

wherein the third SDAP entity is configured to map a QoS flow in MBS identifier information to a PTP radio bearer or a PTM radio bearer.

5 . The method according to claim 2 , wherein the PDCP configuration information comprises at least one of the following:

indicating whether an encryption algorithm is used, timing of discarding a PDCP data packet, whether a PDCP entity continues or resets a robust header compression (ROHC) protocol in a case of reestablishment, header compression configuration, whether the radio bearer is configured with integrity protection, a maximum value of a header compression context identifier (CID) parameter, a PDCP entity being associated with more than one RLC entity in an uplink data transmission, allowing out-of-order, whether an uplink PDCP duplication is configured and activated, a downlink PDCP sequence number size, an uplink PDCP sequence number size, indicating a cell group identifier (ID) corresponding to a main RLC entity and a logical channel identifier corresponding to the main RLC entity in a case where more than one RLC entity is associated in an uplink data transmission, whether the radio bearer is configured to transmit a PDCP status report, reordering time, or a data volume threshold when uplink data uses a split bearer; and

wherein the RLC bearer configuration information comprises at least one of the following:

a logical channel identifier, a radio bearer identifier served by an RLC bearer, RLC configuration, logical channel configuration, an identifier indicating whether to reestablish RLC, a maximum number of retransmissions, a number of poll bytes, a poll PDU, a sequence number (SN)-field length, a timer in an RLC acknowledged mode (AM), a reassembly timer, or a status report timer.

6 . The method according to claim 1 , wherein

the second bearer configuration further comprises at least one of the following: SDAP configuration information or RLC bearer configuration information.

7 . The method according to claim 6 , wherein PTM bearer configuration information required for configuring the PTM bearer comprises at least one of the following: first bearer configuration or the second bearer configuration, wherein the first bearer configuration uses default configuration, and the first bearer configuration comprises at least one of the following: a PTM radio bearer identifier, a logical channel identifier, SDAP configuration information, PDCP configuration information, or RLC bearer configuration information.

8 . The method according to claim 7 , wherein in a case where the PTM bearer configuration information comprises the SDAP configuration information, at least one of following operations is performed:

establishing a second SDAP entity;

configuring the second SDAP entity based on SDAP configuration information of at least one of the first bearer configuration or the second bearer configuration; or

establishing an association between the second SDAP entity and a radio bearer corresponding to the PTM radio bearer identifier,

wherein the second SDAP entity is configured to map a QoS flow in the MBS identifier information to a PTM radio bearer.

9 . The method according to claim 7 , wherein all QOS flows of one piece of MBS identifier information are mapped to one PTM radio bearer, and different PTM radio bearers corresponding to different pieces of MBS identifier information use a same logical channel identifier.

10 . The method according to claim 7 , wherein all QoS flows of one piece of MBS identifier information are mapped to at least one PTM radio bearer, and different PTM radio bearers corresponding to a same piece of MBS identifier information use different logical channel identifiers.

11 . The method according to claim 7 , wherein for each piece of MBS identifier information, at least one of following operations is performed:

establishing a PDCP entity based on at least one of the first bearer configuration or the second bearer configuration;

establishing an RLC entity based on at least one of the first bearer configuration or the second bearer configuration;

configuring an MBS logical channel corresponding to the radio bearer in a media access control (MAC) entity; or

establishing an association between a PDCP entity and an MBS logical channel;

wherein the MBS logical channel uses a default logical channel identifier.

12 . The method according to claim 7 , wherein for each PTM radio bearer identifier, at least one of following operations is performed:

establishing a PDCP entity;

establishing an RLC entity;

configuring an MBS logical channel corresponding to the each PTM radio bearer identifier in an MAC entity; or

establishing an association between a PDCP entity and an MBS logical channel.

13 . A device, comprising

at least one processor; and

a memory configured to store at least one program,

wherein the at least one program, when executed by the at least one program, causes the at least one processor to perform the method according to claim 1 .

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 21, 2025
From: SHENZHEN ZHONGXING SOFTWARE COMPANY LIMITED
To: ZTE CORPORATION
Reel/Frame 072623/0960 →
EMPLOYMENT CONTRACT Recorded Oct 21, 2025
From: ZHU, HAO
To: SHENZHEN ZHONGXING SOFTWARE COMPANY LIMITED
Reel/Frame 073149/0747 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 31, 2023
From: CHEN, LIN; QI, TAO; MA, ZIJIANG; XIE, FENG; HUANG, YING; CAO, KUN; WANG, LIPING
To: ZTE CORPORATION
Reel/Frame 062546/0958 →
Priority Claims (1)
CN 202010345823.3 · Apr 27, 2020 · national
Continuity (1)
Related Publication 20230180349A1 · Jun 8, 2023
References Cited (26)
US 20050282569A1 · Kim et al. · 2005 [cited by applicant]
US 20060146858A1 · Kim · 2006 [cited by examiner]
US 20090219850A1 · Lin et al. · 2009 [cited by applicant]
US 20140029580A1 · Jung · 2014 [cited by examiner]
US 20170013433A1 · Lee et al. · 2017 [cited by applicant]
US 20210068004A1 · Kadiri · 2021 [cited by examiner]
US 20210204248A1 · Zhang · 2021 [cited by examiner]
US 20230199569A1 · Cao · 2023 [cited by examiner]
CN 101155328A · 2008 [cited by applicant]
CN 101166306A · 2008 [cited by applicant]
CN 101350949A · 2009 [cited by applicant]
CN 101351036A · 2009 [cited by applicant]
CN 102404691A · 2012 [cited by applicant]
CN 102595328A · 2012 [cited by applicant]
CN 108260162A · 2018 [cited by applicant]
CN 110447146A · 2019 [cited by applicant]
CN 111901766A · 2020 [cited by applicant]
KR 20190089955A · 2019 [cited by applicant]
International Search Report in Application No. PCT/CN2021/079117, dated May 27, 2021, 6 pages, including English translation. [cited by applicant]
Mikko Säily et al: “Broadcast and Multicast Communication Enablers for the Fifth-Generation of Wireless Systems Deliverable D3.4 Rat Protocols and Radio Resource Management in 5G-Xcast”, Jul. 31, 2019 (Jul. 31, 2019), X… [cited by applicant]
David Vargas et al: “RAN Logical Architecture and Interfaces for 5G-Xcast”, Feb. 28, 2019 (Feb. 28, 2019), pp. 1-95, XP055646813, Retrieved from the Internet: URL: http://5g-xcast.eu/wp-content/uploads/2019/03/5G-Xcast_… [cited by applicant]
Partial European Search Report for Application No. 21797922.8, dated Jul. 28, 2023, 12 pages. [cited by applicant]
Korean Office Action for Application No. 1020227041348, Sep. 28, 2023, 14 pages including translation. [cited by applicant]
First Office Action in European Application No. 21797922.8, dated Jan. 20, 2025, 6 pages. [cited by applicant]
3GPP, “Technical Specification Group Radio Access Network; Introduction of the Multimedia Broadcast/Multicast Service (MBMS) in the Radio Access Network (RAN); Stage 2 (Release 15)”, Jun. 29, 2018 (Jun. 29, 2018), XP051… [cited by applicant]
First Office Action in Chinese Application No. 202010345823.3, dated Jul. 10, 2025, 26 pages, including translation. [cited by applicant]