EP4740448A1 - System and method for nsp - pcf provisioning - Google Patents

Abstract

The present disclosure provides a system (110) and method (400) for network service provider (NSP)-policy control function (PCF) provisioning. The system (110) enables a network service provider (NSP) operator (102) to create, modify, or delete slice-related information in an access and mobility management function (AMF), session management function (SMF), unified data management (UDM), network slicing selection function (NSSF), and policy control function (PCF) from a centralized point using a NSP portal (104). Further, the NSP operator (102) may provision a first and a second set of rules for data network name (DNN) and policy and charging control (PCC). The NSP operator (102) may create policies at the PCF based on the first and second set of rules to enable a communication network to readily configure new slices without any manual intervention on PCF instances.

Description

SYSTEM AND METHOD FOR NSP - PCF PROVISIONING RESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.

FIELD OF DISCLOSURE

[0002] The embodiments of the present disclosure generally relate to a communication network. In particular, the present disclosure relates to a system and method for network service provider (NSP) policy control function (PCF) provisioning in a communication network.

BACKGROUND OF DISCLOSURE

[0003] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0004] Communications networks provide network services to numerous subscribers. The network services may include voice, data, and message. For example, a fifth generation (5G) communication network includes network slices to provide such services. At times when the network load increases there is a need to configure new slices. A new operator at a network service provider side may do such configurations manually. However, at times, the network load may not be properly estimated, and the manual configuration may not be very effective.

[0005] There is, therefore, a need in the art to provide a method and a system that can overcome the shortcomings of the existing prior arts.

OBJECTS OF THE PRESENT DISCLOSURE

[0006] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.

[0007] An object of the present disclosure is to enable a network service provider (NSP) operator to create, modify, or delete slice-related information in an access and mobility management function (AMF), session management function (SMF), unified data management (UDM), network slicing selection function (NSSF), and policy control function (PCF) from a centralized point using a NSP portal.

[0008] An object of the present disclosure is to enable the NSP operator to provision rules for data network name (DNN) and policy and charging control (PCC).

[0009] An object of the present disclosure is to provide policy creation at the PCF by the NSP operator.

[0010] An object of the present disclosure is to enable a communication network to readily configure new network slice without any manual intervention on PCF instances.

SUMMARY

[0011] In an exemplary embodiment, the present disclosure discloses a method for network service provider (NSP) policy control function (PCF) provisioning in a communication network. The method includes receiving, by a processing engine, at least one attach request from a user equipment (UE). The method includes authenticating, by the processing engine, the UE based on the received at least one attach request. The method includes retrieving, by the processing engine, at least one subscription profile of the UE. The method includes providing, by the processing engine, at least one network slice related information based on the retrieved at least one subscription profile. The method includes providing, by the processing engine, a first set of rules for at least one data network name (DNN) to serve the UE. The method includes providing, by the processing engine, a second set of rules for at least one policy and charging control (PCC). The method includes creating, by the processing engine, a set of policies at the policy control function (PCF) each of the first set of rules and the second set of rules.

[0012] In some embodiments, the at least one network slice related information includes at least one virtualized network function (VNF) for providing an end-to-end network service to the UE.

[0013] In some embodiments, the at least one attach request includes information about a type of a service the UE has subscribed.

[0014] In some embodiments, the information about the type of the service includes an information about an application service identifier, an information about the at least one DNN to serve the UE, and an information about at least one network slice to which the UE is previously attached.

[0015] In some embodiments, the at least one subscription profile includes an information about at least one network slice allowed to the UE, and an information about at least one default network slice when the information about the type of service the UE desires to use is not included in the received attach request. [0016] In some embodiments, the first set of rules for at least one DNN includes one or more rules for selecting appropriate data network based on the at least one subscription profile, one or more rules for managing network access and connectivity parameters for the UE, and one or more rules associated with quality of service (QoS) to ensure required performance for the UE.

[0017] In some embodiments, the second set of rules for at least one PCC comprises one or more rules for data usage policies to manage amount of data the UE consumes, and one or more rules to determine billing and charging for the data usage.

[0018] In an exemplary embodiment, the present disclosure discloses a system for network service provider (NSP) policy control function (PCF) provisioning in a communication network. The system includes a memory, and one or more processor(s) coupled with the memory (204), configured to receive at least one attach request from a user equipment (UE). The one or more processor(s) is configured to authenticate the UE based on the received at least one attach request. The one or more processor(s) is configured to retrieve at least one subscription profile of the UE. The one or more processor(s) is configured to provide at least one network slice related information based on the retrieved at least one subscription profile. The one or more processor(s) is configured to provide a first set of rules for at least one data network name (DNN) to serve the UE. The one or more processor(s) is configured to provide a second set of rules for at least one policy and charging control (PCC). The one or more processor(s) is configured to create a set of policies at the policy control function (PCF) based on each of the first set of rules and the second set of rules.

[0019] In some embodiments, the at least one network slice information includes at least one virtualized network function (VNF) for providing an end-to- end network service to the UE.

[0020] In some embodiments, the at least one attach request includes information about a type of a service the UE has subscribed.

[0021] In some embodiments, the information about the type of the service includes an information about an application service identifier, an information about the at least one DNN to serve the UE, and an information about at least one network slice to which the UE is previously attached.

[0022] In some embodiments, the at least one subscription profile includes an information about at least one network slice allowed to the UE, and an information about at least one default network slice when the information about the type of service the UE desires to use is not included in the received attach request. [0023] In some embodiments, the first set of rules for at least one DNN includes one or more rules for selecting appropriate data network based on the at least one subscription profile, one or more rules for managing network access and connectivity parameters for the UE, and one or more rules associated with quality of service (QoS) to ensure required performance for the UE. [0024] In some embodiments, the second set of rules for at least one PCC comprises one or more rules for data usage policies to manage amount of data the UE consumes, and one or more rules to determine billing and charging for the data usage.

[0025] In an exemplary embodiment, the present disclosure discloses a user equipment (UE) communicatively coupled with at least one network slice through an access and mobility management function (AMF), the coupling comprises steps of: receiving, by the at least one network slice, an attach request from the UE, sending an acknowledgment of the attach request to the UE, authenticating the UE based on the received attach request, retrieving at least one subscription profile of the UE from a unified data management (UDM) module, and transmitting at least one network slice related information to the UE, wherein the at least one network slice comprising a session management function (SMF), a network slicing selection function (NSSF), and a policy control function (PCF) configured to implement a first set of rules for data network name (DNN) and a second set of rules for policy and charging control (PCC) for NSP-PCF provisioning in a communication network.

BRIEF DESCRIPTION OF DRAWINGS

[0026] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components. [0027] FIG. 1 illustrates an exemplary network architecture in which or with which a proposed system may be implemented, in accordance with embodiments of the present disclosure.

[0028] FIG. 2 illustrates an exemplary block diagram representing a system for provisioning an NSP operator to configure various network slice modules, in accordance with embodiments of the present disclosure.

[0029] FIG. 3 illustrates an architecture of RESTful application program interface (API), in accordance with embodiments of the present disclosure.

[0030] FIG. 4 illustrates a flow diagram of a method for NSP-PCF provisioning in a communication network, in accordance with embodiments of the present disclosure.

[0031] FIG. 5 illustrates an exemplary computer system in which or with which embodiments of the present disclosure may be implemented.

[0032] The foregoing shall be more apparent from the following more detailed description of the disclosure.

LIST OF REFERENCE NUMERALS

100 - Network architecture

102 - A network service provider (NSP) operator

104 - A NSP portal

106 - A network slice

108 - A data network (DN)

110 - System

200 - Block Diagram

202 - one or more processor(s)

204 - Memory

206 - one or more interface(s) 208 - Processing engine

210, 302 - Database

212 - Acquisition unit

214 - Provisioning unit

216 - Other unit(s)

300 - An architecture of RESTful application program interface (API)

304 - A plurality of server(s)

306 - A computing device

308 - A RESTful API

500 - A computer system

510 - External storage device

520 - Bus

530 - Main memory

540 - Read only memory

550 - Mass storage device

560 - Communication port(s)

570 - Processor

DETAILED DESCRIPTION OF DISCLOSURE

[0033] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.

[0034] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0035] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

[0036] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

[0037] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive — in a manner similar to the term “comprising” as an open transition word — without precluding any additional or other elements.

[0038] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0039] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any and all combinations of one or more of the associated listed items.

[0040] Certain terms and phrases have been used throughout the disclosure and will have the following meanings in the context of the ongoing disclosure.

[0041] The term “SMF” may refer to session management function for collecting information related to packet data unit (PDU) session management from various network components in a 5G core network. [0042] The term “PCF” may refer to policy control function specifying policy rules for application and service data flow detection, gating, Quality of Service (QoS), and flow-based charging to the SMF.

[0043] The term “AMF” may refer to access and mobility management function providing control plane network functions (NF) of the 5G core network.

[0044] The term “NSSF” may refer to Network Slicing Selection Function for selecting an optimal network slice available for a service requested by the user. [0045] The term “UDM” may refer to user data management for managing data for access authorization, user registration, and data network profiles.

[0046] The various embodiments throughout the disclosure will be explained in more detail with reference to FIGs. 1-5.

[0047] In an aspect the present disclosure relates to a system enabling a network service provider (NSP) operator to create, modify, or delete slice-related information in an access and mobility management function (AMF), session management function (SMF), unified data management (UDM), network slicing selection function (NSSF), and policy control function (PCF) from a centralized point using a NSP portal. In some embodiments, the NSP operator may provision rules for data network name (DNN) and policy and charging control (PCC). In an embodiment, the NSP operator may create policies at the PCF to enable a communication network to readily configure new slices without any manual intervention on PCF instances.

[0048] FIG. 1 illustrates an exemplary network architecture (100) in which or with which a proposed system may be implemented, in accordance with embodiments of the present disclosure.

[0049] Referring to FIG. 1, the network architecture (100) may include a NSP operator (102) configuring at least one network slice (106) through a NSP portal (104). The network slice (106) may be connected to a data network (DN) (108). The DN (108) facilitates a transmission and exchange of data within the network architecture (100). It may include various physical and logical components, including switches, routers, cables, and protocols, that enable the connectivity and communication within the network slice (106). Further, the NSP portal (104) may include a system (110) for provisioning centralized management of one or more network slice modules.

[0050] In an embodiment, the network slice (106) may provide one or more services to a user equipment (UE) (not shown). The UE may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of device with wireless communication capabilities, and the like. Alternatively, in some embodiments, the UE may include, but not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general- purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device.

[0051] In an embodiment, the network slice (106) may include a communication network such as, but not limited to, a non- standalone (NSA) 5G network, a standalone 5G network, or the like. The network slice (106) may provide a voice, data, or a message service to the UE in the communication network.

[0052] By way of an example, the UE may be communicatively coupled with at least one network slice (106) through an access and mobility management function (AMF). The coupling may include steps of receiving, by the at least one network slice (106), an attach request from the UE, sending an acknowledgment of the attach request to the UE, authenticating the UE based on the received attach request, retrieving at least one subscription profile of the UE, and transmitting at least one network slice related information to the UE. The at least one network slice may include a SMF, a NSSF, and a PCF configured to implement a first set of rules for data network name (DNN) and a second set of rules for policy and charging control (PCC) for NSP-PCF provisioning in the communication network. [0053] The network slice (106) may include one or more modules for providing one or more services to the UE within the communication network. The one or more modules may include, an AMF module, a SMF module, a NSSF module, a UDM module and a PCF module. The PCF module may include a RESTful API for performing configuration of rules and policies for the DNN, PCC, and PCF. The RESTful API may further enable automatic configuration of new network slices.

[0054] The AMF module is responsible for managing the access and mobility of the UE within the network slice (106). It handles tasks such as UE authentication, mobility management, and connection establishment. The AMF module ensures seamless handover between different network cells and manages the UE movement within a network coverage area.

[0055] Further, the SMF module is tasked with managing the session- related aspects of the UE connection within the network slice (106). It manages creation, modification, and termination of sessions for various services utilized by the UE. This may include managing IP address allocation, Quality of Service (QoS) enforcement, and session continuity across different access networks.

[0056] Further, the NSSF module plays a critical role in selecting the appropriate network slice for the UE based on its specific requirements and network conditions. It evaluates factors such as UE preferences, service characteristics, and network resources to determine the most suitable slice for delivering the desired services to the UE.

[0057] Further, the UDM module serves as a centralized repository for storing and managing subscriber-related data and subscription profiles within the network slice. It stores information such as user identities, authentication credentials, service subscriptions, and policy profiles. The UDM module ensures efficient access to subscriber data for authentication, authorization, and service provisioning purposes.

[0058] Additionally, the PCF module is responsible for enforcing network policies and managing the charging aspects of the network slice (106). It implements policies related to DNN selection, PCC, and overall network resource management. The PCF module utilizes a RESTful API to configure rules and policies dynamically, enabling flexible and automated management of network slices. Additionally, the RESTful API facilitates the automatic configuration of new network slices, ensuring scalability and efficiency in network management operations. An architecture of the RESTful API is depicted in FIG. 3.

[0059] Although FIG. 1 shows exemplary components of the network architecture (100), in other embodiments, the network architecture (100) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture (100) may perform functions described as being performed by one or more other components of the network architecture (100).

[0060] FIG. 2 illustrates an exemplary block diagram (200) representing the system (110) for provisioning the NSP operator (102) to configure one or more network slice modules, in accordance with embodiments of the present disclosure. [0061] Referring to FIG. 2, the PCF system, or the system (110) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (110). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may comprise any non- transitory storage device including, for example, volatile memory such as Random- Access Memory (RAM), or non-volatile memory such as Electrically Erasable Programmable Read-only Memory (EPROM), flash memory, and the like.

[0062] In an embodiment, the system (110) may include one or more interface(s) (206). The one or more interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as input/output (I/O) devices, storage devices, and the like. The interface(s) (206) may facilitate communication for the system (110). The one or more interface(s) (206) may also provide a communication pathway for one or more components of the system (110). Examples of such components include, but are not limited to, processing engine (208) and a database (210).

[0063] The processing engine (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (208). In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (208) may be processor-executable instructions stored on a non- transitory machine-readable storage medium and the hardware for the processing engine (208) may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine- readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine (208). In such examples, the system (110) may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine- readable storage medium may be separate but accessible to the system (208) and the processing resource. In other examples, the processing engine (208) may be implemented by electronic circuitry. In an aspect, the database (210) may comprise data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engine (208).

[0064] In an embodiment, to enable the NSP-PCF provisioning in the communication network, the processing engine (208) may include one or more units and/or modules such as, but not limited to, an acquisition unit (212), a provisioning unit (214), and other unit(s) (216).

[0065] The acquisition unit (212) may be responsible for collecting and acquiring relevant data and information from various sources within the network. It retrieves data related to the UE attach requests, subscription profiles, network slice configurations, and other details necessary for PCF provisioning.

[0066] In other words, the acquisition unit (212) may be configured to receive at least one attach request from the UE. Further, the acquisition unit (212) may be configured to authenticate the UE based on the received at least one attach request. Further, the acquisition unit (212) may be configured to retrieve at least one subscription profile of the UE.

[0067] Additionally, the provisioning unit (214) may utilize the information gathered by the acquisition unit (212) to provision network slices, define policies, and establish rules governing DNN and PCC. The provisioning unit (214) ensures that network resources are allocated efficiently and in accordance with the specified requirements and constraints.

[0068] For example, the provisioning unit (214) may be configured to provide at least one network slice (106) related information based on the retrieved at least one subscription profile. Further, the provisioning unit (214) may be configured to provide a first set of rules for at least one DNN to serve the UE. Further, the provisioning unit (214) may be configured to provide a second set of rules for at least one PCC. Furthermore, the provisioning unit (214) may be configured to create a set of policies at the policy control function (PCF) based on each of the first set of rules and the second set of rules.

[0069] The database (210) may store one or more policy and rules associated with the communication network (100). For example, the database (210) may store one or more rules for selecting appropriate data network based on the at least one subscription profile, one or more rules for managing network access and connectivity parameters for the UE, and one or more rules associated with quality of service (QoS) to ensure required performance for the UE. Additionally, the database (210) may store one or more rules for data usage policies to manage amount of data the UE consumes, and one or more rules to determine billing and charging for the data usage. [0070] A person of ordinary skill in the art will appreciate that the exemplary block diagram (200) may be modular and flexible to accommodate any kind of changes in the system (110).

[0071] FIG. 3 illustrates an architecture (300) of a RESTful application program interface (API) (308), in accordance with embodiments of the present disclosure. The architecture (300) for the RESTful API (308) is designed to facilitate seamless communication and efficient management of the network slice (106) in the communication network. The architecture (300) is essential for implementing various functions such as creating, modifying, and deleting network slice elements, ensuring dynamic and scalable network management.

[0072] As shown in FIG, 3, a plurality of servers (304) is connected to a database (302). The database (302) is a central repository that stores all necessary data required for the operation of the network slice (106). This includes configuration data, user profiles, network policies, and set of rules. The database (302) is structured to handle large volumes of data and provide quick access to the servers (304) for processing requests.

[0073] The plurality of servers (304) is responsible for executing the requests received from the RESTful API interface (308). The plurality of servers (304) performs various functions such as, processing the attach requests, handling initial connection requests from the UE, authenticating an identity of the UE based on the received attach requests, accessing the subscription profiles of the UE from the database (302), and providing rules and policies to network slices for managing DNN and policy and PCC.

[0074] The RESTful API interface (308) acts as a link between the plurality of servers (304) and a plurality of computing devices (306). This interface uses REST principles to provide a flexible and scalable method for network management. The RESTful API (308) is configured for creating network slices (i.e., defining and deploying new network slices as per the requirements), modifying network slices (i.e., updating existing network slices with new configurations, policies, or rules), and deleting network slices (i.e., removing network slices that are no longer needed). [0075] The plurality of computing devices (306) connected to the RESTful API interface (308) may include management consoles, network management systems (NMS), and other tools used by network administrators. The computing devices interact with the RESTful API (308) to send configuration requests (e.g., initiate operations to create, modify, or delete network slices), monitor network performance (e.g., retrieve status and performance metrics of various network slices), and update policies.

[0076] In some embodiments, the RESTful API (308) may specify the set of rules associated with controlling the operation of the AMF module in the network slice such as create, modify, and delete.

[0077] Referring to FIG. 4, a flow diagram of a method (400) for NSP-PCF provisioning in the communication network is illustrated, in accordance with embodiments of the present disclosure. The method (400), at step 402 includes receiving (402), by a processing engine (208), at least one attach request from a user equipment (UE). The method (400), at step 404 further includes authenticating (404), by the processing engine (208), the UE based on the received at least one attach request.

[0078] The method (400), at step 406 further includes retrieving (406), by the processing engine (208), at least one subscription profile of the UE. The method (400), at step 408 further includes providing (408), by the processing engine (208), at least one network slice (106) related information based on the retrieved at least one subscription profile.

[0079] The method (400), at step 410 further includes providing (410), by the processing engine (208), a first set of rules for at least one data network name (DNN) to serve the UE. The method (400), at step 412 further includes providing (412), by the processing engine (208), a second set of rules for at least one policy and charging control (PCC).

[0080] The method (400), at step 414 further includes creating (414), by the processing engine (208), a set of policies at the PCF based on each of the first set of rules and the second set of rules. [0081] In some embodiments, the at least one network slice related information includes at least one virtualized network function (VNF) for providing an end-to-end network service to the UE.

[0082] In some embodiments, the at least one attach request includes information about a type of a service the UE has subscribed.

[0083] In some embodiments, the information about the type of the service includes an information about an application service identifier, an information about the at least one DNN to serve the UE, and an information about at least one network slice to which the UE is previously attached.

[0084] In some embodiments, the at least one subscription profile includes an information about at least one network slice allowed to the UE, and an information about at least one default network slice when the information about the type of service the UE desires to use is not included in the received attach request. [0085] In some embodiments, the first set of rules for at least one DNN includes one or more rules for selecting appropriate data network based on the at least one subscription profile, one or more rules for managing network access and connectivity parameters for the UE, and one or more rules associated with quality of service (QoS) to ensure required performance for the UE.

[0086] In some embodiments, the second set of rules for at least one PCC comprises one or more rules for data usage policies to manage amount of data the UE consumes, and one or more rules to determine billing and charging for the data usage.

[0087] FIG. 5 illustrates an exemplary computer system (500) in which or with which embodiments of the present disclosure may be utilized. As shown in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), communication port(s) (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port for use with a modem- based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) (560) may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (500) connects. The main memory (530) may be random access memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) including, but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or basic input/output system (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution, which may be used to store information and/or instructions.

[0088] The bus (520) communicatively couples the processor (570) with the other memory, storage, and communication blocks. The bus (520) can be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), universal serial bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor (570) to the computer system (500).

[0089] Optionally, operator and administrative interfaces, e.g., a display, keyboard, and a cursor control device, may also be coupled to the bus (520) to support direct operator interaction with the computer system (500). Other operator and administrative interfaces may be provided through network connections connected through the communication port(s) (560). In no way should the aforementioned exemplary computer system (500) limit the scope of the present disclosure.

[0090] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter to be implemented merely as illustrative of the disclosure and not as limitation.

[0091] In an aspect, the present disclosure may be implemented within the communication network for provisioning the NSP-PCF. In an aspect, the present disclosure provides the system, and the method that enables the communication network to readily configure new slice without any manual intervention on PCF instances.

ADVANTAGES OF THE PRESENT DISCLOSURE [0092] The present disclosure enables the NSP operator to create, modify, or delete slice -related information in the AMF, SMF, UDM, NSSF, and PCF from a centralized point using the NSP portal.

[0093] The present disclosure enables the NSP operator to provision rules for the DNN and PCC. [0094] The present disclosure provides policy creation at the PCF by the

NSP operator.

[0095] The present disclosure enables a communication network to readily configure new slice without any manual intervention on PCF instances.

Claims

We Claim:

1. A method (400) for network service provider (NSP) policy control function

(PCF) provisioning in a communication network, the method (400) comprising: receiving (402), by a processing engine (208), at least one attach request from a user equipment (UE); authenticating (404), by the processing engine (208), the UE based on the received at least one attach request; retrieving (406), by the processing engine (208), at least one subscription profile of the UE; providing (408), by the processing engine (208), at least one network slice (106) related information based on the retrieved at least one subscription profile; providing (410), by the processing engine (208), a first set of rules for at least one data network name (DNN) to serve the UE; providing (412), by the processing engine (208), a second set of rules for at least one policy and charging control (PCC); and creating (414), by the processing engine (208), a set of policies at the PCF based on each of the first set of rules and the second set of rules.

2. The method (400) as claimed in claim 1, wherein the at least one network slice (106) related information comprises at least one virtualized network function (VNF) for providing an end-to-end network service to the UE.

3. The method (400) as claimed in claim 1, wherein the at least one attach request comprises information about a type of a service the UE has subscribed.

4. The method (400) as claimed in claim 3, wherein the information about the type of the service comprises an information about an application service identifier, an information about the at least one DNN to serve the UE, and an information about at least one network slice (106) to which the UE is previously attached.

5. The method (400) as claimed in claim 1, wherein the at least one subscription profile comprises an information about at least one network slice (106) allowed to the UE, and an information about at least one default network slice when the information about the type of service the UE desires to use is not included in the received attach request.

6. The method (400) as claimed in claim 1, wherein the first set of rules for at least one DNN comprises one or more rules for selecting appropriate data network based on the at least one subscription profile, one or more rules for managing network access and connectivity parameters for the UE, and one or more rules associated with quality of service (QoS) to ensure required performance for the UE.

7. The method (400) as claimed in claim 1, wherein the second set of rules for at least one PCC comprises one or more rules for data usage policies to manage amount of data the UE consumes, and one or more rules to determine billing and charging for the data usage.

8. A system (110) for network service provider (NSP) policy control function

(PCF) provisioning in a communication network, the system (110) comprising: a memory (204); and one or more processor(s) (202) coupled with the memory (204), configured to: receive at least one attach request from a user equipment (UE); authenticate the UE based on the received at least one attach request; retrieve at least one subscription profile of the UE; provide at least one network slice (106) related information based on the retrieved at least one subscription profile; provide a first set of rules for at least one data network name (DNN) to serve the UE; provide a second set of rules for at least one policy and charging control (PCC); and create a set of policies at the PCF based on each of the first set of rules and the second set of rules.

9. The system (110) as claimed in claim 8, wherein the at least one network slice

(106) related information comprises at least one virtualized network function (VNF) for providing an end-to-end network service to the UE.

10. The system (110) as claimed in claim 8, wherein the at least one attach request comprises information about a type of a service the UE has subscribed.

11. The system (110) as claimed in claim 10, wherein the information about the type of the service comprises an information about an application service identifier, an information about the at least one DNN to serve the UE, and an information about at least one network slice (106) to which the UE is previously attached.

12. The system (110) as claimed in claim 8, wherein the at least one subscription profile comprises an information about at least one network slice (106) allowed to the UE, and an information about at least one default network slice when the information about the type of service the UE has subscribed is not included in the received attach request.

13. The system (110) as claimed in claim 8, wherein the first set of rules for at least one DNN comprises one or more rules for selecting appropriate data network based on the at least one subscription profile, one or more rules for managing network access and connectivity parameters for the UE, and one or more rules associated with quality of service (QoS) to ensure required performance for the UE.

14. The system (110) as claimed in claim 8, wherein the second set of rules for at least one PCC comprises one or more rules for data usage policies to manage amount of data the UE consumes, and one or more rules to determine billing and charging for the data usage.

15. A user equipment (UE) communicatively coupled with at least one network slice (106) through an access and mobility management function (AMF), the coupling comprises steps of: receiving, by the at least one network slice (106), an attach request from the UE; sending an acknowledgment of the attach request to the UE; authenticating the UE based on the received attach request; retrieving at least one subscription profile of the UE from a unified data management (UDM) module; and transmitting at least one network slice (106) related information to the UE, wherein the at least one network slice (106) comprising a session management function (SMF), a network slicing selection function (NSSF), and a policy control function (PCF) configured to implement a first set of rules for data network name (DNN) and a second set of rules for policy and charging control (PCC) for NSP-PCF provisioning in a communication network.

16. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processor(s) (202), cause the one or more processors (202) to: receive at least one attach request from a user equipment (UE); authenticate the UE based on the received at least one attach request; retrieve at least one subscription profile of the UE; provide at least one network slice (106) related information based on the retrieved at least one subscription profile; provide a first set of rules for at least one data network name (DNN) to serve the UE; provide a second set of rules for at least one policy and charging control (PCC); and create a set of policies at the PCF based on each of the first set of rules and the second set of rules.