IP Library › Granted Patent US 12,425,942
Granted Patent B2
US 12,425,942 · App. 17/856,290 · Granted Sep 23, 2025

Communication method and apparatus for sending a handover request

Inventors: Zaifeng Zong (Nanjing, CN); Fenqin Zhu (Shanghai, CN)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
H04W36/26H04W36/0007H04W36/0072
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,425,942
App. No.
17/856,290
Granted
Sep 23, 2025
Kind
B2
Abstract

A communication method implemented by an apparatus includes that a source access network element sends information of a unicast quality of service (QoS) flow of a protocol data unit (PDU) session corresponding to a multicast QoS flow of a multicast broadcast service (MBS) to a target access network element in a handover procedure. The target access network element forwards the information to a session management network element. The session management network element then indicates a user plane network element connected to the target access network element to send data of the MBS to a terminal device through the target access network element and by using a resource of the unicast QoS flow corresponding to the multicast QoS flow of the MBS.

Claims (52)

1. A communication method implemented by a source access network element, comprising:

sending a handover request to a target access network element to hand over a terminal device to the target access network element, wherein the handover request comprises information of a unicast quality of service (QOS) flow of a protocol data unit (PDU) session, and wherein the unicast QoS flow corresponds to a multicast QoS flow of a multicast broadcast service (MBS);

receiving a handover response from the target access network element in response to the handover request, wherein the handover response comprises configuration information of a radio resource corresponding to the unicast QoS flow; and

sending, when the target access network element does not support the MBS and after the terminal device is handed over to the target access network element, the configuration information to the terminal device, wherein the configuration information is used for the terminal device to access the target access network element on the radio resource.

2. The method of claim 1 , further comprising further sending the configuration information in a handover command.

3. The method of claim 1 , further comprising:

receiving a first data packet from a user plane network element, wherein the first data packet comprises a first identifier of the multicast QoS flow and data of the MBS; and

sending a second data packet to the target access network element, wherein the second data packet comprises a second identifier of the unicast QoS flow and the data of the MBS.

4. The method of claim 1 , further comprising:

obtaining, based on a mapping relationship, information of the unicast QoS flow corresponding to the multicast QOS flow, wherein the mapping relationship comprises a correspondence between a first identifier of the multicast QoS flow and a second identifier of the unicast QoS flow.

5. The method of claim 4 , further comprising receiving the mapping relationship.

6. The method of claim 4 , further comprising:

receiving a data packet of the MBS; and

converting, based on the mapping relationship, the data packet into a unicast data packet.

7. The method of claim 1 , further comprising switching the multicast QoS flow to the unicast QoS flow when the target access network element does not support the MBS.

8. A communication apparatus comprising:

a memory configured to store computer instructions; and

one or more processors coupled to the memory, wherein when executed by the one or more processors, the computer instructions cause the communication apparatus to be configured to:

send a handover request to a target access network element to hand over a terminal device to the target access network element, wherein the handover request comprises information of a unicast quality of service (QOS) flow of a protocol data unit (PDU) session, and the unicast QoS flow corresponds to a multicast QoS flow of a multicast broadcast service (MBS);

receive a handover response from the target access network element, wherein the handover response comprises configuration information of a radio resource corresponding to the unicast QoS flow; and

send, when the target access network element does not support the MBS and after the terminal device is handed over to the target access network element, the configuration information to the terminal device, wherein the configuration information is used for the terminal device to access the target access network element on the radio resource.

9. The communication apparatus of claim 8 , wherein the configuration information of the radio resource is sent in a handover command.

10. The communication apparatus of claim 8 , wherein when executed by the one or more processors, the computer instructions further cause the communication apparatus to be configured to:

receive a first data packet from a user plane network element, wherein the first data packet comprises a first identifier of the multicast QoS flow and data of the MBS; and

send a second data packet to the target access network element, wherein the second data packet comprises a second identifier of the unicast QoS flow and the data of the MBS.

11. The communication apparatus of claim 8 , wherein when executed by the one or more processors, the computer instructions further cause the communication apparatus to be configured to obtain, based on a mapping relationship, information of the unicast QOS flow corresponding to the multicast QoS flow, wherein the mapping relationship comprises a correspondence between a first identifier of the multicast QoS flow and a second identifier of the unicast QoS flow.

12. The communication apparatus of claim 11 , wherein when executed by the one or more processors, the computer instructions further cause the communication apparatus to be configured to receive the mapping relationship.

13. The communication apparatus of claim 11 , wherein when executed by the one or more processors, the computer instructions further cause the communication apparatus to be configured to:

receive a data packet of the MBS; and

convert, based on the mapping relationship, the data packet into a unicast data packet.

14. The communication apparatus of claim 8 , wherein when executed by the one or more processors, the computer instructions further cause the communication apparatus to be configured to switch the multicast QoS flow to the unicast QoS flow when the target access network element does not support the MBS.

15. A communication system comprising:

a source access network element configured to:

send a handover request, wherein the handover request comprises information of a unicast quality of service (QOS) flow of a protocol data unit (PDU) session, wherein the unicast QoS flow corresponds to a multicast QOS flow of a multicast broadcast service (MBS);

receive a handover response, wherein the handover response comprises configuration information of a radio resource corresponding to the unicast QoS flow; and

send the configuration information to a terminal device; and

a target access network element, wherein the configuration information is used for the terminal device to access the target access network element on the radio resource, and wherein the target access network element is configured to:

receive, from the source access network element, the handover request; and

send the handover response to the source access network element, wherein, when the target access network element does not support the MBS and after the terminal device is handed over to the target access network element, the source access network element sends the configuration information to the terminal device.

16. The communication system of claim 15 , wherein the source access network element is further configured to:

receive a first data packet from a user plane network element, wherein the first data packet comprises a first identifier of the multicast QoS flow and data of the MBS; and

send a second data packet to the target access network element, wherein the second data packet comprises a second identifier of the unicast QoS flow and the data of the MBS.

17. The communication system of claim 15 , further comprising:

a session management network element configured to send a request message to a user plane network element, wherein the request message is configured to request the user plane network element to send data of the MBS to the target access network element by using the unicast QOS flow; and

a user plane network element configured to:

receive the request message; and

send the data of the MBS to the target access network element by using the unicast QOS flow.

18. The communication system of claim 15 , wherein the source access network element is further configured to obtain, based on a mapping relationship, information of the unicast QoS flow corresponding to the multicast QoS flow, wherein the mapping relationship comprises a correspondence between a first identifier of the multicast QoS flow and a second identifier of the unicast QoS flow.

19. The communication system of claim 18 , wherein the source access network element is further configured to receive the mapping relationship.

20. The communication system of claim 18 , wherein the source access network element is further configured to:

receive a data packet of the MBS; and

convert, based on the mapping relationship, the data packet into a unicast data packet.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 12, 2022
From: ZONG, ZAIFENG; ZHU, FENQIN
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 061392/0876 →
Priority Claims (1)
CN 202010006160.2 · Jan 3, 2020 · national
Continuity (2)
Continuation PCTCN2020127611 · Nov 9, 2020
Related Publication 20220338088A1 · Oct 20, 2022
References Cited (25)
US 20100322196A1 · Cherian et al. · 2010 [cited by applicant]
US 20110292859A1 · So et al. · 2011 [cited by applicant]
US 20190223250A1 · Dao et al. · 2019 [cited by applicant]
US 20190274063A1 · Na · 2019 [cited by examiner]
US 20190380069A1 · Park · 2019 [cited by examiner]
US 20200162855A1 · Li et al. · 2020 [cited by applicant]
US 20210022063A1 · Yang et al. · 2021 [cited by applicant]
US 20210400521A1 · Fiorani · 2021 [cited by examiner]
US 20220369170A1 · Roeland · 2022 [cited by examiner]
CN 109309904A · 2019 [cited by applicant]
CN 109600664A · 2019 [cited by applicant]
EP 3079400A1 · 2016 [cited by applicant]
WO 2019196608A1 · 2019 [cited by applicant]
3GPP TR 23.716 V1.2.0, Nov. 2018, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on the Wireless and Wireline Convergence for the 5G system architecture (Release 16… [cited by applicant]
3GPP TS 38.300 V15.7.0, Sep. 2019, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15),” 99 pages. [cited by applicant]
3GPP TS 38.413 V15.5.0 (Sep. 2019), 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP)(Release 15), 329 pages. [cited by applicant]
3GPP TS 38.423 V15.5.0, Sep. 2019, “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP) (Release 15),” 311 pages. [cited by applicant]
Huawei et al., “Clarification on QoS handling,” 3GPP TSG-WG SA2 Meeting #135, S2-1908922, Split, Croatia, Oct. 14-18, 2019, 5 pages. [cited by applicant]
Huawei et al., “Architectural assumptions,” SA WG2 Meeting #135, S2-1909000, Split, Croatia, Oct. 14-18, 2019, 3 pages. [cited by applicant]
Huawei et al., “Key Issue: MBS session management,” SA WG2 Meeting #135, S2-1909102, Split, Croatia, Oct. 14-18, 2019, 1 page. [cited by applicant]
Huawei et al., “Key Issue: Service continuity,” SA WG2 Meeting #135, S2-1909104, Split, Croatia, Oct. 14-18, 2019, 1 page. [cited by applicant]
Qualcomm Incororporated, “Solution to KI#7: Mobility between 5G MBS supporting and 5G MBS non-supporting NG RAN nodes,” SA WG2 Meeting #139E, S2-2004223, Electronic meeting, Jun. 1-12, 2020, 3 pages. [cited by applicant]
Huawei et al., “KI1: Update of Sol. 3: resolving open issue(s),” 3GPP TSG-WG SA2 Meeting #140E e-meeting, S2-2006299, Elbonia, Aug. 19-Sep. 1, 2020, 15 pages. [cited by applicant]
Nokia et al., “KI#1: Conclusion update for MBS Session activation/deactivation and UE join/leave,” SA WG2 Meeting #143E, S2-2101017, Electronic meeting, Feb. 24-Mar. 9, 2020, 23 pages. [cited by applicant]
“TDoc_List_Meeting_SA2#135”, https://www.3gpp.org/ftp/tsg_sa/WG2_Arch/TSGS2_135_Split/, 2019, 2658 pages. [cited by applicant]
Cited By (1)
US 12,701,467