IP Library › Granted Patent US 12,200,651
Granted Patent B2
US 12,200,651 · App. 17/638,851 · Granted Jan 14, 2025

AMF re-allocation solution with network slice isolation

Inventors: Lasse Olsson (Träslövsläge, SE); Qian Chen (Mölndal, SE); Peter Ramle (Mölnlycke, SE)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
H04W60/04H04W12/06H04W40/34H04W48/18
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,200,651
App. No.
17/638,851
Granted
Jan 14, 2025
Kind
B2
Abstract

Systems and methods are disclosed herein for Access and Mobility Function (AMF) re-allocation. In one embodiment, a method for AMF re-allocation includes, at an initial AMF, receiving a registration request for a User Equipment (UE) from a Radio Access Network (RAN), deciding to initiate an AMF re-allocation procedure, sending the registration request to the RAN for delivery to a target AMF for the AMF re-allocation procedure, and sending a UE security context of the UE to another Network Function (NF). The method further includes, at the target AMF, receiving a message from the RAN wherein the message includes the registration request from the UE, obtaining the UE security context of the UE from the other NF, and performing protected NAS signaling related to a registration procedure for the UE using the UE security context of the UE.

Claims (44)

1. A method for Access and Mobility Function, AMF, re-allocation, comprising:

at an initial AMF:

receiving a registration request for a User Equipment, UE, from a Radio Access Network, RAN; o deciding to initiate an AMF re-allocation procedure by forwarding the registration request to a target AMF for the AMF re-allocation procedure via the RAN;

sending the registration request to the RAN for delivery to the target AMF; and

sending a UE security context of the UE to other Network Function, NF,

wherein:

sending the registration request to the RAN for delivery to the target AMF comprises sending, to the RAN for delivery to the target AMF, the registration request together with information that identifies the other NF, and sending the UE security context of the UE to the other NF comprises storing the UE security context of the UE at the other NF;

at the other NF:

receiving the UE security context of the UE from the initial AMF; and

providing the UE security context of the UE to the target AMF for the AMF re-allocation procedure;

at the target AMF:

receiving a message from the RAN, wherein the message comprises the registration request from the UE;

obtaining the UE security context of the UE from the other NF; and

performing protected NAS signaling related to a registration procedure for the UE using the UE security context of the UE.

2. A method performed by an initial Access and Mobility Function, AMF, for a AMF re-allocation procedure, the method comprising:

receiving a registration request for a User Equipment, UE, from a Radio Access Network, RAN;

deciding to initiate an AMF re-allocation procedure by forwarding the registration request to a target AMF via the RAN;

sending the registration request to the RAN for delivery to the target AMF; and

sending a UE security context of the UE to other Network Function, NF,

wherein:

sending the registration request to the RAN for delivery to the target AMF comprises sending, to the RAN for delivery to the target AMF, the registration request together with information that identifies the other NF, and

sending the UE security context of the UE to the other NF comprises storing the UE security context of the UE at the other NF.

3. The method of claim 2 wherein storing the UE security context of the UE at the other NF comprises storing, at the other NF, the UE security context of the UE and information that indicates a set of AMFs that can serve one or more network slices requested by the UE.

4. The method of claim 3 wherein sending the registration request to the RAN for delivery to the target AMF comprises sending, to the RAN for delivery to the target AMF, the registration request together with the information that indicates the set of AMFs.

5. The method of claim 2 wherein storing the UE security context of the UE at the other NF comprises storing, at the other NF, the UE security context of the UE and a token.

6. The method of claim 5 wherein sending the registration request to the RAN for delivery to the target AMF comprises sending, to the RAN for delivery to the target AMF, the registration request together with token.

7. The method of claim 2 the method further comprises: in response to sending the registration request to the RAN for delivery to the target AMF, receiving, from the RAN, a message comprising a pointer to the target AMF; wherein sending the UE security context of the UE to the other NF comprises sending, to the other NF, the UE security context of the UE and the pointer to the target AMF.

8. A method performed by a target Access and Mobility Function, AMF, for an AMF re-allocation procedure, the method comprising:

receiving a message from a Radio Access Network, RAN, wherein the message comprises a registration request from a User Equipment, UE;

obtaining a UE security context of the UE from a Network Function, NF, other than an initial AMF for the AMF re-allocation procedure; and

performing protected NAS signaling related to a registration procedure for the UE using the UE security context of the UE,

wherein:

the message received from the RAN comprises information that identifies the NF, and fetching the UE security context of the UE from the other NF comprises fetching the UE security context of the UE from the NF using the information that identifies the NF; and obtaining the UE security context of the UE from the NF comprises fetching the UE security context of the UE from the NF.

9. The method of claim 8 further comprising obtaining a token from the RAN, and using the token to validate the UE security context of the UE.

10. The method of claim 8 wherein obtaining the UE security context of the UE from the NF comprises receiving the UE security context of the UE from the other NF via a push mechanism.

11. A method performed by Network Function, NF, for an Access and Mobility Function, AMF, re-allocation procedure, the method comprising:

receiving a User Equipment, UE, security context of a UE from an initial AMF for an AMF re-allocation procedure; and

providing the UE security context of the UE to a target AMF for the AMF re-allocation procedure, wherein:

message that the target AMF received from the initial AMF via RAN comprises a registration request from the UE and information that identifies the NF, and fetching the UE security context of the UE from the NF comprises fetching the UE security context of the UE from the NF using the information that identifies the NF; and obtaining the UE security context of the UE from the NF comprises fetching the UE security context of the UE from the NF.

12. The method of claim 11 wherein the UE security context of the UE is stored by the NF, and providing the UE security context of the UE to the target AMF comprises: receiving, from the target AMF, a request for the UE security context; and sending the UE security context to the target AMF in response to the request.

13. The method of claim 12 wherein receiving the UE security context of the UE from the initial AMF comprises receiving the UE security context together with information that indicates a set of AMFs that can serve one or more network slices requested by the UE.

14. The method of claim 12 wherein receiving the UE security context of the UE from the initial AMF comprises receiving the UE security context together with information that indicates a set of AMFs that can serve one or more network slices requested by the UE and a token.

15. The method of claim 14 wherein the request for the UE context comprises a second token, and the method further comprises validating the request based on a comparison of the token and the second token.

16. The method of claim 11 wherein: receiving the UE security context of the UE from the initial AMF comprises receiving, from the initial AMF, the UE security context of the UE together with a pointer to the target AMF; and providing the UE security context of the UE to the target AMF comprises pushing the UE security context of the UE to the target AMF using the pointer to the target AMF.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 2, 2024
From: OLSSON, LASSE; RAMLE, PETER; CHEN, QIAN
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 068769/0837 →
Continuity (2)
Provisional Application 62893623 · Aug 29, 2019
Related Publication 20220303935A1 · Sep 22, 2022
References Cited (16)
US 20180332523A1 · Faccin · 2018 [cited by examiner]
US 20190199802A1 · Zhu · 2019 [cited by examiner]
US 20210051468A1 · Baskaran · 2021 [cited by examiner]
US 20210084582A1 · Li · 2021 [cited by examiner]
US 20220174580A1 · You · 2022 [cited by examiner]
US 20220201638A1 · Arrobo Vidal · 2022 [cited by examiner]
WO WO2018175498A1 · 2018 [cited by examiner]
International Search Report and Written Opinion of the International Searching Authority, PCT/EP2020/073063, mailed Oct. 13, 2020, 12 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System; Stage 2 (Release 15) 3GPP TS 23.502 V15.5.1 (Apr. 2019) 354 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System; Stage 2 (Release 15) 3GPP TS 23.501 V15.5.0 (Mar. 2019) 241 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3 (Release 16) 3GPP TS 24.501 V16.1.0 (Jun. 2019) 541 pages. [cited by applicant]
3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Security architecture and procedures for 5G system (Release 15) 3GPP TS 33.501 V15.5.0 (Jun. 2019) 190 pages. [cited by applicant]
3GPP TSG-SA WG2 Meeting #128bis S2-1811310 Dongguan, P.R. China, Oct. 15-19, 2018 (Revision of S2-1810250) Excluding sensitive information to be sent in clear (XP051540150) 24 pages. [cited by applicant]
3GPP TSG-SA WG2 Meeting #131 S2-1902677 Feb. 25-Mar. 1, 2019, Tenerife, Spain Introducing Non-public network (XP051611090) 52 pages. [cited by applicant]
3GPP TSG-SA WG3 Meeting #96 S3-192887 Wroclaw, Poland, Aug. 26-30, 2019 revision of S3-19xabc Discussion about the AMF re-allocation due to slicing (XP051776720) 10 pages. [cited by applicant]
3GPP TSG-SA WG3 Meeting #96 Wroclaw, Poland, Aug. 26-30, 2019 53-192888 revision of S3-19xabc AMF Reallocation and Slicing (XP051776721) 3 pages. [cited by applicant]