IP Library › Granted Patent US 12,231,967
Granted Patent B2
US 12,231,967 · App. 17/670,771 · Granted Feb 18, 2025

Devices and methods for supporting handover of UE

Inventors: Qing Wei (Munich, DE); Riccardo Trivisonno (Munich, DE); Apostolos Kousaridas (Munich, DE); Emmanouil Pateromichelakis (Munich, DE); Mirko Schramm (Berlin, DE)
Assignee: HUAWEI TECHNOLOGIES CO., LTD.
H04W36/0044H04W28/0268H04W28/24H04W36/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,231,967
App. No.
17/670,771
Granted
Feb 18, 2025
Kind
B2
Abstract

The present disclosure relates to handover (HO) of a user equipment (UE), which consumes a quality of service (QoS) flow that is associated with multiple QoS profiles. The disclosure proposes a network entity for supporting HO of the UE, and proposes a second network entity that is the target of HO of the UE. The network entity is configured to: obtain multiple QoS profiles associated with a QoS flow; obtain QoS capability information indicating whether the second network entity supports more than one QoS profile and/or whether a first network entity supports more than one QoS profile; and provide at least one message to the second network entity, wherein the at least one message includes at least one QoS profile according to the QoS capability information.

Claims (59)

1. A network entity comprising:

a memory configured to store instructions; and

one or more processors coupled to the memory and configured to execute the instructions to cause the network entity to:

obtain quality of service (QoS) profiles associated with a QoS flow;

obtain QoS capability information indicating whether a second network entity and/or a first network entity supports more than one QoS profile in the QoS profiles; and

send at least one message to the second network entity,

wherein the at least one message comprises at least one QoS profile in the QoS profiles according to the QOS capability information, and

wherein when the first network entity does not support more than one QoS profile and the second network entity supports more than one QoS profile, the at least one message comprises a session modification message that comprises the QoS profiles and that is sent after completion of a handover (HO) of a user equipment (UE) from the first network entity to the second network entity.

2. The network entity of claim 1 , wherein the QoS profiles comprise an active QoS profile and comprise an alternative QoS profile or a preferred QoS profile.

3. The network entity of claim 1 , wherein the one or more processors are further configured to execute the instructions to cause the network entity to obtain the QoS capability information via:

receiving a message or a notification; or

an operations, administration, and maintenance (OAM) configuration.

4. The network entity of claim 1 , wherein the network entity is the first network entity, wherein when the first network entity supports more than one QoS profile and the second network entity does not support more than one QoS profile, the at least one message comprises request messages, and wherein each of the request messages comprises one of the QoS profiles.

5. The network entity of claim 4 , wherein the one or more processors are further configured to execute the instructions to cause the network entity to:

receive at least one acknowledgement message from the second network entity responsive to the request messages, wherein the at least one acknowledgement message comprise respective QoS profiles of the QoS profiles;

select a first QoS profile from the respective QoS profiles; and

support the HO based on the first QoS profile.

6. The network entity of claim 5 , wherein the one or more processors are further configured to execute the instructions to cause the network entity to inform a core network entity about the first QoS profile.

7. The network entity of claim 2 , wherein the network entity is the first network entity, wherein when the first network entity supports more than one QoS profile and the second network entity does not support more than one QoS, the one or more processors are further configured to execute the instructions to cause the network entity to:

send a request message comprising the QoS profiles to the second network entity;

receive an acknowledgement message from the second network entity responsive to the request message, wherein the acknowledgement message acknowledges the active QoS profile among the QoS profiles; and

support the HO based on the active QoS profile.

8. The network entity of claim 7 , wherein the one or more processors are further configured to execute the instructions to cause the network entity is to inform a core network entity about the active QoS profile.

9. The network entity of claim 1 , wherein the network entity is the first network entity or a session management function (SMF), wherein when the first network entity supports more than one QoS profile and the second network entity does not support more than one QoS profile, the one or more processors are further configured to execute the instructions to cause the network entity to:

select a first QoS profile from the QoS profiles; and

send a request message comprising the first QoS profile to the second network entity.

10. The network entity of claim 2 , wherein the network entity is a session management function (SMF), wherein when the first network entity does not support more than one QoS profile and the second network entity supports more than one QoS profile, the at least one message further comprises a request message, and wherein the request message comprises the active QoS profile and other QoS profiles in the QoS profiles.

11. The network entity of claim 10 , wherein the one or more processors are further configured to execute the instructions to cause the network entity to:

receive an acknowledgement message comprising a first QoS profile of the QoS profiles from the second network entity; and

support the HO based on the first QoS profile.

12. The network entity of claim 1 , wherein the network entity is a session management function (SMF).

13. The network entity of claim 1 , wherein the network entity is the first network entity, wherein when the first network entity and the second network entity support more than one QoS profile, the at least one message comprises a request message comprising the QoS profiles and the one or more processors are further configured to execute the instructions to cause the network entity to:

receive an acknowledgement message comprising a first QoS profile of the QoS profiles from the second network entity; and

support the HO based on the first QoS profile.

14. A second network entity comprising:

a memory configured to store instructions; and

one or more processors coupled to the memory and configured to execute the instructions to cause the second network entity to:

receive, from a first network entity or a third network entity, a message comprising quality of service (QOS) profiles associated with a QoS flow;

select a first QoS profile from the QOS profiles;

send a response message comprising the first QoS profile to the first network entity or to the third network entity; and

inform a session management function (SMF) about the first QoS profile after selection of the first QoS profile and/or after completion of a handover (HO) of a user equipment (UE) from the first network entity.

15. The second network entity of claim 14 , wherein the one or more processors are further configured to execute the instructions to cause the second network entity to inform a core network entity comprising the SMF about the first QoS profile.

16. The second network entity of claim 15 , wherein the one or more processors are further configured to execute the instructions to further cause the second network entity to further inform the core network entity by informing the SMF using a new message or reusing an existing message.

17. The second network entity of claim 14 , wherein the one or more processors are further configured to execute the instructions to cause the second network entity to select the first QoS profile from the QoS profiles by selecting:

an active QoS profile when the active QoS profile is supported by the second network entity; or

a lower QoS profile than the active QoS profile when the active QoS profile is not supported by the second network entity.

18. The second network entity of claim 17 , wherein the one or more processors are further configured to execute the instructions to cause the second network entity is to further select the first QoS profile from the QoS profiles by selecting a higher QoS profile than the active QoS profile when the active QoS profile and the higher QoS profile are supported by the second network entity.

19. A method comprising:

obtaining multiple quality of service (QOS) profiles associated with a QoS flow;

obtaining QOS capability information indicating whether a second network entity and/or a first network entity supports more than one QoS profile in the QoS profiles; and

send at least one message to the second network entity,

wherein the at least one message comprises at least one QoS profile according to the QoS capability information, and

wherein when the first network entity does not support more than one QoS profile and the second network entity supports more than one QoS profile, the at least one message comprises a session modification message that comprises the QoS profiles and that is sent after completion of a handover (HO) of a user equipment (UE) from the first network entity to the second network entity.

20. A method for comprising:

receiving, from a first network entity or from a third network entity, a message comprising quality of service (QOS) profiles associated with a QoS flow;

selecting a first QoS profile from the QoS profiles;

sending a response message comprising the first QoS profile to the first network entity or to the third network entity; and

informing a session management function (SMF) about the first QoS profile after selection of the first QoS profile and/or after completion of a handover (HO) of a user equipment (UE) from the first network entity.

21. The method of claim 19 , wherein the QoS profiles comprise an active QoS profile and comprise an alternative QoS profile or a preferred QoS profile.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 30, 2024
From: WEI, QING; TRIVISONNO, RICCARDO; KOUSARIDAS, APOSTOLOS; PATEROMICHELAKIS, EMMANOUIL; SCHRAMM, MIRKO
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 069075/0518 →
Continuity (2)
Continuation PCTEP2019071882 · Aug 14, 2019
Related Publication 20220167217A1 · May 26, 2022
References Cited (32)
US 20180115927A1 · Vesterinen · 2018 [cited by examiner]
US 20180227976A1 · Dudda et al. · 2018 [cited by applicant]
US 20190028920A1 · Pan · 2019 [cited by applicant]
CN 108141899A · 2018 [cited by applicant]
WO 2016171716A1 · 2016 [cited by applicant]
WO 2017123500A1 · 2017 [cited by applicant]
WO 2019081027A1 · 2019 [cited by applicant]
WO 2019158218A1 · 2019 [cited by applicant]
WO 2019158220A1 · 2019 [cited by applicant]
3GPP TR 23.786 V16.1.0 “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on architecture enhancements for the Evolved Packet System (EPS) and the 5G System (5GS) to su… [cited by applicant]
3GPP TS 22.101 V16.2.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service aspects; Service principles (Release 16),” Jun. 2019, 104 pages. [cited by applicant]
3GPP TS 23.501 V16.1.0 “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 16),” Jun. 2019, 367 pages. [cited by applicant]
Huawei, et al., “Discussion Paper on mulitple QoS profile indexing alternatives,” SA WG2 Meeting #134, Sapporo, Japan, Jun. 24-28, 2019, S2-1907422, 4 pages. [cited by applicant]
3GPP TS 23.203 V16.1.0 “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and charging control architecture (Release 16),” Jun. 2019, 262 pages. [cited by applicant]
Huawei, et al., “QoS Handling for V2X Communication Over Uu Reference Point,” 3GPP TSG-SA2 Meeting #134, Sapporo, Japan, Jun. 24-28, 2019, S2-1907423, 5 pages. [cited by applicant]
3GPP TS 23.502 V16.1.1 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2(Release 16), Jun. 2019, 494 pages. [cited by applicant]
Huawei, et al., “Handling of Alternative QoS Profiles at handover,” SA WG2 Meeting #136, Reno, NV, USA, Nov. 18-22, 2019, S2-1911545, 6 pages. [cited by applicant]
3GPP TS 23.287 V1.1.0 “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for 5G System (5GS) to support Vehicle-to-Everything (V2X) services (Releas… [cited by applicant]
Huawei, et al., “QoS Handling for V2X Communication Over Uu Reference Point,” 3GPP TSG-SA2 Meeting #134, Sapporo, Japan , Jun. 24-28, 2019, S2-1907424, 10 pages. [cited by applicant]
3GPP TS 38.300 V15.6.0 “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NR; NR and NG-RAN Overall Description; Stage 2 (Release 15),” Jun. 2019, 99 pages. [cited by applicant]
3GPP TS 23.503 V16.1.0 “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and Charging Control Framework for the 5G System; Stage 2 (Release 16),” Jun. 2019, 98 pages. [cited by applicant]
Huawei, et al., “QoS Handling for V2X Communication Over Uu Ref,” 3GPP TSG-SA2 Meeting #134, Sapporo, Japan, Jun. 24-28, 2019, S2-1907425, 3 pages. [cited by applicant]
3GPP TS 38.413 V15.4.0 “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; NG Application Protocol (NGAP) (Release 15),” Jul. 2019, 328 pages. [cited by applicant]
3GPP TR 23.705 V13.0.0, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on system enhancements for user plane congestion management (Release 13),” Dec. 2014, 61 page… [cited by applicant]
Huawei, et al., “QoS Handling for V2X Communication Over Uu Reference Point,” SA WG2 Meeting #134, SA WG2 Meeting #134, S2-1907426, 3 pages. [cited by applicant]
3GPP TS 38.423 V15.4.0 “3rd Generation Partnership Project; Technical Specification Group Radio Access Network; NG-RAN; Xn application protocol (XnAP) (Release 15),” Jul. 2019, 309 pages. [cited by applicant]
RAN WG3, “Reply LS on QoS Support for eV2X over Uu interface,” SA WG2 Meeting #S2-133, May 13-17, 2019, Reno, Nevada, USA, S2-1904893, 1 page. [cited by applicant]
Ericsson, et al., “Enhancements to QoS Handling for V2X Communication Over Uu Reference Point,” 3GPP TSG SA WG2 Meeting #134, Sapporo, Japan, Jun. 24-28, 2019, S2-1908223, 3 pages. [cited by applicant]
Vodafone, “KI #7: automatic GBR QoS restoration at flow setup and handover using V2X Alternative QoS Profile with best effort 5QI,” SA WG2 Meeting #134, Jun. 24-28, 2019, Sapporo, Japan, S2-1908287, 3 pages. [cited by applicant]
Huawei, et al., “QoS Handling for V2X Communication Over Uu Reference Point,” 3GPP TSG-SA2 Meeting #134, Sapporo, Japan, Jun. 24-28, 2019, S2-1908225, 21 pages. [cited by applicant]
Huawei, et al., QoS Handling for V2X Communication Over Uu Reference Point. SA WG2 Meeting #134, Sapporo, Japan, 2019, S2-1908594, 1 page. [cited by applicant]
Ericsson, et al., “Enhancements to QoS Handling for V2X Communication Over Uu Reference Point,” 3GPP TSG SA WG2 Meeting #134, Sapporo, Japan, Jun. 24-28, 2019 , S2-1908607, 11 pages. [cited by applicant]
Cited By (1)
US 12,598,515