IP Library › Granted Patent US 12,232,023
Granted Patent B2
US 12,232,023 · App. 18/508,427 · Granted Feb 18, 2025

Providing slice attribute information to user equipment in a mobile network environment

Inventors: Srinath Gundavelli (San Jose, CA); Vimal Srivastava (Bangalore, IN); Oliver James Bull (Bristol, GB)
Assignee: CISCO TECHNOLOGY, INC.
H04W48/16H04W12/06H04W60/00H04W76/10
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,232,023
App. No.
18/508,427
Granted
Feb 18, 2025
Kind
B2
Abstract

Presented herein are techniques to facilitate providing slice attribute information to a user equipment (UE) for one or more slice types with which the user equipment is allowed to establish one or more session(s). In one example, a method may include obtaining, by a network element, a registration request for connection of a UE to a mobile network; performing an authentication for connection of the UE to the mobile network; and upon successful authentication, providing, by the network element, a registration response to the UE, wherein the registration response identifies one or more network slice types with which the UE is authorized to establish a session and the registration response identifies one of: attribute information for each of the one or more network slice types or network location information from which attribute information for each of the one or more network slice types is to be obtained.

Claims (50)

1. A method comprising:

communicating, by a user equipment, a registration request to a mobile core network for connection of the user equipment to the mobile core network;

obtaining, upon successful authentication of the user equipment for connection to the mobile core network, a registration response, wherein the registration response identifies a plurality of network slice types with which the user equipment is authorized to establish a session and the registration response identifies network location information associated with one of an application server or a Domain Name System (DNS) server from which attribute information for one or more corresponding network slice types of the plurality of network slice types is to be obtained by the user equipment;

performing, by the user equipment, session establishment for a default network slice type of the plurality of network slice types; and

following the session establishment with the default network slice type, performing one or more corresponding query toward one of the application server or the DNS server utilizing the network location information identified in the registration response to obtain corresponding attribute information for each of the one or more corresponding network slice types of the plurality of network slice types from one of the application server or the DNS server.

2. The method of claim 1 , wherein the attribute information for at least one corresponding network slice type of the plurality of network slice types includes:

an identification of one or more services provided by the at least one corresponding network slice type;

performance parameters associated with the at least one corresponding network slice type that identify, at least in part, a guaranteed bit rate and a maximum bit rate supported by the at least one corresponding network slice type; and

service area information for the at least one corresponding network slice type.

3. The method of claim 1 , the network location information includes each of a corresponding uniform resource indicator (URI) for each of the one or more corresponding network slice types of the plurality of network slice types that enables the user equipment to query the application server to obtain the attribute information for each of the one or more corresponding network slice types of the plurality of network slice types following the session establishment by the user equipment with the default network slice type.

4. The method of claim 1 , the network location information is an identifier associated with DNS server.

5. The method of claim 4 , wherein the identifier associated with the DNS server is one of:

a Fully Qualified Domain Name (FQDN) for each of the one or more corresponding network slice types of the plurality of network slice types with which the user equipment is authorized to establish a session that enables the user equipment to query the DNS server for the attribute information for each of the one or more corresponding network slice types of the plurality of network slice types following the session establishment by the user equipment with the default network slice type; or

an address for the DNS server from which a Fully Qualified Domain Name (FQDN) for each of the one or more corresponding network slice types of the plurality of network slice types with which the user equipment is authorized to establish a session can be generated by the user equipment to enable the user equipment to query the DNS server for the attribute information for each of the one or more corresponding network slice types of plurality of network slice types following the session establishment by the user equipment with the default network slice type.

6. The method of claim 1 , wherein particular attribute information for at least one network slice type of the plurality of network slice types is identified via a DNS text record that is obtained by the user equipment from the DNS server based on a query of the user equipment towards the DNS server to obtain the particular attribute information for the at least one network slice type.

7. The method of claim 1 , further comprising:

storing, by the user equipment, mapping information that associates each corresponding network slice type of the plurality of network slice types to corresponding attribute information for each corresponding network slice type.

8. The method of claim 7 , further comprising:

selecting, by the user equipment, a particular network slice type of the plurality of network slice types with which to establish another session based, at least in part, on the attribute information associated with the particular network slice type contained in the mapping information.

9. The method of claim 8 , wherein the selecting includes determining that the attribute information associated with the particular network slice type satisfies one or more operating criteria for an application configured for the user equipment.

10. The method of claim 9 , further comprising:

performing, by the user equipment, session establishment for the particular network slice type.

11. One or more non-transitory computer readable storage media encoded with instructions that, when executed by a processor, cause the processor to perform operations, comprising:

communicating, by a user equipment, a registration request to a mobile core network for connection of the user equipment to the mobile core network;

obtaining, upon successful authentication of the user equipment for connection to the mobile core network, a registration response, wherein the registration response identifies a plurality of network slice types with which the user equipment is authorized to establish a session and the registration response identifies network location information associated with one of an application server or a Domain Name System (DNS) server from which attribute information for one or more corresponding network slice types of the plurality of network slice types is to be obtained by the user equipment;

performing, by the user equipment, session establishment for a default network slice type of the plurality of network slice types; and

following the session establishment with the default network slice type, performing one or more corresponding query toward one of the application server or the DNS server utilizing the network location information identified in the registration response to obtain corresponding attribute information for each of the one or more corresponding network slice types of the plurality of network slice types from one of the application server or the DNS server.

12. The media of claim 11 , wherein the attribute information for at least one corresponding network slice type of the plurality of network slice types includes:

an identification of one or more services provided by the at least one corresponding network slice type;

performance parameters associated with the at least one corresponding network slice type that identify, at least in part, a guaranteed bit rate and a maximum bit rate supported by the at least one corresponding network slice type; and

service area information for the at least one corresponding network slice type.

13. The media of claim 11 , the network location information includes each of a corresponding uniform resource indicator (URI) for each of the one or more corresponding network slice types of the plurality of network slice types that enables the user equipment to query the application server to obtain the attribute information for each of the one or more corresponding network slice types of the plurality of network slice types following the session establishment by the user equipment with the default network slice type.

14. The media of claim 11 , the network location information is an identifier associated with DNS server.

15. The media of claim 14 , wherein the identifier associated with the DNS server is one of:

a Fully Qualified Domain Name (FQDN) for each of the one or more corresponding network slice types of the plurality of network slice types with which the user equipment is authorized to establish a session that enables the user equipment to query the DNS server for the attribute information for each of the one or more corresponding network slice types of the plurality of network slice types following the session establishment by the user equipment with the default network slice type; or

an address for the DNS server from which a Fully Qualified Domain Name (FQDN) for each of the one or more corresponding network slice types of the plurality of network slice types with which the user equipment is authorized to establish a session can be generated by the user equipment to enable the user equipment to query the DNS server for the attribute information for each of the one or more corresponding network slice types of plurality of network slice types following the session establishment by the user equipment with the default network slice type.

16. A user equipment comprising:

at least one memory element for storing data; and

at least one processor for executing instructions associated with the data, wherein executing the instructions causes the user equipment to perform operations, comprising:

communicating a registration request to a mobile core network for connection of the user equipment to the mobile core network;

obtaining, upon successful authentication of the user equipment for connection to the mobile core network, a registration response, wherein the registration response identifies a plurality of network slice types with which the user equipment is authorized to establish a session and the registration response identifies network location information associated with one of an application server or a Domain Name System (DNS) server from which attribute information for one or more corresponding network slice types of the plurality of network slice types is to be obtained by the user equipment;

performing, by the user equipment, session establishment for a default network slice type of the plurality of network slice types; and

following the session establishment with the default network slice type, performing one or more corresponding query toward one of the application server or the DNS server utilizing the network location information identified in the registration response to obtain corresponding attribute information for each of the one or more corresponding network slice types of the plurality of network slice types from one of the application server or the DNS server.

17. The user equipment of claim 16 , the network location information includes each of a corresponding uniform resource indicator (URI) for each of the one or more corresponding network slice types of the plurality of network slice types that enables the user equipment to query the application server to obtain the attribute information for each of the one or more corresponding network slice types of the plurality of network slice types following the session establishment by the user equipment with the default network slice type.

18. The user equipment of claim 16 , the network location information is an identifier associated with DNS server.

19. The user equipment of claim 18 , wherein the identifier associated with the DNS server is one of:

a Fully Qualified Domain Name (FQDN) for each of the one or more corresponding network slice types of the plurality of network slice types with which the user equipment is authorized to establish a session that enables the user equipment to query the DNS server for the attribute information for each of the one or more corresponding network slice types of the plurality of network slice types following the session establishment by the user equipment with the default network slice type; or

an address for the DNS server from which a Fully Qualified Domain Name (FQDN) for each of the one or more corresponding network slice types of the plurality of network slice types with which the user equipment is authorized to establish a session can be generated by the user equipment to enable the user equipment to query the DNS server for the attribute information for each of the one or more corresponding network slice types of plurality of network slice types following the session establishment by the user equipment with the default network slice type.

20. The user equipment of claim 16 , wherein executing the instructions causes the user equipment to perform further operations, comprising:

storing mapping information that associates each corresponding network slice type of the plurality of network slice types to corresponding attribute information for each corresponding network slice type.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 14, 2023
From: GUNDAVELLI, SRINATH; SRIVASTAVA, VIMAL; BULL, OLIVER JAMES
To: CISCO TECHNOLOGY, INC.
Reel/Frame 065555/0260 →
Continuity (2)
Continuation 17494107 · Oct 5, 2021
Related Publication 20240089844A1 · Mar 14, 2024
References Cited (38)
US 11051192B2 · Li et al. · 2021 [cited by applicant]
US 20190021047A1 · Zong · 2019 [cited by examiner]
US 20200169951A1 · Cai · 2020 [cited by examiner]
US 20200329008A1 · Dao · 2020 [cited by applicant]
US 20210120484A1 · Thorat · 2021 [cited by examiner]
US 20220103987A1 · Shan · 2022 [cited by examiner]
US 20220104164A1 · Kedalagudde et al. · 2022 [cited by applicant]
US 20220264540A1 · Panchal · 2022 [cited by examiner]
US 20220264669A1 · Qiao et al. · 2022 [cited by applicant]
US 20220337993A1 · Landais et al. · 2022 [cited by applicant]
US 20220353151A1 · Yu et al. · 2022 [cited by applicant]
US 20220369155A1 · Hedman · 2022 [cited by examiner]
US 20220386228A1 · Dao · 2022 [cited by examiner]
US 20230022005A1 · Qiao · 2023 [cited by examiner]
US 20230040614A1 · Bakker · 2023 [cited by examiner]
US 20230048066A1 · Lei · 2023 [cited by examiner]
US 20230052699A1 · Ninglekhu · 2023 [cited by examiner]
US 20230070882A1 · Youn · 2023 [cited by examiner]
US 20230087052A1 · Korja · 2023 [cited by examiner]
US 20230094062A1 · Kim et al. · 2023 [cited by applicant]
US 20230096469A1 · Kaippallimalil · 2023 [cited by examiner]
US 20230199632A1 · Talebi Fard · 2023 [cited by examiner]
US 20230269589A1 · Baskaran · 2023 [cited by examiner]
US 20240080923A1 · Qiao · 2024 [cited by examiner]
WO 2020192871A1 · 2020 [cited by applicant]
WO 2021063981A1 · 2021 [cited by applicant]
3GPP: “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS); Stage 3; (Release 17),” 3GPP TS 24.501 V17.2.1, Technical Speci… [cited by applicant]
3GPP: “3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; User Equipment (UE) policies for 5G System (5GS); Stage 3 (Release 17),” 3GPP TS 24.526 V17.3.0, Jun. 2021, 54 pages. [cited by applicant]
3GPP, “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Policy and Charging Control Framework for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.503 V17.1.0, Jun. 20… [cited by applicant]
3GPP: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Procedures for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.502 V17.1.0, Jun. 2021, 692 Pages. [cited by applicant]
3GPP: “3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System Architecture for the 5G System (5GS); Stage 2 (Release 17),” 3GPP TS 23.501 V17.1.1, Technical Specification, … [cited by applicant]
Cheshire S., et al., “DNS-Based Service Discovery,” Internet Engineering Task Force (IETF), Request for Comments: 5763, Category: Standards Track, Feb. 2013, 49 Pages. [cited by applicant]
Cloudflare: “What is a DNS TXT Record?,” Retrieved from URL: https://www.cloudflare.com/learning/dns/dns-records/dns-txt-record/, retrieved Oct. 1, 2021, 4 pages. [cited by applicant]
Crocker D., “DNS AttrLeaf Changes: Fixing Specifications That Use Underscored Node Names,” Internet Engineering Task Force (IETF), Request for Comments: 8553, BCP: 222, Category: Best Current Practice, SSN: 2070-1721, M… [cited by applicant]
GSMA: “Generic Network Slice Template,” Official Document NG.116, Version 2.0, Oct. 16, 2019, 61 pages. [cited by applicant]
Gulbrandsen A., et al., “A DNS RR for Specifying the Location of Services (DNS SRV),” Network Working Group, Request for Comments: 2782, Obsoletes: 2052, Category: Standards Track, Feb. 2000, 12 Pages. [cited by applicant]
Mockapetris P., “Domain Names—Implementation and Specification”, Network Working Group, Request for Comments: 1035, Nov. 1987, 55 pages. [cited by applicant]
Rosenbaum R., “Using the Domain Name System to Store Arbitrary String Attributes”, Network Working Group, Request for Comments: 1464, May 1993, 4 Pages. [cited by applicant]
Cited By (1)
US 12,342,419