IP Library › Granted Patent US 12,477,384
Granted Patent B2
US 12,477,384 · App. 18/422,972 · Granted Nov 18, 2025

Data transmission method and data transmission apparatus

Inventors: Lifeng Han (Shenzhen, CN); Rui Wang (Shanghai, CN); Mingzeng Dai (Shenzhen, CN); Hongping Zhang (Shenzhen, CN); Qinghai Zeng (Shenzhen, CN)
Assignee: Huawei Technologies Co., Ltd.
H04W28/0268H04W36/0069H04W36/30H04W76/12H04W80/08
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,477,384
App. No.
18/422,972
Granted
Nov 18, 2025
Kind
B2
Abstract

This application provides a transmission method and a data transmission apparatus, so as to avoid out-of-order of data packets. The method includes: sending, by a source access network device, a first proportion of data packets in a first Packet Data Convergence Protocol PDCP entity in the source access network device to a target access network device by using a data tunnel between the source access network device and a second PDCP entity of the target access network device, where the first proportion of data packets are data packets of a first quality of service QoS flow in a first protocol data unit PDU session, the first PDU session includes at least one QoS flow, the at least one QoS flow corresponds to at least one PDCP entity, the at least one QoS flow includes the first QoS flow, the at least one PDCP entity includes the first PDCP entity, and the first PDCP entity corresponds to the first QoS flow; and sending, by the source access network device, first indication information to the target access network device, where the first indication information is used to indicate that all the first proportion of data packets in the first PDCP entity have been sent.

Claims (46)

1 . A communication method, comprising:

in response to determining that a terminal no longer sends a first data packet of a first quality of service (QOS) flow in a first protocol data unit (PDU) session to a source base station, generating, by the source base station, end marker packet information, wherein the end marker packet information indicates a target base station to send, to a core network user plane device, a second data packet that is of the first QoS flow and that is sent by the terminal to the target base station; and

sending, by the source base station, the end marker packet information to the target base station.

2 . The method according to claim 1 , further comprising:

sending, by the source base station, a notification message to the terminal, wherein the notification message notifies the terminal to send the second data packet of the first QoS flow to the target base station.

3 . The method according to claim 1 , before generating, by the source base station, the end marker packet information to the target base station, further comprising:

receiving, by the source base station, end packet information from the terminal, wherein the end packet information indicates information about the last data packet that is of the first QoS flow and that is sent by the terminal to the source base station.

4 . The method according to claim 1 , wherein the sending, by the source base station, the end marker packet information to the target base station, comprising:

sending, by the source base station, the end marker packet information to the target base station by using a data forward transmission tunnel between the source base station and the target base station.

5 . The method according to claim 1 , further comprising:

sending, by the source base station, a first request message to the target base station, wherein the first request message comprises a request to transfer the first QoS flow to the target base station.

6 . The method according to claim 1 , wherein the source base station is a master base station, and the target base station is a secondary base station; or the source base station is a secondary base station, and the target base station is a master base station.

7 . The method according to claim 1 , wherein the end marker packet information comprises an identity of the first QoS flow and an identity of the first PDU session; or end marker packet information includes an identity of the first QoS flow and an identity of a first DRB, and the first DRB corresponds to the first QoS flow.

8 . A communication method, comprising:

receiving, by a target base station, an end marker packet information from a source base station, wherein the end marker packet information indicates the target base station to send, to a core network user plane device, a second data packet that is of a first quality of service (QOS) flow and that is sent by a terminal to the target base station; and

sending, by a target base station, the second data packet of the first QOS flow to the core network user plane device.

9 . The method according to claim 8 , before receiving, by the target base station, the end marker packet information from the source base station, further comprising:

receiving, by the target base station, a first request message from the source base station, wherein the first request message comprises a request to transfer the first QoS flow to the target base station;

if the target base station can accept the first QoS flow, sending, by the target base station, a first response message to the source base station; and

receiving, by the target base station, the second data packet that is of the first QoS flow and that are sent by the terminal.

10 . The method according to claim 9 , wherein the first request message is an Xn interface message, or carried in an Xn interface message.

11 . A communication apparatus, comprising:

at least one processor; and

a non-transitory computer-readable medium including computer-executable instructions that, when executed by the at least one processor, cause the apparatus to carry out operations including:

in response to determining that a terminal no longer sends a data packet of a first quality of service (QOS) flow in a first protocol data unit (PDU) session to a source base station, generating end marker packet information, wherein the end marker packet information indicates a target base station to send, to a core network user plane device, a data packet that is of the first QoS flow and that is sent by the terminal to the target base station; and

sending, the end marker packet information to the target base station.

12 . The apparatus according to claim 11 , the operations further comprising:

sending a notification message to the terminal, where the notification message notifies the terminal to send the data packet of the first QoS flow to the target base station.

13 . The apparatus according to claim 11 , before sending the end marker packet information to the target base station, the operations further comprising:

receiving, end packet information from the terminal, wherein the end packet information indicates information about the last data packet that is of the first QoS flow and that is sent by the terminal to the source base station.

14 . The apparatus according to claim 11 , wherein the sending, the end marker packet information to the target base station, comprising:

sending, the end marker packet information to the target base station by using a data forward transmission tunnel between the source base station and the target base station.

15 . The apparatus according to claim 11 , the operations further comprising:

sending, a first request message to the target base station, where the first request message comprises a request to transfer the first QOS flow to the target base station.

16 . The apparatus according to claim 11 , wherein the source base station is a master base station, and the target base station is a secondary base station; or the source base station is a secondary base station, and the target base station is a master base station.

17 . The apparatus according to claim 11 , wherein the end marker packet information comprises an identity of the first QoS flow and an identity of the first PDU session; or the end marker packet information includes an identity of the first QOS flow and an identity of a first DRB, and the first DRB corresponds to the first QoS flow.

18 . A communication apparatus, comprising:

at least one processor; and

a non-transitory computer-readable medium including computer-executable instructions that, when executed by the processor, cause the apparatus to carry out operations including:

receiving, an end marker packet information from a source base station, wherein the end marker packet information indicates a target base station to send, to a core network user plane device, a second data packet that is of a first quality of service (QOS) flow and that is sent by a terminal to the target base station; and

sending, the second data packet of the first QOS flow to the core network user plane device.

19 . The apparatus according to claim 18 , before receiving the end marker packet information from the source base station, the operations further comprising:

receiving, a first request message from the source base station, where the first request message comprises a request to transfer the first QoS flow to the target base station;

sending a first response message to the source base station; and

receiving the second data packet that is of the first QoS flow and that are sent by the terminal.

20 . The apparatus according to claim 19 , wherein the first request message is an Xn interface message, or carried in an Xn interface message.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 6, 2024
From: HAN, LIFENG; WANG, RUI; DAI, MINGZENG; ZHANG, HONGPING; ZENG, QINGHAI
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 067319/0161 →
Priority Claims (1)
CN 201710687846.0 · Aug 11, 2017 · national
Continuity (4)
Continuation 17459667 · Aug 27, 2021
Continuation 16563302 · Sep 6, 2019
Continuation PCTCN2018099967 · Aug 10, 2018
Related Publication 20240276289A1 · Aug 15, 2024
References Cited (77)
US 10419985B2 · Kim et al. · 2019 [cited by applicant]
US 20090225705A1 · Kwon · 2009 [cited by applicant]
US 20100111041A1 · Lim et al. · 2010 [cited by applicant]
US 20120219018A1 · Shi · 2012 [cited by applicant]
US 20130058308A1 · Jaiswal et al. · 2013 [cited by applicant]
US 20140105011A1 · Chandramouli et al. · 2014 [cited by applicant]
US 20150009826A1 · Ma et al. · 2015 [cited by applicant]
US 20160105838A1 · Wang et al. · 2016 [cited by applicant]
US 20170142770A1 · Fu et al. · 2017 [cited by applicant]
US 20170245184A1 · Shetigar et al. · 2017 [cited by applicant]
US 20170332301A1 · Horn et al. · 2017 [cited by applicant]
US 20170373950A1 · Szilagyi et al. · 2017 [cited by applicant]
US 20180192342A1 · Lim et al. · 2018 [cited by applicant]
US 20190074894A1 · Gopal · 2019 [cited by applicant]
US 20190174377A1 · Decarreau · 2019 [cited by examiner]
US 20190313295A1 · Xu et al. · 2019 [cited by applicant]
US 20200015116A1 · Huang et al. · 2020 [cited by applicant]
US 20200015138A1 · Zhu · 2020 [cited by applicant]
US 20220232413A1 · Ma · 2022 [cited by examiner]
US 20220264370A1 · Qiao et al. · 2022 [cited by applicant]
US 20220286896A1 · Wang · 2022 [cited by examiner]
US 20230164619A1 · Shi · 2023 [cited by examiner]
CN 101132609 · 2008 [cited by applicant]
CN 101272315 · 2008 [cited by applicant]
CN 101365239 · 2009 [cited by applicant]
CN 101572929 · 2009 [cited by applicant]
CN 102045802 · 2011 [cited by applicant]
CN 103765955 · 2014 [cited by applicant]
CN 103888222 · 2014 [cited by applicant]
CN 104994551 · 2015 [cited by applicant]
CN 106851856 · 2017 [cited by applicant]
CN 106941733 · 2017 [cited by applicant]
CN 107027136 · 2017 [cited by applicant]
EP 2187664 · 2014 [cited by applicant]
GB 2551485 · 2017 [cited by applicant]
KR 20140036245 · 2014 [cited by applicant]
KR 20140062109 · 2014 [cited by applicant]
WO WO2009132550A1 · 2009 [cited by examiner]
WO WO2016099058 · 2016 [cited by applicant]
WO WO2017222344 · 2017 [cited by applicant]
WO WO2018030982 · 2018 [cited by applicant]
WO WO2018110952 · 2018 [cited by applicant]
3GPP TS 23.401 V15.0.0 (Jun. 2017), “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; General Packet Radio Service (GPRS) Enhancements for Evolved Universal Terrestrial Radi… [cited by applicant]
3GPP TS 23.502 V0.5.0 (Jul. 2017), “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15),” Jul. 2017, 148 pages. [cited by applicant]
3GPP TS 36.300 V14.3.0 (Jun. 2017), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Ac… [cited by applicant]
3GPP TS 37.340 V0.2.1 (Aug. 2017), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and NR; Multi-connectivity; Stage 2 (Releas… [cited by applicant]
3GPP TS 38.300 V0.6.0 (Aug. 2017), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15),” Aug. 7, 2017, 58 pages. [cited by applicant]
3GPP TS 38.323 V0.2.0 (Aug. 2017), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; Packet Data Convergence Protocol (PDCP) specification (Release 15),” Jul. 19, 2017, 27 page… [cited by applicant]
3GPP TS 38.413 V0.2.1 (Aug. 2017), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG Radio Access Network (NG-RAN); NG Application Protocol (NGAP) (Release 15),” Aug. 9, 2017, 8… [cited by applicant]
3GPP TS 38.423 V0.1.1 (Jun. 2017), “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG Radio Access Network (NG-RAN); Xn application protocol (XnAP) (Release 15),” Jun. 19, 2017, … [cited by applicant]
CATT, “Considerations on the flow control,” 3GPP TSG-RAN WG3 #86, R3-142744, San Francisco, USA, Nov. 17-21, 2014, 2 pages. [cited by applicant]
Ericsson, “QoS—Continuation of stage 3 work,” 3GPP TSG RAN WG3 #96, R3-171708, Hangzhou, China, May 15-19, 2017, 15 pages. [cited by applicant]
Ericsson, “TP to clarify that S-GW relocation cannot happen during DC activities,” 3GPP TSG-RAN WG3 #84, R3-141322, Seoul, South Korea, May 19-23, 2014, 3 pages. [cited by applicant]
Ericsson, ZTE, “Notes on email-discussion#03 on data forwarding for split bearers,” 3GPP TSG-RAN WG3 Meeting #86, R3-142925, San Francisco, CA, U.S., Nov. 17-21, 2014, 7 pages. [cited by applicant]
Extended European Search Report issued in European Application No. 18843032.5 on May 4, 2020, 10 pages. [cited by applicant]
Extended European Search Report issued in European Application No. 22157982.4 on Oct. 24, 2022, 12 pages. [cited by applicant]
Huawei, “Data Forwarding For QoS Flow Remapping During Mobility,” 3GPP TSG-RAN WG3 #96, R3-171810, Hangzhou, PR China, May 15-19, 2017, 4 pages. [cited by applicant]
Huawei, “Data forwarding with QoS flow relocation”, 3GPP TSG-RAN3 Meeting # 95bis, R3-171072, Spokane, Washington, USA, Apr. 3-7, 2017, 6 pages. [cited by applicant]
Huawei, HiSilicon, “QoS Flow to DRB Mapping,” 3GPP TSG-RAN2 Meeting #97, R2-1701205, Athens, Greece, Feb. 13-17, 2017, 6 pages. [cited by applicant]
Huawei, HiSilicon, “QoS Flow to DRB Re-Mapping,” 3GPP TSG-RAN WG2 Meeting #98, R2-1704987, Hangzhou, China, May 15-19, 2017, 6 pages. [cited by applicant]
Huawei, HiSilicon, “TS 23.502 End-Marker during HO Procedure,” SA WG2 Meeting #122, S2-174546, San Jose Del Cabo, Mexico, Jun. 26-30, 2017, 13 pages. [cited by applicant]
Huawei, HiSilicon, “TS 23.502 End-Marker during HO Procedure,” SA WG2 Meeting #122, S2-174546, San Jose Del Cabo, Mexico, Jun. 26-30, 2017, 15 pages. [cited by applicant]
Intel, “Solution for mobility in the EPC=>5GC direction,” 3GPP TSG SA WG2 Meeting #121, S2-173522, Hangzhou, PR China, May 15-19, 2017, 4 pages. [cited by applicant]
Nokia et al., “Traffic offloading in NR-NR DC,” 3GPP TSG-RAN WG2 Meeting #98, R2-1704270, Hangzhou, China, May 15-19, 2017, 3 pages. [cited by applicant]
Office Action issued in Chinese Application No. 201710687846.0 on Jul. 15, 2022, 6 pages. [cited by applicant]
Office Action issued in Chinese Application No. 201811004473.3 on Apr. 25, 2019, 8 pages. [cited by applicant]
Office Action issued in Chinese Application No. 201811004473.3 on Aug. 29, 2019, 6 pages (with English translation). [cited by applicant]
Office Action issued in Chinese Application No. 201811004473.3 on Feb. 19, 2019, 15 pages (with English translation). [cited by applicant]
Office Action issued in Japanese Application No. 2020-507598 on Apr. 27, 2021, 4 pages (with English translation). [cited by applicant]
Office Action issued in Japanese Application No. 2021-089396 on May 31, 2022, 4 pages (with English translation). [cited by applicant]
Office Action issued in Japanese Application No. 2021-089396 on Sep. 20, 2022, 4 pages (with English translation). [cited by applicant]
Office Action issued in Korean Application No. 2020-7006996 on Jan. 12, 2021, 8 pages (with English translation). [cited by applicant]
PCT International Search Report and Written Opinion issued in International Application No. PCT/CN2018/099967 on Dec. 31, 2018, 15 pages (with English translation). [cited by applicant]
Samsung, “Data forwarding for Inter-system Inter-RAT handover between NR and E-UTRA,” 3GPP TSG RAN WG3, R3-172224, Qingdao, China, Jun. 27-29, 2017, 5 pages. [cited by applicant]
Samsung, “TS 23.502: Updates to Inter NG-RAN Node HO Procedure (Section 4.9.1.2.2),” SA WG2 Meeting #121, S2-173651, Hangzhou, China, May 15-19, 2017, 6 pages. [cited by applicant]
Search Report issued in Chinese Application No. 201811004473.3 on Nov. 1, 2018, 6 pages. [cited by applicant]
ZTE, “Further discussion on QoS impact on mobility,” 3GPP TSG-RAN WG3 # 95, R3-170562, Athens, Greece, Feb. 13-17, 2017, 4 pages. [cited by applicant]