Abstract: The present disclosure relates to method and system for allocating a network resource quota to a User Equipment (UE) in a network the method comprising receiving an attach request from the UE, wherein the attach request comprises at least a resource allocation request associated with the UE. The method comprises transmitting the resource allocation request to a Charging function (CHF) in the network. The method comprises based on the transmitted resource allocation request, receiving an error response from the CHF, wherein the error response comprises an error code corresponding to an error occurred in the network. The method comprises initiating a credit control failure handling (CCFH) based on the error code corresponding to the error occurred in the network. The method comprises allocating first network resource quota to the UE, wherein the first network resource quota comprises a pre-configured quantity of network resources usable by the UE. [FIG. 3]
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 ALLOCATING A NETWORK RESOURCE QUOTA TO A USER EQUIPMENT (UE) 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.
METHOD AND SYSTEM FOR ALLOCATING A NETWORK RESOURCE QUOTA TO A USER EQUIPMENT (UE) IN A NETWORK
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to network performance management systems. More particularly, embodiments of the present disclosure relate to method and system for for allocating a network resource quota to a User Equipment (UE) in a network.
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 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 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 (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless
communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] Currently, the interaction between the SMF and the CHF for quota assignments is carried out over the N40 interface using the http2 protocol. Additionally, CHF interacts with the Online Charging System (OCS) based on the SMF's request. However, in the event of any errors occurring at the network or the OCS level, the CHF sends a negative response to the SMF.
[0005] Further, over a period of time various solutions have been developed to improve the performance of communication devices and to assign quota to a user. However, there are certain challenges with the existing solutions. The current system faces certain technical limitations in the interaction between the Session Management Function (SMF) and the Charging Gateway Function (CHF) for quota assignments. This interaction takes place over the N40 interface utilizing the http2 protocol. However, this approach has certain constraints that affect its effectiveness. For instance, the http2 protocol may not be able to handle large volumes of data efficiently, leading to delays or even failures in the communication process. Moreover, the current system lacks robust error handling mechanisms, which means that any errors occurring at the network or Online Charging System (OCS) level can result in a negative response being sent from the CHF to the SMF, without providing sufficient details or alternative solutions.
[0006] Thus, there exists an imperative need in the art to assign quota to a user, which the present disclosure aims to address.
SUMMARY
[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.
[0008] An aspect of the present disclosure may relate to a method for allocating a network resource quota to a User Equipment (UE) in a network the method comprising receiving, by a transceiver unit, an attach request from the UE, wherein the attach request comprises at least a resource allocation request associated with the UE, and wherein the resource allocation request is to request a quantity of network resources usable by the UE. The method comprises transmitting, by the transceiver, the resource allocation request to a Charging function (CHF) in the network. The method comprises based on the transmitted resource allocation request, receiving, by the transceiver unit, an error response from the CHF, wherein the error response comprises an error code corresponding to an error occurred in the network. The method comprises initiating, by an initiation unit, a credit control failure handling (CCFH) based on the error code corresponding to the error occurred in the network. The method comprises allocating, by an allocation unit, a first network resource quota to the UE, wherein the first network resource quota comprises a pre-configured quantity of network resources usable by the UE. The pre-configured quantity of network resources refers herewith to a predetermined and fixed amount of network resources allocated to a user, device, or application. The pre-configured quantity of network resources can encompass various types of resources essential for network functionality. This includes bandwidth, data usage, connection time and quality of Service (QoS) parameters, which define the priority and performance level of the connection.
[0009] In an exemplary aspect of the present disclosure, the resource allocation request is transmitted to the Charging function (CHF), over a N40 interface, based on a HTTP2 network protocol.
[0010] In an exemplary aspect of the present disclosure, the error response is received from the Charging function (CHF), over a N40 interface, based on a HTTP2 network protocol.
[0011] In an exemplary aspect of the present disclosure, the error response corresponding to the error occurred in the network comprises at least one of a negative response and a time out response.
[0012] In an exemplary aspect of the present disclosure, the first network resource quota is allocated to the UE for a pre-defined time duration.
[0013] In an exemplary aspect of the present disclosure, the first network resource quota is allocated to the UE, based on initiation of the credit control failure handling (CCFH), via a Specialized Mobile Radio (SMR).
[0014] In an exemplary aspect of the present disclosure, the method further comprising receiving, by the transceiver unit, a subsequent request from the UE, wherein the subsequent request is generated by the UE subsequent to exhaustion of the first network resource quota by the UE and allocating, by the allocation unit, a second network resource quota to the UE.
[0015] Another aspect of the present disclosure may relate to a system for allocation a network resource quota to a User Equipment (UE) in a network, the system comprises a transceiver unit, wherein the transceiver unit is configured to receive an attach request from the UE, wherein the attach request comprises at least a resource allocation request associated with the UE, and wherein the resource allocation request is to request a quantity of network resources usable by the UE. The transceiver unit is further configured to transmit the resource allocation request to a Charging function (CHF) in the network. Further the transceiver unit, based on the transmitted resource allocation request, receive an error response from the CHF, wherein the error response comprises an error code corresponding to an error
occurred in the network. The system comprises an initiation unit connected to at least the transceiver unit, the initiation unit is configured to initiate a credit control failure handling (CCFH) based on the error code corresponding to the error occurred in the network. The system comprises an allocation unit connected to at least the initiation unit, the allocation unit is configured to allocate a first network resource quota to the UE, wherein the first network resource quota comprises a pre-configured quantity of network resources usable by the UE.
[0016] Another aspect of the present disclosure may relate to a User Equipment (UE) comprising a memory: and a processor coupled to the memory, wherein the processor is configured to send an attach request to a system, wherein the attach request is used by the UE for receiving an allocation of a network resource quota, wherein the network resource quota is allocated by the system based on: receiving, by a transceiver unit of the system, the attach request from the UE wherein the attach request comprises at least a resource allocation request associated with the UE, and wherein the resource allocation request is to request a quantity of network resources usable by the UE; transmitting, by the transceiver unit of the system, the resource allocation request to a Charging function (CHF) in the network; based on the transmitted resource allocation request, receiving, by the transceiver unit of the system, an error response from the CHF, wherein the error response comprises an error code corresponding to an error occurred in the network; initiating, by an initiation unit of the system, a credit control failure handling (CCFH) based on the error code corresponding to the error occurred in the network; and allocating, by an allocation unit of the system, a first network resource quota to the UE, wherein the first network resource quota comprises a pre-configured quantity of network resources and usable by the UE.
[0017] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for allocating a network resource quota to a User Equipment (UE) in a network the instructions include executable code which, when executed by a one or more units of a system, causes:
transceiver unit of the system to receive an attach request from the UE, wherein the attach request comprises at least a resource allocation request associated with the UE, and wherein the resource allocation request is to request a quantity of network resources usable by the UE; a transceiver unit of the system to transmit the resource allocation request to a Charging function (CHF) in the network; based on the transmitted resource allocation request, the transceiver unit of the system receive an error response from the CHF, wherein the error response comprises an error code corresponding to an error occurred in the network; an initiation unit of the system to initiate a credit control failure handling (CCFH) based on the error code corresponding to the error occurred in the network; an allocation unit of the system to allocate a first network resource quota to the UE, wherein the first network resource quota comprises a pre-configured quantity of network resources and usable by the UE.
OBJECTS OF THE INVENTION
[0018] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0019] It is an object of the present disclosure to provide a system and a method for assigning quota to a user.
[0020] It is another object of the present disclosure to provide a solution that receives a response comprising an error code from the CHF based on the request associated with quota assignment.
[0021] It is yet another object of the present disclosure to provide a solution to initiate a CCHF by the SMF based on the error code received in the response.
DESCRIPTION OF THE DRAWINGS
[0022] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. 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 components or circuitry commonly used to implement such components.
[0023] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.
[0024] 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.
[0025] FIG. 3 illustrates an exemplary block diagram of a system for allocating a network resource quota to a User Equipment (UE) in a network in accordance with exemplary implementations of the present disclosure.
[0026] FIG. 4 illustrates a method flow diagram for allocating a network resource quota to a User Equipment (UE) in a network in accordance with exemplary implementations of the present disclosure.
[0027] FIG. 5 illustrates a signalling flow diagram for allocating a network resource quota to a User Equipment (UE) in a network in accordance with exemplary implementations of the present disclosure.
[0028] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0029] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may each be used independently of one another or with any combination of other features. An individual feature may not address any of the problems discussed above or might address only some of the problems discussed above.
[0030] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It should be understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.
[0031] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0032] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure.
[0033] The word “exemplary” and/or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and/or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive—in a manner similar to the term “comprising” as an open transition word—without precluding any additional or other elements.
[0034] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[0035] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0036] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read-only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
[0037] 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 called.
[0038] Charging Function (CHF): In a telecommunications network, CHF is a component responsible for managing charging and billing functions, including resource allocation and usage tracking.
[0039] N40 Interface: N40 is a specific interface within a network architecture, often used in telecommunications, to facilitate communication between different network elements or functions.
[0040] HTTP2: HTTP2 is a network protocol used for transmitting data over the World Wide Web. It is designed to improve performance and security compared to its predecessor, HTTP 1.1.
[0041] Credit Control Failure Handling (CCFH): CCFH is a process or mechanism implemented in a network to manage failures related to credit control, such as when there is an issue with allocating resources or processing payments.
[0042] Specialized Mobile Radio (SMR): SMR refers to a type of mobile communication system that is designed for specific applications or industries, often requiring specialized features or capabilities tailored to their needs. It may involve dedicated radio frequencies, protocols, or infrastructure.
[0043] 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 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.
[0044] As used herein the transceiver unit include at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals,
information or a combination thereof between units/components within the system and/or connected with the system.
[0045] As discussed in the background section, the current known solutions have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of allocating a network resource quota to a User Equipment (UE) in a network. The current known solutions for assigning quota to a user have several shortcomings such as the reliance on the http2 protocol for communication between SMF and CHF introduces potential bottlenecks and performance issues, particularly when dealing with substantial data loads. This limitation hampers the efficiency and responsiveness of the system, leading to suboptimal user experiences. Secondly, the lack of comprehensive error handling mechanisms is a significant drawback. When network or OCS errors occur, CHF's negative response to SMF without detailed error information hinders effective troubleshooting and resolution of the underlying issues. This limitation not only impacts system reliability but also slows down the overall error resolution process, negatively affecting the user's perception of the service. Consequently, these shortcomings necessitate the development of an improved solution that addresses these issues and enhances the performance and reliability of the system.
[0046] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by disclosing a novel solution for to improve the quota assignment process during the Attach Procedure in a communication network. The solution focuses on the interaction between the Session Management Function (SMF) and the Charging Function (CHF) for quota assignments. Further the novel solution suggests that SMF can make informed decisions based on the error code received in the negative response from CHF. Specifically, SMF can choose to apply a Charging Control Failure Handling (CCFH) procedure. By applying CCFH, SMF can take appropriate actions to rectify the error and ensure a smooth quota assignment process. Upon successful
5 application of CCFH, SMF can send pre-configured quotas towards the User Plane
Function (UPF), allowing the user to continue utilizing the allocated quota. Additionally, SMF has the flexibility to determine how many times a user can be assigned the pre-configured quota, providing adaptability and customization options to meet specific network requirements. Therefore, the novel solution
10 enhances the quota assignment process during the Attach Procedure by introducing
error handling mechanisms and pre-configured quotas. By utilizing this solution, communication networks can improve the efficiency and reliability of quota assignments, ultimately enhancing the user experience and overall network performance.
15
[0047] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.
[0048] FIG. 1 illustrates an exemplary block diagram representation of 5th
20 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],
25 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
30 User Plane Function (UPF) [128], a data network (DN) [130], wherein all the
components are assumed to be connected to each other in a manner as obvious to
the person skilled in the art for implementing features of the present disclosure.
[0049] Radio Access Network (RAN) [104] is the part of a mobile
35 telecommunications system that connects user equipment (UE) [102] to the core
14
5 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.
[0050] Access and Mobility Management Function (AMF) [106] is a 5G core
10 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.
[0051] Session Management Function (SMF) [108] is a 5G core network function
15 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.
[0052] Service Communication Proxy (SCP) [110] is a network function in the 5G
20 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.
[0053] Authentication Server Function (AUSF) [112] is a network function in the
25 5G core responsible for authenticating UEs during registration and providing
security services. It generates and verifies authentication vectors and tokens.
[0054] Network Slice Specific Authentication and Authorization Function
(NSSAAF) [114] is a network function that provides authentication and
30 authorization services specific to network slices. It ensures that UEs can access only
the slices for which they are authorized.
[0055] Network Slice Selection Function (NSSF) [116] is a network function
responsible for selecting the appropriate network slice for a UE based on factors
35 such as subscription, requested services, and network policies.
15
5
[0056] 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.
10 [0057] 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.
[0058] Policy Control Function (PCF) [122] is a network function responsible for
15 policy control decisions, such as QoS, charging, and access control, based on
subscriber information and network policies.
[0059] Unified Data Management (UDM) [124] is a network function that
centralizes the management of subscriber data, including authentication,
20 authorization, and subscription information.
[0060] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services. 25
[0061] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
30 [0062] 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.
[0063] FIG. 2 illustrates an exemplary block diagram of a computing device [200]
35 (also referred to herein as a computer system [200]) upon which the features of the
16
5 present disclosure may be implemented in accordance with exemplary
implementation of the present disclosure. In an implementation, the computing
device [200] may also implement a method for allocating a network resource quota
to a User Equipment (UE) in a network utilising the system. In another
implementation, the computing device [200] itself implements the method for
10 allocating a network resource quota to a User Equipment (UE) in a network using
one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
15 [0064] The computing device [200] may include a bus [202] or other
communication mechanism for communicating information, and a hardware
processor [204] coupled with bus [202] for processing information. The hardware
processor [204] may be, for example, a general-purpose microprocessor. The
computing device [200] may also include a main memory [206], such as a random-
20 access memory (RAM), or other dynamic storage device, coupled to the bus [202]
for storing information and instructions to be executed by the processor [204]. The
main memory [206] also may be used for storing temporary variables or other
intermediate information during execution of the instructions to be executed by the
processor [204]. Such instructions, when stored in non-transitory storage media
25 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
(ROM) [208] or other static storage device coupled to the bus [202] for storing static
information and instructions for the processor [204].
30
[0065] A storage device [210], such as a magnetic disk, optical disk, or solid-state
drive is provided and coupled to the bus [202] for storing information and
instructions. The computing device [200] may be coupled via the bus [202] to a
display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD),
35 Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for
17
5 displaying information to a computer user. An input device [214], including
alphanumeric and other keys, touch screen input means, etc. may be coupled to the
bus [202] for communicating information and command selections to the processor
[204]. Another type of user input device may be a cursor controller [216], such as
a mouse, a trackball, or cursor direction keys, for communicating direction
10 information and command selections to the processor [204], and for controlling
cursor movement on the display [212]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.
15 [0066] The computing device [200] may implement the techniques described
herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the
20 computing device [200] in response to the processor [204] executing one or more
sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the
25 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.
[0067] The computing device [200] also may include a communication interface
30 [218] coupled to the bus [202]. The communication interface [218] provides a two-
way data communication coupling to a network link [220] that is connected to a
local network [222]. For example, the communication interface [218] may be an
integrated services digital network (ISDN) card, cable modem, satellite modem, or
a modem to provide a data communication connection to a corresponding type of
35 telephone line. As another example, the communication interface [218] may be a
18
5 local area network (LAN) card to provide a data communication connection to a
compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
10
[0068] The computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218]. In the Internet example, a server [230] might transmit a requested code for an application program through the Internet [228], the
15 ISP [226], the host [224], the local network [222] and the communication interface
[218]. The received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution.
20 [0069] Referring to FIG. 3, an exemplary block diagram of a system [300] for
allocating a network resource quota to a User Equipment (UE) in a network is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one transceiver unit [302], at least one initiation unit [304] and at least one allocation unit [306]. Also, all of the
25 components/ units of the system [300] are assumed to be connected to each other
unless otherwise indicated below. As shown in the figures all units shown within the system should also be assumed to be connected to each other. Further, the system resides in the SMF. Also, in FIG. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may
30 comprise any such numbers of said units, as required to implement the features of
the present disclosure.
[0070] In one example, the system [300] may reside in the Session Management
Function [108] as described in FIG. 1. Further, in another implementation, the
35 system [300] may be present in a user device to implement the features of the
19
5 present disclosure. The system [300] may be a part of the user device / or may be
independent of but in communication with the user device (may also referred 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
[0071] The system [300] is configured for allocating a network resource quota to a User Equipment (UE) in a network with the help of the interconnection between the components/units of the system [300].
15 [0072] Particularly, the transceiver unit [302] is configured to receive an attach
request from the UE, wherein the attach request comprises at least a resource allocation request associated with the UE and wherein the resource allocation request is to request a quantity of network resources usable by the UE. The present disclosure encompasses the term “transceiver unit” [302] that may act as an
20 intermediary between the User Equipment (UE) and the network. The User
Equipment (UE), which could be a smartphone, tablet, or any device capable of connecting to a network, sends an attach request when it wants to establish a connection with the network. The resource allocation request by the UE is a request for resource allocation from the network (CHF), wherein the allocation is services
25 based and may relate to bandwidth, data etc. The resource allocation request is
transmitted to the Charging function (CHF), over a N40 interface, based on a HTTP2 network protocol. The network resource quota is a predefined limit set on the utilization of various resources within a network. These resources can include bandwidth, data usage, connection time, number of concurrent connections, and
30 other network-related capabilities.
[0073] For example: Imagine you have an Internet Service Provider (ISP) that
offers different plans. One plan might include 100 GB of data per month, a
maximum internet speed of 50 Mbps, and allow up to 5 devices to be connected at
35 the same time. The ISP uses network resource quotas to make sure you don’t go
20
5 over these limits. If you use up your 100 GB of data, the ISP might slow down your
internet speed or temporarily stop your internet access until the next month starts.
[0074] For Example: Imagine a smartphone (the UE) turning on and trying to connect to a cellular network. It sends an attach request to the network's base station
10 (which includes the transceiver unit [302]). Within this attach request, there is a
resource allocation request asking the network to allocate enough bandwidth for the phone to stream videos, browse the internet, and make calls. The transceiver unit receives this attach request and processes it to determine how much network capacity should be assigned to this particular device.
15
[0075] The transceiver unit [302] further, transmit the resource allocation request to the Charging function (CHF) in the network. The present disclosure encompasses that the charging function (CHF) is a specialized entity within the network responsible for managing the resource allocation and the charging-related
20 processes.
[0076] Furthermore, based on the transmitted resource allocation request, the transceiver unit [302] receive an error response from the CHF, wherein the error response comprises an error code corresponding to an error occurred in the network.
25 The present disclosure encompasses that the action of receiving an error response
may be a consequence of the earlier request sent to the Charging Function (CHF). After the resource allocation request is sent to the CHF, the system anticipates an “error response” to be a type of reply indicating that something went wrong with the processing of the request. In one example, the error response corresponding to
30 the error occurred in the network may include at least one of a negative response
and a time out response. The negative response may indicate rejection of the resource allocation request. On the other hand, the time out response may indicate that the request was not processed within the expected time frame, possibly due to delays or unavailability of the CHF. However, it may be noted that such examples
35 of error responses are only exemplary, and not to be construed to limit the scope of
21
5 the present subject matter in any manner. Other error responses may also be used
and would lie within the scope of the present subject matter.
[0077] Continuing with the present example, as described previously, the error response may be indicative of an error that may have occurred while processing the
10 request. As would be understood and known to a person skilled in the art, there
could be different reasons for occurrence of the error. For example: Imagine a smartphone (UE) requests a specific amount of data bandwidth from the network to stream a video. This request is sent to the network's transceiver unit and then forwarded to the CHF. If there is an issue, such as the network being overloaded or
15 a problem with the CHF, an error response is generated. This error response could
either be a negative response, indicating the request is denied due to lack of available bandwidth, or a time out response, indicating that the request could not be processed in time.
20 [0078] In another example, along with the error response, an error code may also
be generated. Such error codes, as known to a person skilled in the art, would indicate the reason for the error.
[0079] The system comprises, an initiation unit [304] connected to at least the
25 transceiver unit [302], the initiation unit [304] is configured to initiate a credit
control failure handling (CCFH) based on the error code corresponding to the error
occurred in the network. The present disclosure encompasses that the initiation Unit
[304] within the system is responsible for initiating the credit control failure
handling (CCFH) process. The credit Control Failure Handling (CCFH) is
30 procedure that manages situations where the system encounters an error related to
credit control, ensuring continued service or appropriate handling of the error. The
initiation of CCFH is triggered by an error code that the initiation unit [304]
receives. This error code is indicative of a problem that has occurred within the
network. The error response is received from the Charging function (CHF), over a
35 N40 interface, based on a HTTP2 network protocol. The system receives an error
22
5 response from the CHF, which is a network component responsible for handling the
charging and the resource allocation. Further, the error response comprises of at least one of a negative response and a time out response. The communication between the system and the CHF occurs over the N40 interface. Examples of an error codes are ERR_QUOTA_EXCEEDED, which indicates that the user has
10 exceeded their allocated quota for a specific resource.
ERR_BANDWIDTH_LIMIT_REACHED, this error is triggered when the user
reaches the maximum bandwidth limit set by their quota.
ERR_CONNECTION_LIMIT_EXCEEDED, this error occurs when the number of
concurrent connections exceeds the predefined limit.
15 ERR_RESOURCE_NOT_AVAILABLE, this error indicates that the requested
network resource is currently unavailable due to quota restrictions.
[0080] For example: A smartphone (UE) sends a request for additional data bandwidth to stream a high-definition video. This request is processed by the
20 transceiver unit [302] and sent to the CHF. However, due to an issue in the network,
the CHF sends back an error response over the N40 interface using the HTTP2 protocol. This error response contains an error code indicating that the request cannot be fulfilled. The initiation unit [304], upon receiving this error code, initiates the CCFH process to handle the error appropriately, such as allocating a default
25 resource quota or taking other remedial actions to ensure the user continues to have
service.
[0081] The system comprises, an allocation unit [306] connected to at least the initiation unit [304], the allocation unit [306] is configured to allocate a first
30 network resource quota to the UE, wherein the first network resource quota
comprises a pre-configured quantity of network resources usable by the UE. The present disclosure encompasses the allocation Unit [306] within the system responsible for distributing or assigning network resources. Its role is to manage the allocation of resources to the User Equipment (UE). The allocation unit [306] is
35 designed to assign a specified amount of network resources to the UE. The First
23
5 Network Resource Quota is the initial allocation of network resources to the UE.
The first network resource quota is allocated to the UE for a pre-defined time
duration. and the first network resource quota is allocated to the UE, based on
initiation of the credit control failure handling (CCFH), via a Specialized Mobile
Radio (SMR). The allocation of the first network resource quota is triggered by the
10 CCFH process, which is initiated by the initiation unit [304] when an error occurs.
The allocation process involves using the Specialized Mobile Radio (SMR), which is a type of mobile communication system designed for specific functions, such as emergency communication or secure communication.
15 [0082] For example: A smartphone (UE) encounters an issue while requesting
network resources. The initiation unit [304] detects an error and triggers the CCFH process. In response, the allocation unit [306] allocates a first network resource quota to the UE. This quota is pre-configured, meaning the amount of resources (like data or bandwidth) has been set in advance, and it is available for the UE to
20 use. The allocation is done for a pre-defined time duration, say 24 hours, ensuring
the UE has consistent access to the network resources for that period. This process uses a Specialized Mobile Radio (SMR) system to facilitate secure and reliable communication during the allocation.
25 [0083] The system further comprises, the transceiver unit [302] to receive
subsequent request from the UE, wherein the subsequent request is generated by the UE subsequent to exhaustion of the first network resource quota by the UE and the allocation unit [306] allocate a second network resource quota to the UE. The present disclosure encompasses the transceiver unit [302], which handles
30 communication between the User Equipment (UE) and the network, is also
responsible for receiving follow-up requests from the UE. The subsequent request is a new request sent by the UE after it has used up its initially allocated network resources (the first network resource quota). The UE generates this follow-up request when it has fully utilized or consumed the first set of network resources
35 allocated to it. After that, the UE has used up all the resources (like data or
24
5 bandwidth) that were initially provided. Further, the allocation unit [306] responds
to the subsequent request by assigning a new set of network resources to the UE. The Second Network Resource Quota is an additional allocation of network resources provided to the UE after the first quota has been ended.
10 [0084] For example: Imagine a user streaming a video on their smartphone (UE).
Initially, the network allocates a certain amount of data (the first network resource quota) to the smartphone. As the user continues streaming, they use up all the initially allocated data. When this happens, the smartphone sends a subsequent request to the network via the transceiver unit [302], asking for more data. The
15 transceiver unit receives this request, and the allocation unit [306] responds by
allocating an additional amount of data (the second network resource quota) to the smartphone, allowing the user to continue streaming without interruption.
[0085] Referring to FIG. 4, an exemplary method flow diagram [400] for allocating
20 a network resource quota to a User Equipment (UE) in a network 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 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]
25 starts at step [402].
[0086] At step 404, the method for allocating a network resource quota to a User Equipment (UE) in a network, the method comprising receiving, by a transceiver unit [302], an attach request from the UE, wherein the attach request comprises at
30 least a resource allocation request associated with the UE, and wherein the resource
allocation request is to request a quantity of network resources usable by the UE. The present disclosure encompasses the term “transceiver unit” [302] acts as an intermediary between the User Equipment (UE) and the network. The User Equipment (UE), which could be a smartphone, tablet, or any device capable of
35 connecting to a network, sends an attach request when it wants to establish a
25
5 connection with the network. The resource allocation request by the UE is a request
for resource allocation from the network (CHF), wherein the allocation is services
based and may relate to bandwidth, data etc. The resource allocation request is
transmitted to the Charging function (CHF), over a N40 interface, based on a
HTTP2 network protocol. The network resource quota is a predefined limit set on
10 the utilization of various resources within a network. These resources can include
bandwidth, data usage, connection time, number of concurrent connections, and other network-related capabilities.
[0087] For example: Imagine you have an Internet Service Provider (ISP) that
15 offers different plans. One plan might include 100 GB of data per month, a
maximum internet speed of 50 Mbps, and allow up to 5 devices to be connected at the same time. The ISP uses network resource quotas to make sure you don’t go over these limits. If you use up your 100 GB of data, the ISP might slow down your internet speed or temporarily stop your internet access until the next month starts 20
[0088] For Example: Imagine a smartphone (the UE) turning on and trying to
connect to a cellular network. It sends an attach request to the network's base station
(which includes the transceiver unit [302]). Within this attach request, there is a
resource allocation request asking the network to allocate enough bandwidth for the
25 phone to stream videos, browse the internet, and make calls. The transceiver unit
receives this attach request and processes it to determine how much network capacity should be assigned to this particular device.
[0089] At step 406, the method comprising transmitting, by the transceiver [302],
30 the resource allocation request to a Charging function (CHF) in the network. The
present disclosure encompasses that the charging function (CHF) is a specialized entity within the network responsible for managing the resource allocation and the charging-related processes.
26
5 [0090] At step 408, the method comprising based on the transmitted resource
allocation request, receiving, by the transceiver unit [302], an error response from the CHF, wherein the error response comprises an error code corresponding to an error occurred in the network. The present disclosure encompasses that the action of receiving an error response may be a consequence of the earlier request sent to
10 the Charging Function (CHF). After the resource allocation request is sent to the
CHF, the system anticipates an “error response” to be a type of reply indicating that something went wrong with the processing of the request. The error response corresponding to the error occurred in the network comprises at least one of a negative response and a time out response. The negative response may indicate
15 rejection of the resource allocation request. The time out response indicating that
the request was not processed within the expected time frame, possibly due to delays or unavailability of the CHF.
[0091] For example: Imagine a smartphone (UE) requests a specific amount of data
20 bandwidth from the network to stream a video. This request is sent to the network's
transceiver unit and then forwarded to the CHF. If there is an issue, such as the
network being overloaded or a problem with the CHF, an error response is
generated. This error response could either be a negative response, indicating the
request is denied due to lack of available bandwidth, or a time out response,
25 indicating that the request could not be processed in time.
[0092] At step 410, the method comprising initiating, by an initiation unit [304], a credit control failure handling (CCFH) based on the error code corresponding to the
30 error occurred in the network. The present disclosure encompasses the initiation
Unit [304] within the system is responsible for initiating certain the credit control failure handling (CCFH) process. The credit Control Failure Handling (CCFH) is procedure that manages situations where the system encounters an error related to credit control, ensuring continued service or appropriate handling of the error. The
35 initiation of CCFH is triggered by an error code that the initiation unit [304]
27
5 receives. This error code is indicative of a problem that has occurred within the
network. The error response is received from the Charging function (CHF), over a
N40 interface, based on a HTTP2 network protocol. The system receives the error
response from the CHF, which is a network component responsible for handling the
charging and the resource allocation. Further, the error response comprises of at
10 least one of a negative response and a time out response. The communication
between the system and the CHF occurs over the N40 interface.
[0093] For example: A smartphone (UE) sends a request for additional data bandwidth to stream a high-definition video. This request is processed by the
15 transceiver unit [302] and sent to the CHF. However, due to an issue in the network,
the CHF sends back an error response over the N40 interface using the HTTP2 protocol. This error response contains an error code indicating that the request cannot be fulfilled. The initiation unit [304], upon receiving this error code, initiates the CCFH process to handle the error appropriately, such as allocating a default
20 resource quota or taking other remedial actions to ensure the user continues to have
service.
[0094] At step 412, the method comprising allocating, by an allocation unit [306], a first network resource quota to the UE, wherein the first network resource quota
25 comprises a pre-configured quantity of network resources usable by the UE. The
present disclosure encompasses the allocation Unit [306] within the system responsible for distributing or assigning network resources. Its role is to manage the allocation of resources to the User Equipment (UE). The allocation unit [306] is designed to assign a specified amount of network resources to the UE. The First
30 Network Resource Quota is the initial allocation of network resources to the UE.
The first network resource quota is allocated to the UE for a pre-defined time duration and the first network resource quota is allocated to the UE, based on initiation of the credit control failure handling (CCFH), via a Specialized Mobile Radio (SMR). The allocation of the first network resource quota is triggered by the
35 CCFH process, which is initiated by the initiation unit [304] when an error occurs.
28
5 The allocation process involves using the Specialized Mobile Radio (SMR), which
is a type of mobile communication system designed for specific functions, such as emergency communication or secure communication.
[0095] For example: A smartphone (UE) encounters an issue while requesting
10 network resources. The initiation unit [304] detects an error and triggers the CCFH
process. In response, the allocation unit [306] allocates a first network resource
quota to the UE. This quota is pre-configured, meaning the amount of resources
(like data or bandwidth) has been set in advance, and it is available for the UE to
use. The allocation is done for a pre-defined time duration, say 24 hours, ensuring
15 the UE has consistent access to the network resources for that period. This process
uses a Specialized Mobile Radio (SMR) system to facilitate secure and reliable communication during the allocation.
[0096] The method comprising further comprising receiving, by the transceiver
20 unit [302], a subsequent request from the UE, wherein the subsequent request is
generated by the UE subsequent to exhaustion of the first network resource quota
by the UE and allocating, by the system, a second network resource quota to the
UE. The present disclosure encompasses the transceiver unit [302], which handles
communication between the User Equipment (UE) and the network, is also
25 responsible for receiving follow-up requests from the UE. The subsequent request
is a new request sent by the UE after it has used up its initially allocated network
resources (the first network resource quota). The UE generates this follow-up
request when it has fully utilized or consumed the first set of network resources
allocated to it. After that, the UE has used up all the resources (like data or
30 bandwidth) that were initially provided. Further, the allocation unit [306] responds
to the subsequent request by assigning a new set of network resources to the UE. The Second Network Resource Quota is an additional allocation of network resources provided to the UE after the first quota has been ended.
29
5 [0097] For example: Imagine a user streaming a video on their smartphone (UE).
Initially, the network allocates a certain amount of data (the first network resource
quota) to the smartphone. As the user continues streaming, they use up all the
initially allocated data. When this happens, the smartphone sends a subsequent
request to the network via the transceiver unit [302], asking for more data. The
10 transceiver unit receives this request, and the allocation unit [306] responds by
allocating an additional amount of data (the second network resource quota) to the smartphone, allowing the user to continue streaming without interruption.
[0098] Thereafter, the method terminates at step 414. 15
[0099] Referring to FIG. 5 illustrates a signalling flow diagram for allocating a network resource quota to a User Equipment (UE) in a network in accordance with exemplary implementations of the present disclosure.
20 [0100] Step 1: Transmission of the attach request from the UE to the transceiver
unit.
[0101] Step 2: Forwarding of the resource allocation request from the transceiver
unit to the Charging function (CHF) via the N40 interface using the HTTP2 network
25 protocol.
[0102] Step 3: Reception of the error response (including negative or timeout responses) from the CHF back to the transceiver unit.
30 [0103] Step 4: Initiation of credit control failure handling (CCFH) based on the
received error code.
[0104] Step 5: Allocation of the first network resource quota to the UE by the
allocation unit, considering predefined parameters such as bandwidth, data usage,
35 connection time, and QoS.
30
5 [0105] The present disclosure further discloses a non-transitory computer readable
storage medium storing instructions for allocating a network resource quota to a User Equipment (UE) in a network the instructions include executable code which, when executed by a one or more units of a system, causes: transceiver unit [302] of the system to receive an attach request from the UE, wherein the attach request
10 comprises at least a resource allocation request associated with the UE, and wherein
the resource allocation request is to request a quantity of network resources usable by the UE; a transceiver unit [302] of the system to transmit the resource allocation request to a Charging function (CHF) in the network; based on the transmitted resource allocation request, the transceiver unit [302] receive an error response
15 from the CHF, wherein the error response comprises an error code corresponding
to an error occurred in the network; an initiation unit [304] of the system to initiate a credit control failure handling (CCFH) based on the error code corresponding to the error occurred in the network; an allocation unit [306] of the system to allocate a first network resource quota to the UE, wherein the first network resource quota
20 comprises a pre-configured quantity of network resources and usable by the UE.
[0106] As is evident from the above, the present disclosure provides a technically advanced solution for allocating a network resource quota to a User Equipment (UE) in a network. The present solution as disclosed introduces a remarkable
25 technical advancement in the field of user experience enhancement, specifically
addressing the challenge of Outage in Online Charging System (OCS), Diameter Routing Agent (DRA), or Charging Function (CHF). By incorporating innovative methodologies and advanced techniques, this solution ensures that user experience remains unaffected even during OCS/DRA/CHF outages. The technical
30 advancement lies in the implementation of a robust system that seamlessly handles
such outages by leveraging intelligent mechanisms such as intelligent caching, local policy enforcement, or alternative charging methods. This breakthrough innovation revolutionizes the way user experience is maintained during critical service disruptions, setting a new benchmark in the industry and empowering service
35 providers to deliver uninterrupted and exceptional user experiences, regardless of
31
5 OCS/DRA/CHF availability. Further, the inventive solution as disclosed brings
forth significant technical effects that positively impact the user experience. Firstly, it ensures uninterrupted service delivery by seamlessly managing the OCS/DRA/CHF outages, thereby eliminating service disruptions for end-users. This technical effect guarantees that users can continue to enjoy seamless access to
10 essential services and functionalities without any interruptions caused by backend
system failures. Secondly, the solution enhances user satisfaction by mitigating the frustration and inconvenience that users typically face during outages. By maintaining a consistent and uninterrupted user experience, even in the face of OCS/DRA/CHF outages, this solution significantly improves user loyalty,
15 retention, and overall satisfaction. Ultimately, the technical effects of this patent
specification result in a reliable and resilient system that prioritizes user experience, positioning service providers at the forefront of the industry and ensuring maximum customer satisfaction.
20 [0107] 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 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
25 be understood that the foregoing descriptive matter to be implemented is illustrative
and non-limiting.
[0108] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various the components/units can be
30 implemented interchangeably. While specific embodiments may disclose a
particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative
35 arrangements and substitutions of units, provided they achieve the intended
32
5 functionality described herein, are considered to be encompassed within the scope
of the present disclosure.
33
We Claim:
1. A method [400] for allocating a network resource quota to a User
Equipment (UE) in a network, the method [400] comprising:
receiving [404], by a transceiver unit [302], an attach request from the UE, wherein the attach request comprises at least a resource allocation request associated with the UE, and wherein the resource allocation request is to request a quantity of network resources usable by the UE;
transmitting [406], by the transceiver [302], the resource allocation request to a Charging function (CHF) in the network;
based on the transmitted resource allocation request, receiving [408], by the transceiver unit [302], an error response from the CHF, wherein the error response comprises an error code corresponding to an error occurred in the network;
initiating [410], by an initiation unit [304], a credit control failure handling (CCFH) based on the error code corresponding to the error occurred in the network; and
allocating [412], by an allocation unit [306], a first network resource quota to the UE, wherein the first network resource quota comprises a pre-configured quantity of network resources usable by the UE.
2. The method [400] as claimed in claim 1, wherein the resource allocation request is transmitted to the Charging function (CHF), over a N40 interface, based on a HTTP2 network protocol.
3. The method [400] as claimed in claim 1, wherein the error response is received from the Charging function (CHF), over a N40 interface, based on a HTTP2 network protocol.
4. The method [400] as claimed in claim 1, wherein the error response corresponding to the error occurred in the network comprises at least one of a negative response and a time out response.
5. The method [400] as claimed in claim 1, wherein the first network resource quota is allocated to the UE for a pre-defined time duration.
6. The method [400] as claimed in claim 1, wherein the first network resource quota is allocated to the UE, based on initiation of the credit control failure handling (CCFH), via a Specialized Mobile Radio (SMR).
7. The method [400] as claimed in claim 1, further comprising:
receiving, by the transceiver unit [302], a subsequent request from the UE,
wherein the subsequent request is generated by the UE subsequent to exhaustion of the first network resource quota by the UE; and
allocating, by the allocation unit [306], a second network resource quota to the UE.
8. A system [300] for allocation a network resource quota to a User Equipment
(UE) in a network, the system [300] comprising:
a transceiver unit [302], wherein the transceiver unit [302] is configured to:
receive an attach request from the UE, wherein the attach request comprises at least a resource allocation request associated with the UE, and wherein the resource allocation request is to request a quantity of network resources usable by the UE;
transmit the resource allocation request to a Charging function (CHF) in the network;
based on the transmitted resource allocation request, receive an error response from the CHF, wherein the error response comprises an error code corresponding to an error occurred in the network;
an initiation unit [304] connected to at least the transceiver unit [302], the initiation unit [304] configured to initiate a credit control failure handling (CCFH) based on the error code corresponding to the error occurred in the network; and
an allocation unit [306] connected to at least the initiation unit [304], the allocation unit [306] configured to allocate a first network resource quota to the UE, wherein the first network resource quota comprises a pre-configured quantity of network resources usable by the UE.
9. The system [300] as claimed in claim 8, wherein the resource allocation request is transmitted to the Charging function (CHF), over a N40 interface, based on a HTTP2 network protocol.
10. The system [300] as claimed in claim 8, wherein the error response is received from the Charging function (CHF), over a N40 interface, based on a HTTP2 network protocol.
11. The system [300] as claimed in claim 8, wherein the error response corresponding to the error occurred in the network comprises at least one of a negative response and a time out response.
12. The system [300] as claimed in claim 8, wherein the first network resource quota is allocated to the UE for a pre-defined time duration.
13. The system [300] as claimed in claim 8, wherein the first network resource quota is allocated to the UE, based on initiation of the credit control failure handling (CCFH), via a Specialized Mobile Radio (SMR).
14. The system [300] as claimed in claim 8, wherein the transceiver unit [302] is to further:
receive subsequent request from the UE, wherein the subsequent request is generated by the UE subsequent to exhaustion of the first network resource quota by the UE; and
the allocation unit [306] allocate a second network resource quota to the UE.
15. A User Equipment (UE) comprising:
a memory; and
a processor coupled to the memory, wherein the processor is configured to: send an attach request to a system, wherein the attach request is used by the UE for receiving an allocation of a network resource quota, wherein the network resource quota is allocated by the system based on:
receiving, by a transceiver unit [302] of the system, the attach request from the UE wherein the attach request comprises at least a resource allocation request associated with the UE, and wherein the resource allocation request is to request a quantity of network resources usable by the UE;
transmitting, by the transceiver unit [302] of the system, the resource allocation request to a Charging function (CHF) in a network;
based on the transmitted resource allocation request, receiving, by the transceiver unit [302] of the system, an error response from the CHF, wherein the error response comprises an error code corresponding to an error occurred in the network;
initiating, by an initiation unit [304] of the system, a credit control failure handling (CCFH) based on the error code corresponding to the error occurred in the network; and
allocating, by an allocation unit [306] of the system, a first network resource quota to the UE, wherein the first network resource quota comprises a pre-configured quantity of network resources and usable by the UE.
| # | Name | Date |
|---|---|---|
| 1 | 202321045820-STATEMENT OF UNDERTAKING (FORM 3) [07-07-2023(online)].pdf | 2023-07-07 |
| 2 | 202321045820-PROVISIONAL SPECIFICATION [07-07-2023(online)].pdf | 2023-07-07 |
| 3 | 202321045820-FORM 1 [07-07-2023(online)].pdf | 2023-07-07 |
| 4 | 202321045820-FIGURE OF ABSTRACT [07-07-2023(online)].pdf | 2023-07-07 |
| 5 | 202321045820-DRAWINGS [07-07-2023(online)].pdf | 2023-07-07 |
| 6 | 202321045820-FORM-26 [11-09-2023(online)].pdf | 2023-09-11 |
| 7 | 202321045820-Proof of Right [05-10-2023(online)].pdf | 2023-10-05 |
| 8 | 202321045820-ORIGINAL UR 6(1A) FORM 1 & 26)-261023.pdf | 2023-11-04 |
| 9 | 202321045820-ENDORSEMENT BY INVENTORS [20-06-2024(online)].pdf | 2024-06-20 |
| 10 | 202321045820-DRAWING [20-06-2024(online)].pdf | 2024-06-20 |
| 11 | 202321045820-CORRESPONDENCE-OTHERS [20-06-2024(online)].pdf | 2024-06-20 |
| 12 | 202321045820-COMPLETE SPECIFICATION [20-06-2024(online)].pdf | 2024-06-20 |
| 13 | 202321045820-FORM 3 [01-08-2024(online)].pdf | 2024-08-01 |
| 14 | 202321045820-Request Letter-Correspondence [14-08-2024(online)].pdf | 2024-08-14 |
| 15 | 202321045820-Power of Attorney [14-08-2024(online)].pdf | 2024-08-14 |
| 16 | 202321045820-Form 1 (Submitted on date of filing) [14-08-2024(online)].pdf | 2024-08-14 |
| 17 | 202321045820-Covering Letter [14-08-2024(online)].pdf | 2024-08-14 |
| 18 | 202321045820-CERTIFIED COPIES TRANSMISSION TO IB [14-08-2024(online)].pdf | 2024-08-14 |
| 19 | Abstract.jpg | 2024-10-08 |
| 20 | 202321045820-FORM 18A [21-02-2025(online)].pdf | 2025-02-21 |
| 21 | 202321045820-FER.pdf | 2025-11-17 |
| 1 | 202321045820_SearchStrategyNew_E_Search202321045820E_04-11-2025.pdf |