IP Library Granted Patent US 12,520,108
Granted Patent B2
US 12,520,108 · App. 17/882,353 · Granted Jan 6, 2026

Methods and systems for multicast and broadcast service establishment in wireless communication networks

Inventors: Zijiang Ma (Guangdong, CN); Shuang Liang (Guangdong, CN); Zhendong Li (Guangdong, CN)
Assignee: ZTE Corporation
H04W4/06H04W28/0268H04W76/12
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,520,108
App. No.
17/882,353
Granted
Jan 6, 2026
Kind
B2
Abstract

Methods and systems for establishing multicast and broadcast services are described. In one example aspect, the method includes adding, upon determination that flow establishment configuration information does not include a multicast broadcast service (MBS) flow identifier, a first identifier to the user data of the data traffic flow, and transmitting the data traffic flows with the first identifier through the unicast tunnel, or adding, upon determination that the flow establishment configuration information includes the multicast broadcast service (MBS) flow identifier and the corresponding multicast shared tunnel, a second identifier to the user data of the data traffic flows, and transmitting the data traffic flows with the second identifier through the multicast shared tunnel.

Claims (27)

1 . A data communication method, comprising:

determining, by a first communication node, whether to set up one or more data traffic flows for a mobile device;

transmitting, upon determination to set up the one or more data traffic flows, to a second communication node, flow establishment configuration information including a unicast flow identifier, a corresponding unicast tunnel, and a corresponding quality of service (QOS) profile, wherein the unicast flow identifier includes a quality of service (QOS) flow identifier; and

upon determination that the flow establishment configuration information does not include a multicast broadcast service (MBS) flow identifier, a corresponding multicast shared tunnel, and a corresponding multicast quality of service (QOS) profile, adding the QoS flow identifier to an encapsulation header of user data of the data traffic flow, and transmitting, by the first communication node, the user data of the data traffic flows, to which the QoS flow identifier is added, to the second communication node through the unicast tunnel corresponding to the QoS flow identifier; or

upon determination that the flow establishment configuration information includes the MBS flow identifier, the corresponding multicast shared tunnel, and the corresponding QoS profile, configuring, in parallel with the multicast shared tunnel, the unicast tunnel as a dummy tunnel in which no user data of the MBS is transmitted, adding a multicast broadcast service (MBS) identity to an encapsulation header of the user data of the data traffic flows, and transmitting, by the first communication node, the user data of the data traffic flows, to which the MBS identity is added, to the second communication node through the multicast shared tunnel.

2 . The method of claim 1 , wherein the corresponding unicast tunnel includes an existing unicast tunnel or a new unicast tunnel.

3 . The method of claim 1 , wherein the flow establishment configuration information is included in an existing protocol data unit (PDU) session.

4 . The method of claim 3 , wherein the corresponding unicast tunnel is an existing unicast tunnel being used by an existing PDU session.

5 . The method of claim 3 , wherein the corresponding unicast tunnel is a new unicast tunnel being used by a new PDU session.

6 . The method of claim 1 , wherein the flow establishment configuration information is included in a new protocol data unit (PDU) session.

7 . The method of claim 1 , wherein the shared tunnel is established by a multicast broadcast session triggered by a multicast broadcast service function (MBSF).

8 . The method of claim 1 , wherein the first communication node includes a core network, and the second communication node includes a radio access network.

9 . A data communication method, comprising:

receiving, by a second communication node, from a first communication node, flow establishment configuration information to transmit data traffic flows for a mobile device, wherein the flow establishment configuration information includes a unicast flow identifier, a corresponding unicast tunnel, and a corresponding quality of service (QOS) profile, wherein the unicast flow identifier includes a quality of service (QOS) flow identifier;

determining, by the second communication node, whether user data of the data traffic flows is received through a unicast tunnel or a multicast tunnel based on the flow establishment configuration information; and

receiving, by the second communication node, the user data of the data traffic flows through the unicast tunnel or the multicast tunnel based on the determination,

wherein the first communication node is configured to determine which transmission mode is to be used between a unicast mode and a multicast mode, wherein the unicast mode is configured to use the unicast tunnel, and the multicast mode is configured to use the multicast tunnel,

wherein, upon determination that the flow establishment configuration information does not include a multicast broadcast service (MBS) flow identifier, a corresponding multicast shared tunnel, and a corresponding multicast quality of service (QOS) profile, the QoS flow identifier is added to an encapsulation header of user data of the data traffic flow, and the unicast tunnel is used to transmit the user data of the data traffic flows, to which the QoS flow identifier is added, from the first communication node to the second communication node, or upon determination that the flow establishment configuration information includes the multicast broadcast service, MBS, flow identifier, the corresponding multicast shared tunnel, and the corresponding multicast quality of service (QOS) profile, the unicast tunnel is configured as a dummy tunnel in which no user data of the MBS is transmitted, in parallel with the multicast shared tunnel, and a multicast broadcast service (MBS) identity is added to an encapsulation header of the user data of the data traffic flows, and the multicast shared tunnel is used to transmit the user data of the data traffic flows, to which the MBS identity is added, from the first communication node to the second communication node.

10 . The method of claim 9 , wherein the flow establishment configuration information is included in an existing protocol data unit (PDU) session.

11 . The method of claim 10 , wherein the unicast tunnel is an existing unicast tunnel being used by the existing PDU session.

12 . The method of claim 9 , wherein the flow establishment configuration information is included in a new protocol data unit (PDU) session.

13 . The method of claim 12 , wherein the unicast tunnel is a new unicast tunnel being used by the new PDU session.

14 . The method of claim 9 , wherein the first communication node is configured to determine which transmission mode is to be used between the unicast mode and the multicast mode.

15 . The method of claim 14 , wherein the unicast mode is configured to use the unicast tunnel, and the multicast mode is configured to use the multicast tunnel.

16 . The method of claim 9 , wherein the first communication node includes a core network, and the second communication node includes a radio access network.

17 . An apparatus for wireless communication, comprising a memory and a processor, wherein the processor reads code from the memory and implements the method recited claim 1 .

18 . An apparatus for wireless communication, comprising a memory and a processor, wherein the processor reads code from the memory and implements the method recited claim 9 .

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 5, 2022
From: MA, ZIJIANG; LIANG, SHUANG; LI, ZHENDONG
To: ZTE CORPORATION
Reel/Frame 060737/0413 →
Continuity (2)
Continuation PCTCN2020091036 · May 19, 2020
Related Publication 20220377508A1 · Nov 24, 2022
References Cited (26)
US 20100322196A1 · Cherian · 2010 [cited by examiner]
US 20110154421A1 · Chun · 2011 [cited by applicant]
US 20120263089A1 · Gupta et al. · 2012 [cited by applicant]
US 20200374352A1 · Ge et al. · 2020 [cited by applicant]
US 20210352444A1 · Griot · 2021 [cited by examiner]
CN 101090525A · 2007 [cited by applicant]
CN 101155053A · 2008 [cited by applicant]
CN 102379100A · 2012 [cited by applicant]
CN 104105070A · 2014 [cited by applicant]
CN 109982266 · 2019 [cited by applicant]
CN 110167190A · 2019 [cited by applicant]
WO 2011099745A2 · 2011 [cited by applicant]
WO 2014115989A1 · 2014 [cited by applicant]
3GPP; TR 23.757 v0.3.0; Jan. 2020; Study on architectural enhancements for 5G multicast-broadcast services (Year: 2020). [cited by examiner]
International Search Report and Written Opinion for International Application No. PCT/CN2020/091036, mailed on May 19, 2020 (8 pages). [cited by applicant]
Co-Pending Australian Application No. 2020395266, filed May 19, 2020, First Examination Report dated Mar. 17, 2023, 5 pages. [cited by applicant]
Co-Pending EP Application No. 20895049.3, Extended European Search Report dated Nov. 28, 2022, 11 pages. [cited by applicant]
3GPP “Technical Specification Group Core Network and Terminals; General Packet Radio System (GPRS) Tunnelling Protocol”, 3GPP TS 29 .281 V11.6.0 (Mar. 2013) 27 pages. [cited by applicant]
3GPP “Technical Specification Group Services and System Aspects; Study on architectural enhancements for 5G multicast-broadcast services (Release 17)” 3GPP TR 23.757 V0.3.0 (Jan. 2020), 37 pages. [cited by applicant]
Huawei, et al. “Solution to K11 : Establishment of MBS session for multicast” SA WG2 Meeting #136 Reno, NV, USA, Nov. 18-22, 2019, S2-1911645, 3 pages. [cited by applicant]
ZTE “Solution for the Key issue#1 for the Architecture with BS-SC AF” SA WG2 Meeting #S2-136AH Jan. 13-17, 2020, Incheon, South Korea, 4 pages. [cited by applicant]
Co-Pending EP Application No. 20895049.3, Article 94 Communication dated Sep. 27, 2023, 6 pages. [cited by applicant]
CNIPA, First Office Action for Chinese Application No. 202080095027.7, mailed on Apr. 23, 2025, 23 pages with unofficial English translation. [cited by applicant]
Broadband Forum, “LS from the Broadband Forum: WT-134, Broadband Policy Control Framework (PCF),” 3GPP TSG SA #53, Fukuoka, Japan, SP-110450, Sep. 19-21, 2011, 158 pages. [cited by applicant]
Co-Pending EP Application No. 20895049.3, Decision to Refuse dated Mar. 11, 2025, 11 pages. [cited by applicant]
CNIPA, Second Office Action for Chinese Application No. 202080095027.7, mailed on Sep. 19, 2025, 6 pages with Google translation. [cited by applicant]