Abstract: The present disclosure relates to a method and a system for performing a policy control update for an application. The method encompasses receiving, by a transceiver unit [302] at a policy control function (PCF) [122], at least one of a start trigger event (APP_STA) and a stop trigger event (APP_STO) for the application. Next, the method encompasses receiving, by the transceiver unit [302] at the PCF [122], an update instruction relating to the policy control update for the application from a session management function (SMF) [108] wherein the update instruction comprises a set of details relating to the application. Next, the method encompasses performing, by a processing unit [304], the update of the policy control for the application, based on the set of details relating to the application, and the received at least one of the start trigger event (APP_STA) and the stop trigger event (APP_STO) for the application. [FIG. 4]
FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR PERFORMING A POLICY CONTROL UPDATE FOR AN APPLICATION”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.
METHOD AND SYSTEM FOR PERFORMING A POLICY CONTROL UPDATE FOR AN APPLICATION
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to the field of wireless communication systems. More particularly, embodiments of the present disclosure relate to methods and systems for performing a policy control update for an application.
BACKGROUND
[0002] 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.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging was introduced. 3G technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth-generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth-generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect
multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] Policy Control Function (PCF) in 5G networks provides several policy rules for control plane functions. A few of these policy rules may be associated with network slicing, roaming, mobility management. Now, the PCF supports a new 5G quality of service (QoS) policy and charging control function as well. It manages policies, services, subscriptions, quotas, and bearer resources. The policies are created in real time based on a subscriber profile.
[0005] Currently, if an application detection control (ADC) feature is supported, and a user subscription indicates that the application detection and control is required, the PCF needs to provision Policy and Charging Control (PCC) rule(s) for application detection and control in the response message for the received HTTP POST request from the Session Management Function (SMF). Now, if the SMF receives a PCC rule for application detection and control, the SMF shall instruct the User Plane Function (UPF) to detect the associated application traffic.
[0006] The problem in the currently existing solutions is primarily related to implementation of PCC rules for the applications based on detection of the application traffic. Further, the existing solutions fail to deal with a scenario in which the rule sent by the PCF for the application is not declared at the SMF end.
[0007] Thus, there exists an imperative need in the art to overcome the above-stated problems by providing the methods and systems for performing a policy control update for an application.
SUMMARY
[0008] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description.
This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0009] An aspect of the present disclosure may relate to a method for performing a policy control update for an application. The method includes receiving, by a transceiver unit at a policy control function (PCF), at least one of a start trigger event (APP_STA) and a stop trigger event (APP_STO) for the application. Next, the method includes receiving, by the transceiver unit at the PCF, an update instruction relating to the policy control update for the application from a session management function (SMF), wherein the update instruction comprises a set of details relating to the application. Thereafter, the method includes performing, by a processing unit via the PCF, the policy control update for the application, based on the set of details relating to the application, and the received at least one of the start trigger event (APP_STA) and the stop trigger event (APP_STO) for the application.
[00010] In an exemplary aspect of the present disclosure, the set of details includes at least a flow information for the application and an application identifier (APP-ID).
[00011] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the processing unit at the PCF from the SMF, an error notification in one of the events comprising an absence of at least the flow information for the application in the update instruction or invalidation of the APP-ID.
[00012] In an exemplary aspect of the present disclosure, the method further comprises ceasing, by the processing unit at the PCF, the policy control update of the policy control for the application upon reception of the error notification.
[00013] In an exemplary aspect of the present disclosure, the policy control update for the application corresponds to an installation of one of a predefined Policy and Charging Control (PCC) rule or a dynamically created rule.
[00014] Another aspect of the present disclosure may relate to a system for performing a policy control update for an application. The system comprises a transceiver unit. The transceiver unit is configured to receive, at a policy control function (PCF), at least one of a start trigger event (APP_STA) and a stop trigger event (APP_STO) for the application. The transceiver unit is further configured to receive, at the PCF, an update instruction relating to the policy control update for the application from a session management function (SMF) wherein the update instruction comprises a set of details relating to the application. The system further comprises a processing unit connected at least with the transceiver unit. The processing unit is configured to perform, via the PCF, the policy control update for the application, based on the set of details relating to the application, and the received at least one of the APP_STA and the APP_STO for the application.
[00015] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for performing a policy control update for an application, the instructions include executable code which, when executed by one or more units of a system, causes: a transceiver unit of the system to receive, at a policy control function (PCF), at least one of a start trigger event (APP_STA) and a stop trigger event (APP_STO) for the application; a transceiver unit of the system to receive, at the PCF, an update instruction relating to the policy control update for the application from a session management function (SMF) wherein the update instruction comprises a set of details relating to the application; a processing unit of the system to perform, via the PCF, the policy control update for the application, based on the set of details relating to the application, and the received at least one of the APP_STA and the APP_STO for the application.
OBJECTS OF THE INVENTION
[00016] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[00017] It is an object of the present disclosure to provide a system and a method for performing a policy control update for an application.
[00018] It is another object of the present disclosure to provide a system and a method for providing application detection control-based rule support in a Policy Control Function (PCF).
[00019] It is yet another object of the present disclosure to provide a solution by evaluating, at the PCF, each Policy based on APP-ID uniquely.
[00020] Yet another object of the present disclosure is to provide the PCF with a subscription to the event for application start and stop for traffic detection from at least one Network Function (NF) service consumer.
DESCRIPTION OF THE DRAWINGS
[00021] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems 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 disclosure of
electrical components, electronic components or circuitry commonly used to implement such components.
[00022] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
[00023] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented, in accordance with the exemplary implementation of the present disclosure.
[00024] FIG. 3 illustrates an exemplary block diagram of a system for performing a policy control update for an application, in accordance with exemplary implementations of the present disclosure.
[00025] FIG. 4 illustrates a method flow diagram for performing a policy control update for an application, in accordance with exemplary implementations of the present disclosure.
[00026] FIG. 5 illustrates an exemplary block diagram of a system for application detection control-based rule support in a Policy Control Function (PCF), in accordance with exemplary embodiments of the present disclosure.
[00027] FIG. 6 illustrates a system architecture indicating the process for providing application detection control-based rule support in Policy Control Function (PCF), in accordance with exemplary embodiments of the present disclosure.
[00028] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[00029] 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 may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
[00030] 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.
[00031] 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, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[00032] 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 may 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.
[00033] 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.
[00034] As used herein, a “processing unit”, “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[00035] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a
communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit, and any other such unit(s) which are required to implement the features of the present disclosure.
[00036] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices, or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
[00037] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to as a set of rules or protocols that define the communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
[00038] All modules, units, and components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special-purpose processor, a conventional processor, a digital signal processor (DSP), a plurality of microprocessors, one or more
microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[00039] As used herein, the transceiver unit includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information, or a combination thereof between units/components within the system and/or connected with the system.
[00040] As used herein, the policy control and charging (PCC) rule is a set of information elements enabling the detection of a service data flow and providing parameters for policy control and/or charging control. The service data flow is an aggregate set of packet flows that matches a service data flow template. In other words, the service data flow refers to an overall movement of data within a service or system. Further, charging control is the process of associating packets, belonging to the service data flow, and applying online charging and/or offline charging, as appropriate. In other words, charging control involves management of billing of the subscribers for the services consumed by the subscribers. Policy Control refers to the process of managing various policies that determine allocation of network resources for subscribers or applications. Further, the policy control is associated with quality of service (QoS) control and QoS signalling.
[00041] As used herein, predefined PCC rules are preconfigured by the PCF for the SMF. The predefined PCC rules can be activated or deactivated by the PCF at any time. Predefined PCC rules within the PCF may be grouped allowing the PCF to dynamically activate a set of PCC rules.
[00042] As used herein, a dynamically created rule or dynamically created PCC rule is dynamically provisioned by the PCF to the SMF. These rules may dynamically be
generated by the PCF. The dynamic created rules can be installed, modified, and removed at any time.
[00043] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a method and system for performing a policy control update for an application. In the present disclosure, the existing problem may be addressed by receiving, at a Policy Control Function (PCF), at least one of a start trigger event (APP_STA) and a stop trigger event (APP_STO) for the application from at least one NF consumer. Next, the disclosure encompasses receiving, at the PCF, an update instruction relating to the policy control update for the application from a Session Management Function (SMF) wherein the update instruction comprises a set of details relating to the application. Thereafter, the present disclosure encompasses performing, by the PCF, the policy control update for the application, based on the set of details relating to the application, and the received at least one of the start trigger event (APP_STA) and the stop trigger event (APP_STO) for the application. Thus, the present disclosure evaluates, at the PCF, each policy based on application identifier (APP-ID) uniquely.
[00044] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a User Equipment (UE) [102], a Radio Access Network (RAN) [104], an Access and Mobility Management Function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122],
a Unified Data Management (UDM) [124], an Application Function (AF) [126], a User Plane Function (UPF) [128], a Data Network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure. 5
[00045] Radio Access Network (RAN) [104] is part of a mobile telecommunications system that connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
10
[00046] Access and Mobility Management Function (AMF) [106] is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
15
[00047] Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
20
[00048] Service Communication Proxy (SCP) [110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
25
[00049] Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
13
[00050] Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized. 5
[00051] Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.
10 [00052] Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[00053] Network Repository Function (NRF) [120] is a network function that acts 15 as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.
[00054] Policy Control Function (PCF) [122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on 20 subscriber information and network policies.
[00055] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information. 25
[00056] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
14
[00057] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
5 [00058] Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
[00059] FIG. 2 illustrates an exemplary block diagram of a computing device [200] 10 (also referred to herein as a computer system [200]) upon which the features of the present disclosure may be implemented, in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for performing a policy control update for an application utilising the system. In another implementation, the computing 15 device [200] itself implements the method for performing the policy control update for the application using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
20 [00060] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a random-25 access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during the execution of the instructions to be executed by the processor [204]. Such instructions, when stored in non-transitory storage media 30 accessible to the processor [204], render the computing device [200] into a special-
15
purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read-only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204]. 5
[00061] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light
10 Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a
15 trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
20
[00062] The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine. According
25 to one implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the sequences of instructions contained in the main
30 memory [206] causes the processor [204] to perform the process steps described
16
herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[00063] The computing device [200] also may include a communication interface 5 [218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line.
10 As another example, the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of
15 information.
[00064] The computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218]. In the Internet example, a server [230] might
20 transmit a requested code for an application program through the Internet [228], the ISP [226], the local network [222], Host [224], and the communication interface [218]. The received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution.
25
[00065] The computing device [200] encompasses a wide range of electronic devices capable of processing data and performing computations. Examples of computing device [200] include, but are not limited only to, personal computers, laptops, tablets, smartphones, servers, and embedded systems. The devices may
30 operate independently or as part of a network and can perform a variety of tasks such
17
as data storage, retrieval, and analysis. Additionally, computing device [200] may include peripheral devices, such as monitors, keyboards, and printers, as well as integrated components within larger electronic systems, showcasing their versatility in various technological applications. 5
[00066] Referring to FIG. 3, an exemplary block diagram of a system [300] for performing a policy control update for an application, is shown, in accordance with the exemplary implementations of the present disclosure. As used herein, policy control refers to the process of managing or controlling various policies that
10 determine allocation of network resources for subscribers or applications. The policy control is associated with quality of service (QoS) control and QoS signalling. The system [300] comprises at least one Policy Control Function (PCF) [122], which further comprises at least one transceiver unit [302], at least one processing unit [304]. The system [300] further includes at least one Session Management Function
15 [108]. Also, all of the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units, or the system [300] may comprise any such numbers
20 of said units, as required to implement the features of the present disclosure. In an implementation, the system [300] may reside in a server or a network entity. In another implementation, the system [300] may reside partly in the server/ network entity and partly in the user device. Further, in yet another implementation, the system [300] may be present in a user device to implement the features of the present
25 disclosure. The system [300] may be a part of the user device/or may be independent of but in communication with the user device (may also referred to herein as a UE).
[00067] The system [300] is configured for performing the policy control update for the application, with the help of the interconnection between the components/units 30 of the system [300].
18
[00068] The system [300] comprises a transceiver unit [302]. The transceiver unit [302] may be configured to receive, at a Policy Control Function (PCF) [122], at least one of a start trigger event (APP_STA) and a stop trigger event (APP_STO) for 5 the application. The transceiver unit [302] at the PCF [122] is configured to receive the at least one of the start trigger event (APP_STA) and the stop trigger event (APP_STO) for the application, such as, but not limited to, media streaming applications, internet browsing applications, from the session management function (SMF) [108]. In an exemplary implementation, the APP_STA may be associated
10 with the application start event, such as the beginning of the media streaming session. APP_STA trigger informs the PCF [122] that the media streaming application session has begun, so the PCF [122] can apply the necessary policy and charging control rules, QoS flow rules, or any other specific handling required for the media streaming application. In an exemplary implementation, the APP_STO may be
15 associated with the application stop event, such as the stopping of the media streaming session on the media streaming application. APP_STO trigger informs the PCF [122] that the media streaming application session has stopped. Accordingly, the PCF [122] may update or terminate the necessary policy and charging control rules, QoS flow rules, or releasing resources for the media streaming application.
20 Further, at least one of the start trigger event (APP_STA) and the stop trigger event (APP_STO) for the application may be received from at least one consumer network function (NF), such as but not limited to SMF.
[00069] The transceiver unit [302] at the PCF [122] of the system [300] further may 25 be configured to receive, at the PCF [122], an update instruction relating to the policy control update for the application from a Session Management Function (SMF) [108] wherein the update instruction comprises a set of details relating to the application. The transceiver unit [302] at the PCF [122] may receive the set of details such as, but not limited to, at least a flow information for the application and an application 30 identifier (APP-ID) from the SMF [108]. In an example, the flow information
19
corresponds to traffic flow data associated with the application and is managed by the SMF [108]. The SMF [108] may send a SMPolicyControl update request along with the application identifier (APP-ID) and flow description with the update instruction, to the PCF [122]. The flow information of the application may include 5 flow description and flow direction (e.g., uplink, downlink, and bidirectional) for the application’s traffic. In an implementation, the flow description may have information such as, but not limited to quality of service (QoS), bitrate, packet filter and bandwidth resources. In an exemplary implementation, the SMF [108] may send such as, but not limited to, SM policy update request or update instruction for PCC 10 rules with an application identifier (APP-ID) to the PCF [122] for the media streaming application session.
[00070] The PCF [122] may receive the update instruction relating to the policy control update for the application from the Session Management Function (SMF) 15 [108] such as, but not limited to, installing, removing, modifying and authorising the PCC rules and SM policy.
[00071] The system [300] further comprises a processing unit [304], which is connected to the transceiver unit [302]. The transceiver unit [302] may send the
20 received update instruction relating to the policy control update for the application to the processing unit [304]. The processing unit [304] of the system [300] may be configured to perform, at the PCF [122], the policy control update for the application, based on the set of details relating to the application, and the received at least one of the APP_STA and the APP_STO for the application. The processing unit [304] is
25 configured to update the policy control for the application based on the APP-ID, flow description, APP_STA trigger, and APP_STO trigger. The policy control update for the application corresponds to an installation of one of a predefined Policy and Charging Control (PCC) rule or a dynamically created rule. In an exemplary implementation, the PCF [122] may update the PCC rules for the media streaming
30 application based on the application ID, and application start/stop trigger(s) by
20
installing predefined PCC rules or dynamic PCC rules in real-time. In a non-limiting example, the predefined PCC rules or dynamic PCC rules may be installed at the SMF [108] for implementing the PCC rules or dynamic PCC rules for the application. 5
[00072] Further, the transceiver unit [302] of the system [300] may be further configured to receive, at the PCF [122] from the SMF [108], an error notification in one of the events comprising an absence of at least the flow information for the application in the update instruction or invalidation of the APP-ID. The transceiver
10 unit [302] is configured to send an error event message to the processing unit [304] for unknown/invalid APP-ID or missing flow information for the application. In response to this, the processing unit [304] may be further configured to cease, at the PCF [122], the policy control update for the application upon reception of the error notification. In an exemplary implementation, the PCF [122] may stop installing the
15 policy control update of the PCC rules for the media application session after receiving the error notification from the SMF [108].
[00073] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be
20 implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative
25 arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[00074] Referring to FIG. 4, an exemplary method flow diagram [400] for 30 performing a policy control update for an application, in accordance with exemplary
21
implementations of the present disclosure, is shown. In an implementation, the method [400] is performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in FIG. 4, the method [400] starts at step [402]. 5
[00075] At step [404], the method [400] of the present disclosure comprises receiving, by a transceiver unit [302] at a policy control function (PCF) [122], at least one of a start trigger event (APP_STA) and a stop trigger event (APP_STO) for the application. The transceiver unit [302] at the PCF [122] may receive at least one
10 of the start trigger event (APP_STA) and the stop trigger event (APP_STO) for the application, such as, but not limited to, media streaming application, from the Session Management Function (SMF) [108]. In an exemplary implementation, the APP_STA may be associated with the application start event, such as the beginning of the media streaming session. APP_STA trigger informs the PCF [122] that the
15 media streaming application session has begun, so the PCF [122] can apply the necessary policy and charging control rules, QoS flow rules or any other specific handling required for the media streaming application. In an exemplary implementation, the APP_STO may be associated with the application stop event, such as the stopping of the media streaming session. APP_STO trigger informs the
20 PCF [122] that the media streaming application session has stopped, so the PCF [122] can update or terminate the necessary policy and charging control rules, QoS flow rules, or release resources for the media streaming application.
[00076] Next at step [406], the method [400] of the present disclosure comprises 25 receiving, by the transceiver unit [302] at the PCF [122], an update instruction relating to the policy control update for the application from a session management function (SMF) [108] wherein the update instruction comprises a set of details relating to the application. The transceiver unit [302] at the PCF [122] may receive the set of details such as, but not limited to, at least a flow information for the 30 application and an application identifier (APP-ID) from the SMF [108]. The SMF
22
[108] may send an SMPolicyControl update request along with APP-ID, and flow description with the update instruction to the PCF [122]. The flow information of the application may include flow description and flow direction (e.g., uplink, downlink, and bidirectional) for the application’s traffic. In an implementation, the flow description may have information such as, but not limited to quality of service (QoS), bitrate, and bandwidth resources. In an exemplary implementation, the SMF [108] may send such as but not limited to, SM policy update request or update instructions for PCC rules with an application identifier.
[00077] The PCF [122] may receive the update instruction relating to the policy control update for the application from a Session Management Function (SMF) [108] such as, but not limited to, installing, removing, modifying and authorising the PCC rules and SM policy.
[00078] Next at step 408, the method [400] of the present disclosure comprises performing, by a processing unit [304] via the PCF [122], the policy control update for the application, based on the set of details relating to the application, and the received at least one of the start trigger event (APP_STA) and the stop trigger event (APP_STO) for the application. The processing unit [304] of the system [300] may update the policy control for the application based on the APP-ID, flow description, APP_STA trigger, and APP_STO trigger. The policy control update for the application corresponds to an installation of one of a predefined Policy and Charging Control (PCC) rule or a dynamically created rule. In an exemplary implementation, the PCF [122] may update the PCC rules for the media streaming application based on the application ID, and application start/stop trigger by installing predefined PCC rules or dynamic PCC rules in the real-time.
[00079] Further, the transceiver unit [302] of the system [300] may further configured to receive, at the PCF [122] from the SMF [108], an error notification in one of the events comprising an absence of at least the flow information for the
application in the update instruction or invalidation of the APP-ID. The transceiver unit [302] may send an error event message to the processing unit [304] for the unknown/invalid APP-ID or missing flow information for the application. In response to this, the processing unit [304] may cease, at the PCF [122], the policy control update for the application upon reception of the error notification. In an exemplary implementation, the PCF [122] may stop installing the policy control update of the PCC rules for the media application session after receiving the error notification from the SMF [108].
[00080] Thereafter, the method [400] terminates at step [410].
[00081] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for performing a policy control update for an application, the instructions include executable code which, when executed by one or more units of a system [300], causes: a transceiver unit [302] of the system to receive, at a policy control function (PCF) [122], at least one of a start trigger event (APP_STA) and a stop trigger event (APP_STO) for the application; a transceiver unit [302] of the system to receive, at the PCF [122], an update instruction relating to the policy control update for the application from a session management function (SMF) [108] wherein the update instruction comprises a set of details relating to the application; a processing unit [304] of the system to perform, via the PCF [122], the policy control update for the application, based on the set of details relating to the application, and the received at least one of the APP_STA and the APP_STO for the application.
[00082] FIG. 5 illustrates an exemplary block diagram of a system [500] for providing application detection and control (ADC) based rule support in Policy Control Function (PCF), in accordance with exemplary implementations of the present disclosure. The system [500] is configured to provide the ADC based rule support in the Policy Control Function (PCF) [122], with the help of the
interconnection between the components/units of the system [100]. The ADC feature comprise the request to detect the specified application traffic, report to the PCF [122] on the start or stop of application traffic and to apply the specified enforcement and policy and charging actions. More particularly, Application Detection and Control (ADC) feature is used for network management by identifying, monitoring, and managing the traffic generated by various applications on a network.
[00083] The system [500] is configured to provide a rule-engine-based approach. In a preferred implementation, the PCF [122] is configured to provide the rule engine-based approach for the application traffic detection and control. The PCF [122] may include one or more rule engines for creating and providing the PCC rules for the detection and control of the application. The PCF [122] then uses the one or more rule engines to enforce the network policies. In an example, if a user exceeds a certain data threshold while browsing data on an application, the rule engine may trigger a policy to reduce their bandwidth or charge the user for additional usage.
[00084] At step 1, an SMF [108] is configured to send a SMPolicy Control Create Request to a PCF [122] for a user or subscriber for using any application that needs monitoring. Next at step 2, the PCF [122] sends a response dynamically, such as APP_STA dynamic response to the SMF [108] for the SMPolicy Control Create Request within "policyCtrlReqTriggers". In an exemplary implementation, APP_STA refers to application start, and the APP_STA dynamic involves dynamically handling application start processes to monitor the application’s traffic.
[00085] Further at step 3, the SMF [108] sends a SMPolicyControl Update Request to the PCF [122]. The SMPolicyControl Update Request includes at least one of an APP-ID and flow description associated with the application. The flow description may include such as, but not limited to, information of flow direction (e.g., uplink or downlink or bidirectional), packet rate, packet filter and QoS. Furthermore, at step 4, the PCF [122] is configured to check if any rule is defined for the received APP-
ID. If the rule is already defined for the received APP-ID then, the PCF [122] installs rules at the SMF [108]. Further, if there is no rule or any update of rule is defined for the received APP-ID, the PCF [122] mirrors the flow description that is received in the update request and sends the same parameters or values of the flow description in the response. The PCF [122] only authorises the flow description as received at the SMPolicyControl Update Request. Thus, the PCF [122], upon unavailability of any updated PCC rule for the received APP-ID, mirrors the flow description to the SMF [108] so that SMF [108] may control the application traffic using the existing flow information and rules.
[00086] Now, at step 5, the SMF [108] sends an update request to the PCF [122] with a rule report and application ID error (APP_ID_ERR) in case the rule is not defined at the SMF [108] for the particular application ID and the flow information is not available for the application. The SMF [108] then at step 6 receives a dynamic rule flow information from the PCF [122] for the application. Additionally, if no condition matches the APP-ID then the PCF [122] is configured to send a success response to the SMF [108].
[00087] In an exemplary implementation, if the application identifier (APP_ID) provided in the "(APP_ID)" attribute may be at least one of invalid, unknown, and not applicable, then in that scenario the PCF [122] may suppress a PCC rule to prevent breaking into an infinite loop of APP_ID_ERR.
[00088] FIG. 6 illustrates a system [600] architecture indicating the process for providing application detection control-based rule support in the Policy Control Function (PCF), in accordance with exemplary implementations of the present disclosure. As shown in FIG. 6, a PCF [122] may communicate Npcf_SMPolicyControl via interface Npcf with a SMF [108]. The system [600] is configured to provide a rule-engine based approach. The PCF [122] may have one or more rule-engine. The PCF [122] is configured to provide support for application
detection control (ADC) with support to at least one of install, remove, and modify APP_STA and APP_STO triggers. Further, the PCF [122] is configured to provide at least one of the install predefined PCC rules and dynamically create rules based on at least one of a trigger comprising at least one of App-ID, APP_STA/APP_STO. In an implementation, when no flow information or rule is defined at the PCC for the received APP-ID, then the PCF [122] may populate FlowInformation, that may be received from the SMF [108]. Accordingly, the ADC condition in the PCC rule may be checked for both create and update messages. Also, for FailureCode "APP_ID_ERR" received from the SMF [108], the PCF [122] may suppress the rule as part of RuleReport.
[00089] In an exemplary implementation, a UE starts a media application. In case the application detection feature is enabled, then PCF [122] receives application start/stop detection or update event from the SMF [108] via UPF [128]. The SMF [108] sends an application identifier (APP-ID) with flow information to the PCF [122] for the media application for getting policy and charging control. The PCF [122] checks the PCC rule or business rule for the received APP-ID and flow information and sends a policy response to the SMF [108]. If there is no policy defined in PCC rule or business rule for the received APP-ID, the PCF [122] mirrors the received flow information to the SMF [108] so that the SMF [108] may apply the policy for the media application. Further, if the SMF [108] sends a request to the PCF [122] with a rule report and application ID error (APP_ID_ERR) i.e., when the rule is not defined at the SMF [108] for the application ID, and the flow information is not available for the application. The PCF [122] sends a dynamic rule flow information to the SMF [108] for the application to enforce the policy using the dynamic rule flow.
[00090] As is evident from the above, the present disclosure provides a technically advanced solution to provide a rule-engine based approach. The present solution evaluates Policy based on APP-ID uniquely to perform the efficient policy control
update for the application. Further, the PCF may receive a subscription to the event for application start and stop for traffic detection from other NF service consumers to quickly determine the application’s traffic. Further, if the application identifier provided in the "appId" attribute is invalid, unknown, or not applicable, then the present disclosure returns a PCC Rule Error Report and sets the "failureCode" attribute to "APP_ID_ERR". Accordingly, the PCF suppresses the PCC rule in further updates breaking the infinite loop of APP_ID_ERR.
[00091] While considerable emphasis has been placed herein on the disclosed embodiments, it will be appreciated that many embodiments can be made and that many changes can be made to the embodiments without departing from the principles of the present disclosure. These and other changes in the embodiments of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.
We Claim:
1. A method for performing a policy control update for an application, the
method comprising:
- receiving, by a transceiver unit [302] at a policy control function (PCF) [122], at least one of a start trigger event (APP_STA) and a stop trigger event (APP_STO) for the application;
- receiving, by the transceiver unit [302] at the PCF [122], an update instruction relating to the policy control update for the application from a session management function (SMF) [108], wherein the update instruction comprises a set of details relating to the application; and
- performing, by a processing unit [304] via the PCF [122], the policy control update for the application, based on the set of details relating to the application, and the received at least one of the start trigger event (APP_STA) and the stop trigger event (APP_STO) for the application.
2. The method as claimed in claim 1, wherein the set of details comprises at least a flow information for the application and an application identifier (APP-ID).
3. The method as claimed in claim 2, further comprises receiving, by the processing unit [304] at the PCF [122] from the SMF [108], an error notification in one of events comprising an absence of at least the flow information for the application in the update instruction or invalidation of the APP-ID.
4. The method as claimed in claim 3, wherein the method comprises ceasing, by the processing unit [304] at the PCF [122], the policy control update for the application upon reception of the error notification.
5. The method as claimed in claim 1, wherein the policy control update for the application corresponds to an installation of one of a predefined Policy and Charging Control (PCC) rule or a dynamically created rule.
6. A system for performing a policy control update for an application, the system comprising:
a transceiver unit [302], the transceiver unit [302] is configured to:
- receive, at a policy control function (PCF) [122], at least one of a start trigger event (APP_STA) and a stop trigger event (APP_STO) for the application;
- receive, at the PCF [122], an update instruction relating to the policy control update for the application from a session management function (SMF) [108] wherein the update instruction comprises a set of details relating to the application;
a processing unit [304] connected at least with the transceiver unit [302], the processing unit [304] is configured to:
- perform, via the PCF [122], the policy control update for the
application, based on the set of details relating to the
application, and the received at least one of the APP_STA and
the APP_STO for the application.
7. The system as claimed in claim 6, wherein the set of details comprises at least a flow information for the application and an application identifier (APP-ID).
8. The system as claimed in claim 7, wherein the transceiver unit [302] is further configured to receive, at the PCF [122] from the SMF [108], an error notification in one of events comprising of an absence of at least the flow information for the application in the update instruction or invalidation of the APP-ID.
9. The system as claimed in claim 8, wherein the processing unit [304] is further configured to cease, at the PCF [122], the policy control update of the application upon reception of the error notification.
10. The system as claimed in claim 6, wherein the policy control update for the application corresponds to an installation of one of a predefined Policy and Charging Control (PCC) rule or a dynamically created rule.
| # | Name | Date |
|---|---|---|
| 1 | 202321060040-STATEMENT OF UNDERTAKING (FORM 3) [06-09-2023(online)].pdf | 2023-09-06 |
| 2 | 202321060040-PROVISIONAL SPECIFICATION [06-09-2023(online)].pdf | 2023-09-06 |
| 3 | 202321060040-POWER OF AUTHORITY [06-09-2023(online)].pdf | 2023-09-06 |
| 4 | 202321060040-FORM 1 [06-09-2023(online)].pdf | 2023-09-06 |
| 5 | 202321060040-FIGURE OF ABSTRACT [06-09-2023(online)].pdf | 2023-09-06 |
| 6 | 202321060040-DRAWINGS [06-09-2023(online)].pdf | 2023-09-06 |
| 7 | 202321060040-Proof of Right [26-12-2023(online)].pdf | 2023-12-26 |
| 8 | 202321060040-ORIGINAL UR 6(1A) FORM 1 & 26-050424.pdf | 2024-04-15 |
| 9 | 202321060040-FORM-5 [02-09-2024(online)].pdf | 2024-09-02 |
| 10 | 202321060040-ENDORSEMENT BY INVENTORS [02-09-2024(online)].pdf | 2024-09-02 |
| 11 | 202321060040-DRAWING [02-09-2024(online)].pdf | 2024-09-02 |
| 12 | 202321060040-CORRESPONDENCE-OTHERS [02-09-2024(online)].pdf | 2024-09-02 |
| 13 | 202321060040-COMPLETE SPECIFICATION [02-09-2024(online)].pdf | 2024-09-02 |
| 14 | 202321060040-Request Letter-Correspondence [09-09-2024(online)].pdf | 2024-09-09 |
| 15 | 202321060040-Power of Attorney [09-09-2024(online)].pdf | 2024-09-09 |
| 16 | 202321060040-Form 1 (Submitted on date of filing) [09-09-2024(online)].pdf | 2024-09-09 |
| 17 | 202321060040-Covering Letter [09-09-2024(online)].pdf | 2024-09-09 |
| 18 | 202321060040-CERTIFIED COPIES TRANSMISSION TO IB [09-09-2024(online)].pdf | 2024-09-09 |
| 19 | Abstract 1.jpg | 2024-09-23 |
| 20 | 202321060040-FORM 3 [08-10-2024(online)].pdf | 2024-10-08 |