DESC:
FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
THE PATENTS RULES, 2003

COMPLETE SPECIFICATION
(See section 10 and rule 13)
1. TITLE OF THE INVENTION
METHOD AND SYSTEM FOR MANAGING NETWORK RESOURCES ALLOCATION IN A TELECOMMUNICATION NETWORK
2. APPLICANT(S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED INDIAN Office-101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India
3. PREAMBLE TO THE DESCRIPTION
The following specification particularly describes the invention and the manner in which it is to be performed.

RESERVATION OF RIGHTS
[001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, integrated circuit (IC) layout design, and/or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (herein after referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.
TECHNICAL FIELD
[002] The present disclosure generally relates to the field of wireless communications. More particularly, the present disclosure relates to a method and a system for managing network resources allocation in a telecommunication network.

DEFINITION
[003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.
[004] The expression ‘a unique user key’ used hereinafter in the specification refers to a unique key that is pre-assigned to a User Equipment (UE). The unique user key is an Internet Protocol (IP) Multimedia Private Identity (IMPI) or an IP Multimedia Public Identity (IMPU).
[005] The expression ‘IP Multimedia Subsystem (IMS) network’ used hereinafter in the specification refers to a standards-based architectural framework for delivering multimedia communications services such as voice, video, and text messaging over IP networks.
[006] The expression ‘IP Multimedia Private Identity (IMPI)’ used hereinafter in the specification refers to a unique identifier associated with a user (e.g., a subscriber) of the UE in the IMS network (i.e., the telecommunication network).
[007] The expression ‘IP Multimedia Public Identity (IMPU)’ used hereinafter in the specification refers to a unique public identifier assigned to the UE. The IMPU is used by other users or UEs to initiate communication sessions with the UE associated with a specific user in the IMS network.
[008] The expression ‘low weightage procedure’ used hereinafter in the specification refers to a procedure (such as routine maintenance, monitoring, or administrative tasks, etc.,) that do not directly impact a real-time performance or an immediate operation of the telecommunication network.
[009] The expression ‘high weightage procedure’ used hereinafter in the specification refers to a procedure (e.g., a registration termination procedure, a bearer resource control procedure, an emergency call procedure, etc.) that is crucial for maintaining a connectivity, managing the network resources, or ensuring a quality of critical services, such as a bearer resource control service, or an emergency call handling service.
[010] The expression ‘Serving Call session control function (S-CSCF)’ used hereinafter in the specification refers to a network component that is configured for managing sessions in an IMS architecture. The S-CSCF is responsible for conducting UE registration and session control for registered UE, user profile handling, authentication/ authorization, service invocation, session routing, and the like. The S-CSCF also facilitates interworking between the IMS network and other networks, allowing seamless communication between IMS network users and users on non-IMS networks.
[011] The expression ‘Interrogating Call Session Control Function (I-CSCF)’ used hereinafter in the specifications refer to a network component that serves as an entry point into the IMS network from an internet and selects an appropriate S-CSCF for a particular UE’s incoming session.
[012] The expression ‘Breakout Gateway Control Function (BGCF)’ used hereinafter in the specifications refer to a network component that facilitates communication between the IMS network and external networks, enabling services that require interaction with non-IMS networks.
[013] The expression ‘Proxy Call Session Control Function (P-CSCF)’ used hereinafter in the specifications refer to a network component that serves as a first point of contact for the UE, within the IMS network.
[014] The expression ‘Media Resource Function (MRF)’ used hereinafter in the specifications refer to a network component that handles media processing tasks, such as mixing audio streams or generating tones, required for multimedia sessions.
[015] The expression ‘data context mapping’ used hereinafter in the specifications refers to a process of associating and managing various pieces of data (e.g., a unique user key) with a procedure associated with the UE. The data pertain to a specific user (also referred as a subscriber) associated with the UE, a session, or an application within the telecommunication network.

BACKGROUND
[016] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.
[017] The widespread adoption of broadband internet has generated a significant need for a multimedia communication over an Internet Protocol (IP) network (i.e., a telecommunication network). In response to increasing demand, a 3rd Generation Partnership Project (3GPP) introduced an IP Multimedia Subsystem (IMS) to facilitate seamless multimedia communications over these IP networks. The IMS is designed to provide a framework for various multimedia services, including voice, video, messaging, and presence, allowing them to work together seamlessly.
[018] In the telecommunication networks, the IMS registration is initiated by a User Equipment (UE) registration request. It is essential for core network elements, such as a Serving Call Session Control Function (S-CSCF), a Home Subscriber Server (HSS), and/or other nodes to perform this IMS registration. The S-CSCF provides an updated address of the S-CSCF to the HSS and download a service profile for a corresponding subscriber associated with a UE provisioned at the HSS. Once the UE is authenticated, the S-CSCF must perform a third-party registration with an application server on behalf of the UE.
[019] Additionally, in the telecommunication networks, data (e.g., a request for execution of a certain procedure) is communicated between the UE associated with a user and the telecommunication network through various components (such as routers, switches, access points, etc.) along its path. In the telecommunication network (e.g., a Fifth Generation (5G) network), network resource allocation and data path configuration are performed either statically or semi-statically. To ensure optimization for each individual UE or use case (such as a rush hour traffic, a regular hour traffic, an enhanced mobile broadband (eMBB), an Internet of Things (IoT), etc.), all these components are to be optimized. The network resource allocation and parameters (e.g., routing protocols, a throughput, a switching capacity, a port speed, etc.) of these components can be configured dynamically through automation, or a set of parameters of all components along the data path for a specific UE or a use case may also be defined by a network operator.
[020] In the IMS, certain procedures are given more importance than others, such as registration and termination requests, bearer resource control procedures, handover procedures, and the like. Therefore, these procedures must be handled with high priority. Hence, it is necessary to maintain a balance in a utilization of the network resources to ensure that current running procedures are served while also prioritizing higher weightage procedures.
[021] There is, therefore, a requirement in the art for a means to provide a method and a system for managing network resources allocation in a telecommunication network.
OBJECTS
[022] An object of the present disclosure is to provides a method and a system for managing network resources allocation in a telecommunication network.
[023] Another object of the present disclosure is to allow efficient usage of the network resources while handling multiple procedures in the telecommunication network on a priority basis (i.e., by giving a priority to a procedure with a high weightage than a procedure with a low weightage) for a User Equipment (UE).
[024] Another object of the present disclosure is to improve an overall performance of the telecommunication network by making more efficient use of available network resources.
[025] Another object of the present disclosure is to reduce delays or issues in a high weightage procedure by prioritizing the high weightage procedure over a low weightage procedure. For this, the present disclosure facilitates releasing the network resources from the low weightage procedure temporarily for serving the high weightage procedure which require immediate action.
[026] Another object of the present disclosure is to provides flexibility to dynamically adapt to changing conditions and priorities corresponding to the UE by re-allocating the network resources to high weightage procedures as needed.
[027] Other objects and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.
SUMMARY
[028] In an exemplary embodiment, a method for managing network resources allocation in a telecommunication network is disclosed. The method includes receiving a first procedure execution request corresponding to a first procedure from a User Equipment (UE) for executing the first procedure. A unique user key is pre-assigned to the UE. The method includes creating a data context mapping between the unique user key associated with the UE and the first procedure, upon receiving the first procedure execution request. The method includes receiving a second procedure execution request corresponding to a second procedure associated with the UE during an execution of the first procedure. The data context mapping is used to determine the execution of the first procedure. The method includes determining a weightage of the first procedure and the second procedure based on a plurality of weight parameters. The method includes upon determining the weightage of the second procedure to be higher than the first procedure, re-allocating one or more network resources from the first procedure to the second procedure for executing the second procedure.
[029] In an embodiment, the unique user key is at least one of an Internet Protocol (IP) multimedia private identity (IMPI) and an IP multimedia public identity (IMPU).
[030] In an embodiment, the method for creating the data context mapping between the unique user key and the first procedure includes linking the unique user key with the first procedure to denote the execution of the first procedure.
[031] In an embodiment, the method for re-allocating the one or more network resources includes upon determining the weightage of the second procedure to be higher than the first procedure, identifying the one or more network resources associated with the first procedure for allocating to the second procedure.
[032] In an embodiment, the method for re-allocating the one or more network resources includes releasing the one or more network resources from the first procedure. The method further includes performing the data context mapping between the unique user key and the second procedure in response to the releasing the one or more network resources.
[033] In an embodiment, the method for performing the data context mapping between the unique user key and the second procedure includes linking the unique user key with the second procedure to denote the execution of the second procedure.
[034] In an embodiment, the plurality of weight parameters comprises a procedure type, a user subscription and service plan, a network load, a resource utilization, historical usage patterns, and QoS (Quality of Service) requirements.
[035] In another exemplary embodiment, a system for managing network resources allocation in a telecommunication network is disclosed. The system includes a processing unit and a memory coupled to the processing unit and configured to store instructions executable by the processing unit causes the processing unit to receive a first procedure execution request corresponding to a first procedure from a User Equipment (UE) for executing the first procedure. A unique user key is pre-assigned to the UE. The processing unit is further configured to create a data context mapping between the unique user key associated with the UE and the first procedure, upon receiving the first procedure execution request. The processing unit is further configured to receive a second procedure execution request corresponding to a second procedure associated with the UE during an execution of the first procedure. The data context mapping is used to determine the execution of the first procedure. The processing unit is further configured to determine a weightage of the first procedure and the second procedure based on a plurality of weight parameters. The processing unit is further configured to upon determining the weightage of the second procedure to be higher than the first procedure, re-allocate one or more network resources from the first procedure to the second procedure for executing the second procedure.
[036] In an embodiment, the unique user key is at least one of an Internet Protocol (IP) multimedia private identity (IMPI) and an IP multimedia public identity (IMPU).
[037] In an embodiment, to create the data context mapping between the unique user key and the first procedure, the processing unit is configured to link the unique user key with the first procedure to denote the execution of the first procedure.
[038] In an embodiment, to re-allocate the one or more network resources, the processing unit is further configured to identify the one or more network resources associated with the first procedure for allocating to the second procedure, upon determining the weightage of the second procedure to be higher than the first procedure.
[039] In an embodiment, to re-allocate the one or more network resources, the processing unit is further configured to release the one or more network resources from the first procedure. The processing unit is further configured to perform the data context mapping between the unique user key and the second procedure in response to the releasing the one or more network resources.
[040] In an embodiment, to perform the data context mapping between the unique user key and the second procedure, the processing unit is configured to link the unique user key with the second procedure to denote the execution of the second procedure.
[041] In an embodiment, the plurality of weight parameters comprises a procedure type, a user subscription and service plan, a network load, a resource utilization, historical usage patterns, and QoS (Quality of Service) requirements.
[042] The present disclosure discloses a User Equipment (UE) communicatively coupled with a network. The coupling includes a step of receiving, by the network, a connection request from the UE. The coupling includes a step of sending, by the network, an acknowledgment of the connection request to the UE. The coupling includes a step of transmitting a plurality of signals in response to the connection request. Based on the connection request, a management of network resources allocation in the network is performed.
BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING
[043] 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. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[044] FIG. 1 illustrates an exemplary network architecture for implementing a system for managing network resources allocation in a telecommunication network, in accordance with an embodiment of the present disclosure.
[045] FIG. 2 illustrates an exemplary block diagram of the system configured for managing network resources allocation in a telecommunication network, in accordance with an embodiment of the present disclosure.
[046] FIG. 3 illustrates a flow diagram of a method for managing network resources allocation in a telecommunication network, in accordance with an embodiment of the present disclosure.
[047] FIG. 4 illustrates an exemplary process flow for managing network resources allocation in a telecommunication network, in accordance with an embodiment of the present disclosure.
[048] FIG. 5 illustrates an exemplary computer system in which or with which the embodiments of the present disclosure may be implemented.
[049] The foregoing shall be more apparent from the following more detailed description of the disclosure.
LIST OF REFERENCE NUMERALS
100 – Network architecture
102-1, 102-2…102-N – Plurality of Users
104-1, 104-2…104-N – Plurality of User Equipments
106 – Network
108 – System
110 – Entity
112 – Centralized Server
200 – Block Diagram
202 – Memory
204 – A Plurality of Interfaces
206 – Processing Unit
208 – Database
300 – Flow Diagram
400 – Process Flow Diagram
402 – User Equipment (UE)
404 – Home Subscriber Server (HSS)
406 - Servicing Call Session Control Function (S-CSCF)
500 – Computer System
510 – External Storage Device
520 – Bus
530 – Main Memory
540 – Read Only Memory
550 – Mass Storage Device
560 – Communication Port
570 – Processor
DETAILED DESCRIPTION
[050] 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 can 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. Some of the problems discussed above might not be fully addressed by any of the features described herein. Example embodiments of the present disclosure are described below, as illustrated in various drawings in which like reference numerals refer to the same parts throughout the different drawings.
[051] 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.
[052] 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, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.
[053] Also, it is noted that individual embodiments may be described as a process that 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 can 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. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.
[054] 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 like the term “comprising” as an open transition word without precluding any additional or other elements.
[055] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.
[056] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. As used herein, the term “and/or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.
[057] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and/or transmitting one or parameters, performing function/s, communicating with other user devices and transmitting data to the other user devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and/or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to an IP-enabled communication, a Zig Bee, a Bluetooth, a Bluetooth Low Energy, a Near Field Communication, a Z-Wave, a Wi-Fi, a Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.
[058] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The 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 Processor (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 is a hardware processor.
[059] Embodiments herein relate to a method for managing network resources allocations in a telecommunication network. In particular, a first procedure execution request corresponding to a first procedure may be received from a User Equipment (UE) for executing the first procedure. A unique user key is pre-assigned to the UE. The unique user key is an Internet Protocol (IP) Multimedia Private Identity (IMPI) or an IP Multimedia Public Identity (IMPU). Upon receiving the first procedure execution request, a data context mapping is created between the unique user key associated with the UE and the first procedure. Further, a second procedure execution request corresponding to a second procedure may be received corresponding to the UE during an execution of the first procedure. The execution of the first procedure is determined based on the data context mapping. Upon receiving the second procedure execution request, a weightage of the first procedure and the second procedure may be determined based on a plurality weight of parameters. Once the weightage is determined, upon determining the weightage of the second procedure to be higher than the first procedure, one or more network resources from the first procedure may be re-allocated to the second procedure for executing the second procedure.
[060] It is well known to the person skilled in the art, that in a context of Internet Protocol (IP) Multimedia Subsystem (IMS), the IMPI is a unique identifier associated with a user (e.g., a subscriber) of a User Equipment (UE) in the telecommunication network, e.g., an IMS network. The IMPI is used for an authentication and an authorization purpose of the user associated with the UE in the IMS network. The IMPI is used to authenticate the user during registration and communication establishment sessions. Each subscriber in the IMS network has a unique IMPI. Further, the IMPU is another unique identifier (i.e., a public identifier) used in the IMS network. The IMPU is used by other users or UEs to initiate communication sessions with a specific UE associated with a specific user in the IMS network. The IMPU is mapped to a user's current IP address, enabling the other users or the UEs to reach the specific UE regardless of a current location of the specific UE in the IMS network.
[061] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 5.
[062] FIG. 1 illustrates an exemplary network architecture 100 for implementing a system 108 for managing network resources allocations in a telecommunication network, in accordance with an embodiment of the present disclosure. The system 108 may correspond to an Internet Protocol (IP) Multimedia Subsystem (IMS). Further, in an embodiment, the telecommunication network (i.e., a network 106), for example may be a wireless network, such as, an IMS network, a Long-Term Evolution (LTE) network, a Fourth Generation (4G) network, a Fifth Generation (5G) network, a Sixth Generation (6G) network, and the like. In an embodiment, the network architecture 100 may include one or more computing devices or User Equipments (UEs) 104-1, 104-2…104-N associated with one or more users 102-1, 102-2…102-N in an environment. A person of ordinary skill in the art will understand that one or more users 102-1, 102-2…102-N may be individually referred to as the user 102 and collectively referred to as the users 102. Similarly, a person of ordinary skill in the art will understand that one or more UEs 104-1, 104-2…104-N may be individually referred to as the UE 104 and collectively referred to as the UEs 104. A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three UEs 104 are depicted in FIG. 1, however, any number of the UEs 104 may be included without departing from the scope of the ongoing description.
[063] In an embodiment, the UE 104 may include smart devices operating in a smart environment, for example, an Internet of Things (IoT) system. In such an embodiment, the UE 104 may include, but is not limited to, smart phones, smart watches, smart sensors (e.g., a mechanical sensor, a thermal sensor, an electrical sensor, a magnetic sensor, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart televisions (TVs), computers, smart security systems, smart home systems, other devices for monitoring or interacting with or for the user 102 and/or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE 104 may include, but is not limited to, intelligent, multi-sensing, network-connected devices, that can integrate seamlessly with each other and/or with a central server or a cloud-computing system or any other device that is network-connected.
[064] In an embodiment, the UE 104 may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and/or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE 104 may include, but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, the UE 104 may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user 102 or an entity 110 such as a touch pad, a touch enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE 104 may not be restricted to the mentioned devices and various other devices may be used.
[065] In FIG. 1, the UE 104 may communicate with the system 108 through the network 106. In particular, the UE 104 may be communicatively coupled with the network 106. The coupling including steps of receiving, by the network 106, a connection request from the UE 104. Upon receiving the connection request, the coupling including steps of sending, by the network 106, an acknowledgment of the connection request to the UE 104. Further, the coupling including steps of transmitting a plurality of signals in response to the connection request. The plurality of signals is responsible for communicating with the system 108 to manage the network resources allocation in the network 106.
[066] In an embodiment, the network 106 may include at least one of the 4G network, the 5G network, the 6G network, or the like. The network 106 may enable the UE 104 to communicate with other devices in the network architecture 100 and/or with the system 108. The network 106 may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network 106 may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. In another embodiment, the network 106 includes, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, waves, voltage or current levels, some combination thereof, or so forth.
[067] In another exemplary embodiment, a centralized server 112 may include or comprise, by way of example but not limitation, one or more of: a stand-alone server, a server blade, a server rack, a bank of servers, a server farm, a hardware supporting a part of a cloud service or a system, a home server, a hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof.
[068] Although FIG. 1 shows exemplary components of the network architecture 100, in other embodiments, the network architecture 100 may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture 100 may perform functions described as being performed by one or more other components of the network architecture 100.
[069] FIG. 2 illustrates an exemplary block diagram 200 of the system 108 configured for managing network resources allocation in the telecommunication network (e.g., the network 106), in accordance with an embodiment of the present disclosure. FIG. 2 is explained in conjunction with FIG. 1. The telecommunication network may correspond to the wireless network. Examples of the telecommunication network includes, the IMS network, the LTE network, the 4G network, the 5G network, the 6G network, and the like.
[070] The system 108 includes one or more processor(s) or a processing unit 206. The one or more processor(s) may be implemented as one or more microprocessors, microcomputers, microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, one or more processor(s) may be configured to fetch and execute computer-readable instructions stored in a memory 202 of the system 108. The memory 202 may be configured to store one or more computer-readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory 202 may comprise any non-transitory storage device including, for example, a volatile memory such as a Random-Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read-Only Memory (EPROM), a flash memory, and the like.
[071] In an embodiment, the system 108 may include an interface(s) 204. The interface(s) 204 may comprise a variety of interfaces, for example, interfaces for data input and output devices (I/O), storage devices, and the like. The interface(s) 204 may facilitate communication through the system 108. The interface(s) 204 may also provide a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, the processing unit 206 and a database 208. In an embodiment, the processing unit 206 may correspond to the one or more processor(s). In one embodiment, the processing unit 206 may include a Servicing Call Session Control Function (S-CSCF), an Interrogating Call Session Control Function (I-CSCF), and a Breakout Gateway Control Function (BGCF). The S-CSCF, the I-CSCF, and the BGCF are collectively referred as a SIB. In addition, to the S-CSCF, the I-CSCF, and the BGCF (i.e., the SIB), the processing unit 206 may include, but are not limited, a proxy CSCF (P-CSCF) and a Media Resource Function (MRF). In some embodiment, the processing unit 206 may include a Mobility Management Entity (MME) or an Access and Mobility Management Function (AMF). The S-CSCF of the SIB refers to a network component that is configured for managing call sessions in an Internet Protocol (IP) Management Subsystem (IMS) architecture. The S-CSCF is responsible for conducting UE registration and session control for registered UE, user profile handling, authentication/ authorization, service invocation, session routing, and the like. The S-CSCF also facilitates interworking between the IMS network and other networks, allowing seamless communication between IMS users and users on non-IMS networks. The I-CSCF of the SIB is a network component that serves as an entry point into the IMS network from the internet and selects the appropriate S-CSCF for a particular UE’s incoming session. The BGCF of the SIB is a network component that facilitates communication between the IMS network and external networks, enabling services that require interaction with non-IMS networks. The P-CSCF is a network component that serves as a first point of contact for the UE, within the IMS network. The UE sends its session initiation protocol (SIP) signaling messages (e.g., a first procedure execution request and a second procedure execution request), which are used to set up and control multimedia sessions (e.g., a first procedure and a second procedure), to the P-CSCF. The MRF is a network component that handles media processing tasks, such as mixing audio streams or generating tones, required for multimedia sessions.
[072] The processing unit 206 may be configured to receive a first procedure execution request corresponding to the first procedure from the UE. The UE, for example may correspond to the UE 104. The first procedure execution request may be received for executing the first procedure. In an embodiment, a unique user key is pre-assigned to the UE. The unique user key may be at least one of an Internet Protocol (IP) Multimedia Private Identity (IMPI) and an IP Multimedia Public Identity (IMPU). Further, the processing unit 206 may be configured to create a data context mapping between the unique user key associated with the UE and the first procedure upon receiving the first procedure execution request. In particular, to create the data context mapping between the unique user key and the first procedure, the unique user key is linked to the first procedure to denote the execution of the first procedure. As already known to the present skilled in art, the data context mapping in telecommunications refers to a process of associating and managing various pieces of data (e.g., i.e., the unique user key) with procedures (e.g., the first procedure or a second procedure) associated with the UE. The data pertain to a specific user (also referred as a subscriber) associated with the UE, a session, or an application within the telecommunication network. For example, in the data context mapping, user identifiers, i.e., the unique user key (e.g., the IMPI and the IMPU) are associated with current sessions (i.e., the first procedure or the second procedure) associated with the UE, activities, and a state of the telecommunication network. This may ensure that any actions or requests (i.e., the first procedure execution request or a second procedure execution request) made by the user of the UE may be tracked and managed effectively.
[073] Further, the processing unit 206 may be configured to receive the second procedure execution request corresponding to a second procedure associated with the UE during an execution of the first procedure. In other words, while the first procedure is in execution, the processing unit 206 may be configured to receive the second procedure execution request corresponding to the second procedure for executing the second procedure. The execution of the first procedure is determined based on the data context mapping. In other words, the first procedure is under execution may be determined based on the data context mapping created between the unique user key and the first procedure. Upon receiving the second procedure execution request, the processing unit 206 may be configured to determine a weightage of the first procedure and the second procedure. The weightage of the first procedure and the second procedure may be determined based on a plurality of weight parameters. The plurality of weight parameters, for example may include, but are not limited to, a procedure type, a user subscription and service plan, a network load, a resource utilization, historical usage patterns, and QoS (Quality of Service) requirements. In an embodiment, the weightage of the first procedure and the second procedure may be determined to identify a procedure that has a high weightage. Upon determining the weightage of the second procedure to be higher than the first procedure, the processing unit 206 may be configured to re-allocate one or more network resources from the first procedure to the second procedure for executing the second procedure. A method for managing the network resources allocation in the telecommunication network is further explained in detail in conjunction with FIG. 3 and FIG. 4.
[074] In an embodiment, the processing unit 206 may be implemented as a combination of a hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing unit 206. In examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing unit 206 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing unit 206 may comprise a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing unit 206. In such examples, the system 108 may comprise the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system 108 and the processing resource. In other examples, the processing unit 206 may be implemented by electronic circuitry.
[075] FIG. 3 illustrates a flow diagram of a method 300 for managing network resources allocation in the telecommunication network (e.g., the network 106), in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with FIG. 1 and 2. The telecommunication network may correspond to the wireless network. Examples of the telecommunication network may include, the IMS network, the LTE network, the 4G network, the 5G network, the 6G network, and the like. Each step of the method 300 may be performed by one of the S-CSCF of the SIB, the MME, and an Access and Mobility Management Function (AMF) within the processing unit 206 of the system 108.
[076] In order to manage the network resources allocation in the telecommunication network, initially, at step 302, the first procedure execution request corresponding to the first procedure may be received from the UE. In an embodiment, the UE may correspond to the UE 104. The first procedure execution request may be received for executing the first procedure. In an embodiment, the unique user key is pre-assigned to the UE. The unique user key may be at least one of the IMPI and the IMPU. As already known to the person skilled in art, the IMPI is a unique identifier assigned to a user (e.g., a subscriber) of the UE. The IMPI is used for the authentication and the authorization purpose of the user associated with the UE. The IMPI is used to authenticate the user during registration and communication establishment sessions. Each subscriber associated with the UE has a unique IMPI. The IMPI is kept private, ensuring that the user’s identity remains secure during communications. Further, the IMPU is another unique public identifier associated with the UE, typically represented as a Uniform Resource Identifier (URI). The IMPU is used by other users or UEs to initiate communication sessions with the UE associated with the user. The IMPU is mapped to the user's current IP address, enabling the other users or the UEs to reach the UE regardless of a current location of the UE in the telecommunication network.
[077] The unique user key is pre-assigned to the user of the UE during a registration process of the UE with the telecommunication network, upon receiving a registration request from the UE. During the registration process, the user may create user credentials, i.e., a username and a password to connect with the telecommunication network. Upon creating the username and the password, a Home Subscriber Server (HSS) may assign the unique user key to the user of the UE. Further, the HSS may map the unique user key assigned to the user with the user’s subscription information (e.g., the user credentials, the user subscription and service plan, location information, usage history, etc.). Further, the HSS may store the unique user key associated with the user in a database (e.g., the database 208) post mapping.
[078] Upon receiving the first procedure execution request corresponding to the first procedure, at step 304, the data context mapping may be created between the unique user key associated with the UE and the first procedure. In particular, the S-CSCF is configured to create the data context mapping between the unique user key associated with the UE and the first procedure. As already known to the present skilled in art, the data context mapping in telecommunications refers to the process of associating and managing various pieces of data associated with the UE of the user with the procedures (e.g., the first procedure or a second procedure) associated with the UE via the unique user key. The data pertain to the user associated with the UE, a session associated with the UE, or the application within the telecommunication network. For example, in the data context mapping, the user identifiers, i.e., the unique user key (e.g., the IMPI and the IMPU) are associated with current sessions (e.g., the first procedure or the second procedure) associated with the UE, activities, and the state of the telecommunication network. This may ensure that any actions or requests (e.g., the first procedure execution request or the second procedure execution request) made by the user of the UE may be tracked and managed effectively. For example, upon receiving the first procedure execution request for the first procedure, e.g., a video streaming procedure from the UE associated with the user. Initially, the unique user key that is assigned to the user of the UE during the registration process is retrieved from the database. Further, upon retrieving the unique user key, the unique user key is linked to the video streaming procedure to denote that the video streaming procedure is under execution. In particular, the data context mapping of the unique user key with details of the video streaming procedure is performed. The details of the video streaming procedure may be continuously captured in real-time (i.e., during the execution of the video streaming procedure) and stored in the database based on the linking of the unique user key with the video streaming procedure. The details of the video streaming procedure may include, for example, a current state (in progress) of the video streaming procedure, a bandwidth allocated to the video streaming procedure, a time duration associated with the video streaming procedure, an action (e.g., a selection of a video) performed by the user of the UE during the video streaming process, and the like.
[079] Further, at step 306, the second procedure execution request corresponding to the second procedure associated with the UE may be received. In an embodiment, the second procedure execution request may be received by the S-CSCF from the HSS. In some embodiment, the second procedure execution request may be received by S-CSCF from the UE directly. Further, the second procedure execution request corresponding to the second procedure may be received during the execution of the first procedure. In other words, while the first procedure is in execution, the second procedure execution request corresponding to the second procedure may be received for executing the second procedure. In an embodiment, the first procedure is under the execution is determined based on the data context mapping. In other words, the first procedure is under execution may be determined based on the data context mapping created between the unique user key and the first procedure. In continuation to the above example, where the data context mapping was created by linking the unique user key assigned to the UE of the user with the first procedure, i.e., the video streaming procedure. In this case, based on linking the unique user key with the video streaming procedure, the execution of the video streaming procedure is determined. In other words, when the unique user key is linked to the video streaming procedure, the unique user key denotes that the video streaming procedure is under execution or is ongoing. In an embodiment, the data context mapping created between the unique user key and the video streaming procedure may be used to retrieve the details (e.g., the bandwidth, the time duration, etc.) of the video streaming procedure that is captured and stored in the database in while the video streaming process is in execution.
[080] Upon receiving the second procedure execution request, at step 308, a weightage of the first procedure and the second procedure may be determined. The weightage of the first procedure and the second procedure may be determined based on the plurality of weight parameters. The plurality of weight parameters, for example may include, but are not limited to, the procedure type, the user subscription and service plan, the network load, the resource utilization, the historical usage patterns, and the QoS requirements. In should be noted, the weightage of the first procedure and the second procedure may be determined to identify a high weightage procedure and a low weightage procedure between the first procedure and the second procedure. The low weightage procedure, such as routine maintenance, monitoring, or administrative tasks, etc., may correspond to a procedure that do not directly impact a real-time performance or an immediate operation of the telecommunication network. The low weightage procedure is important for an overall efficiency of a system (i.e., the system 108) or the telecommunication network (e.g., the IMS network) but do not require a same level of urgency or the network resources allocation as the high weightage procedure. On the other hand, the high weightage procedure may correspond to a procedure that is crucial for maintaining a connectivity, managing the network resources, or ensuring a quality of critical services. The high weightage procedure is essential for real-time operation and user satisfaction. Examples of the low weightage procedure may include, a background synchronization procedure, a non-emergency network registration procedure, a non-critical service discovery procedure, and the like. Further, examples of the high weightage procedure may include, an emergency call procedure, a registration termination procedure, an admin-initiated procedure, a bearer resource control procedure, and the like.
[081] Further, based on the determined weightage, upon determining the weightage of the second procedure to be higher than the first procedure, the one or more network resources associated with the first procedure may be identified for allocating to the second procedure. The one or more network resources may be identified by the SIB (i.e., the S-CSCF, the I-CSCF, and the BGCF) using an IMPI and IMPU data associated with the UE. The IMPI and IMPU data are maintained within a database (e.g., the database 208) associated with the SIB. Further, using the IMPI and IMPU data, the SIB may decide which network resources (i.e., the one or more network resources) can be re-allocated from the first procedure to the second procedure. Examples of the network resources may include a bandwidth, load balancers, firewalls, Quality of Service (QoS) settings, radio frequency (RF) resources, and the like. Further, once the one or more network resources are identified, at step 310, the one or more network resources may be re-allocated from the first procedure to the second procedure for executing the second procedure. In other words, when the second procedure is determined to be the high weightage procedure and the first procedure is determined to be the low weightage procedure, then the one or more network resources used for executing the first procedure may be re-allocated to the second procedure for executing the second procedure.
[082] In other words, upon determining the second procedure to the high weightage procedure, some network resources or all network resources allocated to the first procedure may be re-allocated to the second procedure based on processing requirements of the second procedure. The processing requirements may be for example, a bandwidth required for processing the second procedure, a latency required for processing the second procedure, a packet loss tolerance required for processing the second procedure, and the like. In some embodiments, the re-allocation of the one or more resources from the first procedure to the second procedure may either be complete or partial. For example, when the first procedure is the video streaming procedure, and the second procedure is a voice calling procedure. In this case, upon determining the upon determining the voice calling procedure to the high weight procedure than the video streamlining procedure, the one or more network resources (e.g., the bandwidth and the QoS settings (e.g., the latency, the packet loss tolerance, etc.)) of all the network resources allocated to the video streaming procedure may be partially re-allocated to the voice calling procedure. For example, the bandwidth that was allocated to the video streaming procedure initially, may be re-allocated partially to the voice calling procedure, such that the bandwidth of the voice calling procedure is higher than the video streaming procedure. In an embodiment, when the bandwidth allocated to the video streaming procedure initially is already less, then the complete bandwidth allocated to the video streaming procedure may be re-allocated to the voice calling procedure.
[083] In order to re-allocate the one or more resources to the second procedure, the one or more network resources may be released from the first procedure. Upon releasing the one or more network resources from the first procedure, the data context mapping is performed between the unique user key and the second procedure in response to releasing. In other words, in the data context mapping, the unique user key is now linked with the second procedure (e.g., the voice calling procedure). The data context mapping is performed between the unique user key and the voice calling procedure to denote that the voice calling procedure is now under execution. In an embodiment, based on the data context mapping, the details corresponding to the voice calling procedure start getting captured and stored in the database in real-time based on linking the unique user key with the voice calling procedure. Once the data context mapping is performed between the unique user key and the second procedure, the one or more network resources that are released from the first procedure get allocated to the second procedure for executing the second procedure. In an embodiment, the data context mapping created between the unique user key and the second procedure may represent that the second procedure is under execution. In some embodiments, based the weightage determined at step 308, when the first procedure is determined to be the high weightage procedure, and the second procedure is determined to be the low weightage procedure. In this embodiment, first the execution of the first procedure is completed, and then the execution of the second procedure may start.
[084] By way of an example, consider a scenario where the first procedure corresponding to which the first procedure execution request is received from the UE may be a background synchronization procedure. The background synchronization procedure is a procedure where a periodic synchronization of data corresponding to the UE associated with the telecommunication network is performed. Further, the second procedure corresponding to which the second procedure execution request associated with the UE is received may be an emergency call procedure. The emergency call procedure is a procedure where a connection needs to be established for the emergency call corresponding to the UE. In this case, the weightage of the second procedure may be determined to be higher than the first procedure. The weightage of the second procedure may be determined to be higher than the first procedure based a weight parameter, e.g., the procedure type. For example, the procedure type of the first procedure may be determined to a periodic (or a regular) procedure type as the background synchronization procedure is carried on a period basis, and the procedure type of the second procedure may be determined to be an urgent (or a critical) procedure type as the emergency call procedure might occur rarely. Further, upon determining the weightage of the emergency call procedure to higher than the weightage of the background synchronization procedure, the one or more resources that were allocated to the background synchronization procedure may be re-allocated from the background synchronization procedure to the emergency call procedure for executing the emergency call procedure.
[085] In an embodiment, upon receiving the registration request from the UE associated with the user, the unique user key is assigned to the UE of the user during the registration process to uniquely identify the user within the telecommunication network. The unique user key is used to authorize the user of the UE, upon receiving a procedure execution request (e.g., the first procedure execution request) corresponding to a procedure (e.g., the first procedure). Further, based on a successful authorization of the user based on the unique user key, the procedure was executed. Notably, in this embodiment, no data context mapping was performed between the unique user key of the user and the procedure to determine that the procedure is under execution. Whereas, in the present invention, the unique user key assigned to the user, is used for creating the data context mapping between the unique user key and the procedure to denote that the procedure is under execution.
[086] In an embodiment, when a new procedure execution request (e.g., the second procedure execution request) corresponding to a new procedure (e.g., the second procedure) is received from the UE of the user. The new procedure only gets executed after the completion of an existing procedure (i.e., the first procedure). There is no provision of determining the weightage of the existing procedure and the new procedure to execute a procedure with a high weightage. In addition, since there is no provision to determine the weightage of procedures (i.e., the existing procedure and the new procedure), then even if the existing procedure is the low weightage procedure, the network resources allocated to the existing procedure cannot be re-allocated to the new procedure. The network resources allocated to the existing procedure get re-allocated to the new procedure only after completely executing the existing procedure. Otherwise, new network resources are allocated to the new resources. However, in the present invention, the weightage of the procedures, e.g., the existing procedure and the new procedure, can be determined. Further, based on the determined weightage, the one or more network resources allocated to the existing procedure can be re-allocated to the new procedure), upon determining the new procedure to be the high weightage procedure. In this way, the present invention facilities efficient user of the network resources in the telecommunication network.
[087] FIG. 4 illustrates an exemplary process flow 400 for managing network resources allocations in the telecommunication network (e.g., the network 106), in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIG. 1, 2 and 3. The telecommunication network may correspond to the wireless network. Examples of the telecommunication network includes, the IMS network, the LTE network, the 4G network, the 5G network, the 6G network, and the like.
[088] FIG. 4 depicts a UE 402, a HSS 404, and a S-CSCF 406. The UE 402 may correspond to the UE 104. In an embodiment, the HSS 404 may correspond to the centralized server 112 that is in communication with the processing unit 206 of the system 108. The S-CSCF 406 may be present within the processing unit 206 of the system 108. It should be noted that, the HSS 404 may be configured to manage subscriber data (i.e., the data associated with the user of the UE) and perform key functions related to user authentication, authorization, and profile management. The HSS 404 may include a database that contains the IMPI and IMPU data, which is user-related information like a user profile, authentication data, and service-related information associated with the user of the UE. The HSS 404, thus, acts as hub for user-related information within the telecommunication network. Further, the S-CSCF 406 may be responsible for managing and controlling call and session setup for multimedia services in the telecommunication network (also referred as the IMS network).
[089] In order to manage the network resources allocation in the telecommunication network, at step 408, the S-CSCF 406 may receive a procedure execution request corresponding to a procedure P1 from the UE 402. The procedure execution request may correspond to the first procedure execution request. Further, the procedure P1 may correspond to the first procedure.
[090] Upon receiving the procedure execution request corresponding to the procedure P1, at step 410, the S-CSCF 406 may create and maintain a data context mapping between a unique user key and the procedure P1. Further, the user key may be one of the IMPI and the IMPU or both.
[091] Further, at step 412, the S-CSCF 406 may be configured to receive a procedure execution request corresponding to a procedure P2 from the HSS 404 with which the UE 402 is associated. In some embodiments, the S-CSCF 406 may receive the procedure execution request corresponding to the procedure P2 from the UE 402. Further, upon receiving the procedure execution request corresponding to the procedure P2, a weightage of the procedure P1 and the procedure P2 may be determined. The weightage may be determined based on the plurality of weight parameters. The plurality of weight parameters, for example may include, but are not limited to, the procedure type, the user subscription and service plan, the network load, the resource utilization, the historical usage patterns, and the QoS requirements.

[092] Upon determining the weightage of the procedure P2 to be higher than the weightage of the procedure P1, at step 414, the one or more network resources associated with the procedure P1 are released for re-allocating the one or more network resources to the procedure P2. In an embodiment, the one or more resources to be re-allocated to the procedure P2 may be identified by the SIB (i.e., the S-CSCF 406, the I-CSCF, and the BGCF) based on the IMPI and IMPU data associated with the unique user key of the UE 402. The IMPI and IMPU data may be maintained within the database (e.g., the database 208) associated with the SIB. Further, to re-allocate the one or more network resources to the procedure P2, the data context mapping may be performed between the user key, i.e., the unique user key (e.g., the IMPI and IMPU) and the procedure P2. Once the data context mapping is performed, the procedure P2 is executed using the one or more network resources captured by the SIB from procedure the P1 and re-allocated to the procedure P2.
[093] Apart from the IMS network, i.e., the telecommunication network, the managing of the network resources allocation of the present disclosure applies to various other telecommunication networks, e.g., the LTE network or the 4G network and the 5G network. In case of the LTE network or the 4G network, the managing of the network resources allocation may be performed at the MME. In case of the LTE network or the 4G network, the unique user key may preferably be an International Mobile Subscriber Identity (IMSI) and an International Mobile Equipment Identity (IMEI). The IMSI is a unique 15-digit number that identifies a specific user associated with the UE in the LTE network or the 4G network. Additionally, the IMEI may be a unique 15-digit number assigned to every UE for identifying the UE. In some embodiments, for the 5G networks, the managing of the network resources allocation of the present disclosure may also be performed at an AMF where the unique user key may preferably be a Subscription Permanent Identifier (SUPI) or the IMEI. The SUPI is a unique identifier used in the 5G network to permanently identify the user of the UE. The SUPI replaces the IMSI and is designed to enhance privacy and security by using a hashed or anonymized form of the user identity to protect it from an unauthorized access and tracking.

[094] FIG. 5 illustrates an exemplary computer system 500 in which or with which embodiments of the present disclosure may be implemented. As shown in FIG. 5, the computer system 500 may include an external storage device 510, a bus 520, a main memory 530, a read-only memory 540, a mass storage device 550, communication port(s) 560, and a processor 570. A person skilled in the art will appreciate that the computer system 500 may include more than one processor and communication ports. The processor 570 may include various modules associated with embodiments of the present disclosure. The communication port(s) 560 may be any of an RS-232 port for use with a modem-based dialup connection, a 10/100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port(s) 560 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 500 connects.
[095] The main memory 530 may be Random-Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 540 may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input/Output System (BIOS) instructions for the processor 570. The mass storage device 550 may be any current or future mass storage solution, which can be used to store information and/or instructions. The mass storage device 550 includes, but is not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and/or Firewire interfaces), one or more optical discs, a Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks.
[096] The bus 520 communicatively couples the processor 570 with the other memory, storage, and communication blocks. The bus 520 may be, e.g. a Peripheral Component Interconnect (PCI)/PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB), or the like, for connecting expansion cards, drives, and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 570 to the computer system 500.
[097] Optionally, operator and administrative interfaces, e.g. a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus 520 to support direct operator interaction with the computer system 500. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) 560. Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 500 limit the scope of the present disclosure.
[098] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.
[099] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.
[0100] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be implemented merely as illustrative of the disclosure and not as a limitation.
[0101] The present disclosure provides technical advancement related to management of network resources allocation in a telecommunication network. This advancement addresses the limitations of existing solutions by determining a weight of procedures sent by a UE and accordingly re-allocating network resources to a procedure with a high weightage. In other words, the present disclosure allows handling of multiple procedures in the telecommunication network based on a priority for the UE. This is done by releasing the network resources from the low weightage procedure temporarily for serving the high weightage procedure which require immediate action. In this way, the present disclosure allows efficient usage of the network resources while executing multiple procedures. In addition, the present disclosure provides flexibility to a system (e.g., the system 108) to dynamically adapt to changing conditions and priorities corresponding to the UE by re-allocating the network resources as needed based on real-time data associated with the UE. Further, the present disclosure improves an overall performance of the telecommunication network by making more efficient use of available network resources and reducing delays or issues in high-weightage procedures.
ADVANTAGES OF THE PRESENT DISCLOSURE
[0102] The present disclosure provides a method and a system for managing network resources allocation in a telecommunication network.
[0103] The present disclosure allows efficient usage of the network resources while handling multiple procedures in the telecommunication network on a priority basis for a User Equipment (UE). The priority for a procedure is determined based on weightage of the procedure, i.e., a procedure with a high weightage may be executed first than a procedure with a low weightage.
[0104] The present disclosure improves an overall performance of the telecommunication network by making more efficient use of available network resources.
[0105] The present disclosure reduces delays or issues in a high weightage procedure by prioritizing the high weightage procedure over a low weightage procedure. For this, the present disclosure facilitates releasing the network resources from the low weightage procedure temporarily for serving the high weightage procedure which require immediate action.
[0106] The present disclosure provides flexibility to dynamically adapt to changing conditions and priorities corresponding to the UE by re-allocating the network resources to high weightage procedures as needed.

,CLAIMS:Claims
We claim:
1. A method (300) for managing network resources allocation in a telecommunication network, the method (300) comprising:
receiving (302), by a processing unit (206), a first procedure execution request corresponding to a first procedure from a User Equipment (UE) for executing the first procedure, wherein a unique user key is pre-assigned to the UE;
upon receiving the first procedure execution request, creating (304), by the processing unit (206), a data context mapping between the unique user key associated with the UE and the first procedure;
receiving (306), by the processing unit (206), a second procedure execution request corresponding to a second procedure associated with the UE, during an execution of the first procedure, wherein the data context mapping is used to determine the execution of the first procedure;
determining (308), by the processing unit (206), a weightage of the first procedure and the second procedure based on a plurality of weight parameters; and
upon determining the weightage of the second procedure to be higher than the first procedure, re-allocating (310), by the processing unit (206), one or more network resources from the first procedure to the second procedure for executing the second procedure.

2. The method (300) as claimed in claim 1, wherein the unique user key is at least one of an Internet Protocol (IP) Multimedia Private Identity (IMPI) and an IP Multimedia Public Identity (IMPU).

3. The method (300) as claimed in claim 1, wherein creating the data context mapping between the unique user key and the first procedure comprises:
linking, by the processing unit (206), the unique user key with the first procedure to denote the execution of the first procedure.

4. The method (300) as claimed in claim 1, wherein re-allocating the one or more network resources comprising:
upon determining the weightage of the second procedure to be higher than the first procedure, identifying the one or more network resources associated with the first procedure for allocating to the second procedure.

5. The method (300) as claimed in claim 1, wherein re-allocating the one or more network resources comprising:
releasing the one or more network resources from the first procedure; and
performing the data context mapping between the unique user key and the second procedure in response to the releasing the one or more network resources.

6. The method (300) as claimed in claim 5, wherein performing the data context mapping between the unique user key and the second procedure comprises:
linking, by the processing unit (206), the unique user key with the second procedure to denote the execution of the second procedure.

7. The method (300) as claimed in claim 1, wherein the plurality of weight parameters comprises a procedure type, a user subscription and service plan, a network load, a resource utilization, historical usage patterns, and QoS (Quality of Service) requirements.

8. A system (108) for managing network resources allocation in a telecommunication network, the system (108) comprising:
a memory (202); and
a processing unit (206) coupled to the memory (202), configured to:
receive (302) a first procedure execution request corresponding to a first procedure from a User Equipment (UE) for executing the first procedure, wherein a unique user key is pre-assigned to the UE;
upon receiving the first procedure execution request, create (304) a data context mapping between the unique user key associated with the UE and the first procedure;
receive (306) a second procedure execution request corresponding to a second procedure associated with the UE during an execution of the first procedure, wherein the data context mapping is used to determine the execution of the first procedure;
determine (308) a weightage of the first procedure and the second procedure based on a plurality weight of parameters; and
upon determining the weightage of the second procedure to be higher than the first procedure, re-allocate (310) one or more network resources from the first procedure to the second procedure for executing the second procedure.

9. The system (108) as claimed in claim 8, wherein the unique user key is at least one of an Internet Protocol (IP) Multimedia Private Identity (IMPI) and an IP Multimedia Public Identity (IMPU).

10. The system (108) as claimed in claim 8, wherein, to create the data context mapping between the unique user key and the first procedure, the processing unit (206) is configured to:
link the unique user key with the first procedure to denote the execution of the first procedure.

11. The system (108) as claimed in claim 8, wherein, to re-allocate the one or more network resources, the processing unit (206) is further configured to:
upon determining the weightage of the second procedure to be higher than the first procedure, identify the one or more network resources associated with the first procedure for allocating to the second procedure.

12. The system (108) as claimed in claim 8, wherein, to re-allocate the one or more network resources, the processing unit (206) is configured to:
release the one or more network resources from the first procedure; and
perform the data context mapping between the unique user key and the second procedure in response to the releasing the one or more network resources.

13. The system (108) as claimed in claim 12, wherein, to perform the data context mapping between the unique user key and the second procedure, the processing unit (206) is configured to:
link the unique user key with the second procedure to denote the execution of the second procedure.

14. The system (108) as claimed in claim 8, wherein the plurality of weight parameters comprises a procedure type, a user subscription and service plan, a network load, a resource utilization, historical usage patterns, and QoS (Quality of Service) requirements.

15. A user equipment (UE) communicatively coupled with a network (106), the coupling comprises steps of:
receiving, by the network (106), a connection request from the UE;
sending, by the network (106), an acknowledgment of the connection request to the UE; and
transmitting a plurality of signals in response to the connection request, wherein based on the connection request, a management of network resources allocation by the network (106) is performed by the method (300) as claimed in claim 1.