IP Library Granted Patent US 12,745,150
Granted Patent B2
US 12,745,150 · App. 18/764,628 · Granted Sep 22, 2026

Handover method, apparatus, and system

Inventors: Qi Pan (Beijing, CN); Zhenglei Huang (Shenzhen, CN); Hui Ni (Beijing, CN)
Assignee: Huawei Technologies Co., Ltd.
H04W36/08H04W36/0033H04W40/36
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,745,150
App. No.
18/764,628
Granted
Sep 22, 2026
Kind
B2
Abstract

Embodiments of this application provide a handover method. The method is performed by an access network device, and includes: determining that at least one terminal device is handed over from a first access network device to a second access network device, where the at least one terminal device accesses a network by using an IAB node; and sending first request information, where the first request information notifies a first access and mobility management function AMF network element to perform path handover on the at least one terminal device, and the first AMF network element serves the at least one terminal device. The first request information includes at least one first request message, and the at least one first request message is in one-to-one correspondence with the at least one terminal device.

Claims (37)

1 . A method, applied to an access network device, the method comprising:

determining that at least one terminal device is handed over from a first access network device to a second access network device, wherein the at least one terminal device accesses a network through a first device;

sending first request information, wherein the first request information notifies a first mobility management network element to perform path handover on the at least one terminal device, and the first mobility management network element serves the at least one terminal device, wherein the first request information comprises at least one first request message, and the at least one first request message is in one-to-one correspondence with the at least one terminal device;

obtaining first device identification information, wherein the first device identification information identifies the first device;

determining a same first mobility management network element for each of the at least one terminal device based on the first device identification information; and

storing a correspondence between the first device identification information, identification information of the at least one terminal device, and identification information of the first mobility management network element, wherein sending the first request information comprises sending the first request information to the first mobility management network element based on the correspondence.

2 . The method according to claim 1 , wherein the method further comprises:

sending the correspondence between the identification information of the at least one terminal device and the identification information of the first mobility management network element to a second mobility management network element, wherein the second mobility management network element serves the first device.

3 . The method according to claim 1 , wherein the method further comprises:

sending second request information to the first mobility management network element, wherein the second request information comprises the first device identification information, and the first device identification information identifies the first device.

4 . The method according to claim 1 , wherein the first device is an integrated access and backhaul (IAB) node.

5 . A method, performed by a first mobility management network element, the method comprising:

receiving first request information, wherein the first request information notifies the first mobility management network element to perform path handover on at least one terminal device, the first mobility management network element serves the at least one terminal device, and the at least one terminal device accesses a network through a first device;

performing path handover on the at least one terminal device based on the first request information, wherein the first request information comprises at least one first request message, and the at least one first request message is in one-to-one correspondence with the at least one terminal device;

obtaining first device identification information, wherein the first device identification information identifies the first device;

storing a correspondence between the first device identification information, identification information of the at least one terminal device, identification information of a session management network element of the at least one terminal device, and identification information of a packet data unit (PDU) session; and

sending first session information to the session management network element based on the correspondence, wherein a context of a PDU session of the at least one terminal device is created based on the first session information, wherein the first session information comprises at least one first session message, and the first session message is in one-to-one correspondence with the PDU session of the at least one terminal device.

6 . The method according to claim 5 , wherein the method further comprises:

determining a same session management network element for each of the at least one terminal device based on the first device identification information.

7 . The method according to claim 5 , wherein the obtaining first device identification information further comprises:

receiving second request information, wherein the second request information comprises the first device identification information.

8 . The method according to claim 5 , wherein the first session information comprises the first device identification information.

9 . The method according to claim 5 , wherein the first device is an integrated access and backhaul (IAB) node.

10 . An apparatus, comprising:

at least one processor; and

at least one memory coupled to the at least one processor and configured to store programming instructions that, when executed by the at least one processor, cause the apparatus to:

determine that at least one terminal device is handed over from a first access network device to a second access network device, wherein the at least one terminal device accesses a network through a first device;

send first request information, wherein the first request information notifies a first mobility management network element to perform path handover on the at least one terminal device, and the first mobility management network element serves the at least one terminal device, wherein the first request information comprises at least one first request message, and the at least one first request message is in one-to-one correspondence with the at least one terminal device;

obtain first device identification information, wherein the first device identification information identifies the first device;

determine a same first mobility management network element for each of the at least one terminal device based on the first device identification information; and

store a correspondence between the first device identification information, identification information of the at least one terminal device, and identification information of the first mobility management network element, wherein sending the first request information comprises sending the first request information to the first mobility management network element based on the correspondence.

11 . The apparatus according to claim 10 , wherein the programming instructions that, when executed by the at least one processor, further cause the apparatus to:

send the correspondence between the identification information of the at least one terminal device and the identification information of the first mobility management network element to a second mobility management network element, wherein the second mobility management network element serves the first device.

12 . The apparatus according to claim 10 , wherein the programming instructions that, when executed by the at least one processor, further cause the apparatus to:

send second request information to the first mobility management network element, wherein the second request information comprises the first device identification information, and the first device identification information identifies the first device.

13 . The apparatus according to claim 10 , wherein the first device is an integrated access and backhaul (IAB) node.

14 . The apparatus according to claim 10 , wherein the apparatus is an access network device.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 26, 2025
From: PAN, QI; HUANG, ZHENGLEI; NI, HUI
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 073316/0359 →
Priority Claims (1)
CN 202210018463.5 · Jan 7, 2022 · national
Continuity (2)
Continuation PCTCN2023070314 · Jan 4, 2023
Related Publication 20240365191A1 · Oct 31, 2024
References Cited (30)
US 10708824B2 · Lee · 2020 [cited by examiner]
US 10945261B2 · Wu · 2021 [cited by examiner]
US 11019536B2 · Yuan · 2021 [cited by examiner]
US 11729675B2 · Chong · 2023 [cited by examiner]
US 12604347B2 · Wang · 2026 [cited by examiner]
US 20130083721A1 · Wu et al. · 2013 [cited by applicant]
US 20200053617A1 · Park · 2020 [cited by examiner]
US 20200196200A1 · Lu · 2020 [cited by examiner]
US 20210250838A1 · Lu · 2021 [cited by examiner]
US 20220078677A1 · Yin · 2022 [cited by examiner]
US 20220361072A1 · Zhu · 2022 [cited by examiner]
US 20230117232A1 · Thanneeru · 2023 [cited by examiner]
US 20230262790A1 · Liu · 2023 [cited by examiner]
US 20230269630A1 · Teyeb et al. · 2023 [cited by applicant]
US 20260019902A1 · Zhuo · 2026 [cited by examiner]
CN 110720238A · 2020 [cited by applicant]
CN 110753314A · 2020 [cited by applicant]
CN 110050483B · 2020 [cited by applicant]
KR 20230170788A · 2023 [cited by applicant]
WO 2014124558A1 · 2014 [cited by applicant]
WO 2018205100A1 · 2018 [cited by applicant]
WO 2021121113A1 · 2021 [cited by applicant]
WO 2023187662A1 · 2023 [cited by applicant]
3GPP TSG-RAN WG3 #102 R3-186751, “Inter-donor topology adaptation for architecture 1a,” LG Electronics Inc, Spokane, WA, USA, Nov. 12-16, 2018, total 7 pages, XP051558513. [cited by applicant]
3GPP TSG-RAN WG3 Meeting #109e R3-204917, “Inter-Donor CU topology adaptation,” Lenovo, Motorola Mobility, Online, Aug. 17-28, 2020, total 4 pages, XP052397989. [cited by applicant]
3GPP TS 23.501 V17.3.0 (Dec. 2021), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 17), total 559 pages. [cited by applicant]
3GPP TS 23.502 V17.3.0 (Dec. 2021), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17), total 727 pages. [cited by applicant]
3GPP TR 22.839 V18.1.0 (Dec. 2021), 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Vehicle-Mounted Relays; Stage 1 (Release 18), total 58 pages. [cited by applicant]
Qualcomm, S2-2104762, Rel-18 new SID: Motivation for study of Architecture Enhancements for Vehicle Mounted Relays (FS_VMR_ARC), May 17-28, 2021, total 9 pages. [cited by applicant]
SA WG2 Meeting #S2-150e(e-meeting), S2-2202216, “Solution for mobility”, Ericsson, Apr. 6-12, 2022, Electronic Meeting, total 6 pages. [cited by applicant]