DESC:FORM 2
THE PATENTS ACT, 1970 (39 OF 1970)
&
THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)

SYSTEM AND METHOD FOR MANAGING QUALITY OF SERVICE PARAMETERS IN A COMMUNICATION NETWORK

Jio Platforms Limited, an Indian company, having registered address at Office -101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India

The following complete specification particularly describes the disclosure and the manner in which it is performed.
TECHNICAL FIELD

[0001] The embodiments of the present disclosure generally relate to the field of communication networks and systems. More particularly, the present disclosure relates to a system and a method for managing and validating Quality of Service parameters between various entities of a communication network.

BACKGROUND OF THE INVENTION

[0002] The subject matter disclosed in the background section should not be assumed or construed to be prior art merely due to its mention in the background section. Similarly, any problem statement mentioned in the background section or its association with the subject matter of the background section should not be assumed or construed to have been previously recognized in the prior art.

[0003] In a communication network, especially a 5th Generation (5G) communication network, control of policy and charging function plays a very critical role. Policy control provides transparency and control over the consumption of network resources of the communication network. Different network entities or modules of the communication network function together to support policy charging functions in the communication network. For management of network behavior, network operators utilize a Policy Control Function (PCF) module for governing policy rules in a control plane of the communication network and policy enforcement in a user plane of the communication network. The PCF module may govern policy control decisions by controlling the communication network regarding the service data flow detection, Quality of Service (QoS) flow, and flow-based charging towards a Session Management Function (SMF) module. As the QoS flow may vary for different user requirements of data transfer, control of Quality of Service (QoS) flow for policy control is necessary. Further, every service or application each with specific performance parameter requirements may require its own Application Function (AF) module. The AF module may reside in a control plane for establishing the QoS for subscribers to access a service or an application. The AF module may interact with policy charging function.

[0004] While establishing an AF session with a User Equipment (UE), a pre-defined QoS parameter may be used by the communication network at the PCF module. While requesting for establishment of the session, the AF module needs to include the pre-defined QoS parameter for use during the session. However, the pre-defined QoS parameter available at the PCF may not be synched with the pre-defined QoS parameter specified by the AF. This means that even if the pre-defined QoS parameter is sent by the AF to the PCF, there is no method or mechanism available to the AF to check if the pre-defined QoS parameter is indeed supported by PCF module. This may lead to a mismatch in the QoS and an error in provisioning the specified QoS to an end user.

[0005] Therefore, there lies a need for a technical solution that can overcome challenges and limitations associated with management and validation of the QoS parameters between various entities of the communication network.

SUMMARY

[0006] The following embodiments present a simplified summary in order to provide a basic understanding of some aspects of the disclosed invention. This summary is not an extensive overview, and it is not intended to identify key/critical elements or to delineate the scope thereof. Its sole purpose is to present some concepts in a simplified form as a prelude to the more detailed description that is presented later.

[0007] According to an embodiment, a method for managing a Quality of Service (QoS) parameter in a communication network is provided. The method includes receiving from a consumer NF, by a data processing Network Function (NF), a request to update the QoS parameter in a QoS reference associated with data flow in the communication network. The request includes QoS attribute(s) associated with the QoS parameter. Updating the QoS parameter includes either an addition, removal, or modification of the QoS parameter in the QoS reference. The method further includes determining, by the data processing NF, whether each QoS attribute matches with predefined attribute(s). Furthermore, the method includes authenticating, by the data processing NF, the request to update the QoS parameter in the QoS reference, in response to the determination that the QoS attribute(s) match with the predefined QoS attribute(s). Furthermore, the method includes generating, by the data processing NF, a tagged QoS parameter entry by associating marker tag(s) with the QoS parameter. Each of the marker tag(s) corresponds to one of the QoS attribute(s) of the QoS parameter. Furthermore, the method includes updating, by the data processing NF, the QoS reference stored in a database by updating the tagged QoS parameter entry in the QoS reference, based on the request. Furthermore, the method includes determining, by the data processing NF, whether the consumer NF and the data processing NF has subscribed to access information from the database. Moreover, the method includes receiving, by the data processing NF, a QoS reference update notification from the database in response to the determination that the consumer NF and the data processing NF have subscribed to access information from the database. Furthermore, the method includes transmitting, by the data processing NF, the QoS reference update notification to the consumer NF.

[0008] In some aspects of the present disclosure, the data processing NF is a Policy Control Function (PCF) or a User Defined Repository (UDR).

[0009] In some aspects of the present disclosure, the consumer NF includes an Application Function (AF), a Network Exposure Function (NEF), or a combination of both.

[0010] In some aspects of the present disclosure, the QoS attribute(s) include at least one of, a QoS value for the QoS parameter, an identifier for the QoS parameter, and information associated with generation of the QoS parameter.

[0011] In some aspects of the present disclosure, the identifier for the QoS parameter includes at least one of, an AF application identifier, a sponsor identifier, a slice, a customized AF identifier, or a combination thereof.

[0012] In some aspects of the present disclosure, the method further includes determining when the QoS attribute(s) mismatch with predefined attribute(s). Moreover, the method includes discarding the request to update the QoS parameter in the QoS reference in response to the mismatch.

[0013] In some aspects of the present disclosure, the method further includes comparing, by the data processing NF, each QoS attribute with each of the predefined attribute(s) to determine the match or mismatch between the QoS attribute and the predefined attribute(s).

[0014] In some aspects of the present disclosure, the method further includes determining when the consumer NF and the data processing NF have not subscribed to access the information from the database. Moreover, the method includes disabling the reception of the QoS reference update notification from the database, in response to the determination that the consumer NF and the data processing NF have not subscribed to access information from the database.

[0015] According to another embodiment, a system to manage Quality of Service (QoS) parameters in a communication network. The system includes a consumer Network Function (NF) and a data processing NF and communicatively coupled with the database. The data processing NF is configured to receive, from the consumer NF, a request to update a QoS parameter in a QoS reference associated with data flow in the communication network. The request comprises QoS attribute(s) associated with the QoS parameter. The data processing NF is further configured to determine whether the QoS attribute(s) match with predefined attribute(s). Furthermore, the data processing NF is configured to authenticate the request to update the QoS parameter in the QoS reference, in response to the determination that the QoS attribute(s) match with the predefined QoS attribute(s). Furthermore, the data processing NF is configured to generate a tagged QoS parameter entry by associating marker tag(s) with the QoS parameter. Each of the marker tag(s) corresponds to one of the QoS attribute(s). Furthermore, the data processing NF processor is configured to update the QoS reference stored in the database by updating the tagged QoS parameter entry in the QoS reference, based on the request. Furthermore, the data processing NF is configured to determine whether the consumer NF and the data processing NF has subscribed to access information from the database. Moreover, the data processing NF is configured to receive a QoS reference update notification from the database in response to the determination that the consumer NF and the data processing NF have subscribed to access information from the database and transmit the QoS reference update notification to the consumer NF.

BRIEF DESCRIPTION OF DRAWINGS

[0016] Various embodiments disclosed herein will become better understood from the following detailed description when read with the accompanying drawings. The accompanying drawings constitute a part of the present disclosure and illustrate certain non-limiting embodiments of inventive concepts. Further, components and elements shown in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. For the purpose of consistency and ease of understanding, similar components and elements are annotated by reference numerals in the exemplary drawings.

FIG. 1 presents an operational environment of a communication system to manage Quality of Service (QoS) parameters, in accordance with an exemplary aspect of the present disclosure.

FIG. 2 illustrates a block diagram depicting operational entities in the communication network, in accordance with an exemplary embodiment of the present disclosure.

FIG. 3 illustrates a block diagram depicting a data processing Network Function, in accordance with an exemplary embodiment of the present disclosure.

FIG. 4 illustrates a flowchart of a method for managing the Quality of Service (QoS) parameters in the communication network, in accordance with an embodiment of the present disclosure.

FIG. 5 presents an information-flow diagram that depicts instructions exchange between the operational entities of the communication network, in accordance with an embodiment of the present disclosure.

FIG. 6 presents another information-flow diagram that depicts instructions exchange between the operational entities of the communication network, in accordance with an embodiment of the present disclosure.

LIST OF REFERENCE NUMERALS

100 – System
101 – Core Network
103 – Nodes
105 – User Device
200 – Network Entities
204 – Radio Access Network
206 – Data Processing Network Functions
206-1 – Policy Control Function
206-2 – User Defined Repository
208 – Access and Mobility Function
210 – Section and Mobility Function
212-1 – Network Function
212-2 – Network Exposure Function
216 – Network Data Analytics Function
218 – Database
220 – User Plane Function
310 – Processor
320 – Memory
330 – Communication Interface

DETAILED DESCRIPTION OF THE INVENTION

[0017] Inventive concepts of the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which examples of one or more embodiments of inventive concepts are shown. Inventive concepts may, however, be embodied in different forms and should not be construed as limited to the embodiments set forth herein. Further, the one or more embodiments disclosed herein are provided to describe the inventive concept thoroughly and completely, and to fully convey the scope of each of the present inventive concepts to those skilled in the art. Furthermore, it should be noted that the embodiments disclosed herein are not mutually exclusive concepts. Accordingly, one or more components from one embodiment may be tacitly assumed to be present or used in any other embodiment.

[0018] The following description presents various embodiments of the present disclosure. The embodiments disclosed herein are presented as teaching examples and are not to be construed as limiting the scope of the present disclosure. The present disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary design and implementation illustrated and described herein, but may be modified, omitted, or expanded upon without departing from the scope of the present disclosure.

[0019] The following description contains specific information pertaining to embodiments in the present disclosure. The detailed description uses the phrases “in some embodiments” which may each refer to one or more or all of the same or different embodiments. The term “some” as used herein is defined as “one, or more than one, or all.” Accordingly, the terms “one,” “more than one,” “more than one, but not all” or “all” would all fall under the definition of “some.” In view of the same, the terms, for example, “in an embodiment” refers to one embodiment and the term, for example, “in one or more embodiments” refers to “at least one embodiment, or more than one embodiment, or all embodiments.”

[0020] The term “comprising,” when utilized, means “including, but not necessarily limited to;” it specifically indicates open-ended inclusion in the so-described one or more listed features, elements in a combination, unless otherwise stated with limiting language. Furthermore, to the extent that the terms “includes,” “has,” “have,” “contains,” and other similar words are used in either the detailed description, such terms are intended to be inclusive in a manner similar to the term “comprising.”

[0021] In the following description, for the purposes of explanation, various specific details are set forth 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.

[0022] The description provided herein discloses exemplary embodiments only and is not intended to limit the scope, applicability, or configuration of the present disclosure. Rather, the foregoing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing any of the exemplary embodiments. Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it may be understood by one of the ordinary skilled in the art that the embodiments disclosed herein may be practiced without these specific details.

[0023] 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 description, the singular forms "a", "an", and "the" include plural forms unless the context of the invention indicates otherwise.

[0024] The terminology and structure employed herein are for describing, teaching, and illuminating some embodiments and their specific features and elements and do not limit, restrict, or reduce the scope of the present disclosure. Accordingly, unless otherwise defined, all terms, and especially any technical and/or scientific terms, used herein may be taken to have the same meaning as commonly understood by one having ordinary skill in the art.

[0025] In the present disclosure, various embodiments are described using terms such as extensible radio access network (xRAN), and open-radio access network (O-RAN)) that are commonly used in communication standards (e.g., 3rd generation partnership project (3GPP), but these are merely examples for description. Various embodiments of the disclosure may also be easily modified and applied to other communication systems.

[0026] The present disclosure relates to a system and a method for managing Quality of Service (QoS) parameters between various entities in a communication network. In a communication network, a plurality of Protocol Data Unit (PDU) sessions may be established with a User Equipment (UE) for transferring data packets having different QoS requirements. Each PDU session of the plurality of PDU sessions may further be bound to an Application Function (AF) session. For accessing a different application service such as video streaming, voice and video calls, messaging, and social media over the UE, the communication network may assign a different AF module. The AF module may be trusted or non-trusted. A trusted AF may reside in a trusted data network and may interact directly with the NFs. The trusted AFs may include voice and video calls, SMS/messaging, and XR applications. A non-trusted AF may reside externally in an untrusted data network and use a Network Exposure Function for communication with the core network entities. The non-trusted AFs may include mobile or internet browsing, and social media streaming.

[0027] Flow of data packets in an AF session of any of the trusted AF and the non-trusted AF may be mapped to a different QoS flow. Each QoS flow may include QoS parameters and QoS characteristics. The QoS parameters may include a pre-defined reference string (hereinafter referred to as a QoS reference). The QoS reference may be a string name that defines values of the QoS attributes. The QoS attributes may include a 5G Quality of Service Identifier (5QI), a maximum Uplink (UL) bitrate, a maximum Downlink (DL) bitrate, a Guaranteed Bit Rate (GBR) UL QoS flow, a GBR DL QoS flow, Allocation and Retention Priority (ARP), a priority level, an averaging window, Maximum Data Burst Volume (MDBV), Packet loss rate, a Packet Delay Budget (PDB), and a Packet Error Rate (PER).

[0028] The trusted AF and the non-trusted AF may interact with a Policy Control Function (PCF) module during a session and expect a specific QoS flow to be applied during the session. In one or more embodiments, the present disclosure provides a system and a method for validating a QoS reference parameter at the PCF by both the trusted AF modules and the non-trusted AF modules.

[0029] The following description provides specific details of certain aspects of the disclosure illustrated in the drawings to provide a thorough understanding of those aspects. It should be recognized, however, that the present disclosure can be reflected in additional aspects and the disclosure may be practiced without some of the details in the following description.

[0030] Embodiments of the present disclosure will be described below in detail with reference to the accompanying drawings. FIG. 1 through FIG. 6, discussed below, and the embodiments used to describe the principles of the present disclosure are by way of illustration only and should not be construed in any way to limit the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure may be implemented in any suitably arranged system or device.

[0031] Various aspects including the example aspects are now described more fully with reference to the accompanying drawings, in which the various aspects of the disclosure are shown. The disclosure may, however, be embodied in different forms and should not be construed as limited to the aspects set forth herein. Rather, these aspects are provided so that this disclosure is thorough and complete, and fully conveys the scope of the disclosure to those skilled in the art. In the drawings, the sizes of components may be exaggerated for clarity.

[0032] Various aspects of the present disclosure provide a system and a method for managing QoS parameters defined across various network entities in the communication network. In some aspects of the present disclosure, the system and the method relate to validating the QoS parameters to be used by the various network entities of the communication network. In some other aspects of the present disclosure, the system and the method relate to providing synchronization between various network entities regarding use of a pre-defined QoS parameter during a session established in the communication network. In yet other aspects of the present disclosure, the system and the method relate to avoiding an error due to mismatch of the pre-defined QoS reference used by different network entities. In yet other aspects of the present disclosure, the system and the method relate to reducing manual intervention involved at a level of network entities for validating the pre-defined QoS parameter.

[0033] FIG. 1 presents an operational environment of a communication system 100 to manage the QoS parameters, in accordance with an exemplary aspect of the present disclosure. The system 100 includes a core network 101. The core network 101 may be coupled with a plurality of nodes including Node 103-1 through Node 103-N and is configured to facilitate a secured communication among the plurality of nodes (collectively referred to as the “Nodes 103”, and individually referred to as the “Node 103”, hereinafter).

[0034] In an embodiment, each node may be coupled with user device(s) 105 (presented by way of first through Nth user device 105-1 to 105-N) (collectively referred to as the “user devices 105”, and individually referred to as the “user device 105”, hereinafter). For example, the core network 101 may establish a secured communication between the user device 105-2 and the user device 105-N with equal effectiveness, where the user device 105- 2 is coupled with the Node 103-1 and the user device 105-N is coupled with the Node 103-N.

[0035] In one embodiment, the core network 101 may establish a secured communication between the user devices 105 associated with the plurality of nodes 103. In another embodiment, the core network 101 may establish a secured communication between the user devices 105 associated with the same node 103. For example, the core network 101 may effectively establish a secured communication between the user device 105-1 and the user device 105-2, where the user device 105-1 and the user device 105-2 both are coupled with the Node 103-1.

[0036] In an exemplary embodiment, the core network 101 (hereinafter interchangeably referred to and designate as ‘network 101’) may be configured as an application server and may be communicably operational or may be integrated with a user device 105 via a network coupled with a server. In another exemplary embodiment, the user device 105 may be a wireless device. The wireless device may be a mobile device that may include, for example, cellular telephone, such as a feature phone or smartphone and other devices. The user device 105 may not be limited to the above-mentioned devices but may include any type of device capable of providing wireless communication, such as a cellular phone, a tablet computer, a Personal Digital Assistant (PDA), a Personal Computer (PC), a laptop computer, a media center, a workstation, and other such devices. In some aspects of the present disclosure, the core network 101 may include a variety of operational entities (as presented later in FIG. 2) that enable the system 100 to manage the QoS parameters.

[0037] The network 101 may pertain to 5G service-based architecture and may be configured to interconnect distinct networks associated with the architecture. Therefore, the core network 101 may provide a path for the exchange of information between one or more of the networks, and corresponding subnetworks. Further, as the backbone, the core network may tie together diverse networks, say Local Area Network (LAN), Wide Area Network (WAN), Metropolitan Area Network (MAN), etc. which may be there within the same building, in different buildings, in a campus environment, or remotely located over wide areas. The system may also boost the network performance by continuously coordinating with other network functions.

[0038] In an example embodiment, the network 101 may pertain to at least one of a wireless network, a wired network, or a combination thereof. The network may be implemented as one of the different types of networks, such as Intranet, LAN, WAN, Internet, and the like. Further, the network may either be a dedicated network or a shared network. The shared network may represent an association of the different types of networks that may use variety of protocols, for example, Hypertext Transfer Protocol (HTTP), Transmission Control Protocol/Internet Protocol (TCP/IP), Wireless Application Protocol (WAP), Automatic Repeat Request (ARQ), and the like. In an embodiment, the network may pertain to, for example a 5G network that may be facilitated through, for example, Global System for Mobile communication (GSM) network; a Universal Terrestrial Radio Access Network (UTRAN), an Enhanced Data rates for GSM Evolution (EDGE) Radio Access Network (GERAN), an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a Wi-Fi or other LAN access network, or a satellite or terrestrial wide-area access network such as a Worldwide Interoperability for Microwave Access (WiMAX) network. Various other types of communication network or service may be possible.

[0039] In an example, the network 101 may utilize different sort of air interface, such as a Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), or Frequency Division Multiple Access (FDMA), air interface and other implementation. In an example embodiment, the wire-line user device may use wired access networks, exclusively or in combination with wireless access networks, for example, including Plain Old Telephone Service (POTS), Public Switched Telephone Network (PSTN), Asynchronous Transfer Mode (ATM), and other network technologies configured to transport Internet Protocol (IP) packets.

[0040] FIG. 2 illustrates a block diagram depicting operational network entities 200 (hereinafter interchangeably referred to as ‘operational entities 200’ or ‘network entities 200’) in the network 101, in accordance with an exemplary embodiment of the present disclosure. The embodiments of the operational entities 200 in the network 101 shown in FIG. 2 are for illustration only. Other embodiments of the operational entities 200 in the network 101 may be used without departing from the scope of this disclosure.

[0041] The operational entities 200 may be coupled to the user device (UD) 105. Examples of the user device 105 may include “mobile station”, “subscriber station”, “remote terminal”, “wireless terminal”, “receive point”, “end user device”, and the like. The operational entities may include a Radio Access Network (RAN) 204. Typically, the RAN 204 may be a network infrastructure that provides wireless access to one or more terminals. The RAN 204 may have wireless communication coverage defined for a predetermined geographic area based on the distance over which a signal may be transmitted. Examples of the RAN 204 may include, but are not limited to a base station, an access point (AP), an evolved NodeB (eNB), a 5th Generation (5G) node, a next generation NodeB (gNB), a wireless point, and a transmission/reception point (TRP), a Radio Access Network (RAN).

[0042] The network entities 200 may further include data processing Network Functions (NF) 206. More particularly, the data processing NF 206 may include a Policy Control Function (PCF) 206-1 and a User Defined Repository (UDR) 206-2. The data processing NF 206 may be configured to perform various data processing tasks for managing the QoS parameters, as discussed in detail in FIG. 3. The UDR 206-2 may be a database that stores subscription data, application data, policy data, and data related to QoS flow from the NF consumers (such as a Network Exposure Function (NEF) 212-2, Access Function (AF) 212-1, and the PCF 206-1). The UDR 206-2 may also notifies to the NF consumers of changes in the subscription data. The PCF 206-1 may retrieve the subscription data, application data, policy data, and data related to QoS flow from the NF consumers from the UDR 206-2. In some aspects of the present disclosure, the network entities 200 may further include a database 218 configured to store data associated with the QoS parameters in the form of QoS references. In some aspects of the present disclosure, the database 218 may be shared by the UDR 206-2.

[0043] The network entities 200 may further include consumer NF 212. More particularly, the consumer NF 212 may include the Application Function (AF) module 212-1 and the Network Exposure Function (NEF) module 212-2. The NEF 212-2 may expose third party applications to access services and resources of the network 101. The NEF 212-2 may act as a security layer when the third-party application tries to connect with the network entities. The AF 212-1 may be configured to perform operations for accessing the NEF 212-2 to retrieve resources, interaction with the PCF 206-1 for policy control, applications traffic routing, exposing services to the end users. The AF 212-1 may expose application layer for interacting with resources of the network 101. The AF 212-1 may include multiple trusted AFs and multiple non-trusted AFs.

[0044] Moreover, the network entities 200 may further include an Access and Mobility Management Function (AMF) 208, a Session Management Function (SMF) 210, a Network Data Analytics Function (NWDAF) 216, a database 218, and a User Plane Function (UPF) 220.

[0045] The SMF 210 may be configured to perform operations for service and session management with the UD 105, IP address allocation and management for the UD 105, user plane selection and routing of packets, QoS and policy enforcement for the control plane. The AMF 208 may be configured to perform operations for mobility management, registration management, connection management, and authentication. Based on a service requested by the UD 105, the AMF 208 may select a respective SMF module 210 for managing a user session context.

[0046] The NWDAF 216 may be used for data collection and analytics for computing resources in the network 101. The NWDAF module 216 may provide network slice specific data analytics to the PCF 206-1 that may be utilized for making policy decisions by the PCF 206-1 and for making selection of slice.

[0047] The UPF 220 may maintain an end-to-end user plane connectivity during a Protocol Data Unit (PDU) session between the UD 105 and the RAN 204 or a data network. The UPF 220 may also perform packet routing and forwarding, packet inspection, policy enforcement and handling the QoS flow. The UPF 220 may forward packets that are transmitted and received by the UD 105 to the network 101.The network entities 200 may be configured to communicate with each other and with the UD 105 and RAN 204 using communication interfaces.

[0048] For initiating establishment of a session with the UD 105, the AF 212-1 may send a request to the PCF 206-1 for establishing the session with the UD 302. The request may be sent to the PCF 206-1 directly or via NEF 212-2. The request may include the QoS reference for application of a specific QoS in the session. At the PCF 206-1, the values of the QoS attributes are pre-defined in the database 218 accessible by the PCF 206-1. To initiate establishment of the session with the specific QoS used by the AF 212-1 and/or the NEF 212-2, the PCF 206 may be configured to map the QoS reference with the values of the QoS attributes pre-defined at the PCF 206-1.

[0049] In one embodiment, when a session request is sent by the trusted AF along with a specific QoS reference to the PCF 206-1, the trusted AF may validate the use of the specific QoS reference by the PCF 206-1. To validate the use of the specific QoS reference, the trusted AF 212-1 and/or the NEF 212-2 may initiate a request to the PCF 206-1 to create a new QoS parameter or modify or delete an existing QoS parameter. Along with the request, the trusted AF 212-1 and/or the NEF 212-2 may send data including an AF application identifier (AF App ID), a sponsor identifier (SP ID), a slice, and a customized AF identifier (AF ID), to enable the PCF 206-2 to authorize the request. Upon authorization, the new QoS parameter may be created or the existing QoS parameter may be deleted or updated in the database 218.

[0050] The database 218 may be one of a central database, a local database, and the UDR 206-2. The trusted AF 212-1 and/or the NEF212-2 and/or the PCF 206-1 may be a part of a subscribe and notification model for checking for specified QoS reference. The trusted AF 212-2 and/or the NEF 212-2 and/or the PCF 206-1 may send a service operation to the database 218 for creating a subscription for notification on modifications in the QoS reference. The database 218 may send notifications towards the PCF 206-1 and/or the trusted AF 212-1 and/or the NEF 212-2 that have subscribed for receiving notification regarding modifications in the QoS reference. The modification may correspond to creation of the new QoS reference, deletion of the existing QoS reference or update in definition of the existing QoS reference. The trusted AF 212-1 and/or the NEF212-2 may then fetch the new QoS parameter or the modified QoS parameter from the database 218 via the PCF 206-1 for validating the specified QoS parameter.

[0051] Each of the network entities 200 (cumulatively referred to as ‘the servers 200’) may be a network of computers, a software framework, or a combination thereof, that may provide a generalized approach to create a data processing and storage server implementation. Examples of the servers 200 may include, but are not limited to, personal computers, laptops, mini-computers, mainframe computers, any non-transient and tangible machine that can execute a machine-readable code, cloud-based servers, distributed server networks, or a network of computer systems. The servers 200 may be realized through various web-based technologies such as, but not limited to, a Java web-framework, a .NET framework, a personal home page (PHP) framework, or any web-application framework. In various aspects of the present disclosure, the servers 200 may be configured to perform data processing and/or storage operations to manage the QoS parameters in the network 101.

[0052] FIG. 3 illustrates a block diagram depicting the data processing Network Function 206, in accordance with an exemplary embodiment of the present disclosure.

[0053] The data processing NF 206 may be a network of computers, a software framework, or a combination thereof, that may provide a generalized approach to create a server implementation. Examples of the data processing NF 206 may include, but are not limited to, personal computers, laptops, mini-computers, mainframe computers, any non-transient and tangible machine that can execute a machine-readable code, cloud-based servers, distributed server networks, or a network of computer systems. The data processing NF 206 may be realized through various web-based technologies such as, but not limited to, a Java web-framework, a .NET framework, a personal home page (PHP) framework, or any web-application framework. In various aspects of the present disclosure, the data processing NF 206 may be configured to perform data processing and/or storage operations to enable management of QoS parameters in the network 101. In some aspects of the present disclosure, the data processing NF 206 may be the PCF 206-1 or the UDR 206-2. In some other aspects of the present disclosure, the data processing NF 206 may have multiple PCF 206-1 (presented later in FIG 5 and FIG. 6 as first PCF 206-1a and second PCF 206-1b).

[0054] The data processing NF 206 may include data processing circuitry 310 (hereinafter interchangeably referred to and designated as ‘processor 310’), a communication interface 320, and a memory 330. The processor 310 may be configured with suitable logic, instructions, circuitry, interfaces, and/or codes for executing operations of various operations performed by the data processing NF 206 for computations and data processing related to management of QoS parameters in the network 101. Examples of the processor 310 may include, but are not limited to, an Application Specific Integrated Chip (ASIC) processor, a RISC processor, a CISC processor, a Field Programmable Gate Array (FPGA), and the like.

[0055] Particularly, the processor 310 may be configured to receive a request to update a QoS parameter in a QoS reference from the consumer NF 212. In some aspects of the present disclosure, the consumer NF may be the AF 212-1, the NEF 212-2, or a combination thereof. The request includes QoS attribute(s) associated with the QoS parameter. In some aspects of the present disclosure, the QoS attribute(s) may correspond to, but not limited to, a QoS value for the QoS parameter, an identifier for the QoS parameter, and information associated with generation of the QoS parameter. The information associated with the generation of the QoS parameter may include data associated with the consumer NF 212 responsible for the generation of the QoS parameter, and temporal data (such as data and time) for generation of the QoS parameter. In some aspects of the present disclosure, the identifier for the QoS parameter includes at least one of, an AF application identifier, a sponsor identifier, a slice, a customized AF identifier, or a combination thereof.

[0056] The processor 310 may further be configured to determine whether the QoS attribute(s) match with predefined attribute(s). In some aspects of the present disclosure, the predefined attributes may include a predefined configuration of QoS attribute(s) such as, but not limited to a predefined value of 5G Quality of Service Identifier (5QI), a predefined value of maximum Uplink (UL) bitrate, a predefined value of maximum Downlink (DL) bitrate, a predefined value of Guaranteed Bit Rate (GBR) UL QoS flow, a predefined value of GBR DL QoS flow, a predefined Allocation and Retention Priority (ARP), a predefined priority level, a predefined averaging window, a predefined value of Maximum Data Burst Volume (MDBV), a predefined value of Packet loss rate, a predefined Packet Delay Budget (PDB), and a predefined Packet Error Rate (PER). The predefined attribute(s) may be stored either in the memory 330 or in the database 218. The processor 310 may generate a data fetch trigger to retrieve the predefined attribute(s). Moreover, the processor 310 may compare the QoS parameters with the predefined QoS parameters to determine a match or mismatch. In an exemplary scenario, when the processor determines a mismatch, the processor 310 may discard the request.
[0057] Furthermore, the processor 310 may be configured to authenticate the request to update the QoS parameter in the QoS reference, in response to the determination that the QoS attribute(s) match with the predefined QoS attribute(s). Furthermore, the processor 310 may be configured to generate a tagged QoS parameter entry by associating marker tag(s) with the QoS parameter, where each marker tag corresponds to one of the QoS attribute(s). Preferably, the tagged QoS parameter entry may be a data entry comprising multiple data fields. Each data field may be indicative of a QoS parameter, and a value of each data field may represent the value of the QoS parameter. Moreover, each value may be tagged with an identifier (i.e., a marker tag) of the QoS parameter in the tagged QoS parameter entry. The processor 310 may be configured to update the QoS reference stored in the database 218 by updating the tagged QoS parameter entry in the QoS reference, based on the request. Preferably, when the request to update the QoS parameter(s) in the QoS reference is authenticated, the processor 310 may identify data field(s) in the tagged QoS parameter entry, corresponding to the QoS parameter(s) for update using the marker tag(s). Moreover, the processor 310 may update the data field(s) with marker tag(s) corresponding to the QoS parameter(s) needed to be updated based on the request. Furthermore, the processor 310 may be configured to determine whether the consumer NF 212 and the data processing NF 206 have subscribed to access information from the database 218. The processor 310 may be configured to receive a QoS reference update notification from the database 218 in response to the determination that the consumer NF and the data processing NF have subscribed to access information from the database 218 and transmit the QoS reference update notification to the consumer NF 212. The processor 310 may further be configured to disable the reception of the QoS reference update notification from the database 218, in response to a determination that the consumer NF 212 and the data processing NF 206 have subscribed to access information from the database 218.
[0058] The communication interface 320 may be configured to enable the data processing NF 206 to communicate with various other entities of the network 101. Examples of the communication interface 320 may include, but are not limited to, a MODEM, a network interface such as an Ethernet card, a communication port, and/or a Personal Computer Memory Card International Association (PCMCIA) slot and card, an antenna, a radio frequency (RF) transceiver, amplifier(s), a tuner, oscillator(s), a digital signal processor, a coder-decoder (CODEC) chipset, a Subscriber Identity Module (SIM) card, and a local buffer circuit. It will be apparent to a person of ordinary skill in the art that the communication interface 320 may include any device and/or apparatus capable of providing wireless or wired communications between the data processing NF 206 and various other entities of the network 101.

[0059] The memory 330 may be configured to store the logic, instructions, circuitry, interfaces, and/or codes of the processor 310 for executing various operations of the data processing NF 206. Aspects of the present disclosure are intended to include and/or otherwise cover any type of the data associated with the data processing NF 206, without deviating from the scope of the present disclosure. Examples of the memory 330 may include but are not limited to, a ROM, a RAM, a flash memory, a removable storage drive, a HDD, a solid-state memory, a magnetic storage drive, a PROM, an EPROM, and/or an EEPROM.

[0060] According to an embodiment of the present disclosure, the instructions the memory 330 may be configured to store computer program instructions corresponding to the operation(s) performed by various engines in the processor 310. In an embodiment of the present disclosure, the memory 330 may be configured as a non-transitory storage medium. Examples of the memory 330 configured as the non-transitory storage medium includes hard drives, solid-state drives, flash drives, Compact Disk (CD), Digital Video Disk (DVD), and the like. Aspects of the present disclosure are intended to include or otherwise cover any type of non-transitory storage medium as the memory 330, without deviating from the scope of the present disclosure. As will be appreciated, any such computer program instructions stored in the memory 330 may be executed by the processor 310, including without limitation a general-purpose computer or special purpose computer, or other programmable processing apparatus to produce a machine, such that the computer program instructions which execute on the computer processor(s) or other programmable processing apparatus create means for implementing the function(s) specified.

[0061] FIG. 4 illustrates a flowchart of a method 400 for managing the Quality of Service (QoS) parameters in the network 101, in accordance with an embodiment of the present disclosure.

[0062] At block 402, the data processing NF 206 may receive the request to update a QoS parameter in a QoS reference from the consumer NF 212. In some aspects of the present disclosure, the consumer NF may be the AF 212-1, the NEF 212-2, or a combination thereof. The request includes QoS attribute(s) associated with the QoS parameter. Particularly, the request may correspond to addition, removal, or modification of the QoS reference in the database 218 based on the QoS parameter and a type of the request determined through an instruction contained in the request.

[0063] At block 404, the data processing NF 206 may retrieve the QoS attributes from the QoS parameter and compare the QoS attributes with the predefined QoS attributes. In some aspects of the present disclosure, the QoS attribute(s) may correspond to, but not limited to, the QoS value for the QoS parameter, the identifier for the QoS parameter, and the information associated with generation of the QoS parameter. The information associated with the generation of the QoS parameter may include data associated with the consumer NF 212 responsible for the generation of the QoS parameter, and the temporal for generation of the QoS parameter. In some aspects of the present disclosure, the identifier for the QoS parameter includes at least one of, the AF application identifier, the sponsor identifier, the slice, the customized AF identifier, or a combination thereof.

[0064] At block 406, the data processing NF 206 may determine whether the QoS attribute(s) match with predefined attribute(s). When the data processing NF 206 determines a mismatch between the QoS attribute(s) and the predefined attribute(s), the method 400 proceeds to block 408. Else when the data processing NF 206 determines a match between the QoS attribute(s) and the predefined attribute(s), the method 400 proceeds to block 410.

[0065] At block 408, the data processing NF 206 may discard the request and halts the method 400 for updating the QoS reference in the database 218.

[0066] At block 410, the data processing NF 206 may authenticate the request to update the QoS parameter in the QoS reference.

[0067] At block 412, the data processing NF 206 may generate a tagged QoS parameter entry by associating marker tag(s) with the QoS parameter, where each marker tag corresponds to one of the QoS attribute(s).

[0068] At block 414, the data processing NF 206 may update the QoS reference stored in the database 218 by updating the tagged QoS parameter entry in the QoS reference, based on the request (i.e., addition, removal, or modification of the QoS parameter in the QoS reference).

[0069] At block 416, the data processing NF 206 may determine whether the consumer NF 212 and the data processing NF 206 have subscribed to access information from the database 218. When the data processing NF 206 determines that the consumer NF 212 and the data processing NF 206 have not subscribed to access the information from the database 218, the method proceeds to block 418. Else when the data processing NF 206 determines that the consumer NF 212 and the data processing NF 206 have subscribed to access the information from the database 218, the method proceeds to block 420.

[0070] At block 418, the data processing NF 206 may disable the reception of the QoS reference update notification from the database 218.

[0071] At block 420, the data processing NF 206 may receive the QoS reference update notification from the database 218.
[0072] At block 422, the data processing NF 206 may transmit the QoS reference update notification to the consumer NF 212 for validation of the QoS parameter throughout the network entities 200.

[0073] FIG. 5 presents an information-flow diagram 500 that depicts instructions exchange between the operational entities of the network 101, in accordance with an exemplary embodiment of the present disclosure. The instruction exchange is specific to a case when the data processing NF 206 is the PCF 206-1. The information flow diagram 500 includes a series of operations steps indicated by instances 502 through 514.

[0074] At instance 502, the consumer NF 212 (e.g., AF 212-1 and/or NEF 212-2) may initiate the request for the data processing NF 206 (e.g., the PCF 206-1) for performing an at least one of creation of a QoS reference, updating a QoS reference, and deleting a QoS reference in a QoS parameter. The request may be initiated by invoking “Npcf_PolicyAuthorization_qosRefCreate/update/delete” service operation.

[0075] In a first scenario, the consumer NF 212 may request for creating a new QoS parameter at a first PCF 206-1(a) (hereinafter interchangeably referred to as ‘PCF-1 206-1a’) by invoking “Npcf_PolicyAthorization_qosRefCreate” service operation. The new QoS parameter may include a string value of the QoS reference, corresponding values of the QoS attribute(s) and data such as the AF application identifier, the sponsor identifier, the slice, and the customized AF identifier. The new QoS parameter may further include the string value of the QoS reference and the corresponding values of the QoS attributes. For creating the new QoS parameter, the PCF-1 206-1(a) may utilize the string value of the QoS reference and the corresponding values of the QoS attributes. In a scenario, for optional data in the new QoS parameters not included by the trusted consumer NF 212, the PCF-1 206-1(a) may use default configured values of the optional data. Upon authorization of the QoS reference creation request, the PCF-1 206-1(a) may create the new QoS reference including markers indicating information of generation of the QoS parameter or the QoS reference (for example, information of the consumer NF 212 that generated the QoS parameter, and a temporal value depicting date and time of generation of the QoS parameter). The new QoS reference may include the string value of the QoS reference, the corresponding values of the QoS attribute(s) along with default values of other data selected by the PCF-1 206-1(a). Similarly, the PCF-1 206-1(a) may authorize the request for updating and deletion of existing QoS reference.

[0076] In a second scenario, the trusted consumer NF 212 may initiate a request for deleting a specific existing QoS parameter at the PCF-1 206-1(a) by invoking “Npcf_PolicyAthorization_qosRefDelete” service operation. The trusted consumer NF 212 may send name of a specific QoS reference (or parameters) to be deleted along with attribute(s) of the QoS parameter to be deleted. The PCF-1 206-1(a) may authorize the request for deleting the specified QoS parameter. Upon authorization, the PCF-1 206-1(a) may check the definition of the QoS reference in the QoS parameter and an associated set of identifiers for identifying the trusted consumer NF 212 that are using the same QoS reference. The associated set of identifiers may be an array indicating other AFs, application, or sponsors using the same QoS reference. Upon identifying the other consumer NF 212 using the same QoS reference, the PCF-1 206-1(a) may remove the QoS parameter from the database 218 (or the UDR 206-2). However, the PCF-1 206-1(a) may continue to maintain the definition of the specified QoS reference in the specified QoS parameter. In another scenario, when the PCF-1 206-1(a) discovers that the specified QoS reference is being uniquely used by the trusted consumer NF 212, the PCF-1 206-1(a) may remove the definition of the specified QoS reference.

[0077] In yet another scenario, the trusted consumer NF 212 may initiate a request for updating (or modifying) a specific existing QoS parameter at the PCF-1 206-1(a) by invoking “Npcf_PolicyAthorization_qosRefUpdate” service operation. The trusted consumer NF 212 may send name of a specific existing QoS reference to be updated along with modified data (such as the AF application identifier, the sponsor identifier, the slice, and the customized AF identifier) to the PCF-1 206-1(a). Based on the received data, the PCF-1 206-1(a) may authorize the request for updating the specified QoS parameter. Once authorized, the PCF-1 206-1(a) may check whether the modified data belongs to the trusted consumer NF 212 making the request for updating the specified QoS parameter. In a scenario, when the PCF-1 206-1(a) determines that the modified data belongs to the trusted consumer NF 212, the PCF-1 206-1(a) may then proceed to update the definition of the QoS reference in the specified QoS parameter.

[0078] At instance 504, for completion of the request for updating and deleting of the specified existing QoS parameter or creating the new QoS parameter, the PCF-1 206-1(a) may store the new QoS parameter or modify the specified existing QoS parameter in the database 218 (or the UDR 206-2) using a data storage request. The data storage request may be initiated by invoking “Nudr_DataRepository” service operation.

[0079] In an embodiment, the PCF-1 206-1(a) may invoke “Nudr_DataRepository_qosRefCreate” service operation for creation of the new QoS parameter in the UDR 206-2. In another embodiment, the PCF-1 206-1(a) may invoke “Nudr_DataRepository_qosRefUpdate” service operation for updating the QoS reference in the specified existing QoS parameter in the UDR 206-2. In yet another embodiment, the PCF-1 206-1(a) may invoke “Nudr_DataRepository_qosRefDelete” service operation for deleting the QoS reference in the specified existing QoS parameter in the UDR 206-2.

[0080] In an exemplary scenario, at instance 502, when the PCF-1 206-1(a) fails to perform the authorization or the QoS reference to be updated or deleted is already in use, then the PCF-1 206-1(a) may not send the data storage request towards the UDR 206-2.

[0081] At instance 506, the PCF-1 206-1(a) may communicate a response towards the trusted consumer NF 212 regarding successful creation, deletion or update in the QoS reference definitions. The response may be sent by invoking a “Npcf_PolicyAthorization_qosRefCreate/Update/Delete_Response” service operation. The PCF-1 206-1(a) may also send a negative response towards the trusted consumer NF 212 indicating an error in authorization of the request for creation, updating or deletion of the QoS reference.

[0082] At instance 508, a second PCF 206-1(b) (hereinafter interchangeably referred to as ‘PCF-2 206-1(b)’) and/or the trusted consumer NF 212 may invoke a subscribe request for creating a subscription for receiving the modifications in the QoS reference definition in the QoS parameter due to the request for creation, deletion and updating the QoS parameter. A “Nudr_DataRepository_qosRefSubscribe” service operation may be sent by the PCF-2 206-1(b) and/or consumer NF 212 to the UDR 206-2. The subscription may include a Network Function type of the PCF-2 206-1(b) along with other conditions such as the PLMN ID, slice, and a notification Uniform Resource Locator (URL) for indicating to the UDR 206-2 that all modifications in the QoS reference and the QoS parameters for the specified conditions need to be notified. The UDR 206-2 may respond with a subscription marker including a validity time and a subscription ID. The subscription marker may be used for providing an update on subscription services, notification correlation, and unsubscribe services.

[0083] For the trusted consumer NF 212 to subscribe for update notification(s), the trusted consumer NF 212 may send a subscription request including a type of NF, an AFID, an Application ID, and a Sponsor ID along with other parameters that limit the subscription for specific subset of QoS reference in the QoS parameter. For changing the subscription condition(s) and/or updating the validity of the subscription, the PCF-2 206-1(b) and/or the trusted consumer NF 212 may use a patch method by invoking the subscribe request and the subscription ID. The PCF-2 206-1(b) and/or the trusted consumer NF 212 may delete the subscription created in the UDR 206-2 for modifications in the QoS parameter by invoking a subscription deletion request using a “Nudr_DataRepository_qosRefUnsubscribe” service operation.

[0084] At instance 510, the UDR 206-2 may send notifications towards the PCF-2 206-1(b) and/or the trusted consumer NF 212 that have subscribed for notification regarding modifications in the QoS reference. The modification may correspond to creation of the new QoS reference, deletion of the existing QoS reference or update in definition of the existing QoS reference. Through the notification, the PCF 206-1 and the consumer NF 212 are notified for modifications in the new QoS reference definition.

[0085] At instance 512, the trusted consumer NF 212 may initiate a fetch request to the PCF-1 206-1(a) for authorization, validating and fetching the new QoS parameter or the modified existing specified QoS parameter. The fetch request may be initiated by invoking a “Npcf_DataRepository_qosRefGet” service operation. In the fetch request, the trusted consumer NF 212 may include the application identifier, the sponsor identifier, the slice, and the AF identifier. The PCF-1 206-1(a) may further authorize the fetch request based on the application identifier, the sponsor identifier, the slice, and/or the AF identifier.

[0086] At instance 514, in response to the fetch request, the PCF-1 206-1(a) may fetch the new QoS parameter or the modified specified existing QoS parameter from the UDR 206-2. The UDR 206-2 through the PCF-1 206-1(a) may return a response to the trusted consumer NF 212 including the new QoS parameter and/or the modified specified existing QoS parameter. The response may be sent by the PCF-1 206-1(a) by invoking a “Npcf_DataRepository_qosRefGet_Response” service operation. In another scenario, the PCF-1 206-1(a) may also send a negative response towards the trusted consumer NF 212 indicating an error in authorization of the request or when the new QoS parameter or the modified specified existing QoS parameter is not found in the UDR 206-2.

In another embodiment, when a session request is sent by the trusted/non-trusted consumer NF 212 along with a specific QoS reference to the PCF 206-1, the trusted/non-trusted consumer NF 212 may validate the use of the specific QoS reference by the PCF 206-1. To validate the use of the specific QoS reference, the trusted/non-trusted consumer NF 212 may initiate a request to the database 218 (or the UDR 206-2) to create a new QoS parameter or modify or delete an existing QoS parameter. The database 218 may be one of a central database, a local database, a Subscriber Repository (SPR), and the UDR 206-2. Along with the request, the trusted/non-trusted consumer NF 212 may send data including an AF application identifier, a sponsor identifier, a slice, and a customized AF identifier, to enable the UDR 206-2 to authorize the request. Upon authorization, the new QoS parameter may be created or the existing QoS parameter may be deleted or updated in the UDR 206-2. The trusted/non-trusted consumer NF 212 and/or the PCF 206-1 may be a part of a subscribe and notification model for checking for specified QoS reference with the UDR 206-2. The PCF 206-2 may send a service operation to the UDR 206-2 for creating a subscription for receiving notification on modifications in the QoS reference. The UDR 206-2 may send notifications towards the PCF 206-1 that have subscribed for notification regarding modifications in the QoS reference. The modification may correspond to creation of the new QoS reference, deletion of the existing QoS reference or update in definition of the existing QoS reference. The consumer NF 212 may then fetch the new QoS parameter or the modified QoS parameter from the UDR 206-2 via the PCF 206-1. It must be noted that the information flow diagram 500 indicates two PCFs 206-1 (i.e., the first PCF 206-1(a) and the second PCF 206-1(b) such that the operation(s) performed by the PCF 206-1 can be segregated in parts and performed by two similar functional units to enhance throughput and performance efficiency. However, it will be apparent to a person skilled in the art that the presence of two PCFs is particular to an embodiment as presented in FIG. 5 and must not be considered as a limitation of the present disclosure. In some other embodiments, the functionality, as presented through FIG. 5, may be derived using a single PCF 206-1, without deviating from the scope of the present disclosure.
[0087] FIG. 6 presents another information-flow diagram 600 that depicts instructions exchange between the operational entities of the network 101, in accordance with an exemplary embodiment of the present disclosure. The instruction exchange is specific to a case when the data processing NF 206 is the UDR 206-2. The information flow diagram 600 includes a series of operations steps indicated by instances 602 through 616.

[0088] At instance 602, the consumer NF 212 such as may initiate a policy authorization request to the UDR 206-2 for performing an at least one of creation of a QoS reference, updating a QoS reference, and deleting a QoS reference in a QoS parameter. The policy authorization request may be initiated by invoking a “Nudr_DataRepository_qosRefCreate/update/delete” service operation. The service operation may create a new QoS reference, update or delete an existing QoS reference at the UDR 206-2.

[0089] In a first scenario, the consumer NF 212 may request for creating a new QoS parameter at the UDR 206-2 by invoking “Nudr_DataRepository_qosRefCreate” service operation. The new QoS parameter may include a string value of the QoS reference, corresponding values of the QoS attribute(s) and data such as the AF application identifier, the sponsor identifier, the slice, and the customized AF identifier. The new QoS parameter may further include the string value of the QoS reference and the corresponding values of the QoS attributes. For creating the new QoS parameter, the UDR 206-2 may utilize the string value of the QoS reference and the corresponding values of the QoS attributes. In a scenario, for optional data in the new QoS parameters not included by the trusted consumer NF 212, the UDR 206-2 may use default configured values of the optional data. Upon authorization of the QoS reference creation request, the UDR 206-2 may create the new QoS reference including markers indicating information of generation of the QoS parameter or the QoS reference (for example, information of the consumer NF 212 that generated the QoS parameter, and a temporal value depicting date and time of generation of the QoS parameter). The new QoS reference may include the string value of the QoS reference, the corresponding values of the QoS attribute(s) along with default values of other data selected by the PCF-1 206-1(a). Similarly, the UDR 206-2 may authorize the request for updating and deletion of existing QoS reference.

[0090] In a second scenario, the trusted consumer NF 212 may initiate a request for deleting a specific existing QoS parameter at the PCF-1 206-1(a) by invoking “Nudr_DataRepository_qosRefDelete” service operation. The trusted consumer NF 212 may send name of a specific QoS reference (or parameters) to be deleted along with attribute(s) of the QoS parameter to be deleted. The UDR 206-2 may authorize the request for deleting the specified QoS parameter. Upon authorization, the UDR 206-2 may check the definition of the QoS reference in the QoS parameter and an associated set of identifiers for identifying the trusted consumer NF 212 that are using the same QoS reference. The associated set of identifiers may be an array indicating other AFs, application, or sponsors using the same QoS reference. Upon identifying the other consumer NF 212 using the same QoS reference, the UDR 206-2 may remove the QoS parameter from the database 218 (or the UDR 206-2). However, the UDR 206-2 may continue to maintain the definition of the specified QoS reference in the specified QoS parameter. In another scenario, when the UDR 206-2 discovers that the specified QoS reference is being uniquely used by the trusted consumer NF 212, the UDR 206-2 may remove the definition of the specified QoS reference.

[0091] In yet another scenario, the trusted consumer NF 212 may initiate a request for updating (or modifying) a specific existing QoS parameter at the PCF-1 206-1(a) by invoking “Nudr_DataREpository_qosRefUpdate” service operation. The trusted consumer NF 212 may send name of a specific existing QoS reference to be updated along with modified data (such as the AF application identifier, the sponsor identifier, the slice, and the customized AF identifier) to the UDR 206-2. Based on the received data, the UDR 206-2 may authorize the request for updating the specified QoS parameter. Once authorized, the UDR 206-2 may check whether the modified data belongs to the trusted consumer NF 212 making the request for updating the specified QoS parameter. In a scenario, when the UDR 206-2 determines that the modified data belongs to the trusted consumer NF 212, the UDR 206-2 may then proceed to update the definition of the QoS reference in the specified QoS parameter.

[0092] At instance 604, the UDR 216-2 may communicate a response towards the consumer NF 212 regarding successful creation, deletion or update in the QoS reference definitions. The response may be sent by invoking a “Nudr_DataRepository_qosRefCreate/Update/Delete_Response” service operation. In case, at instance 602, the UDR 206-2 fails to perform the authorization or the QoS reference that is to be updated or deleted is already in use, then the UDR 206-2 may send a negative response towards the consumer NF 212 indicating an error in authorization of the request for creation, updating or deletion of the QoS reference.

[0093] At instance 606, the PCF-1 206-1(a) and at instance 508, the PCF-2 206-1(b) may invoke a subscribe request for creating a subscription for receiving the modifications in the QoS reference definition in the QoS parameter due to the request for creation, deletion and updating the QoS parameter. A “Nudr_DataRepository_qosRefSubscribe” service operation may be sent by the PCF-1 206-1(a), the PCF-2 206-1(b) and/or the consumer NF 212 to the UDR 206-2.

[0094] When the PCF 206-1 subscribe to the modifications, the subscription may include at least one of, a type NF of the PCF 206-1 along with other conditions such as the PLMN Id, slice, and a notification Uniform Resource Locator (URL) indicating that the modifications in the QoS reference and the QoS parameters for the specified conditions need to be notified to the UDR 206-2. The UDR 206-2 may respond with a subscription marker including a validity time and a subscription ID. The subscription marker may be used for providing an update on subscription services, notification correlation, and unsubscribe services. A request to subscribe for a trusted consumer NF 212 may include a type of NF, an Application Id, and a Sponsor Id along with other parameters that limit the subscription for specific subset of QoS reference in the QoS parameter. For changing the subscription condition(s) and/or updating the validity of the subscription, the PCF-2 206-1(b) and/or the trusted consumer NF 212 may use a patch method by invoking the subscribe request and the subscription ID. The PCF-2 and/or the trusted consumer NF 212 may delete the subscription created in the UDR 206-2 for modifications in the QoS parameter by invoking a subscription deletion request using a “Nudr_DataRepository_qosRefUnsubscribe” service operation.

[0095] At instance 610, the UDR 206-2 may send notifications towards the PCF-1 206-1(a) and at instance 612, the UDR 206-2 may send notifications towards the PCF-2 206-1(b) regarding modifications in the QoS reference. The modification may correspond to creation of the new QoS reference, deletion of the existing QoS reference or update in definition of the existing QoS reference. Through the notification, the PCF 206-1 and the consumer NF 212 are notified for modifications in the new QoS reference definition.

[0096] At instance 612, the trusted consumer NF 212 may initiate a fetch request for authorization to the UDR 206-2, validating and fetching the new QoS parameter or the modified existing specified QoS parameter. The fetch request may be initiated by invoking a “Npcf_DataRepository_qosRefGet” service operation. In the fetch request, the trusted consumer NF 212 may include the application identifier, the sponsor identifier, the slice, and the AF identifier. The PCF-1 206-1(a) and/or the PCF-2 206-1(b) may further authorize the fetch request based on the application identifier, the sponsor identifier, the slice, and/or the AF identifier.

[0097] At instance 616, in response to the fetch request, the UDR 206-2 may send the new QoS parameter or the modified specified existing QoS parameter to the consumer NF 212. The UDR 206-2 may return a response including the new QoS parameter or the modified specified existing QoS parameter to the consumer NF 212. The response may be sent by invoking a “Npcf_DataRepository_qosRefGet_Response” service operation. In another scenario, the UDR 206-2 may also towards the trusted consumer NF 212 indicating an error in authorization of the request or when the new QoS parameter or the modified specified existing QoS parameter is not found in the UDR 206-2. It must be noted that the information flow diagram 600 indicates two PCFs 206-1 (i.e., the first PCF 206-1(a) and the second PCF 206-1(b) such that the operation(s) performed by the PCF 206-1 can be segregated in parts and performed by two similar functional units to enhance throughput and performance efficiency. However, it will be apparent to a person skilled in the art that the presence of two PCFs is particular to an embodiment as presented in FIG. 6 and must not be considered as a limitation of the present disclosure. In some other embodiments, the functionality, as presented through FIG. 6, may be derived using a single PCF 206-1, without deviating from the scope of the present disclosure.

[0098] Referring to the technical abilities and advantageous effect of the present disclosure, operational advantages that may be provided by one or more embodiments may include providing the system 100 and the method 400 that enables better visibility in the communication network related to QoS parameters definition utilized by the PCF 206-1 to the consumer NF 212 (i.e., the AFs 212-1 and/ or the NEF 212-2) that are authorized to use the specific QoS parameter. For an example, only the trusted consumer NF 212 may fetch the QoS reference and associated definitions in the QoS parameter. The QoS reference may be synchronized between PCFs 206-1 and the consumer NF 212 and error due to mismatch of QoS reference may be avoided.

[0099] A further potential advantage of the one or more embodiments disclosed herein may include increasing an ability to set a baseline by the consumer NF 212 (i.e., the Afs 212-1 and/or the NEF 212-2) for monitoring network reports against actual targeted value of the QoS reference used by the PCF 206-1 rather than just the agreed values of the QoS reference. Another noteworthy advantage of the embodiments disclosed herein may include providing flexibility to add automation of provisioning of the QoS references in the communication network, thereby reducing manual intervention for the PCF 206-1. Furthermore, the embodiments disclosed in the present disclosure provides an ability to the consumer NF 212 for configuring QoS reference definition in the PCF 206-1, thereby reducing the parameter to be transferred such as in a case when individual QoS parameter are sent from the consumer NF 212 towards the PCF 206-1.

[00100] Those skilled in the art will appreciate that the methodology described herein in the present disclosure may be carried out in other specific ways than those set forth herein in the above disclosed embodiments without departing from essential characteristics and features of the present invention. The above-described embodiments are therefore to be construed in all aspects as illustrative and not restrictive.

[00101] The drawings and the forgoing description give examples of embodiments. Those skilled in the art will appreciate that one or more of the described elements may well be combined into a single functional element. Alternatively, certain elements may be split into multiple functional elements. Elements from one embodiment may be added to another embodiment. For example, orders of processes described herein may be changed and are not limited to the manner described herein. Any combination of the above features and functionalities may be used in accordance with one or more embodiments.

[00102] In the present disclosure, each of the embodiments has been described with reference to numerous specific details which may vary from embodiment to embodiment. The foregoing description of the specific embodiments disclosed herein may reveal the general nature of the embodiments herein that others may, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications are intended to be comprehended within the meaning of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and is not limited in scope.
,CLAIMS:We Claim:

1. A method for managing a Quality of Service (QoS) parameter in a communication network, the method (400) comprising:
receiving, by a data processing Network Function (NF) (206), a request to update the QoS parameter in a QoS reference associated with data flow in the communication network, from a consumer NF (212), wherein the request comprises one or more QoS attributes associated with the QoS parameter;
determining, by the data processing NF (206), whether each QoS attribute of the one or more QoS attributes matches with an attribute of one or more predefined attributes;
authenticating, by the data processing NF (206), the request to update the QoS parameter in the QoS reference, in response to the determination that each QoS attribute of the one or more QoS attributes matches with the one or more predefined attributes;
generating, by the data processing NF (206), a tagged QoS parameter entry by associating one or more marker tags with the QoS parameter, wherein each of the one or more marker tags corresponds to one of the one or more QoS attributes;
updating, by the data processing NF (206), the QoS reference stored in a database (218) by updating the tagged QoS parameter entry in the QoS reference, based on the request;
determining, by the data processing NF (206), whether the consumer NF (212) and the data processing NF (206) have subscribed to access information from the database (218);
receiving, by the data processing NF (206), a QoS reference update notification from the database (218) in response to the determination that the consumer NF (212) and the data processing NF (206) have subscribed to access information from the database (218); and
transmitting, by the data processing NF (206), the QoS reference update notification to the consumer NF (212).

2. The method as claimed in claim 1, wherein the data processing NF (206) is a Policy Control Function (PCF) (206-1) or a User Defined Repository (UDR) (206-2).

3. The method as claimed in claim 1, wherein the consumer NF (212) is at least one of an Application Function (AF) (212-1) and a Network Exposure Function (NEF) (212-2).

4. The method as claimed in claim 1, wherein the one or more QoS attributes comprises at least one of, a QoS value for the QoS parameter, an identifier for the QoS parameter, and information associated with generation of the QoS parameter.

5. The method as claimed in claim 4, wherein the identifier for the QoS parameter comprises at least one of an AF application identifier, a sponsor identifier, a slice, a customized AF identifier, or a combination thereof.

6. The method as claimed in claim 1, further comprising:
determining, by the data processing NF (206), when at least one QoS attribute of the one or more QoS attributes mismatches with at least one attribute of the one or more predefined attributes; and
discarding, by the data processing NF (206) in response to the mismatch of the at least one QoS attribute with the at least one attribute, the request to update the QoS parameter in the QoS reference.

7. The method as claimed in claim 6, further comprises comparing, by the data processing NF (206), each QoS attribute with each of the one or more predefined attributes to determine the match or mismatch between the QoS attribute and the one or more predefined attributes.

8. The method as claimed in claim 1, further comprising:
determining when the consumer NF (212) and the data processing NF (206) have not subscribed to access the information from the database (218); and
disabling the reception of the QoS reference update notification from the database (218), in response to the determination that the consumer NF (212) and the data processing NF (206) have not subscribed to access information from the database (218).

9. A system (100) to manage a Quality of Service (QoS) parameter in a communication network, the system (100) comprising:
a consumer Network Function (NF) (212); and
a data processing NF (206) communicatively coupled with the consumer NF (212), wherein the data processing NF (106) is configured to:
receive, from the consumer NF (212), a request to update a QoS parameter in a QoS reference associated with data flow in the communication network, wherein the request comprises one or more QoS attributes associated with the QoS parameter;
determine whether each QoS attribute of the one or more QoS attributes matches with an attribute of one or more predefined attributes;
authenticate the request to update the QoS parameter in the QoS reference, in response to the determination that each QoS attribute of the one or more QoS attributes matches with the one or more predefined attributes;
generate a tagged QoS parameter entry by associating one or more marker tags with the QoS parameter, wherein each of the one or more marker tags corresponds to one of the one or more QoS attributes;
update the QoS reference stored in the database (218) by updating the tagged QoS parameter entry in the QoS reference, based on the request;
determine whether the consumer NF (212) and the data processing NF (206) have subscribed to access information from the database (218);
receive a QoS reference update notification from the database (218) in response to the determination that the consumer NF (212) and the data processing NF (206) have subscribed to access information from the database (218); and
transmit the QoS reference update notification to the consumer NF (212).

10. The system (100) as claimed in claim 9, wherein the data processing NF (206) is a Policy Control Function (PCF) (206-1) or a User Defined Repository (UDR) (206-2).

11. The system (100) as claimed in claim 9, wherein the consumer NF (212) is at least one of an Application Function (AF) (212-1) and a Network Exposure Function (NEF) (212-2).

12. The system (100) as claimed in claim 9, wherein the one or more QoS attributes comprises at least one of, a QoS value for the QoS parameter, an identifier for the QoS parameter, and information associated with generation of the QoS parameter.

13. The system (100) as claimed in claim 12, wherein the identifier for the QoS parameter comprises at least one of an AF application identifier, a sponsor identifier, a slice, a customized AF identifier, or a combination thereof.

14. The system (100) as claimed in claim 9, wherein the data processing NF (206) is further configured to:
determine when at least one attribute of the one or more QoS attributes mismatches with at least one attribute of the one or more predefined attributes; and
discard, in response to the mismatch of the at least one QoS attribute with the at least one attribute, the request to request to update the QoS parameter in the QoS reference.

15. The system (100) as claimed in claim 14, wherein the data processing NF (206) is further configured to compare each QoS attribute with each of the one or more predefined attributes to determine the match or mismatch between the QoS attribute and the one or more predefined attributes.

16. The system (100) as claimed in claim 9, wherein the data processing NF (206) is further configured to:
determine when the consumer NF (212) and the data processing NF (206) have not subscribed to access the information from the database (218); and
disable the reception of the QoS reference update notification from the database (218), in response to the determination that the consumer NF (212) and the data processing NF (206) have not subscribed to access information from the database (218).