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 SUBSCRIBER QUOTA
MANAGEMENT IN A NETWORK”
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.
2
METHOD AND SYSTEM FOR SUBSCRIBER QUOTA MANAGEMENT
IN A NETWORK
FIELD OF INVENTION
5
[0001] Embodiments of the present disclosure generally relate to wireless
communication systems. More particularly, embodiments of the present disclosure
relate to methods and systems for subscriber quota management in a network.
10 BACKGROUND
[0002] The following description of the 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
15 present disclosure. However, it should be appreciated that this section is used only
to enhance the understanding of the reader with respect to the present disclosure,
and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few
20 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. The third-generation
25 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
30 connect multiple devices simultaneously. With each generation, wireless
3
communication technology has become more advanced, sophisticated, and capable
of delivering more services to its users.
[0004] In the 5G communication system, there is provided a plurality of network
5 functions (NFs), for example an Access and Mobility Management Function
(AMF), session management function (SMF), Authentication Server function
(AUSF), a Network Slice Selection Function (NSSF), Policy control function
(PCF), a Network Repository Function (NRF), Network Exposure Function (NEF),
Converged Charging Function (CHF) and the like. One or more of the
10 aforementioned NFs communicate with each other, to implement multiple activities
on the 5G communication system. For example, CHF is one of the key network
functions, which supports charging or billing services for user consumption of
services.
15 [0005] In communication network, user may connect in any of available network
such as 5G communication network or 4G communication network as per location
and service usages. When a user at present is connected to 5G network and is
moving to 4G network or vice versa, the billing of such user service usage is
cumbersome task. There is a need of more than one network function nodes, which
20 act as intermediate node(s) between 4G network and 5G network and perform
protocol conversion and billing functionality for charging the service usages of the
user. The current systems and methods for charging and billing functionality for
such communication network where service usage may involve 4G and 5G
network, are not efficient and require more network functions nodes architecture
25 for billing and charging the service usages in the network.
[0006] Thus, there exists an imperative need in the art to provide an efficient system
and method for charging or billing of service usages of a user.
30 SUMMARY
4
[0007] 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.
5
[0008] An aspect of the present disclosure may relate to a method for subscriber
quota management in a network. The method comprises enabling, by a processing
unit, at a charging function (CHF) node, a set of flags. The method further
comprises receiving, by the transceiver unit, from a network function node among
10 a plurality of network function nodes, a quota management request. In an event the
set of flags are set as true, the method comprises converting, by the processing unit,
the quota management request to a diameter request. The method further comprises
sending, by the transceiver unit to an online charging system (OCS), the diameter
request. The method further comprises facilitating, by the processing unit, an
15 execution of a quota management procedure, based on the diameter request. The
method further comprises receiving, by the transceiver unit, from the OCS, a set of
details related to the subscriber quota management based on the executed quota
management procedure. In an event the set of flags are set as false, the method
comprises executing, by the processing unit, the quota management procedure in
20 response to the quota management request. The method further comprises
generating, by the processing unit, a set of details related to the subscriber quota
management based on the executed quota management procedure.
[0009] In an exemplary aspect of the present disclosure, the method further
25 comprises sending, by the transceiver unit to the network function node among the
plurality of network function nodes, the set of details related to the subscriber quota
management based on the executed quota management procedure.
[0010] In another exemplary aspect of the present disclosure, the plurality of
30 network function nodes comprises at least one of a session management function
(SMF) node and a policy control function (PCF) node.
5
[0011] Another aspect of the present disclosure may relate to a system for
subscriber quota management in a network. The system comprises a processing unit
at a Charging Function (CHF) node and a transceiver unit connected with each
5 other. The processing unit is configured to enable a set of flags. The transceiver unit
is configured to receive, from a network function node among a plurality of network
function nodes, a quota management request. In an event the set of flags are set as
true, the processing unit is configured to convert the quota management request to
a diameter request. Then the transceiver unit is configured to send, to an online
10 charging system (OCS), the diameter request. The processing unit is further
configured to facilitate an execution of a quota management procedure at the OCS
based on the diameter request. The transceiver unit is further configured to receive,
from the OCS, a set of details related to the subscriber quota management based on
the executed quota management procedure. In an event the set of flags are set as
15 false, the processing unit is configured to execute the quota management procedure
in response to the quota management request. The processing unit is further
configured to generate a set of details related to the subscriber quota management
based on the executed quota management procedure.
20 [0012] Yet another aspect of the present disclosure may relate to a non-transitory
computer readable storage medium storing instructions for subscriber quota
management in the network. The instructions include executable code which, when
executed by one or more units of a system, causes a processing unit of the system
to enable a set of flags. Further, the instructions include executable code which,
25 when executed, causes a transceiver unit to receive, from a network function node
among a plurality of network function nodes, a quota management request. In an
event the set of flags are set as true, the instructions include executable code which,
when executed, causes the processing unit of the system to convert the quota
management request to a diameter request. Further, the instructions include
30 executable code which, when executed, causes the transceiver unit to send, to an
online charging system (OCS), the diameter request. Further, the instructions
6
include executable code which, when executed, causes the processing unit to
facilitate an execution of a quota management procedure at the OCS, based on the
diameter request. Further, the instructions include executable code which, when
executed, causes the transceiver unit to receive, from the OCS, a set of details
5 related to the subscriber quota management based on the executed quota
management procedure. In an event the set of flags are set as false, the instructions
include executable code which, when executed, causes the processing unit to
execute the quota management procedure in response to the quota management
request. Further, the instructions include executable code which, when executed,
10 causes the processing unit to generate a set of details related to the subscriber quota
management based on the executed quota management procedure.
OBJECTS OF THE DISCLOSURE
15 [0013] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0014] It is an object of the present disclosure to provide a system and a method for
subscriber quota management in a network.
20
[0015] It is another object of the present disclosure to provide a system and a
method for controlling network function, such as a Charging Function (CHF), that
acts as a gateway between 4G and 5G network.
25 [0016] It is yet another object of the present disclosure to provide a solution in
which the CHF converts the HTTP/2 messages received from SMF/ PCF in 5G
network, to diameter messages before forwarding them to 4G OCS and vice versa.
[0017] It is yet another object of the present disclosure to provide a system and a
30 method for enabling dual functionality in a single network function node based on
controlling flag status.
7
BRIEF DESCRIPTION OF THE DRAWINGS
[0018] The accompanying drawings, which are incorporated herein, and constitute
5 a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
and systems in which like reference numerals refer to the same parts throughout the
different drawings. Components in the drawings are not necessarily to scale,
emphasis instead being placed upon clearly illustrating the principles of the present
disclosure. Also, the embodiments shown in the figures are not to be construed as
10 limiting the disclosure, but the possible variants of the method and system
according to the disclosure are illustrated herein to highlight the advantages of the
disclosure. It will be appreciated by those skilled in the art that disclosure of such
drawings includes disclosure of electrical components or circuitry commonly used
to implement such components.
15
[0019] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture;
[0020] FIG. 2 illustrates an exemplary block diagram of a computing device upon
20 which the features of the present disclosure may be implemented in accordance with
exemplary implementation of the present disclosure;
[0021] FIG. 3 illustrates an exemplary block diagram of a system for subscriber
quota management in a network, in accordance with exemplary implementations of
25 the present disclosure;
[0022] FIG. 4 illustrates a network flow diagram for subscriber quota management
in the network, in accordance with exemplary implementations of the present
disclosure; and
30
8
[0023] FIG. 5 illustrates a method flow diagram for subscriber quota management
in the network, in accordance with exemplary implementations of the present
disclosure.
5 [0024] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
DETAILED DESCRIPTION
10 [0025] 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
15 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.
[0026] The ensuing description provides exemplary embodiments only, and is not
20 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
25 disclosure as set forth.
[0027] 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
30 specific details. For example, circuits, systems, processes, and other components
9
may be shown as components in block diagram form in order not to obscure the
embodiments in unnecessary detail.
[0028] It should be noted that the terms "first", "second", "primary", "secondary",
5 "target" and the like, herein do not denote any order, ranking, quantity, or
importance, but rather are used to distinguish one element from another.
[0029] 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
10 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.
15
[0030] 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
20 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
25 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0031] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for
30 processing instructions. A processor may be a general-purpose processor, a special
purpose processor, a conventional processor, a digital signal processor, a plurality
10
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,
5 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.
[0032] As used herein, “a user equipment”, “a user device”, “a smart-user-device”,
10 “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
15 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 unit(s) which
are required to implement the features of the present disclosure.
20
[0033] 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”),
25 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.
30 [0034] As used herein “interface” or “user interface refers to a shared boundary
across which two or more separate components of a system exchange information
11
or data. The interface may also be referred to a set of rules or protocols that define
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.
5
[0035] All modules, units, 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
10 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.
[0036] As used herein the transceiver unit include at least one receiver and at least
15 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.
[0037] As discussed in the background section, the current known solutions have
20 several shortcomings. The present disclosure aims to overcome the abovementioned and other existing problems in this field of technology by providing
method and system of subscriber quota management in a network.
[0038] FIG. 1 illustrates an exemplary block diagram representation of 5th
25 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],
30 an Authentication Server Function (AUSF) [112], a Network Slice Specific
Authentication and Authorization Function (NSSAAF) [114], a Network Slice
12
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
5 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.
[0039] Radio Access Network (RAN) [104] is the part of a mobile
telecommunications system that connects user equipment (UE) [102] to the core
10 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.
[0040] Access and Mobility Management Function (AMF) [106] is a 5G core
15 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.
[0041] Session Management Function (SMF) [108] is a 5G core network function
20 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.
[0042] Service Communication Proxy (SCP) [110] is a network function in the
25 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.
[0043] Authentication Server Function (AUSF) [112] is a network function in
30 the 5G core responsible for authenticating UEs during registration and providing
security services. It generates and verifies authentication vectors and tokens.
13
[0044] 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
5 the slices for which they are authorized.
[0045] 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
[0046] 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.
15 [0047] Network Repository Function (NRF) [120] is a network function that acts
as a central repository for information about available network functions and
services. It facilitates the discovery and dynamic registration of network functions.
[0048] Policy Control Function (PCF) [122] is a network function responsible for
20 policy control decisions, such as QoS, charging, and access control, based on
subscriber information and network policies.
[0049] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication,
25 authorization, and subscription information.
[0050] Application Function (AF) [126] is a network function that represents
external applications interfacing with the 5G core network to access network
capabilities and services.
30
14
[0051] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS
enforcement.
5 [0052] 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.
[0053] Charging Function (CHF) [132] may refer to a network function
10 responsible for converged online charging and offline charging functionalities. The
CHF [132] provides Quota, Re-authorisation triggers, Notifications when Charging
Domain determines rating conditions is affected or when CHF determines to
terminate the charging service. The CHF [132] receives service usage reports from
NF Service Consumers. The CHF [132] is also responsible for generation of
15 charging data request.
[0054] The 5GC network architecture also comprises a plurality of interfaces for
connecting the network functions with a network entity for performing the network
functions. The NSSF [116] is connected with the network entity via the interface
20 denoted as (Nnssf) interface in FIG. 1. The NEF [118] is connected with the network
entity via the interface denoted as (Nnef) interface in FIG. 1. The NRF [120] is
connected with the network entity via the interface denoted as (Nnrf) interface in
FIG. 1. The PCF [122] is connected with the network entity via the interface
denoted as (Npcf) interface in FIG. 1. The UDM [124] is connected with the
25 network entity via the interface denoted as (Nudm) interface in FIG. 1. The AF
[126] is connected with the network entity via the interface denoted as (Naf)
interface in FIG. 1. The NSSAAF [114] is connected with the network entity via
the interface denoted as (Nnssaaf) interface in FIG. 1. The AUSF [112] is connected
with the network entity via the interface denoted as (Nausf) interface in FIG. 1. The
30 AMF [106] is connected with the network entity via the interface denoted as (Namf)
interface in FIG. 1. The SMF [108] is connected with the network entity via the
15
interface denoted as (Nsmf) interface in FIG. 1. The SMF [108] is connected with
the UPF [128] via the interface denoted as (N4) interface in FIG. 1. The UPF [128]
is connected with the RAN [104] via the interface denoted as (N3) interface in FIG.
1. The UPF [128] is connected with the DN [130] via the interface denoted as (N6)
5 interface in FIG. 1. The CHF [132] is connected with the network entity via the
interface demoted as (Nchf) interface in FIG. 1. The RAN [104] is connected with
the AMF [106] via the interface denoted as (N2) in FIG. 1. The AMF [106] is
connected with the RAN [104] via the interface denoted as (N1) in FIG. 1. The UPF
[128] is connected with other UPF [128] via the interface denoted as (N9) in FIG.
10 1.
[0055] The interfaces such as Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nnssaaf, Nausf,
Namf, Nsmf, Nchf, N9, N6, N4, N3, N2, and N1 can be referred to as a
communication channel between one or more functions or modules for enabling
15 exchange of data or information between such functions or modules, and network
entities.
[0056] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
upon which the features of the present disclosure may be implemented in
20 accordance with exemplary implementation of the present disclosure. In an
implementation, the computing device [200] may also implement a method for
subscriber quota management in a network utilising the system [300]. In another
implementation, the computing device [200] itself implements the method for
subscriber quota management in the network using one or more units configured
25 within the computing device [200], wherein said one or more units are capable of
implementing the features as disclosed in the present disclosure.
[0057] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a hardware
30 processor [204] coupled with the bus [202] for processing information. The
hardware processor [204] may be, for example, a general-purpose microprocessor.
16
The computing device [200] may also include a main memory [206], such as a
random-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
5 other intermediate information during execution of the instructions to be executed
by the processor [204]. Such instructions, when stored in non-transitory storage
media accessible to the processor [204], render the computing device [200] into a
special-purpose machine that is customized to perform the operations specified in
the instructions. The computing device [200] further includes a read only memory
10 (ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
[0058] 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
15 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 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
20 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 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]. The input device typically has two degrees
25 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.
[0059] The computing device [200] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware
30 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.
17
According 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,
5 such as the storage device [210]. Execution of the sequences of instructions
contained in the main memory [206] causes the processor [204] to perform the
process steps described herein. In alternative implementations of the present
disclosure, hard-wired circuitry may be used in place of or in combination with
software instructions.
10
[0060] The computing device [200] also may include a communication interface
[218] coupled to the bus [202]. The communication interface [218] provides a twoway 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
15 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. 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
20 implementation, the communication interface [218] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing
various types of information.
[0061] The computing device [200] can send messages and receive data, including
25 program code, through the network(s), the network link [220] and the
communication interface [218]. In the Internet example, a server [230] might
transmit a requested code for an application program through the Internet [228], the
ISP [226], the local network [222], a host [224] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received,
30 and/or stored in the storage device [210], or other non-volatile storage for later
execution.
18
[0062] Referring to FIG. 3, an exemplary block diagram of a system [300] for
subscriber quota management in the network, is shown, in accordance with the
exemplary implementations of the present disclosure. In one example, the system
5 [300] may be implemented as or within a Charging Function node. Such Charging
Function (CHF) node may be understood as CHF [132] explained in conjunction
with FIG. 1.
[0063] FIG. 4 illustrates an exemplary network flow diagram [400] for subscriber
10 quota management in the network is shown in accordance with exemplary
implementations of the present disclosure.
[0064] It may be noted that FIG. 3 and FIG. 4 have been explained simultaneously
and may be read in conjunction with each other.
15
[0065] In one example, the system [300] may be in communication with other
network entities/components as depicted in FIG. 4. It may be further noted that any
other network entities/components known to a person skilled in the art and not
depicted in FIG. 4, may also be in communication with the system [300]. Such
20 network entities/components have not been explained here for the sake of brevity.
[0066] As depicted in FIG. 3, the system [300] may comprise at least one
processing unit [302] and at least one transceiver unit [304]. In cases where the
system [300] may be implemented as the CHF [132] node, the aforementioned units
25 may be a part of the CHF [132] node.
[0067] 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 FIG. 3, all
units shown within the system [300] should also be assumed to be connected to
30 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
19
numbers of said units, as required to implement the features of the present
disclosure. Further, in an implementation, the system [300] may be present in a user
device/ user equipment [102] to implement the features of the present disclosure.
The system [300] may be a part of the user device [102]/ or may be independent of
5 but in communication with the user device [102] (may also referred herein as a UE).
In another implementation, the system [300] may reside in a server or a network
entity. In yet another implementation, the system [300] may reside partly in the
server/ network entity and partly in the user device.
10 [0068] The system [300] is configured for subscriber quota management in the
network, with the help of the interconnection between the components/units of the
system [300].
[0069] As would be understood, the subscriber quota management may refer to the
15 allocation or assignment of specific limits or boundaries to various resources
available which may be utilised by a subscriber or a user, such as bandwidth,
storage, processing power, and memory and setting such limits or boundaries for
managing charges for the services utilised by the subscriber.
20 [0070] In operation, for subscriber quota management in a network, the processing
unit [302] is configured to enable a set of flags. The set of flags may refer to a binary
value or a Boolean variable, which may, for example, indicate a presence or an
absence of a condition. In an example, due to a presence of a condition, the set of
flags may be set to ‘true’. In another example, due to an absence of the condition,
25 the set of flags may be set to ‘false’.
[0071] As would be described later, such flags may enable the system [300] to take
a set of pre-defined actions on receiving a quota management request from a NF
node [402]. If the received quota management request satisfies the conditions, as
30 set by the system [300], the flag may set to ‘true’, and the system [300] may perform
certain set of actions. However, if the received quota management request does not
20
satisfy the conditions, the flag may set to ‘false’, and the system [300] may perform
another set of actions.
[0072] In the context of the present example, in one example, the set of flags may
5 be a ‘GyOCSEnable’ Flag, and/or a ‘SyOCSEnable’ Flag. As would be understood,
‘Sy’may refer to and be understood as an interface between the Policy and Charging
Rules Function (PCRF) and the Online Charging System (OCS) that enables
transfer of policy counter status information relating to subscriber spending from
OCS to PCRF. Similarly, ‘Gy’ may refer to and be understood as an interface
10 between the OCS and Policy and Charging Enforcement Function (PCEF) that
allows online credit control for service data flow-based charging. It would be noted
that the ‘GyOCSEnable’ and the ‘SyOCSEnable’ flags may refer to a flag which
indicates the availability of the Gy interface and the Sy interface respectively which
may enable communication respective communication of PCEF and PCRF with the
15 OCS.
[0073] Continuing further, the transceiver unit [304] may then receive, from a
network function (NF) node [402] among a plurality of network function (NF)
nodes, a quota management request. This has been depicted by Step [406] in FIG.
20 4.
[0074] The NF node may refer to a network component used in implementation of
the network functions within the telecommunication network. The quota
management request may refer to a request for managing the quota management for
25 the user/subscriber. In an example, the quota management request may be a
hypertext transfer protocol (HTTP) request which may be sent over HTTP2.
[0075] In an implementation of the present disclosure, the plurality of network
function nodes may be a session management function (SMF) node or a policy
30 control function (PCF) node. The SMF node and the PCF node may be understood
as the SMF [108] and the PCF [122] respectively, as described in conjunction with
21
FIG. 1. In such cases, the quota management request may be received either from
either the SMF node [108] or the PCF node [122].
[0076] However, it may be noted that aforementioned examples of the NF are only
5 exemplary, and in no manner is construed to limit the scope of the present subject
matter in any manner. The NF may be implemented as any other NF as well, such
as a Charging Trigger Function (CTF). As would be understood, CTF may generate
charging events based on the observation of network resource usage. All such
examples would lie within the scope of the present subject matter.
10
[0077] In one example, in an event where the set of flags are set to be true, then the
processing unit [302] converts the quota management request to a diameter request.
As would be understood, the diameter request may refer to a request based on
diameter protocols which may be one of several defined Authentication,
15 Authorization, and Accounting (AAA) protocols. Further, the AAA protocol may
be understood to be the activities used by a data network to control access and
services which allows the service provider to restrict access and to ultimately bill
the subscriber for services like bandwidth.
20 [0078] Continuing further, then the transceiver unit [304] sends the diameter
request to an online charging system (OCS) [404]. This has been depicted by Step
[408] in FIG. 4. The OCS [404] may be a network component responsible for eventbased charging and credit-control function on different levels and session-based
charging control function on different levels.
25
[0079] Since, the OCS [404] may only support diameter protocol, and may not
support the HTTP, then in such case, conversion is required in order to enable the
OCS [404] to perform the functions.
30 [0080] Continuing further in the event where the set of flags are true, based on the
diameter request, the processing unit [302] facilitates an execution of a quota
22
management procedure at the OCS [404]. In an example, the quota management
procedure may refer to a procedure for managing a quota allocated to the subscriber.
In such example, the quota management procedure may involve updating the quota
used, quota allocated quota removed, quota granted in case of remaining/available
5 quota, etc. By quota management the network entities manage the resources and
services that are consumed by the subscriber, and accordingly manage the usage or
resources and services by the subscriber.
[0081] Based on the execution of the quota management procedure, the OCS [404]
10 may generate a set of details related to the subscriber quota management. The set
of details related to the subscriber quota management may refer to information
associated with available quota, used quota, requested quota, granted quota, charges
associated with the quota, call details record, etc.
15 [0082] Such set of details related to the subscribed quota management may then be
transmitted back to the system [300]. This has been depicted by Step [410] in FIG.
4. The transceiver unit [304] may receive these details.
[0083] In another example, in case of an event where the set of flags are set to be
20 false, then the processing unit [302], at the CHF [132] node, may execute the quota
management procedure in response to the quota management request. Then, based
on the executed quota management procedure, the processing unit [302] generates
the set of details related to the subscriber quota management.
25 [0084] It is pertinent to note that, in cases of the flag to be true, the execution of the
quota management procedure and the generation of the set of details may be
performed at the OCS [404]. These details may then be transmitted back to the
system [300], i.e., the CHF [132] node. However, in cases of the flag to be false,
the execution of the quota management procedure and the generation of the set of
30 the details may be performed at the CHF [132] node itself.
23
[0085] Continuing further, after the CHF [132] node has the set of details related to
the subscriber quota management based on the executed quota management
procedure, the system [300] may transmit said set of details to the network function
node [402] among the plurality of network function nodes. This has been depicted
5 by Step [412] in FIG. 4.
[0086] Referring to FIG. 5, an exemplary method flow diagram [500] for
subscriber quota management in a network, in accordance with exemplary
implementations of the present disclosure is shown. In an implementation the
10 method [500] 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. 5, the method [500] starts at step [502].
[0087] As would be understood, the subscriber quota management may refer to the
15 allocation or assignment of specific limits or boundaries to various resources
available which may be utilised by a subscriber or a user, such as bandwidth,
storage, processing power, and memory and setting such limits or boundaries for
managing charges for the services utilised by the subscriber.
20 [0088] For subscriber quota management in a network, in operation, at step [504],
the method [500] involves enabling, by a processing unit [302] at a charging
function (CHF) node [132], a set of flags.
[0089] In operation, for subscriber quota management in a network, the processing
25 unit [302] is configured to enable a set of flags. The set of flags may refer to a binary
value or a Boolean variable, which may, for example, indicate a presence or an
absence of a condition. In an example, due to a presence of a condition, the set of
flags may be set to ‘true’. In another example, due to an absence of the condition,
the set of flags may be set to ‘false’.
30
24
[0090] As would be described later, such flags may enable the system [300] to take
a set of pre-defined actions on receiving a quota management request from a NF
node [402]. If the received quota management request satisfies the conditions, as
set by the system [300], the flag may set to ‘true’, and the system [300] may perform
5 certain set of actions. However, if the received quota management request does not
satisfy the conditions, the flag may set to ‘false’, and the system [300] may perform
another set of actions.
[0091] In the context of the present example, in one example, the set of flags may
10 be a GyOCSEnable Flag, and/or a SyOCS Enable Flag.
[0092] On enabling the set of flags, then at step [506], the method [500] involves
receiving, by the transceiver unit [304], from a network function node among a
plurality of network function nodes, a quota management request.
15
[0093] Continuing further, the transceiver unit [304] may then receive, from a
network function (NF) node [402] among a plurality of network function (NF)
nodes, a quota management request.
20 [0094] The NF node may refer to a network component used in implementation of
the network functions within the telecommunication network. The quota
management request may refer to a request for managing the quota management for
the user/subscriber. In an example, the quota management request may be a
hypertext transfer protocol (HTTP) request which may be sent over HTTP2.
25
[0095] In an implementation of the present disclosure, the plurality of network
function nodes may be a session management function (SMF) node or a policy
control function (PCF) node. The SMF node and the PCF node may be understood
as the SMF [108] and the PCF [122] respectively, as described in conjunction with
30 FIG. 1. In such cases, the quota management request may be received either from
either the SMF node [108] or the PCF node [122].
25
[0096] However, it may be noted that aforementioned examples of the NF are only
exemplary, and in no manner is construed to limit the scope of the present subject
matter in any manner. The NF may be implemented as any other NF as well, such
5 as a Charging Trigger Function (CTF). As would be understood, CTF may generate
charging events based on the observation of network resource usage. All such
examples would lie within the scope of the present subject matter.
[0097] In one example, in an event where the set of flags are set to be true, then the
10 method [500] may proceed to Steps [508]-[514]. In another example, in an event
the set of flags are set to be false, then the method [500] may proceed to Steps
[516]-[518].
[0098] For example, in an event when the set of flags are set to be true, at step
15 [508], the method [500] comprises converting, by the processing unit [302], the
quota management request to a diameter request.
[0099] In one example, in an event where the set of flags are set to be true, then the
processing unit [302] converts the quota management request to a diameter request.
20 As would be understood, the diameter request may refer to a request based on
diameter protocols which may be one of several defined Authentication,
Authorization, and Accounting (AAA) protocols. Further, the AAA protocol may
be understood to be the activities used by a data network to control access and
services which allows the service provider to restrict access and to ultimately bill
25 the subscriber for services like bandwidth.
[0100] Continuing further, then at step [510], the method [500] leads to sending,
by the transceiver unit [304] to an online charging system (OCS) [404] the diameter
request.
30
26
[0101] Continuing further, then the transceiver unit [304] sends the diameter
request to an online charging system (OCS) [404]. The OCS [404] may be a network
component responsible for event-based charging and credit-control function on
different levels and session-based charging control function on different levels.
5
[0102] Since, the OCS [404] may only support diameter protocol, and may not
support the HTTP, then in such case, conversion is required in order to enable the
OCS [404] to perform the functions.
10 [0103] Then, based on the diameter request, the method [500] leads to step [512],
leading to facilitating, by the processing unit, an execution of a quota management
procedure at the OCS [404], based on the diameter request.
[0104] Continuing further in the event where the set of flags are true, based on the
15 diameter request, the processing unit [302] facilitates an execution of a quota
management procedure at the OCS [404]. In an example, the quota management
procedure may refer to a procedure for managing a quota allocated to the subscriber.
In such example, the quota management procedure may involve updating the quota
used, quota allocated quota removed, quota granted in case of remaining/available
20 quota, etc. By quota management the network entities manage the resources and
services that are consumed by the subscriber, and accordingly manage the usage or
resources and services by the subscriber.
[0105] Based on the execution of the quota management procedure, the OCS [404]
25 may generate a set of details related to the subscriber quota management. The set
of details related to the subscriber quota management may refer to information
associated with available quota, used quota, requested quota, granted quota, charges
associated with the quota, call details record, etc.
27
[0106] Such set of details related to the subscribed quota management may then be
transmitted back to the system [300]. The transceiver unit [304] may receive these
details.
5 [0107] In another example, in an event when the set of flags are set to be false, at
step [516], the method [500] comprises executing, by the processing unit [302], the
quota management procedure in response to the quota management request.
[0108] In another example, in case of an event where the set of flags are set to be
10 false, then the processing unit [302], at the CHF [132] node, may execute the quota
management procedure in response to the quota management request.
[0109] Thereafter, at step [518], the method [500] involves generating, by the
processing unit [302], a set of details related to the subscriber quota management
15 based on the executed quota management procedure.
[0110] Then, based on the executed quota management procedure, the processing
unit [302] generates the set of details related to the subscriber quota management.
20 [0111] It is pertinent to note that, in cases of the flag to be true, the execution of the
quota management procedure and the generation of the set of details may be
performed at the OCS [404]. These details may then be transmitted back to the
system [300], i.e., the CHF [132] node. However, in cases of the flag to be false,
the execution of the quota management procedure and the generation of the set of
25 the details may be performed at the CHF [132] node itself.
[0112] Continuing further, after the CHF [132] node has the set of details related to
the subscriber quota management based on the executed quota management
procedure, the system [300] may transmit said set of details to the network function
30 node [402] among the plurality of network function nodes.
28
[0113] Thereafter, at step [520], the method [500] is terminated.
[0114] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for subscriber quota management in the
5 network. The instructions include executable code which, when executed by one or
more units of a system [300], causes a processing unit [302] of the system [300] to
enable a set of flags. Further, the instructions include executable code which, when
executed, causes a transceiver unit [304] to receive, from a network function node
among a plurality of network function nodes, a quota management request. In an
10 event the set of flags are set as true, the instructions include executable code which,
when executed, causes the processing unit [302] of the system [300] to convert the
quota management request to a diameter request. Further, the instructions include
executable code which, when executed, causes the transceiver unit [304] to send, to
an online charging system (OCS), the diameter request. Further, the instructions
15 include executable code which, when executed, causes the processing unit [302] to
facilitate an execution of a quota management procedure at the OCS [404], based
on the diameter request. Further, the instructions include executable code which,
when executed, causes the transceiver unit [304] to receive, from the OCS [404], a
set of details related to the subscriber quota management based on the executed
20 quota management procedure. In an event the set of flags are set as false, the
instructions include executable code which, when executed, causes the processing
unit [302] to execute the quota management procedure in response to the quota
management request. Further, the instructions include executable code which, when
executed, causes the processing unit [302] to generate a set of details related to the
25 subscriber quota management based on the executed quota management procedure.
[0115] As is evident from the above, the present disclosure provides a technically
advanced solution for subscriber quota management in the network. The present
solution provides a network function which act as gateway between the 4G and 5G
30 communication network. The present disclosure provides a network function, such
as, CHF-Lite, which acts as a CHF and CHF-PC (protocol converter) for
29
interactions with the existing 4G network Diameter protocol-based Online
Charging System (OCS). The network function, such as CHF-Lite, converts the
HTTP/2 messages received from SMF/ PCF in 5G network, to diameter messages
before forwarding them to 4G OCS and vice versa. The CHF (Converged Charging
5 Function) is responsible for creating connections, and Quota management for
subscribers as per the data and resource usage. The Gy and Sy interfaces/flags are
responsible for creating and maintaining peer connections and provide services for
the connected users. The Gy and Sy flags may be enable, so that CHF-Lite converts
HTTP/2 message to Diameter messages and forwards it to 4G OCS. OCS performs
10 the Quota Management and sends response back to CHF-Lite. In another case, the
Gy and Sy flags are disable, the CHF-Lite performs the Quota Management and
sends response back to client nodes.
[0116] While considerable emphasis has been placed herein on the disclosed
15 implementations, it will be appreciated that many implementations can be made and
that many changes can be made to the implementations without departing from the
principles of the present disclosure. These and other changes in the implementations
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
20 and non-limiting.
[0117] Further, in accordance with the present disclosure, it is to be acknowledged
that the functionality described for the various components/units can be
implemented interchangeably. While specific embodiments may disclose a
25 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
arrangements and substitutions of units, provided they achieve the intended
30 functionality described herein, are considered to be encompassed within the scope
of the present disclosure.
30
We Claim:
1. A method for subscriber quota management in a network, the method
comprising:
5 - enabling, by a processing unit [302] at a charging function (CHF) node
[132], a set of flags;
- receiving, by a transceiver unit [304], from a network function node
among a plurality of network function nodes, a quota management
request,
10 wherein:
- in an event the set of flags are set as true, the method comprises:
o converting, by the processing unit [302], the quota
management request to a diameter request;
o sending, by the transceiver unit [304] to an Online Charging
15 System (OCS) [404], the diameter request;
o facilitating, by the processing unit [302], an execution of a
quota management procedure at the OCS [404], based on the
diameter request; and
o receiving, by the transceiver unit [304], from the OCS [404],
20 a set of details related to the subscriber quota management
based on the executed quota management procedure; and
- in an event the set of flags are set as false, the method comprises:
o executing, by the processing unit [302], the quota
management procedure in response to the quota management
25 request; and
o generating, by the processing unit [302], a set of details
related to the subscriber quota management based on the
executed quota management procedure.
30 2. The method as claimed in claim 1, wherein the method further comprises:
31
- sending, by the transceiver unit [304] to the network function node
among the plurality of network function nodes, the set of details
related to the subscriber quota management based on the executed
quota management procedure.
5
3. The method as claimed in claim 1, wherein the plurality of network function
nodes comprises at least one of a session management function (SMF) node
[108], and a policy control function (PCF) node [122].
10 4. A system [300] for subscriber quota management in a network, the system
[300] comprising:
- a processing unit [302] at a charging function (CHF) node [132], the
processing unit [302] configured to enable a set of flags;
- a transceiver unit [304] connected at least to the processing unit
15 [302], the transceiver unit [304] configured to receive, from a
network function node among a plurality of network function nodes,
a quota management request,
wherein, in an event the set of flags are set as true:
o the processing unit [302] is configured to convert
20 the quota management request to a diameter request;
o the transceiver unit [304] is configured to send, to
an online charging system (OCS) [404], the
diameter request;
o the processing unit [302] is further configured to
25 facilitate an execution of a quota management
procedure at the OCS [404], based on the diameter
request; and
o the transceiver unit [304] is further configured to
receive, from the OCS [404], a set of details related
30 to the subscriber quota management based on the
executed quota management procedure; and
32
wherein, in an event the set of flags are set as false:
o the processing unit [302] is further configured to
execute, via the CHF node [132], the quota
management procedure in response to the quota
5 management request; and
o the processing unit [302] is further configured to
generate a set of details related to the subscriber
quota management based on the executed quota
management procedure.
10
5. The system [300] as claimed in claim 4, wherein the processing unit [302]
is further configured to:
- send, to the network function node among the plurality of network
function nodes, a set of details related to the subscriber quota
15 management based on the executed quota management procedure.
6. The system [300] as claimed in claim 4, wherein the plurality of network
function nodes comprises at least one of a session management function
(SMF) node [108], and a policy control function (PCF) node [122].