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 MANAGING A NETWORK
RESOURCE QUOTA ALLOCATION”
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 MANAGING A NETWORK RESOURCE
QUOTA ALLOCATION
FIELD OF INVENTION
5
[0001] Embodiments of the present disclosure generally relate to network resource
management systems. More particularly, embodiments of the present disclosure
relate to methods and systems for managing a network resource quota allocation.
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. 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] Moreover, the 5G core networks are based on Service Based Architecture
(SBA) that is centred around Network Function 5 (NF) services. In said SBA, a set
of interconnected NFs delivers the control plane functionality and common data
repositories of the 5G network, where each NF is authorized to access services of
other NFs. Particularly, each NF can register itself and its supported services to a
Network Repository Function (NRF), which is used by other NFS for the discovery
10 of NF instances and their services. The NRF therefore supports functions such as
maintaining the profiles of the available network function (NF) instances and their
supported services in the 5G core network. Further, the NRF allows NF instances
to discover other NF instances in the 5G core network. Also, the NRF allows the
NF instances to track the status of other NF instances.
15
[0005] The 5G Core Network consists of a multitude of Network Functions (NFs)
such as Policy Control Function (PCF), Binding Support Function (BSF), Charging
Function (CHF), Network Repository Function (NRF), Access and Mobility
Management Function (AMF) and Session Management Function (SMF). They
20 perform their roles in ensuring end to end transfer of data (User Plane Function) as
well as controlling the access and availability of the network resources to the user
(Control Plane Function). The CHF handles control plane signalling and
management functions within the network. When a subscriber's device initiates a
session or transaction that could incur charges (such as premium content access or
25 data usage), the PCF or another relevant network element might query the CHF to
retrieve the subscriber's current spending limit (data limit). The CHF provides the
spending limit information to the PCF. Earlier this information was provided on the
basis of Subscription Permanent Identifier (SUPI). Further, the CHF (Converged
Charging Function) is responsible for creating connections and managing quota for
30 subscribers based on their data and resource usage. It interacts with a database (DB)
to ensure the accuracy of the mentioned services. Earlier this quota management
4
was done on the basis of Subscription Permanent Identifier (SUPI). Since same
SUPI may be assigned to multiple users because of multiple Home Gateway
(HGWs) with multiple MAC IDs may be related to a single SUPI and there may be
a different charging or the Policy Counter ID (PCID) required for that individual
HGW which is assigned to the single SUPI 5 and, therefore there is a need to find
solutions to identify the subscriber’s device based on which quota of the subscriber
may be managed accordingly.
[0006] Thus, there exists an imperative need in the art for managing quota allocated
10 to each HGW subscriber based on the MAC ID associated with each HGW, which
the present disclosure aims to address.
SUMMARY
15 [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.
20 [0008] An aspect of the present disclosure may relate to a method for managing a
network resource quota allocation. The method comprises receiving, by a
transceiver unit, a request from a Network Function (NF), wherein the request
comprises a request type and a Media Access Control Identifier (MAC ID). Further,
based on the MAC ID, the method comprises identifying, by an identification unit,
25 a provisioned user profile associated with a user, wherein the identified user profile
comprises one or more user profile data. Further, based on the received request type
and the identified one or more user profile data, the method comprises processing,
by a processing unit, the request to generate a response. The method further
comprises transmitting, by the transceiver unit, the response to the Network
30 Function (NF), wherein the response is to manage an allocation of the network
resource quota on the NF.
5
[0009] In another exemplary aspect of the present disclosure, the MAC ID is
associated with a Home Gateway (HGW) of the network.
[0010] In another exemplary aspect of the present disclosure, the request is a HTTP
5 request.
[0011] In another exemplary aspect of the present disclosure, the request type is
associated with one of a create new session, an update session, and a terminate
session.
10
[0012] In another exemplary aspect of the present disclosure, the one or more user
profile data of the identified user profile comprises at least one of a HGW status, an
allocated plan, an active Plan, a remaining quota, an allowed rating, a quota
allocation policy, a plan validity, and a policy counter identifier.
15
[0013] In another exemplary aspect of the present disclosure, the method further
comprises determining, by a determination unit, a status of an Online Charging
System (OCS) capability, wherein the status of the OCS capability is one of a true
and a false.
20
[0014] In another exemplary aspect of the present disclosure, on determining that
the status of the OCS capability is true, the step of processing, by the processing
unit, the request to generate the response comprises converting by a converter unit
[310], the received request to a diameter request. The step further comprises
25 transmitting by the transceiver unit, the diameter request to an Online Charging
System (OCS). Also, the step further comprises receiving by the transceiver unit,
from the OCS, the response, wherein the response is generated by the OCS based
on the network resource quota allocation for the NF.
30 [0015] In another exemplary aspect of the present disclosure, on determining that
the status of the OCS capability is false, the step of processing, by the processing
6
unit, the request to generate the response comprises generating, by the processing
unit, the response based on the network resource quota allocation for the NF.
[0016] In another exemplary aspect of the present disclosure, based on the received
request type, the method further comprises 5 performing one or more actions, wherein
the one or more actions comprises one of a creating a new session, updating the
session, and terminating the session.
[0017] In another exemplary aspect of the present disclosure, the method further
10 comprises, based on the processing of the request, updating the one or more user
profile data associated with the provisioned user profile.
[0018] In another exemplary aspect of the present disclosure, the Network Function
(NF) is one of a Session Management Function (SMF) and a Policy Control
15 Function (PCF).
[0019] In another exemplary aspect of the present disclosure, in an event when the
NF is the SMF, the request received from the SMF is a converged charging request
from the SMF, wherein the converged charging request comprises data pertaining
20 to network resources consumed by the user.
[0020] In another exemplary aspect of the present disclosure, in an event when the
NF is the SMF, the response generated by the processing unit comprises data
pertaining to network resources allocated to the user.
25
[0021] In another exemplary aspect of the present disclosure, in an event when the
NF is the SMF, the method further comprises: generating, by the processing unit, a
Call Detail Record (CDR) associated with the received request.
30 [0022] In another exemplary aspect of the present disclosure, in an event when the
NF is the PCF, the request received from the PCF is a spending limit control request,
7
wherein the spending limit control request comprises data pertaining to one or more
policy counter IDs.
[0023] In another exemplary aspect of the present disclosure, in an event when the
NF is the PCF, the response generated 5 by the processing unit comprises data
pertaining to one or more policy counter IDs and corresponding status of each of
the policy counter IDs.
[0024] Another aspect of the present disclosure may relate to a system for
10 managing a network resource quota allocation. The system comprises a transceiver
unit. The transceiver unit is configured to receive a request from a Network
Function (NF), wherein the request comprises a request type and a Media Access
Control Identifier (MAC ID). The system further comprises an identification unit
connected at least to the transceiver unit. The identification is configured to identify
15 a provisioned user profile associated with a user, based on the MAC ID, wherein
the identified provisioned user profile comprises one or more user profile data. The
system further comprises a processing unit connected at least to the identification
unit. The processing unit is configured to process the request to generate a response,
based on the identified user profile and one or more user profile data. The
20 transceiver unit is further configured to transmit the response to the Network
Function (NF), wherein the response is to manage an allocation of the network
resource quota on the NF.
[0025] Yet another aspect of the present disclosure may relate to a non-transitory
25 computer readable storage medium storing instructions for managing a network
resource quota allocation. 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 a request from a Network Function (NF). The request comprises a request
type and a Media Access Control Identifier (MAC ID). Further, the instructions
30 include executable code which, when executed, causes an identification unit to
identify a provisioned user profile associated with a user, based on the MAC ID.
8
The identified user profile comprises one or more user profile data. Further, the
instructions include executable code which, when executed, causes a processing
unit to process the request, based on the received request type and the identified one
or more user profile data, to generate a response. Further, the instructions include
executable code which, when executed, cause 5 the transceiver unit to transmit the
response to the Network Function (NF). The response is to manage an allocation of
the network resource quota on the NF.
OBJECTS OF THE DISCLOSURE
10
[0026] Some of the objects of the present disclosure, which at least one
embodiment disclosed herein satisfies are listed herein below.
[0027] It is an object of the present disclosure to provide a system and a method for
15 managing a network resource quota allocation.
[0028] It is another object of the present disclosure to provide a system and a
method managing quota allocated to each HGW subscriber based on the MAC Id
associated with each HGW.
20
[0029] It is yet another object of the present disclosure to provide a solution that
avoids any disruption to the call-flow and avoid hindering in the functionality of
node.
25 BRIEF DESCRIPTION OF THE DRAWINGS
[0030] The accompanying drawings, which are incorporated herein, and constitute
a part of this disclosure, illustrate exemplary embodiments of the disclosed methods
and systems in which like reference numerals refer to the same parts throughout the
30 different drawings. Components in the drawings are not necessarily to scale,
emphasis instead being placed upon clearly illustrating the principles of the present
9
disclosure. Also, the embodiments shown in the figures are not to be construed as
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 5 components or circuitry commonly used
to implement such components.
[0031] FIG. 1 illustrates an exemplary block diagram representation of 5th
generation core (5GC) network architecture;
10
[0032] 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
exemplary implementation of the present disclosure;
15 [0033] FIG. 3 illustrates an exemplary block diagram of a system for managing a
network resource quota allocation, in accordance with exemplary implementations
of the present disclosure;
[0034] FIG. 4 illustrates a method flow diagram for managing a network resource
20 quota allocation, in accordance with exemplary implementations of the present
disclosure; and
[0035] FIG. 5 illustrate an exemplary environment for managing a network
resource allocation, in accordance with exemplary implementations of the present
25 disclosure.
[0036] The foregoing shall be more apparent from the following more detailed
description of the disclosure.
30 DETAILED DESCRIPTION
10
[0037] 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 5 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.
10 [0038] 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
15 arrangement of elements without departing from the spirit and scope of the
disclosure as set forth.
[0039] Specific details are given in the following description to provide a thorough
understanding of the embodiments. However, it will be understood by one of
20 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.
25 [0040] It should be noted that the terms "first", "second", "primary", "secondary",
"target" and the like, herein do not denote any order, ranking, quantity, or
importance, but rather are used to distinguish one element from another.
[0041] Also, it is noted that individual embodiments may be described as a process
30 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
11
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.
5
[0042] 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
10 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
15 similar to the term “comprising” as an open transition word—without precluding
any additional or other elements.
[0043] As used herein, a “processing unit” or “processor” or “operating processor”
includes one or more processors, wherein processor refers to any logic circuitry for
20 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
25 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.
30 [0044] 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”,
12
“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-5 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.
10
[0045] 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”),
15 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.
20 [0046] 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 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
25 called.
[0047] 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
30 digital signal processor (DSP), a plurality of microprocessors, one or more
microprocessors in association with a DSP core, a controller, a microcontroller,
13
Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array
circuits (FPGA), any other type of integrated circuits, etc.
[0048] As used herein the transceiver unit include at least one receiver and at least
one transmitter configured respectively 5 for receiving and transmitting data, signals,
information or a combination thereof between units/components within the system
and/or connected with the system.
[0049] As discussed in the background section, the current known solutions have
10 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 managing a network resource quota allocation.
[0050] FIG. 1 illustrates an exemplary block diagram representation of 5th
15 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],
20 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
25 User Plane Function (UPF) [128], a data network (DN) [130] and a charging
function. It may be noted that all the components may be 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.
30 [0051] Radio Access Network (RAN) [104] is the part of a mobile
telecommunications system that connects user equipment (UE) [102] to the core
14
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.
[0052] Access and Mobility Management 5 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.
10 [0053] 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.
15 [0054] 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.
20 [0055] 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.
[0056] Network Slice Specific Authentication and Authorization Function
25 (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.
[0057] Network Slice Selection Function (NSSF) [116] is a network function
30 responsible for selecting the appropriate network slice for a UE based on factors
such as subscription, requested services, and network policies.
15
[0058] 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.
5
[0059] 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.
10 [0060] Policy Control Function (PCF) [122] is a network function responsible for
policy control decisions, such as QoS, charging, and access control, based on
subscriber information and network policies.
[0061] Unified Data Management (UDM) [124] is a network function that
15 centralizes the management of subscriber data, including authentication,
authorization, and subscription information.
[0062] Application Function (AF) [126] is a network function that represents
external applications interfacing with the 5G core network to access network
20 capabilities and services.
[0063] User Plane Function (UPF) [128] is a network function responsible for
handling user data traffic, including packet routing, forwarding, and QoS
enforcement.
25
[0064] 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.
30 [0065] Charging Function (CHF) [132] may refer to a network function
responsible for converged online charging and offline charging functionalities. The
16
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 Call
5 Detail Record (CDR).
[0066] 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
10 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
15 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
20 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
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.
25 1. The UPF [128] is connected with the DN [130] via the interface denoted as (N6)
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
30 [128] is connected with other UPF [128] via the interface denoted as (N9) in FIG.
1.
17
[0067] The interfaces such as Nnssf, Nnef, Nnrf, Npcf, Nudm, Naf, Nnssaaf, Nausf,
Namf, Nsmf, N9, N6, N4, N3, N2, and N1 can be referred to as a communication
channel between one or more functions or modules for enabling exchange of data
or information be 5 tween such functions or modules, and network entities.
[0068] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
upon which the features of the present disclosure may be implemented in
accordance with exemplary implementation of the present disclosure. In an
10 implementation, the computing device [200] may also implement a method for
managing a network resource quota allocation utilising the system [300]. In another
implementation, the computing device [200] itself implements the method for
managing the network resource quota allocation using one or more units configured
within the computing device [200], wherein said one or more units are capable of
15 implementing the features as disclosed in the present disclosure.
[0069] 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
20 processor [204] may be, for example, a general-purpose microprocessor. The
computing device [200] may also include a main memory [206], such as a randomaccess
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
25 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 specialpurpose
machine that is customized to perform the operations specified in the
instructions. The computing device [200] further includes a read only memory
30 (ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
18
[0070] 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 5 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
bus [202] for communicating information and command selections to the processor
10 [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
of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow
15 the device to specify positions in a plane.
[0071] 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
20 or programs the computing device [200] to be a special-purpose machine.
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,
25 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.
30
19
[0072] 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
integrated services di 5 gital 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
10 implementation, the communication interface [218] sends and receives electrical,
electromagnetic or optical signals that carry digital data streams representing
various types of information.
[0073] The computing device [200] can send messages and receive data, including
15 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,
20 and/or stored in the storage device [210], or other non-volatile storage for later
execution.
[0074] Referring to FIG. 3, an exemplary block diagram of a system [300] for
managing a network resource quota allocation, is shown, in accordance with the
25 exemplary implementations of the present disclosure. In one exemplary
implementation of the present disclosure, the system [300] may be implemented as
or within the Charging Function (CHF) [132], as described in conjunction with
FIG.1. In such cases, the system [300], among other functionalities, may be
responsible to perform the functions of the CHF [132].
30
20
[0075] In another example, the system [300] may be in communication with
multiple network entities, and/or components which may be known to a person
skilled in the art. Such network entities and/or components have not been depicted
in FIG. 3, and not explained here for the sake of brevity.
5
[0076] As depicted in FIG. 3, the system [300] may include at least one transceiver
unit [302], at least one identification unit [304], at least one processing unit [306],
at least one determination unit [308], and at least one converter unit [310]. In cases,
where the system [300] is implemented as a CHF [132], the aforementioned units,
10 may be a part of the CHF [132].
[0077] Continuing further, all of the components/ units of the system [300] may be
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
15 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 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.
20 The system [300] may be a part of the user device [102]/ or may be independent of
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.
25
[0078] The system [300] is configured for managing a network resource quota
allocation, with the help of the interconnection between the components/units of
the system [300].
30 [0079] As would be understood, the network resource quota allocation may refer to
the allocation or assignment of specific limits or boundaries to various resources
21
available within the network such as bandwidth, storage, processing power, and
memory and setting such limits or boundaries for managing congestion, prioritizing
traffic.
[0080] In operation, for managing 5 a network resource quota allocation, the
transceiver unit [302] may receive a request from a Network Function (NF). It one
example, the request may include a request type and a Media Access Control
Identifier (MAC ID). The request from the NF may refer to a request for managing
a network resource quota allocation. The MAC ID may refer to a unique identifier
10 used for identifying a device on a network, and, for example, may be a 12-digit
hexadecimal number.
[0081] In one of the implementations of the present disclosure, the Network
Function (NF) is one of a Session Management Function (SMF) and a Policy
15 Control Function (PCF). The SMF and the PCF may be understood as the SMF
[108] and the PCF [122] as described in conjunction with FIG. 1. 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 as a Charging Trigger
20 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.
[0082] Continuing further, in an implementation of the present disclosure, the MAC
25 ID may be associated with a Home Gateway (HGW) of the network. In an example,
the home gateway may refer to the network device which may be used for
connecting the telecommunication network to the internet, and may include a router,
and access points. The HGW may be a component used for managing network
traffic, assigning IP addressed to devices, and also provides certain security
30 features.
22
[0083] In certain implementations of the present disclosure, the request is a
hypertext transfer protocol (HTTP) request. As would be understood, the HTTP
request may be a message sent from a client to a server for requesting a resource
associated with network resource quota allocation.
5
[0084] Also, in certain other implementations of the present disclosure, the request
type may be associated with one of a create new session, an update session, and a
terminate session. In order to manage the network resource quota allocation, the
request may comprise the request type which may contain a command related to
10 required action for managing the network resource quota. Accordingly, the request
type may determine one or more actions such as creation of a new session, updating
of the existing session, and termination of the existing session. The create new
session may refer to a command for creating new session. The update session may
refer to a command for updating the existing session. The terminate session may
15 refer to a command for terminating the existing session.
[0085] In an example, for creating new session, a service operation may be
performed such as a Nchf_ConvergedCharging_Create service operation which
provides means for NF to request quotas for service delivery or initial report of
20 service usage. Similarly, in another example, for updating the existing session, a
service operation may be performed such as a Nchf_ConvergedCharging_Update
service operation which provides means for NF to update the charging data. Also,
in another example, for terminating the existing session, a service operation may be
performed such as a Nchf_ConvergedCharging_Release service operation which
25 provides means for NF to terminate charging Session.
[0086] Also, in an example, for creating new session, the NF service consumer may
send an HTTP POST request to create a subscription for retrieval of the policy
counter status and spending limit reporting. Similarly, in another example, for
30 updating the existing session, the NF service consumer may send an HTTP PUT
request to modify the subscription for retrieval of the policy counter status and
23
spending limit reporting. Also, in another example, for terminating the existing
session, a service operation may be performed such as
Nchf_SpendingLimitControl_Unsubscribe service operation, in which the NF
service consumer may send an HTTP DELETE request, along with a subscription
Id for identification of the 5 existing subscription to be deleted, to remove the
corresponding subscription.
[0087] Continuing further, after the request is received, then the identification unit
[304] identifies a provisioned user profile associated with a user, based on the MAC
10 ID. The identified provisioned user profile comprises one or more user profile data.
The user may refer to a user equipment for which the network resource data
allocation is required. Further, the provisioned user profile may refer to a profile of
the user which may be identified based on a subscription permanent identifier
(SUPI). In the present case, the user is identified using the MAC ID of the home
15 gateway instead of identifying using the SUPI. It may be noted that the identified
provisioned user profile may refer to the stored profile of the user which may
comprise the one or more user profile data. The one or more user profile data may
refer to the information associated with the user.
20 [0088] Further, in various implementations of the present disclosure, the one or
more user profile data of the identified user profile may comprise at least one of a
HGW status, an allocated plan, an active Plan, a remaining quota, an allowed rating,
a quota allocation policy, a plan validity, and a policy counter identifier.
25 [0089] As would be understood, the HGW status may refer to the operational status
and connectivity of the home gateway. The allocated plan may refer to a
subscription plan which has been subscribed by the user. The active plan may refer
to the subscription plan which is currently active. The remaining quota may refer to
a remaining quantity of data traffic which the user was allocated based on the
30 subscription plan. The allowed rating may refer to a rating associated with the usage
of the network resources by the user. The quota allocation policy may refer to a set
24
of rules which may be referred to during the allocation of the quota associated with
the utilisation of data traffic by the user. The plan validity may refer to a time period
for which the subscription plan remains active. The policy counter identifier (PCID)
may refer to a unique identifier which may be assigned to different policies which
may be generated by the PCF [122]. Further, 5 in other words, the PCID may refer a
reference to a policy counter which may be a mechanism within the OCS [134] to
track spending applicable for a subscriber.
[0090] After the provisioned user profile and the one or more user profile data are
10 identified, then the processing unit [306] processes the request to generate a
response, based on the identified user profile and one or more user profile data. The
processing of the request results in generating a response which may comprise the
information associated with network resource allocation quota.
15 [0091] In one of the implementations of the present disclosure, the determination
unit [308] may be configured to determine a status of an Online Charging System
(OCS) capability, wherein the status of the OCS capability is one of a true and a
false. The OCS capability may refer to a capability of a Charging function (CHF)
to communicate with the OCS [134]. The OCS [134] may be responsible for event20
based charging and credit-control function on different levels and session-based
charging control function on different levels. The OCS capability may be indicated
by a flag or a Boolean variable which may indicate a capability (in case of true) and
an incapability (in case of false) of communicating with the OCS [134].
25 [0092] In one example, on determining that the status of the OCS capability is true,
to process the request to generate the response, the converter unit [310] converts
the received request to a diameter request. Then the transceiver unit [302] transmits
the diameter request (DIA) to an Online Charging System (OCS) [134]. Thereafter,
the transceiver unit [302] receives from the OCS [134], the response. The response
30 may be generated by the OCS [134] based on the network resource quota allocation
for the NF. It may be understood, that the diameter request may refer to a request
25
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
the subscriber for services like 5 bandwidth. Since, the OCS [134] may only support
diameter protocol, and may not support the HTTP, then in such case, conversion is
required in order to enable the OCS [134] to perform the functions.
[0093] In another example, on determining that the status of the OCS capability is
10 false, then the processing unit [306] may be configured to generate the response
based on the network resource quota allocation for the NF. The response may be
generated to process the request to generate the response.
[0094] In one of the various implementations of the present disclosure, the
15 processing unit [306] may also perform one or more actions based on the received
request type. The one or more actions comprises one of a creating a new session,
updating the session, and terminating the session. As would be understood, the one
or more actions may refer to the actions performed by the CHF [132] based on the
request which may be creation of the new session, updating the session and
20 terminating the session as provided above in detail.
[0095] In further implementations of the present disclosure, the processing unit
[302] may update the one or more user profile data associated with the provisioned
user profile, based on the processing of the request. For example, once the network
25 resource quota has been allocated to the NF, the processing unit [302] may update
the user profile data, as stored in the provisioned user profile. Such updation of the
data may allow the system [300] to effectively allocate network quota, in cases
when a subsequent request is received from the NF.
26
[0096] Continuing further, the transceiver unit [302] transmits the response to the
Network Function (NF). The response may include information, which may be used
to manage an allocation of the network resource quota on the NF.
[0097] As described previously, 5 in the context of the present invention, the Network
Function (NF) may be one of a Session Management Function (SMF) [108] and a
Policy Control Function (PCF) [122].
[0098] In one example, in an event when the NF is the SMF [108], the request
10 received from the SMF [108] is a converged charging request from the SMF [108].
The converged charging request may comprise data pertaining to network resources
consumed by the user. Further, it may be noted that the converged charging request
may be a request for converged charging for both events and sessions in cases of
Converged Event based charging as well as Converged Session based charging.
15 Also, it may be noted that the network resources consumed by the user may refer
to the data traffic which may be used by user during a session.
[0099] Further, when the NF is the SMF [108], the response generated by the
processing unit [306] may comprise data pertaining to network resources allocated
20 to the user. The network resources allocated to the user may refer to the data which
has been allocated by the user for a particular session.
[0100] Also, when the NF is the SMF [108], the processing unit [306] may also
generate a Call Detail Record (CDR) associated with the received request. As would
25 be understood, the Call Detail Record (CDR) may refer to a formatted collection of
information about a chargeable event (e.g. time of call set-up, duration of the call,
amount of data transferred, etc) for use in billing and accounting.
[0101] In another example, in an event when the NF is the PCF [122], the request
30 received from the PCF [122] is a spending limit control request, wherein the
spending limit control request comprises data pertaining to one or more policy
27
counter IDs. As would be understood, the spending limit control request may refer
to a request for controlling a spending limit by controlling the usage limit of a policy
counter (e.g. monetary, volume, duration) that a subscriber is allowed to consume.
[0102] Also, when the NF 5 is the PCF [122], the response generated by the
processing unit [306] may comprise data pertaining to one or more policy counter
IDs and corresponding status of each of the policy counter IDs. As would be
understood, the status of the PCID may be a label whose values are not standardized
and that is associated with a policy counter's value relative to the spending limit(s)
10 (the number of possible policy counter status values for a policy counter is one
greater than the number of thresholds associated with that policy counter, i.e., policy
counter status values describe the status around the thresholds). This is used to
convey information relating to subscriber spending from OCS to PCRF. Specific
labels are configured jointly in OCS and PCRF.
15
[0103] Referring to FIG. 4, an exemplary method flow diagram [400] for managing
a network resource quota allocation, in accordance with exemplary
implementations of the present disclosure is shown. In an implementation the
method [400] is performed by the system [300]. Further, in an implementation, the
20 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].
[0104] Initially, for managing the network resource quota allocation, the method
[400] at step [404] comprises receiving, by a transceiver unit [302], a request from
25 a Network Function (NF), wherein the request comprises a request type and a Media
Access Control Identifier (MAC ID).
[0105] In operation, for managing a network resource quota allocation, the
transceiver unit [302] may receive a request from a Network Function (NF). It one
30 example, the request may include a request type and a Media Access Control
28
Identifier (MAC ID). The request from the NF may refer to a request for managing
a network resource quota allocation.
[0106] In one of the implementations of the present disclosure, the Network
Function (NF) is one of a Session Management 5 Function (SMF) and a Policy
Control Function (PCF).
[0107] Continuing further, in an implementation of the present disclosure, the MAC
ID may be associated with a Home Gateway (HGW) of the network.
10
[0108] In certain implementations of the present disclosure, the request is a
hypertext transfer protocol (HTTP) request.
[0109] Also, in certain other implementations of the present disclosure, the request
15 type may be associated with one of a create new session, an update session, and a
terminate session. In order to manage the network resource quota allocation, the
request may comprise the request type which may contain a command related to
required action for managing the network resource quota. Accordingly, the request
type may determine one or more actions such as creation of a new session, updating
20 of the existing session, and termination of the existing session. The create new
session may refer to a command for creating new session. The update session may
refer to a command for updating the existing session. The terminate session may
refer to a command for terminating the existing session.
25 [0110] Based on the MAC ID, at step [406], the method [400] comprises
identifying, by an identification unit [304], a provisioned user profile associated
with a user, wherein the identified user profile comprises one or more user profile
data.
30 [0111] Continuing further, after the request is received, then the identification unit
[304] identifies a provisioned user profile associated with a user, based on the MAC
29
ID. The identified provisioned user profile comprises one or more user profile data.
The user may refer to a user equipment for which the network resource data
allocation is required. Further, the provisioned user profile may refer to a profile of
the user which may be identified based on a subscription permanent identifier
(SUPI). In the present case, 5 the user is identified using the MAC ID of the home
gateway instead of identifying using the SUPI. It may be noted that the identified
provisioned user profile may refer to the stored profile of the user which may
comprise the one or more user profile data. The one or more user profile data may
refer to the information associated with the user.
10
[0112] Further, in various implementations of the present disclosure, the one or
more user profile data of the identified user profile may comprise at least one of a
HGW status, an allocated plan, an active Plan, a remaining quota, an allowed rating,
a quota allocation policy, a plan validity, and a policy counter identifier.
15
[0113] Based on the received request type and the identified one or more user
profile data, at step [408], the method [400] comprises processing, by a processing
unit [306], the request to generate a response.
20 [0114] After the provisioned user profile and the one or more user profile data are
identified, then the processing unit [306] processes the request to generate a
response, based on the identified user profile and one or more user profile data. The
processing of the request results in generating a response which may comprise the
information associated with network resource allocation quota.
25
[0115] In one of the implementations of the present disclosure, the determination
unit [308] may be configured to determine a status of an Online Charging System
(OCS) capability, wherein the status of the OCS capability is one of a true and a
false. The OCS [134] capability may refer to a capability of an Charging function
30 (CHF) to communicate with the OCS [134]. The OCS [134] may be responsible for
event-based charging and credit-control function on different levels and session30
based charging control function on different levels. The OCS capability may be
indicated by a flag or a Boolean variable which may indicate a capability (in case
of true) and an incapability (in case of false) of communicating with the OCS [134].
[0116] In one example, on determining 5 that the status of the OCS capability is true,
to process the request to generate the response, the converter unit [310] converts
the received request to a diameter request. Then the transceiver unit [302] transmits
the diameter request to an Online Charging System (OCS) [134]. Thereafter, the
transceiver unit [302] may receive the response from the OCS [134]. The response
10 may be generated by the OCS [134] based on the network resource quota allocation
for the NF.
[0117] In another example, on determining that the status of the OCS capability is
false, then the processing unit [306] may be configured to generate the response
15 based on the network resource quota allocation for the NF. The response may be
generated to process the request to generate the response.
[0118] In one of the various implementations of the present disclosure, the
processing unit [306] may also perform one or more actions based on the received
20 request type. The one or more actions comprises one of a creating a new session,
updating the session, and terminating the session. As would be understood, the one
or more actions may refer to the actions performed by the CHF [132] based on the
request which may be creation of the new session, updating the session and
terminating the session as provided above in detail.
25
[0119] In further implementations of the present disclosure, the processing unit
[302] may update the one or more user profile data associated with the provisioned
user profile, based on the processing of the request. For example, once the network
resource quota has been allocated to the NF, the processing unit [302] may update
30 the user profile data, as stored in the provisioned user profile. Such updation of the
31
data may allow the system [300] to effectively allocate network quota, in cases
when a subsequent request is received from the NF.
[0120] At step [410], the method [400] comprises transmitting, by the transceiver
unit [302], the response to the Network 5 Function (NF), wherein the response is to
manage an allocation of the network resource quota on the NF.
[0121] Continuing further, the transceiver unit [302] transmits the response to the
Network Function (NF). The response may include information, which may be used
10 to manage an allocation of the network resource quota on the NF.
[0122] Thereafter, at step [412], the method [400] is terminated.
[0123] FIG. 5 illustrate an exemplary environment [500] for managing a network
15 resource allocation, in accordance with exemplary implementations of the present
disclosure.
[0124] Initially, at step [502], the Network Function (NF) such as the SMF [108]
or the PCF [122], sends a request to the CHF [132]. In other words, the CHF
20 receives the request from either the SMF [108] or the PCF [122]. It may be noted
that the request may comprise information associated with the request type and the
Media Access Control Identifier (MAC ID). In case, the SMF [108] sends the
request, then the request will be sent as the Converged Charging request towards
the CHF [132] along with information associated with the MAC ID of the HGW. In
25 case the PCF [122] sends the request, then the request will be sent as the Spending
Limit Control request towards the CHF [132] along with information associated
with the MAC ID of HGW for either specific or all PCIDs.
[0125] Then in case the request is an initial request, the CHF [132] will create the
30 new session in case of the NF being SMF [108], and create a spending limit session
32
in case of the NF being PCF [122]. Also, in case of request type being update or
terminate request then the CHF [132] may update/ terminate the existing session.
[0126] Further, at step [504], the CHF [132] may use the MAC ID received in the
request to identify a provisioned user profile 5 comprising one or more user profile
data associated with a user. Then the CHF may check the one or more user profile
data like HGW status, Allocated/Active Plan, Remaining Quota, Allowed Ratings,
Quota allocation policy, Plan Validity, Policy Counter IDs etc.
10 [0127] Further, based on the received request type and the identified one or more
user profile data, the request is processed at the CHF [132] to generate a response.
[0128] The CHF [132] is required to send a response back to the SMF [108] or the
PCF [122] after processing the request. In case of the request sent by the SMF [108],
15 the request may also include the consumed units of resources, and allocated units
of resources based on which the CHF [132] will update the one or more user profile
data such as used quota, remaining quota, Policy Counter ID status etc. Also, in
case of the PCF [122] sending the request, then the CHF [132] will update the
PCIDs, value and status.
20
[0129] Additionally in case if received request has a request type as the terminate
session, then the CHF [132] will remove the session before sending the response
back to SMF [108]. If the received request was associated with termination of the
PCF [122], then the CHF [132] will remove the associated spending limit
25 subscription. Also, the CHF will create the Call Detail Record (CDR) for the
received request.
[0130] In case of change in status of the PCIDs for individual HGW and the
corresponding Spending limit session, then the CHF [132] may send a notification
30 in the response towards the PCF [122] and also contain the updated Policy Counter
ID status (after the update of the one or more user profile data).
33
[0131] Accordingly, after the response has been generated, then at step [506], the
CHF [132] transmits the response to the respective network function (NF) i.e. either
the SMF [108] or the PCF [122]. The response may be then used to manage an
allocation of 5 the network resource quota on the respective NF.
[0132] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for managing a network resource quota
allocation. The instructions include executable code which, when executed by one
10 or more units of a system [300], causes a transceiver unit of the system to receive a
request from a Network Function (NF). The request comprises a request type and a
Media Access Control Identifier (MAC ID). Further, the instructions include
executable code which, when executed, causes an identification unit to identify a
provisioned user profile associated with a user, based on the MAC ID. The
15 identified user profile comprises one or more user profile data. Further, the
instructions include executable code which, when executed, causes a processing
unit to process the request, based on the received request type and the identified one
or more user profile data, to generate a response. Further, the instructions include
executable code which, when executed, cause the transceiver unit to transmit the
20 response to the Network Function (NF). The response is to manage an allocation of
the network resource quota on the NF.
[0133] As is evident from the above, the present disclosure provides a technically
advanced solution for managing a network resource quota allocation. The present
25 solution enables monitoring and handling request races which results in minimizing
the probability of exceptions occurring in the network. Further, the present solution
enables data consistency since, the present solution provides creation of consistent
data as the requests hit and access services in order of expectation. If terminate
requests are not handled as provided in the present disclosure, then there may be a
30 situation where it might lead to update of a non-existing session which causes
inconsistency and request loss. Accordingly, the present solution provided data
34
consistency. Further, the present solution avoids disruption of the call flow and
avoids causing any hindrance of the functionalities of the node. The implementation
of the present disclosure solves this problem by improving the call-flow success.
Further, the present solution provides conversion of the http messages to diameter
5 messages, absence of which may lead to improper quota management.
[0134] While considerable emphasis has been placed herein on the disclosed
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
10 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
and non-limiting.
15 [0135] 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
particular functionality of these units for clarity, it is recognized that various
configurations and combinations thereof are within the scope of the disclosure. The
20 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
functionality described herein, are considered to be encompassed within the scope
of the present disclosure.
35
We Claim:
1. A method for managing a network resource quota allocation, the method
comprising:
- receiving, by a transceiver 5 unit [302], a request from a Network
Function (NF), wherein the request comprises a request type and a
Media Access Control Identifier (MAC ID);
- based on the MAC ID, identifying, by an identification unit [304], a
provisioned user profile associated with a user, wherein the identified
10 user profile comprises one or more user profile data;
- based on the received request type and the identified one or more user
profile data, processing, by a processing unit [306], the request to
generate a response; and
- transmitting, by the transceiver unit [302], the response to the Network
15 Function (NF), wherein the response is to manage an allocation of the
network resource quota on the NF.
2. The method as claimed in claim 1, wherein the MAC ID is associated with a
Home Gateway (HGW) of the network.
20
3. The method as claimed in claim 1, wherein the request is a HTTP request.
4. The method as claimed in claim 1, wherein the request type is associated with
one of a create new session, an update session, and a terminate session.
25
5. The method as claimed in claim 1, wherein the one or more user profile data
of the identified user profile comprises at least one of a HGW status, an
allocated plan, an active Plan, a remaining quota, an allowed rating, a quota
allocation policy, a plan validity, and a policy counter identifier.
30
36
6. The method as claimed in claim 1, further comprising: determining, by a
determination unit [308], a status of an Online Charging System (OCS)
capability, wherein the status of the OCS capability is one of a true and a
false.
5
7. The method as claimed in claim 6, on determining that the status of the OCS
capability is true, the step of processing, by the processing unit [306], the
request to generate the response comprises:
- converting by a converter unit [310], the received request to a diameter
10 request;
- transmitting by the transceiver unit [302], the diameter request to an
Online Charging System (OCS) [134]; and
- receiving by the transceiver unit [302], from the OCS [134] the
response, wherein the response is generated by the OCS [134] based on
15 the network resource quota allocation for the NF.
8. The method as claimed in claim 6, on determining that the status of the OCS
capability is false, the step of processing, by the processing unit [306], the
request to generate the response comprises:
20 - generating, by the processing unit [306], the response based on the
network resource quota allocation for the NF.
9. The method as claimed in claim 1, further comprising
- based on the received request type, performing one or more actions,
25 wherein the one or more actions comprises one of a creating a new
session, updating the session, and terminating the session.
10. The method as claimed in claim 1, further comprising:
- based on the processing of the request, updating the one or more user
30 profile data associated with the provisioned user profile.
37
11. The method as claimed in claim 1, wherein the Network Function (NF) is one
of a Session Management Function (SMF) [108] and a Policy Control
Function (PCF) [122].
12. The method as claimed in claim 11, in an event 5 when the NF is the SMF
[108], the request received from the SMF [108] is a converged charging
request from the SMF [108], wherein the converged charging request
comprises data pertaining to network resources consumed by the user.
10 13. The method as claimed in claim 11, in an event when the NF is the SMF
[108], the response generated by the processing unit [306] comprises data
pertaining to network resources allocated to the user.
14. The method as claimed in claim 11, in an event when the NF is the SMF
15 [108], the method further comprises: generating, by the processing unit [306],
a Call Detail Record (CDR) associated with the received request
15. The method as claimed in claim 11, in an event when the NF is the PCF [122],
the request received from the PCF [122] is a spending limit control request,
20 wherein the spending limit control request comprises data pertaining to one
or more policy counter IDs.
16. The method as claimed in claim 11, in an event when the NF is the PCF [122],
the response generated by the processing unit [306] comprises data pertaining
25 to one or more policy counter IDs and corresponding status of each of the
policy counter IDs.
17. A system [300] for managing a network resource quota allocation, the system
[300] comprising:
38
- a transceiver unit [302] configured to receive a request from a Network
Function (NF), wherein the request comprises a request type and a
Media Access Control Identifier (MAC ID);
- an identification unit [304] connected at least to the transceiver unit
[302], the identification u 5 nit [304] configured to identify a provisioned
user profile associated with a user, based on the MAC ID, wherein the
identified provisioned user profile comprises one or more user profile
data;
- a processing unit [306] connected at least to the identification unit
10 [304], the processing unit [306] configured to process the request to
generate a response, based on the identified user profile and one or more
user profile data;
- the transceiver unit [302] further configured to transmit the response to
the Network Function (NF), wherein the response is to manage an
15 allocation of the network resource quota on the NF.
18. The system [300] as claimed in claim 17, wherein the MAC ID is associated
with a Home Gateway (HGW) of the network.
20 19. The system [300] as claimed in claim 17, wherein the request is a HTTP
request.
20. The system [300] as claimed in claim 17, wherein the request type is
associated with one of a create new session, an update session, and a terminate
25 session.
21. The system [300] as claimed in claim 17, wherein the one or more user profile
data of the identified user profile comprises at least one of a HGW status, an
allocated plan, an active Plan, a remaining quota, an allowed rating, a quota
30 allocation policy, a plan validity, and a policy counter identifier.
39
22. The system [300] as claimed in claim 17, further comprising a determination
unit [308] connected at least to the processing unit [306], the determination
unit [308] configured to determine a status of an Online Charging System
(OCS) capability, wherein the status of 5 the OCS capability is one of a true
and a false.
23. The system [300] as claimed in claim 22, on determining that the status of the
OCS capability is true, to process the request to generate the response, the
10 system [300] further comprises:
- a converter unit [310] connected at least to the transceiver unit [302],
the converter unit [310] configured to convert the received request to a
diameter request;
- the transceiver unit [302] further configured to transmit the diameter
15 request to an Online Charging System (OCS) [134]; and
- the transceiver unit [302] further configured to receive from the OCS
[134], the response, wherein the response is generated by the OCS [134]
based on the network resource quota allocation for the NF.
20 24. The system [300] as claimed in claim 22, on determining that the status of the
OCS capability is false, to process, the request to generate the response, the
system [300] further comprises:
- the processing unit [306] further configured to generate the response
based on the network resource quota allocation for the NF.
25
25. The system [300] as claimed in claim 17, wherein the processing unit [306]
is further configured to, based on the received request type, perform one or
more actions, wherein the one or more actions comprises one of a creating a
new session, updating the session, and terminating the session.
30
40
26. The system [300] as claimed in claim 17, wherein the processing unit [302]
is further configured to, based on the processing of the request, update the one
or more user profile data associated with the provisioned user profile.
27. The system [300] as claimed in claim 5 17, wherein the Network Function (NF)
is one of a Session Management Function (SMF) [108] and a Policy Control
Function (PCF) [122].
28. The system [300] as claimed in claim 27, in an event when the NF is the SMF
10 [108], the request received from the SMF [108] is a converged charging
request from the SMF [108], wherein the converged charging request
comprises data pertaining to network resources consumed by the user.
29. The system [300] as claimed in claim 27, in an event when the NF is the SMF
15 [108], the response generated by the processing unit [306] comprises data
pertaining to network resources allocated to the user.
30. The system [300] as claimed in claim 27, in an event when the NF is the SMF
[108], the processing unit [306] is further configured to generate a Call Detail
20 Records (CDR) associated with the received request.
31. The system [300] as claimed in claim 27, in an event when the NF is the PCF
[122], the request received from the PCF [122] is a spending limit control
request, wherein the spending limit control request comprises data pertaining
25 to one or more policy counter IDs.
32. The system [300] as claimed in claim 27, in an event when the NF is the PCF
[122], the response generated by the processing unit [306] comprises data
pertaining to one or more policy counter IDs and corresponding status of each 30 of the policy counter IDs.