IP Library Granted Patent US 12,137,409
Granted Patent B2
US 12,137,409 · App. 17/509,802 · Granted Nov 5, 2024

Registration procedure for ensuring service based on a selection of the best available network slice of the same slice type

Inventors: Ravi Shekhar (Pune, IN); Aditya Prakash (Bangalore, IN); Amit Shivhare (Gurgaon, IN); Vimal Srivastava (Bangalore, IN)
Assignee: CISCO TECHNOLOGY, INC.
H04W48/18H04W8/18H04W60/00H04W72/54H04W72/563H04W76/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,137,409
App. No.
17/509,802
Granted
Nov 5, 2024
Kind
B2
Abstract

A control plane (CP) function for mobility management may receive, from a user equipment (UE), a message which indicates a registration request for registration to a network slice. The CP function may select, as an allowed slice ID, a first slice ID of a first network slice in which to register the UE. The first slice ID has a slice/service type (SST) value indicating an SST and a first slice differentiator (SD) value associated with a first level of service to be provided. The CP function may alternatively select, as the allowed slice ID, a second slice ID of a second network slice in which to register the UE based on unavailability of the slice type associated with the first level of service. The second slice ID has the SST value indicating the slice type and a second SD value associated with a second level of service to be provided.

Claims (61)

1. A method comprising:

at a control plane function for mobility management,

receiving, from a user equipment (UE), a message which indicates a registration request for registration to a network slice of a mobile network;

obtaining subscription information associated with the UE, the subscription information including a subscribed slice ID having a slice type value indicating a slice type and having a subscription attribute indicating whether a requirement or preference for registration to a network slice having a best available or alternative level of service for the slice type indicated by the slice type value is enabled or disabled for the UE;

selecting, as an allowed slice ID, a first slice ID of a first network slice in which to register the UE based on availability of the first network slice, the first slice ID having the slice type value indicating the slice type and having a first slice differentiator value associated with a first level of service;

based on unavailability of the slice type having the first slice differentiator value associated with the first level of service and based on the subscription attribute indicating the requirement or preference for registration to a network slice having a best available or alternative level of service for the slice type indicated by the slice type value is enabled, alternatively selecting, as the allowed slice ID, a second slice ID of a second network slice in which to register the UE, the second slice ID having the slice type value indicating the slice type and having a second slice differentiator value associated with a second level of service; and

sending, to the UE, a message which indicates a registration accept including the allowed slice ID.

2. The method of claim 1 , wherein the message which indicates the registration request for registration includes a requested network slice ID comprising the first slice ID.

3. The method of claim 1 , wherein the message which indicates the registration request for registration includes a requested network slice ID comprising a wildcard slice ID, the wildcard slice ID having the slice type value and a wildcard slice differentiator value that is associated with the subscription attribute indicating the requirement or preference for registration to a network slice having a best available or alternative level of service for the slice type indicated by the slice type value.

4. The method of claim 1 , wherein the first level of service comprises:

a higher level of service than the second level of service,

one or more services that are unavailable in the second level of service, or

an allocation or reservation of resources according to one or more service parameters that are not provided in the second level of service.

5. The method of claim 1 , wherein the first network slice is available in a first location and unavailable in a second location, and the second network slice is available in the first location and the second location, and wherein:

selecting, as the allowed slice ID, the first slice ID of the first network slice is performed when the UE is identified to operate in the first location, and

alternatively selecting, as the allowed slice ID, the second slice ID of the second network slice is performed when the UE is identified to operate in the second location.

6. The method of claim 1 , further comprising:

at the control plane function for mobility management,

causing charging information to be communicated to a charging function, the charging information being indicative of charging according to one of the first level of service of the first network slice that is selected for registration or the second level of service of the second network slice that is alternatively selected for registration.

7. The method of claim 1 , wherein the control plane function for mobility management comprises an access and mobility management function (AMF).

8. The method of claim 1 , wherein the first level of service is a higher level of service than the second level of service for the slice type.

9. A network node comprising:

one or more processors;

one or more interfaces to connect in a mobile network; and

one or more memory elements for storing instructions executable by the one or more processors for operation as a control plane function for mobility management, including for:

receiving, from a user equipment (UE), a message which indicates a registration request for registration to a network slice of a mobile network;

obtaining subscription information associated with the UE, the subscription information including a subscribed slice ID having a slice type value indicating a slice type and having a subscription attribute indicating whether a requirement or preference for registration to a network slice having a best available or alternative level of service for the slice type indicated by the slice type value is enabled or disabled for the UE;

selecting, as an allowed slice ID, a first slice ID of a first network slice in which to register the UE based on availability of the first network slice, the first slice ID having the slice type value indicating the slice type and having a first slice differentiator value associated with a first level of service;

based on unavailability of the slice type having the first slice differentiator value associated with the first level of service and based on the subscription attribute indicating the requirement or preference for registration to a network slice having a best available or alternative level of service for the slice type indicated by the slice type value is enabled, alternatively selecting, as the allowed slice ID, a second slice ID of a second network slice in which to register the UE, the second slice ID having the slice type value indicating the slice type and having a second slice differentiator value associated with a second level of service; and

sending, to the UE, a message which indicates a registration accept including the allowed slice ID.

10. The network node of claim 9 , wherein the message which indicates the registration request for registration includes a requested network slice ID comprising the first slice ID.

11. The network node of claim 9 , wherein the message which indicates the registration request for registration includes a requested network slice ID comprising a wildcard slice ID, the wildcard slice ID having the slice type value and a wildcard slice differentiator value that is associated with the subscription attribute indicating the requirement or preference for registration to a network slice having a best available or alternative level of service for the slice type indicated by the slice type value.

12. The network node of claim 9 , wherein:

the first level of service comprises: a higher level of service than the second level of service, one or more services that are unavailable in the second level of service, or an allocation or reservation of resources according to one or more service parameters that are not provided in the second level of service,

the first network slice is available in a first location and unavailable in a second location,

the second network slice is available in the first location and the second location,

selecting, as the allowed slice ID, the first slice ID of the first network slice is performed when the UE is identified to operate in the first location, and

alternatively selecting, as the allowed slice ID, the second slice ID of the second network slice is performed when the UE is identified to operate in the second location.

13. The network node of claim 9 , wherein the instructions executable by the one or more processors for operation as the control plane function for mobility management for:

causing charging information to be communicated to a charging function, the charging information being indicative of charging according to one of the first level of service of the first network slice that is selected for registration or the second level of service of the second network slice that is alternatively selected for registration.

14. The network node of claim 9 , wherein the control plane function for mobility management comprises an access and mobility management function (AMF).

15. A computer program product comprising:

a non-transitory computer readable medium;

instructions in the non-transitory computer readable medium; and

the instructions being executable by one or more processors of a control plane function for mobility management including:

receiving, from a user equipment (UE), a message which indicates a registration request for registration to a network slice of a mobile network;

obtaining subscription information associated with the UE, the subscription information including a subscribed slice ID having a slice type value indicating a slice type and having a subscription attribute indicating whether a requirement or preference for registration to a network slice having a best available or alternative level of service for the slice type indicated by the slice type value is enabled or disabled;

selecting, as an allowed slice ID, a first slice ID of a first network slice in which to register the UE based on availability of the first network slice, the first slice ID having the slice type value indicating slice type and having a first slice differentiator value associated with a first level of service;

based on unavailability of the slice type having the first slice differentiator value associated with the first level of service and based on the subscription attribute indicating the requirement or preference for registration to a network slice having a best available or alternative level of service for the slice type indicated by the slice type value is enabled, alternatively selecting, as the allowed slice ID, a second slice ID of a second network slice in which to register the UE, the second slice ID having the slice type value indicating the slice type and having a second slice differentiator value associated with a second level of service; and

sending, to the UE, a message which indicates a registration accept including the allowed slice ID.

16. The computer program product of claim 15 , wherein the message which indicates the registration request for registration includes a requested network slice ID comprising the first slice ID.

17. The computer program product of claim 15 , wherein the message which indicates the registration request for registration includes a requested network slice ID comprising a wildcard slice ID, the wildcard slice ID having the slice type value and a wildcard slice differentiator value that is associated with the subscription attribute indicating the requirement or preference for registration to a network slice having a best available or alternative level of service for the slice type indicated by the slice type value.

18. The computer program product of claim 15 , wherein the first level of service comprises:

a higher level of service than the second level of service,

one or more services that are unavailable in the second level of service, or

an allocation or reservation of resources according to one or more service parameters that are not provided in the second level of service.

19. The computer program product of claim 15 , wherein the first network slice is available in a first location and unavailable in a second location, and the second network slice is available in the first location and the second location, and wherein the instructions are further executable by the one or more processors of the control plane function for mobility management for:

selecting, as the allowed slice ID, the first slice ID of the first network slice when the UE is identified to operate in the first location, and

alternatively selecting, as the allowed slice ID, the second slice ID of the second network slice when the UE is identified to operate in the second location.

20. The computer program product of claim 15 , wherein the instructions are further executable by the one or more processors of the control plane function for mobility management for:

causing charging information to be communicated to a charging function, the charging information being indicative of charging according to one of the first level of service of the first network slice that is selected for registration or the second level of service of the second network slice that is alternatively selected for registration.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 25, 2021
From: SHEKHAR, RAVI; PRAKASH, ADITYA; SHIVHARE, AMIT; SRIVASTAVA, VIMAL
To: CISCO TECHNOLOGY, INC.
Reel/Frame 057903/0144 →
Continuity (1)
Related Publication 20230132096A1 · Apr 27, 2023