IP Library › Granted Patent US 12,356,321
Granted Patent B2
US 12,356,321 · App. 17/877,541 · Granted Jul 8, 2025

Entity and method for network slice enablement for a vertical application

Inventors: Emmanouil Pateromichelakis (Munich, DE); Xueli An (Munich, DE); Cuili Ge (Beijing, CN); Yanmei Yang (Beijing, CN); Ishan Vaishnavi (Munich, DE)
Assignee: Huawei Technologies Co., Ltd.
H04W48/18H04W24/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,356,321
App. No.
17/877,541
Granted
Jul 8, 2025
Kind
B2
Abstract

The present disclosure relates to network slicing, in particular, in 5G networks systems. The disclosure is concerned with network slice enablement for (vertical) applications. Thus, an entity for inter-operation between a network system and at least one application is provided. The entity provides a request to the network system, for selection and/or adjustment of a network slice instance (NSI) providing one or more services to the at least one application. The request comprises a set of requirements for the at least one application and/or the one or more services. The set of requirements comprises a required configuration or adaption of at least one NSI related parameter. The entity further receives a response to the request from the network system. The response indicates a decision of the network system regarding the selection and/or adjustment of the NSI.

Claims (153)

1. An entity for inter-operation between a network system and at least one application, the entity being configured to:

provide, to the network system, a request for at least one of selection and adjustment of a network slice instance (NSI) for providing one or more services to the at least one application,

wherein the request comprises a set of requirements for the at least one application and the one or more services, the set of requirements comprising a required configuration or adaption of at least one NSI related parameter;

receive, from the network system, a response to the request, wherein the response indicates a decision of the network system regarding at least one of the selection and adjustment of the NSI; and

receive:

a set of quality of experience (QoE) parameters for the at least one application and the one or more services, and

from a network data analytics function (NWDAF), quality of service (QoS) status information for at least one of the one or more application and the one or more services.

2. The entity according to claim 1 , wherein the response to the request comprises one of:

a recommended NSI that satisfies the set of requirements;

a recommended adaption of the set of requirements; and

an indication that the set of requirements cannot be satisfied.

3. The entity according to claim 1 further configured to:

provide, to the at least one application, a notification regarding at least one of the selection and adjustment of the NSI, according to the response received from the network system.

4. The entity according to claim 1 , wherein

the required configuration or adaption of the at least one NSI related parameter included in the set of requirements comprises at least one of:

a required configuration or adaption of the mapping of the one or more NSIs;

a required configuration or adaption of the one or more NSI parameters;

a required configuration or adaption of one or more NSI subnet parameters for one or more User Equipments (UEs); and

a required configuration or adaption of the one or more network slice types.

5. The entity according to claim 1 , wherein

the request comprises a request for selection of at least one NSI.

6. The entity according to claim 4 , wherein

the one or more NSI parameters comprise at least one of:

a slice type;

a charging requirement;

a coverage area requirement;

end-to-end latency requirement;

an overall user density requirement;

a service availability requirement;

a service reliability requirement;

a priority requirement;

a degree of isolation requirement;

an area traffic capacity requirement;

a mobility requirement;

a UE speed requirement;

a delay tolerance;

a deterministic communication;

download (DL) and/or upload (UL) throughput per UE;

at least one of a DL and UL throughput per network slice;

a maximum packet size;

a maximum number of connections;

Key performance indicator (KPI) monitoring;

one or more supported access technologies;

user management open;

one or more Vehicle-to-Anything (V2X) models;

term density;

an activity factor;

Jitter;

Survival time; and

Reliability.

7. The entity according to claim 1 , further configured to:

obtain at least one of:

NSI status information from the network system, and

application information related to the at least one application; and

provide the request for at least one of selection and adjustment of a NSI based on at least one of the NSI status information and the application information.

8. A network entity, configured to:

receive, from a first entity, a request for at least one of selection and adjustment of a network slice instance (NSI) for providing one or more services to at least one application,

wherein the request comprises a set of requirements of the at least one application and the one or more services, the set of requirements comprising a required configuration or adaption of at least one NSI related parameter;

provide, to the first entity, a response to the request, the response comprising one of:

a recommended NSI that satisfies the set of requirements;

a recommended adaption of the set of requirements;

an indication that the set of requirements cannot be satisfied; and

provide:

a set of quality of experience (QoE) parameters for the at least one application and the one or more services, and

from a network data analytics function (NWDAF), quality of service (QoS) status information for at least one of the one or more application and the one or more services.

9. The network entity according to claim 8 , further configured to:

adjust one or more NSIs based on the request, if a NSI can satisfy the set of requirements.

10. A method for inter-operation between a network system and at least one application, the method comprising:

providing, to the network system, a request for at least one of selection and adjustment of a network slice instance (NSI) for providing one or more services to the at least one application,

wherein the request comprises a set of requirements for the at least one application and the one or more services, the set of requirements comprising a required configuration or adaption of at least one NSI related parameter;

receiving, from the network system, a response to the request, wherein the response indicates a decision of the network system regarding at least one of the selection and adjustment of the NSI; and

receiving:

a set of quality of experience (QoE) parameters for the at least one application and the one or more services, and

from a network data analytics function (NWDAF), quality of service (QOS) status information for at least one of the one or more application and the one or more services.

11. The network entity according to claim 8 , wherein the required configuration or adaption of the at least one NSI related parameter included in the set of requirements comprises at least one of:

a required configuration or adaption of the mapping of the one or more NSIs;

a required configuration or adaption of the one or more NSI parameters;

a required configuration or adaption of one or more NSI subnet parameters for one or more User Equipments (UEs); and

a required configuration or adaption of the one or more network slice types.

12. The network entity according to claim 8 , wherein the request comprises a request for selection of at least one NSI.

13. The network entity according to claim 11 , wherein the one or more NSI parameters comprise at least one of:

a slice type;

a charging requirement;

a coverage area requirement;

end-to-end latency requirement;

an overall user density requirement;

a service availability requirement;

a service reliability requirement;

a priority requirement;

a degree of isolation requirement;

an area traffic capacity requirement;

a mobility requirement;

a UE speed requirement;

a delay tolerance;

a deterministic communication;

download (DL) and/or upload (UL) throughput per UE;

at least one of a DL and UL throughput per network slice;

a maximum packet size;

a maximum number of connections;

Key performance indicator (KPI) monitoring;

one or more supported access technologies;

user management open;

one or more Vehicle-to-Anything (V2X) models;

term density;

an activity factor;

Jitter;

Survival time; and

Reliability.

14. The method according to claim 10 , wherein the response to the request comprises one of:

a recommended NSI that satisfies the set of requirements;

a recommended adaption of the set of requirements; and

an indication that the set of requirements cannot be satisfied.

15. The method according to claim 10 , further comprising:

providing, to the at least one application, a notification regarding at least one of the selection and adjustment of the NSI, according to the response received from the network system.

16. The method according to claim 10 , wherein the required configuration or adaption of the at least one NSI related parameter included in the set of requirements comprises at least one of:

a required configuration or adaption of the mapping of the one or more NSIs;

a required configuration or adaption of the one or more NSI parameters;

a required configuration or adaption of one or more NSI subnet parameters for one or more User Equipments (UEs); and

a required configuration or adaption of the one or more network slice types.

17. The method according to claim 10 , wherein the request comprises a request for selection of at least one NSI.

18. The method according to claim 16 , wherein the one or more NSI parameters comprise at least one of:

a slice type;

a charging requirement;

a coverage area requirement;

end-to-end latency requirement;

an overall user density requirement;

a service availability requirement;

a service reliability requirement;

a priority requirement;

a degree of isolation requirement;

an area traffic capacity requirement;

a mobility requirement;

a UE speed requirement;

a delay tolerance;

a deterministic communication;

download (DL) and/or upload (UL) throughput per UE;

at least one of a DL and UL throughput per network slice;

a maximum packet size;

a maximum number of connections;

Key performance indicator (KPI) monitoring;

one or more supported access technologies;

user management open;

one or more Vehicle-to-Anything (V2X) models;

term density;

an activity factor;

Jitter;

Survival time; and

Reliability.

19. The method according to claim 10 , further comprising:

obtaining at least one of:

NSI status information from the network system, and

application information related to the at least one application; and

providing the request for at least one of selection and adjustment of a NSI based on at least one of the NSI status information and the application information.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 28, 2025
From: PATEROMICHELAKIS, EMMANOUIL; AN, XUELI; GE, CUILI; YANG, YANMEI; VAISHNAVI, ISHAN
To: HUAWEI TECHNOLOGIES CO., LTD.
Reel/Frame 071242/0898 →
Continuity (2)
Continuation PCTEP2020052458 · Jan 31, 2020
Related Publication 20220369221A1 · Nov 17, 2022
References Cited (45)
US 8190191B2 · Livet et al. · 2012 [cited by applicant]
US 11050626B2 · Senarath · 2021 [cited by examiner]
US 11405931B2 · Gupta · 2022 [cited by examiner]
US 20170070892A1 · Song · 2017 [cited by examiner]
US 20170339688A1 · Singh · 2017 [cited by examiner]
US 20170367036A1 · Chen · 2017 [cited by examiner]
US 20180139107A1 · Senarath et al. · 2018 [cited by applicant]
US 20180332485A1 · Senarath et al. · 2018 [cited by applicant]
US 20190109768A1 · Senarath et al. · 2019 [cited by applicant]
US 20190261233A1 · Duan · 2019 [cited by examiner]
US 20210306973A1 · Casati · 2021 [cited by examiner]
US 20220200874A1 · Fendt · 2022 [cited by examiner]
US 20220338062A1 · Bennett · 2022 [cited by examiner]
US 20220369221A1 · Pateromichelakis · 2022 [cited by examiner]
US 20220408293A1 · Han · 2022 [cited by examiner]
WO 2018103865A1 · 2018 [cited by applicant]
WO 2019161925A1 · 2019 [cited by applicant]
WO 2020011350A1 · 2020 [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Telecommunication management; Study on management and orchestration of network slicing for next generation network (Release… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for cyber-physical control applications in vertical domains; Stage 1 (Release 16),” 3GPP TS 22.104 V16… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Architecture for Next Generation System (Release 14),” 3GPP TR 23.799 V1.1.0, Total 501 pages, 3rd Generation Part… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Enhancement of 3GPP support for V2X scenarios; Stage 1 (Release 16),” 3GPP TS 22.186 V16.2.0, Total 18 pages, 3rd Generatio… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service requirements for the 5G system; Stage 1 (Release 17),” 3GPP TS 22.261 V17.0.0, Total 83 pges, 3rd Generation Partne… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Mission Critical Services Common Requirements (MCCoRe); Stage 1 (Release 17),” 3GPP TS 22.280 V17.2.0, Total 97 pages, 3rd … [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Communication for Automation in Vertical Domains (Release 16),” 3GPP TR 22.804 V16.2.0, Total 196 pages, 3rd Gener… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Application layer support for Vehicle-to-Everything (V2X) services; Functional architecture and information flows; (Release… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Architecture enhancements for 5G System (5GS) to support network data analytics services (Release 16),” 3GPP TS 23.288 V16.… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service Enabler Architecture Layer for Verticals (SEAL); Functional architecture and information flows; (Release 16),” 3GPP… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS); Stage 2 (Release 15),” 3GPP TS 23.501 V15.8.0, Total 248 pages, 3rd Generation… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on application layer support for Factories of the Future in 5G network; (Release 17),” 3GPP TR 23.745 V0.7.0, Total 2… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on enhancements to application layer support for V2X services; (Release 17),” 3GPP TR 23.764 V0.4.0, Total 20 pages, … [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on Mission Critical services support over 5G System (Release 16),” 3GPP TR 23.783 V0.9.0, Total 41 pages, 3rd Generat… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Common functional architecture to support mission critical services; Stage 2 (Release 17),” 3GPP TS 23.280 V17.0.0, Total 2… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Functional architecture and information flows to support Mission Critical Push To Talk (MCPTT); Stage 2 (Release 17),” 3GPP… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Functional architecture and information flows to support Mission Critical Video (MCVideo); Stage 2 (Release 17),” 3GPP TS 2… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Functional architecture and information flows to support Mission Critical Data (MCData); Stage 2 (Release 17),” 3GPP TS 23.… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Mission Critical Communication Interworking with Land Mobile Radio Systems; Stage 2 (Release 17),” 3GPP TS 23.283 V17.0.0, … [cited by applicant]
“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 support advanced V2X serv… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Study on application layer support for V2X services; (Release 16),” 3GPP TR 23.795 V16.1.0, Total 77 pages, 3rd Generation … [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Concepts, use cases and requirements (Release 15),” 3GPP TS 28.530 V15.3.0, Total 29 pages, 3… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Provisioning; (Release 15),” 3GPP TS 28.531 V15.5.0, Total 66 pages, 3rd Generation Partnersh… [cited by applicant]
“3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Management and orchestration; Architecture framework (Release 16),” 3GPP TS 28.533 V16.2.0, Total 29 pages 3rd Generation P… [cited by applicant]
Held, “A Broadband Strategy for German Critical Communications,” Barbara Held (BDBOS), CCEurope 2019, Federal Agency for Public Safety, Digital Radio,Total 16 pages (Mar. 12, 2019). [cited by applicant]
Huawei et al., “Proposal for solution to key issue on supporting network slicing,” 3GPP TSG-SA WG6 Meeting #25, Sophia Antipolis, France, S6-181272(revision of S6-181107, 1167, 1236), Total 4 pages, 3rd Generation Partn… [cited by applicant]
BDBOS, “Pseudo-CR on 5GS network slicing supporting Mission Critical,” 3GPP TSG-SA WG6 Meeting #30, Newport Beach, CA, USA, S6-190542(revision of S6-19xxxx), Total 2 pages 3rd Generation Partnership Project, Valbonne, F… [cited by applicant]