DESC:FORM 2
THE PATENTS ACT, 1970
(39 of 1970)
&
The Patent Rules, 2003
COMPLETE SPECIFICATION
(See section 10 & rule 13)
1. TITLE OF THE INVENTION

SYSTEMS AND METHODS FOR MANAGING APPLICATION CONTEXT IN A NETWORK
2. APPLICANT (S)
NAME NATIONALITY ADDRESS
JIO PLATFORMS LIMITED IN 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
[0001] 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 (hereinafter 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.
FIELD OF DISCLOSURE
[0002] The present disclosure relates generally to the field of wireless communication systems. More particularly, the present disclosure relates to systems and methods for managing one or more application contexts in a network.

DEFINITIONS
[0003] 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.
[0004] The expression ‘Network node or a serving-call session control function (S-CSCF)’ refers to the network component responsible for session control and management within the IP Multimedia Subsystem (IMS) network. It plays a central role in handling session-related tasks, including user registration, session establishment, and routing
[0005] The expression ‘Proxy-call session control function (P-CSCF)’ refers to the entry point for the user equipment (UE) into the IMS network. The P-CSCF handles initial registration, forwards requests, and ensures that signalling messages from the UE are properly routed within the network.
[0006] The term ‘Interrogating-call session control function (I-CSCF)’ refers to a network component that serves as the contact point within an operator’s network for all connections destined for a subscriber. The I-CSCF assigns a suitable S-CSCF to handle the session and routes incoming requests accordingly
[0007] The expression ‘Home Subscriber Server (HSS)’ refers to a central database that contains subscriber-related information, such as user profiles, authentication data, and service-related information. It interacts with other network components to authenticate and authorize users and to manage their service subscriptions.
[0008] The term ‘Application Server (AS)’ refers to a server that hosts specific applications and services, such as voicemail, multimedia messaging, and presence services. The AS interacts with the core IMS components to provide additional functionalities and value-added services to users.
[0009] The term ‘application context’ refers to a set of data and parameters used by the network node to manage, track the state and details of a particular session, transaction, or service.
[0010] The term ‘procedure’ refers to a defined set of instructions or rules that outline how a specific task or operation should be carried out within the network or an IMS network, such as initiating a multimedia session or handling user authentication.
[0011] The term ‘audit timer’ refers to a timer mechanism started by a network node to monitor the lifespan of an application context, ensuring that the context is automatically released if not cleared within a specified period, thus preventing resource wastage.
[0012] These definitions are in addition to those expressed in the art.
BACKGROUND OF DISCLOSURE
[0013] 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.
[0014] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog technology that offered only voice services. Further, when the second-generation (2G) technology was introduced, text messaging and data services became possible. The 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, improved network coverage, and security. Currently, the fifth-generation (5G) technology is being deployed, with even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way we connect and interact with technology.
[0015] The widespread adoption of broadband internet has generated a significant need for multimedia communication over IP (Internet Protocol) networks. In response to the increasing demand, an IP Multimedia Subsystem (IMS) to facilitate seamless multimedia communication over these 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. A call session control function (CSCF) in IMS includes three distinct roles: a proxy CSCF (P-CSCF), an interrogating CSCF (I-CSCF), and a serving CSCF (S-CSCF). The CSCF manage all signalling from an end user to services and other networks.
[0016] Cloud computing utilizes centralized resource management and control to uniformly manage, schedule, and distribute software and hardware resources. However, with the emergence of 5G, the internet of things, and the growing popularity of cloud computing applications, the demands for cloud resources in terms of time delay, bandwidth, and other aspects are increasing. This necessitates a more efficient and effective solution.
[0017] In conventional resource allocation systems, a plurality of application context parameters is stored in the S-CSCF and can remain there for a longer period of time due to various reasons such as programming faults or errors at the S-CSCF. This can cause hindrances in building a session when new or impending procedures arrive at the S-CSCF. It is necessary to release the stored parameters in the S-CSCF such that efficient use of resources and application contexts can be achieved.
[0018] There is, therefore, a need in the art to provide a method and a system that can overcome the shortcomings of the existing prior arts.
OBJECTS OF THE PRESENT DISCLOSURE
[0019] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.
[0020] An object of the present disclosure is to provide a system and a method for managing one or more application context in a network.
[0021] Another object of the present disclosure is to release unused application context not only when new procedures are received but also when existing procedures have completed or become idle.
[0022] Another object of the present disclosure is to provide a network node that deploys a session audit timer for releasing the unused application context.
[0023] Yet another object of the present disclosure is to provide a network node that releases the application context upon the expiry of the session audit timer if the application context is not released before the expiry of the audit timer for an impending procedure.
[0024] 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
[0025] In an exemplary embodiment, the present invention discloses a method for managing one or more application contexts in a network. The method comprises receiving, by a network node, at least one procedure from one or more user equipments (UEs) and creating the one or more application contexts corresponding to each of the received at least one procedure. The method further comprises initiating, by the network node, a session audit timer corresponding to the created application context and releasing, by the network node, the one or more application contexts upon expiry of the session audit timer if the one or more application contexts are not released after execution of the received at least one procedure.
[0026] In some embodiments, the present disclosure further comprises releasing a plurality of associated contexts along with the created one or more application contexts. For example, application contexts such as a session application context, a transaction application context, or a service application context are released upon expiry of the session audit timer.
[0027] In some embodiments, the network node is a serving call session control function (S-CSCF).
[0028] In some embodiments, the at least one procedure includes a set of instructions defining how a task is to be performed by the network node.
[0029] In some embodiments, the session audit timer is started simultaneously with the creation of one or more application contexts.
[0030] In some embodiments, the session audit timer has a configurable duration determined based on the type of the received at least one procedure.
[0031] In some embodiments, the releasing of the one or more application contexts includes clearing all associated session resources allocated to the one or more application contexts.
[0032] In an exemplary embodiment, a system for managing one or more application context in a network. The system comprises a processing unit coupled to a network node, wherein the network node is configured to receives at least one procedure from one or more user equipments (UEs). Next, the network node creates the one or more application contexts corresponding to each received procedure. This involves setting up the necessary details and parameters to manage the procedure effectively. Following this, the network node initiates a session audit timer associated with the created one or more application contexts to monitor its usage. Finally, releasing, by the network node, the one or more application contexts upon expiry of the session audit timer if the one or more application contexts are not released after execution of the received at least one procedure. This process ensures that unused application contexts are cleared, optimizing resource management in the network.
[0033] In an exemplary embodiment, user equipment (UE) communicatively coupled with a network node is disclosed. The network node receives at least one procedure from one or more user equipments (UEs) and creates one or more application contexts corresponding to each of the received at least one procedure. The network node initiates a session audit timer corresponding to the created application context and releases the one or more application contexts upon expiry of the session audit timer if the one or more application contexts is not released after execution of the received at least one procedure.
[0034] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure and are not restrictive.
BRIEF DESCRIPTION OF DRAWINGS
[0035] 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 the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.
[0036] FIG. 1 illustrates an exemplary network architecture for managing one or more application contexts in a network, in accordance with embodiments of the present disclosure.
[0037] FIG. 2A illustrates a block diagram of a system for managing one or more application contexts in the network, in accordance with embodiments of the present disclosure.
[0038] FIG. 2B illustrates an exemplary system architecture for managing one or more application contexts in the network, in accordance with an embodiment of the present disclosure, in accordance with embodiments of the present disclosure.
[0039] FIG. 3 illustrates an exemplary flow diagram, in accordance with embodiments of a prior art.
[0040] FIG. 4 illustrates an exemplary flow diagram for managing one or more application contexts in the network, in accordance with embodiments of the present disclosure.
[0041] FIG. 5 illustrates an exemplary flow diagram of a method for managing one or more application contexts in the network, in accordance with embodiments of the present disclosure.
[0042] FIG. 6 illustrates an exemplary computer system in which or with which the system may be implemented, in accordance with an embodiment of the present disclosure.
[0043] 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 – Users
104-1, 104-2…104-N, 302 – User equipments (UEs)
106 – Network
108 – System
200B – System block diagram
202 – One or more processor(s)
204 – Memory
206 – Interface
210 – Processing engine
212, 306 – Network node or serving-call session control function (S-CSCF)
220 – Database
200B – System architecture
214 – Proxy- call session control function (P-CSCF)
216 – Interrogating-call session control function (I-CSCF)
218, 304 – Home subscriber server (HSS)
222 – Application server (AS)
300 – Prior art
400 – Flow diagram
500 – Method flow diagram
600 – Exemplary computer system
610 – External storage device
620 – Bus
630 – Main memory
640 – Read only memory
650 – Mass storage device
660 – Communication port
670 – Processor

DETAILED DESCRIPTION OF DISCLOSURE
[0044] 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 all 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.
[0045] 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.
[0046] 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.
[0047] 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 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.
[0048] 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.
[0049] 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.
[0050] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly 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 and all combinations of one or more of the associated listed items.
[0051] Unless the context otherwise requires any other specific meaning in the entire description, the term “release” and their grammatical variants may also indicate, but not limited to, the activity of clearing, deleting, erasing, cancelling, discarding, freeing, removing, overriding, omitting, aborting, relinquishing, overwriting, or renouncing the unused application context for new upcoming procedure(s) in a network and specifically an IMS network.
[0052] Considering the above problem of non-clearance of application context, the present disclosure describes a method of managing application context of a procedure in the IMS network in a timely manner with the help of a session audit timer. The session audit timer is maintained in the IMS network node, preferably at the S-CSCF node for each procedure. When a procedure is received at the IMS network node, the application context with context parameters is created and a session audit timer is associated with the procedure. Meanwhile, when a new procedure arrives at the same IMS network node, the IMS network node creates an application context with context parameters for the new procedure and starts a new session audit timer. Ideally, the application context with context parameters should be automatically or normally released once the procedure is over with the IMS network node. If not, the session audit timer runs till the timeout condition or expiry and the application context is released by the IMS network node. Releasing the application context helps prevent resource wastage and ensures that unused application contexts are cleared in a timely manner.
[0053] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 6.
[0054] Referring to FIG. 1, the architecture (100) may include one or more computing devices or user equipments (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 user equipments (104-1, 104-2…104-N) may be individually referred to as the user equipment (104) and collectively referred to as the user equipment (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 two user equipments (104) are depicted in FIG. 1, however any number of the user equipments (104) may be included without departing from the scope of the ongoing description.
[0055] In an embodiment, the user equipment (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 user equipment (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, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, where the user equipment (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 the entity such as a touchpad, touch-enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the user equipment (104) may not be restricted to the mentioned devices and various other devices may be used.
[0056] In an embodiment, the user equipment (104) may include smart devices operating in a smart environment, for example, an internet of things (IoT) system. In such an embodiment, the user equipment (104) may include but is not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and/or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the user equipment (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.
[0057] Referring to FIG. 1, the user equipment (104) may communicate with a system (108) through a network (106). In an embodiment, the network (106) may include at least one of a Fifth Generation (5G) network, 6G network, or the like. The network (106) may enable the user equipment (104) to communicate with other devices in the 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), the Internet, the Public Switched Telephone Network (PSTN), or the like. In an embodiment, each of the UE (104) may have a unique identifier attribute associated in addition to that. In an embodiment, the unique identifier attribute may be indicative of Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, International Mobile Subscriber Identity (IMSI), Subscriber Permanent Identifier (SUPI) and the like.
[0058] FIG. 2A illustrates a block diagram (200A) of the system (108) for managing one or more application contexts in a network (106), in accordance with embodiments of the present disclosure.
[0059] In an aspect, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and/or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) 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 (204) may include any non-transitory storage device including, for example, volatile memory such as Random Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.
[0060] Referring to FIG. 2A, the system (108) may include an interface(s) (206). The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I/O devices, storage devices, and the like. The interface(s) (206) may facilitate communication to/from the system (108). The interface(s) (206) 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, processing unit/engine(s) (210) and a database (220).
[0061] In an embodiment, the processing unit/engine(s) (210) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (210). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (210) may be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the processing engine(s) (210) may include 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 engine(s) (210). In such examples, the system (108) may include 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 engine(s) (210) may be implemented by electronic circuitry.
[0062] In an embodiment, the database (220) may include data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor (202) or the processing engines (210). In an embodiment, the database (220) may be separate from the system (108). In an embodiment, the database (220) may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like.
[0063] In an embodiment, the processing engine (210) may include but is not limited to a S-CSCF (212) that may be referred to as a network node (212).
[0064] In an embodiment, the network node (212) is responsible for receiving, creating, and managing one or more application contexts based on at least one procedure received from the one or more UEs (104).
[0065] In an embodiment, the network node (212) may receive the at least one procedure (P1, P2) from the one or more UEs (104). The at least one procedure (P1, P2) represents requests or instructions for initiating multimedia sessions or services. For example, when a user (102) wants to start a video call, the corresponding UE (104) may send a procedure request to the network node (212). This initial step ensures that the system (108) is aware of the requirements of the user (102) and can begin the session management process. Further, the at least one procedure (P1, P2) received by the network node (212) includes instructions defining how tasks are to be performed. These instructions guide the network node (212) in creating and managing the one or more application contexts, ensuring that each procedure (P1, P2) is handled according to predefined rules and protocols. For instance, a procedure (P1, P2) may include detailed steps for authenticating the user (102), allocating necessary resources, and establishing the connection for the video call. This ensures that the at least one procedure (P1, P2) is executed efficiently and consistently, adhering to the established standards within the IMS network. Additionally, the network node (212) is designed to manage these procedures effectively, even when no new procedures are received, by releasing unused one or more application contexts that are no longer needed, optimizing resource utilization.
[0066] In an embodiment, the system (108) may release one or more associated contexts (e.g. child application context) (D2, T2, S2) along with the primary (e.g. parent) application context or created application contexts (D1, T1, S1). The associated contexts (D2, T2, S2), such as child contexts or related contexts created as part of the primary application context (D1, T1, S1), are also managed and released to ensure comprehensive resource management. The release of one or more application contexts includes clearing all associated session resources allocated to one or more application contexts. For example, if a primary session context (D1, T1, S1) has a child context (D2, T2, S2) related to specific services, the system (108) may ensure that all these contexts are released together, freeing up resources.
[0067] In another embodiment, upon receiving the at least one procedure (P1, P2), the network node (212) creates the one or more application contexts (D1, D2, T1, T2, S1, S2) corresponding to the at least one procedure (P1, P2). The created one or more application contexts (D1, D2, T1, T2, S1, S2) includes all necessary information for managing the application context, such as session application context (D1, D2), transaction application context (T1, T2), or service application context (S1, S2). The creation of the one or more application contexts (D1, D2, T1, T2, S1, S2) ensures that all relevant data is organized and accessible, allowing the network node (212) to manage the session effectively.
[0068] In an aspect, the session application context (D1, D2) may be created to manage the entire duration and state of a communication session. For example, during a video call between two users, the session application context (D1, D2) includes parameters like media streams (audio and video), codec information, and quality of service (QoS) requirements. The session application context (D1, D2) ensures smooth setup and maintenance of the call.
[0069] In an aspect, the transaction application context (T1, T2) may be created to handle a specific transaction or task within a session. For example, when a user (102) logs into an online service, the transaction application context (T1, T2) is created for the authentication process. The transaction application context (T1, T2) may include parameters like authentication tokens, user credentials, and security measures, ensuring the login is processed securely and efficiently.
[0070] In an aspect, the service application context (S1, S2) may be created to manage the delivery of a specific service to the user (102). For example, accessing voicemail involves the service application context (S1, S2) that includes user preferences, message retrieval settings, and notification options. The service application (S1, S2) context may ensure the user (102) can listen to, save, or delete messages and receive notifications about new voicemails.
[0071] In an embodiment, the network node (212) initiates a session audit timer (t1, t2) corresponding to the created one or more application contexts (D1, D2, T1, T2, S1, S2). The session audit timer (t1, t2) tracks the duration for which the created application context remains active. The session audit timer has a configurable duration determined based on the type of the received at least one procedure (P1, P2). For instance, if the user (102) starts a multimedia session, the session audit timer (t1, t2) begins counting down from when the one or more application contexts (D1, D2, T1, T2, S1, S2) are created.
[0072] In one aspect, the session audit timer (t1, t2) can be started simultaneously with the created one or more application contexts (D1, D2, T1, T2, S1, S2). This ensures the timing mechanism is in place right from when the one or more application contexts (D1, D2, T1, T2, S1, S2) are created, providing precise control over context duration. For example, the session audit timer (t1, t2) may start as soon as the user (102) initiates a session, allowing the network node (212) to track the session accurately from start to finish.
[0073] In an embodiment, if the created one or more application contexts (D1, D2, T1, T2, S1, S2) are not released before the session audit timer (t1, t2) expires, the network node (212) automatically releases it upon the expiry of the audit timer (t1, t2). This automatic release mechanism prevents inactive or obsolete contexts from occupying valuable network resources.
[0074] In an embodiment, upon receipt of a network internal indication to release an existing multimedia session, the S-CSCF shall generate a BYE request destined for the called user based on the information saved for the related dialog if the S-CSCF serves the calling user of the session. If the S-CSCF requests the session to be refreshed periodically, and the S-CSCF gets the indication that the session will be refreshed, when the session timer expires, the S-CSCF shall delete all the stored information related to the dialog.
[0075] FIG. 2B illustrates a system architecture (200B) for managing one or more application contexts in the network (106), in accordance with the present invention.
[0076] The system architecture (200B) that may interchangeably be used as an IMS network or an IMS control layer may include several components such as a P-CSCF (214), an I-CSCF (216), the network node (212), and an HSS (218). The HSS (218) is connected to an application server (AS) (222). Each of the P-CSCF (214), the I-CSCF (216), the HSS (218) and the AS (222) is connected to the network node (212). The one or more UEs (104) are connected to the system architecture (200B). The one or more UEs (104) may be any device used by the end user to access multimedia services through the system architecture (200B). The one or more UEs (104) may initiate and receive multimedia sessions. The P-CSCF (214) may serve as the first point of contact within the IMS network. The one or more UEs (104) send its session initiation protocol (SIP) signalling messages, which are used to set up and control multimedia sessions, to the P-CSCF (214). The I-CSCF (216) serves as the entry point into the system architecture (200B) from the internet and selects the appropriate network node (212) for the one or more UEs (104) incoming sessions.
[0077] The network node (212) is a fundamental component in the system architecture (200B). The network node (212) plays a central role in session control and management within the system architecture (200B). The network node (212) executes the role of session control, user profile handling, authentication/ authorization, service invocation, session routing and IMS registration. The network node (212) also facilitates interworking between the system architecture (200B) and other networks, allowing seamless communication between IMS users and users on non-IMS networks. In an embodiment, the session control may involves managing the establishment, maintenance, and termination of communication sessions between the users, ensuring smooth data flow by coordinating the exchange of signalling messages and resource allocation. The network node (212) may also handle user profiles, storing and managing the user information, preferences, and service subscriptions for authentication, authorization, and service personalization. Through authentication and authorization, the network node (212) may verify user identities and authorize access to services based on their credentials and privileges, ensuring secure access to the network. As a mediator, the network node (212) may facilitate service invocation by receiving user service requests, routing them to the appropriate providers, and managing service delivery. The network node (212) may also perform session routing, determining optimal paths for communication-based on network topology, resource availability, and quality of service, ensuring efficient data traffic management. The network node (212) may also be responsible for IMS registration, enabling users to access the network (106), receive calls, and maintain availability. Additionally, through interworking, the network node (212) may ensure seamless communication between IMS users and those on non-IMS networks like GSM or UMTS, translating protocols and formats for compatibility. These functionalities enable the network node (212) to support effective and secure communication, ensuring efficient service delivery and resource management within the system architecture (200B).
[0078] The HSS (218) includes a database that contains subscriber-related information like user profiles, authentication data, and service-related information. The HSS (218), thus, becomes a hub for user-related information within the system architecture (200B). The AS (222) hosts specific applications and services like value-added services like voicemail, multimedia messaging, and presence services. These services interact with the core IMS components to provide additional features to the users (102) or the UEs (104). However, a single UE (104), the P-CSCF (214), I-CSCF (216), the network node (212), the HSS (218) and the AS (222) are shown in FIG. 2B, it is understood that more than one entity above may be deployed in the expanding system architecture (200B).
[0079] Additionally, the system architecture (200B) may also include media resource function (MRF) and breakout gateway control function (BGCF) which are not shown in FIG. 2B. The MRF may handle media processing tasks, such as mixing audio streams or generating tones, required for multimedia sessions. The BGCF may facilitate communication between IMS and external networks, enabling services that require interaction with non-IMS networks.
[0080] In an embodiment, the network node (212) is deployed within the system architecture (200B). In another embodiment, the network node (212) is the S-CSCF. The network node (212) may receive at least one procedure (P1, P2) from the one or more UEs (104). Upon receiving the at least one procedure (P1, P2), the network node (212) may create one or more application contexts (D1, D2, T1, T2, S1, S2) corresponding to each of the received plurality of procedures. In an example, the created one or more application contexts (D1, D2, T1, T2, S1, S2) is a session application context (D1, D2), a transaction application context (T1, T2), or a service application context (S1, S2).
[0081] On creating the created one or more application contexts (D1, D2, T1, T2, S1, S2), the network node (212) starts a session audit timer (t1, t2) corresponding to the created one or more application contexts (D1, D2, T1, T2, S1, S2). Further, the network node (212) releases the created one or more application contexts (D1, D2, T1, T2, S1, S2) upon the expiry of the session audit timer (t1, t2) if the created one or more application contexts (D1, D2, T1, T2, S1, S2) are not released before the expiry of the session audit timer (t1, t2) for the at least one procedure (P1, P2).
[0082] FIG. 3 illustrates a problem observed in conventional IMS node regarding the non-clearance of the application context. As shown in FIG. 3, when the S-CSCF or a network node (306 analogous to network node (212)) receives a procedure from the UE (302) analogous to UE (104) or any other network element, it follows a series of steps to create an application context for a session. The term “procedure” may be defined as a set of rules or instructions defining how a particular task should be performed by any IMS network node. The procedure may also include a request from the UE (302) or another network component to initiate a multimedia session or perform a specific service within the IMS network. Upon receiving the procedure (procedure P1), the S-CSCF (306) (also known as an IMS node) creates the application context. The application context includes the required information, parameters, and states related to the specific service or session requested in the procedure. The aforesaid context ensures that the session operates according to the requirements of the service.
[0083] In an embodiment, when the S-CSCF receives, destined for a registered served user, an initial request for a dialog or a request for a standalone transaction, and the request is received either from a functional entity within the same trust domain or contains a valid original dialog identifier or the dialog identifier (From, To and Call-ID header fields) relates to an existing request processed by the S-CSCF, then prior to forwarding the request, the S-CSCF shall:
• check if an original dialog identifier that the S-CSCF previously placed in a Route header field is present in the topmost Route header field of the incoming request.
• remove its own URI from the topmost Route header field.
• if there was an original dialog identifier present in the topmost Route header field of the incoming request then check whether the Request-URI matches the saved Request-URI. The Request-URI and saved Request-URI are considered a match.
If there was an original dialog identifier present in the topmost Route header field of the incoming request, then check whether the Request-URI matches the saved Request-URI. The Request-URI and saved Request-URI are considered a match.
[0084] At step 1 (308) of FIG. 3, the S-CSCF (306) creates the application context with parameters such as session (D1), transaction (T1) and/or services (S1) for procedure P1. The application context parameters are stored in the S-CSCF (306) and may not be cleared or released, and they stay for a longer time with the S-CSCF (306), particularly with the buffer of S-CSCF (306). There may be multiple reasons behind such non-clearance like programming fault or error caused at the S-CSCF (306). When the impending procedure(s) or new procedure(s) such as procedure P2 arrives at the S-CSCF (306) from the HSS (304 analogous to HSS (218)). The S-CSCF (306) may not be able to create application context for new procedures and causes a hindrance in building the session (as shown in step 2 (310) of FIG. 3).
[0085] FIG. 4 illustrates a high-level exemplary flow diagram (400) for managing one or more application contexts in the network (106), in accordance with the present invention.
[0086] At step (402), the network node (212) receives a procedure (P1) from the one or more UEs (104). The procedure (P1) may refer to a set of instructions or requests sent by the one or more UEs (104) to initiate a specific service or session within the IMS network. For example, this could be a request to start a voice call, video call, or any multimedia session. The network node (212) may process these incoming requests and manage the associated application contexts.
[0087] At step (404), the network node (212) creates the one or more application contexts such as a session application context (D1), a transaction application context (T1) and/or a service application context (S1) for the procedure P1. The created one or more application contexts (D1, T1, S1) capture the information and states required to handle the requested service or session. For instance, if the procedure P1 is a request for a video call, the session application context (D1) would include details about the call session, the transaction application context (T1) might include signalling information, and service application context (S1) could encompass media services needed for the video call. Further, the network node (212) starts the session audit timer (timer t1) for the one or more application contexts after the creation of the application contexts. Alternatively, the session audit timer (timer t1) may also be started with the creation of the application context such as on (D1). The session audit timer (t1) ensures that resources are efficiently utilized and released when no longer needed.
[0088] At step (406), the network node (212) receives another procedure (P2) from HSS (218). The HSS (218) may manage user profiles and authentication data. The procedure (P2) may be, for example, an update to the user profile or a new service request. The network node (212) must handle the procedure (P2) similarly to the procedure (P1), ensuring that all necessary resources and the one or more application contexts (D2, T2, S2) associated with (P2) are created and managed properly.
[0089] At step (408), similar to step 404, the network node (212) creates one or more application contexts like session context (D2), transaction context (T2) and/or service context (S2) for the procedure (P2). For instance, if the procedure (P2) is an update to the service plan of the user (102), the session context (D2) would include the updated session details, the transaction context (T2) would handle the signalling for the update, and the service context (S2) might include any additional services activated as part of the new plan. Further, the network node (212) starts the session audit timer (timer t2) for the respective contexts such as on (D2) after creating the application contexts.
[0090] At step (410), the procedure (P2) is completed with the network node (212). Thus, the one or more application contexts parameters like (D2, T2, S2) associated with the procedure (P2) are released normally or automatically. This means that the resources allocated for the procedure (P2) are freed up, ensuring optimal resource utilization within the network (106). For example, after updating the user’s service plan, the network node (212) releases all the application contexts (D2, T2, S2) to avoid unnecessary resource usage.
[0091] At step (412), the procedure (P1) is completed by the network node (212) but the created one or more application contexts like the session context (D1), the transaction context (T1) and/or the service context (S1) associated with the procedure (P1) are not released. This could occur due to various reasons such as programming errors or network issues that prevent the automatic release of resources. For example, suppose the network (106) fails to release the created one or more application contexts (D1, T1, S1) for a completed video call due to a bug. In that case, the created one or more application contexts (D1, T1, S1) remain in the system (108), potentially leading to resource inefficiencies.
[0092] At step (414), the session audit timer (t1) eventually expires for the one or more application contexts (D1, T1, S1) associated with the procedure (P1). The audit timer (t1) is initiated to track the lifecycle of the created one or more application contexts (D1, T1, S1), ensuring that the created one or more application contexts (D1, T1, S1) do not persist longer than necessary. Once the audit timer (t1) expires, the network node (212) forcefully releases the created one or more application contexts like the session context (D1), the transaction context (T1) and/or the service context (S1). This ensures that the audit timer (t1) provides a fallback mechanism to free up resources even if the automatic release fails. For instance, after the timer expiry, the resources tied to the completed video call are finally released, ensuring they can be used for other active procedures.
[0093] FIG. 5 illustrates a method (500) for managing one or more application contexts in the network (106), in accordance with embodiments of the present disclosure.
[0094] At step 502, a network node (212) receives at least one procedure (P1, P2) from the one or more UEs (104). The network node (212) is typically a S-CSCF. The S-CSCF (212) plays a central role in managing sessions and services within the IMS network, making it the logical choice for handling the procedures and one or more application context. The at least one procedure (P1, P2) includes requests or instructions sent by the one or more UEs (104) to initiate or manage services within the IMS network. For example, the one or more UEs (104) could send the at least one procedure (P1, P2) or instructions to initiate a voice call, start a video conference, or update its service profile.
[0095] In an aspect, the at least one procedure (referred here as P1, P2) encompasses a set of instructions that define how a task may be performed by the network node (212). For example, the set of instructions could be a request to start a voice call, video call, or any multimedia session. The network node (212) may process these incoming requests and manage the one or more application contexts. The at least one procedure (P1, P2) may range from simple service requests to complex session management tasks, each triggering the creation and management of the one or more application contexts. For example, the user (102) wants to listen to their voicemail messages. The procedure begins when the UE (104) requests the network node (212) to retrieve and playback the voicemail messages. The network node (212) creates a service application context to manage this request. The service application context may include essential information such as user details, voicemail metadata, and playback instructions, ensuring that the voicemail retrieval is processed efficiently and correctly. Additionally, the user (102) may initiate a video conference involving multiple participants for the complex session management tasks. The UE (104) sends a detailed request to the network node (212) to set up and manage the video conference session. This includes tasks such as inviting participants and configuring media settings.
[0096] At step 504, the method (500) is configured to create, by the network node (212), the one or more application contexts corresponding to the received at least one procedure (P1, P2). Additionally, the method (500) can handle various types of one or more application contexts, including the session application context (D1, D2), a transaction application context (T1, T2), and a service application context (S1, S2). Each type of the created one or more application contexts corresponds to different aspects of the service or procedure requested by the one or more UEs (104).
[0097] At step 506, the method (500) is configured to initiate, by the network node (212), a session audit timer corresponding to the created one or more application contexts (D1, D2, T1, T2, S1, S2). The session audit timer (t1, t2) serves as a monitoring mechanism to track and define the maximum lifespan of the created one or more application contexts (D1, D2, T1, T2, S1, S2). The session audit timer has a configurable duration determined based on the type of the received at least one procedure (P1, P2). For example, if a video call session is initiated, the session audit timer (t1, t2) starts counting down from a predefined time value. The session audit timer (t1, t2) helps ensure that the created one or more application contexts (D1, D2, T1, T2, S1, S2) do not persist longer than necessary, thus preventing resource wastage.
[0098] At step 508, the method (500) is configured to release, by the network node (212), the created one or more application contexts (D1, D2, T1, T2, S1, S2) upon expiry of the session audit timer (t1, t2) if the created one or more application contexts (D1, D2, T1, T2, S1, S2) are not released before the expiry of the session audit timer. This means that if the service or session associated with the at least one procedure (P1, P2) is completed and the created one or more application contexts (D1, D2, T1, T2, S1, S2) are no longer needed, the created one or more application contexts (D1, D2, T1, T2, S1, S2) should be automatically released when the corresponding session timer (t1, t2) expires.
[0099] In an embodiment, the procedure (P2) is completed with the network node (212). Thus, the one or more associated application context parameters like the session (D2), the transaction (T2) and/or the services (S2) associated with the procedure (P2) are released normally or automatically. This means that the resources allocated for the procedure (P2) are freed up, ensuring optimal resource utilization within the network (106). For example, after updating the user’s service plan, the network node (212) releases all the associated context parameters (D2, T2, S2) to avoid unnecessary resource usage.
[00100] In an embodiment, the procedure (P1) is completed by the network node (212) but the created one or more application contexts like the session (D1), the transaction (T1) and/or the services (S1) associated with the procedure (P1) are not released. This could occur due to various reasons such as programming errors or network issues that prevent the automatic release of resources. For example, suppose the network (106) fails to release the created one or more application contexts (D1, T1, S1) for a completed video call due to a bug. In that case, the created one or more application contexts (D1, T1, S1) remain in the system (108), potentially leading to resource inefficiencies.
[00101] In an embodiment, the session audit timer (t1) eventually expires for the one or more application contexts (D1, T1, S1) associated with the procedure (P1). The audit timer (t1) is initiated to track the lifecycle of the created one or more application contexts (D1, T1, S1), ensuring that the created one or more application contexts (D1, T1, S1) do not persist longer than necessary. Once the audit timer (t1) expires, the network node (212) forcefully releases the created one or more application contexts like the session (D1), the transaction (T1) and/or the services (S1). The release of one or more application contexts includes clearing all associated session resources allocated to one or more application contexts. This ensures the audit timer (t1) provides a fallback mechanism to free up resources even if the automatic release fails. For instance, after the timer expiry, the resources tied to the completed video call are finally released, ensuring they can be used for other active procedures
[00102] FIG. 6 illustrates an exemplary computer system (600) in which or with which embodiments of the present disclosure may be implemented. As shown in FIG. 6, the system (108) may include an external storage device (610), a bus (620), a main memory (630), a read-only memory (640), a mass storage device (650), a communication port (660), and a processor (670). A person skilled in the art will appreciate that the system (108) may include more than one processor (670) and communication ports (660). Processor (670) may include various modules associated with embodiments of the present disclosure.
[00103] In an embodiment, the communication port (660) is 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 (660) is chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the system (108) connects.
[00104] In an embodiment, the memory (630) is Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (640) is 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 (670).
[00105] In an embodiment, the mass storage (650) is any current or future mass storage solution, which is used to store information and/or instructions. Exemplary mass storage solutions include, but are 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, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks (e.g., SATA arrays).
[00106] In an embodiment, the bus (620) communicatively couples the processor(s) (670) with the other memory, storage, and communication blocks. The bus (620) is, 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 (670) to the system (108).
[00107] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus (620) to support direct operator interaction with the system (108). Other operators and administrative interfaces are provided through network connections connected through the communication port (660). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary illustration (600) limit the scope of the present disclosure.
[00108] In an exemplary embodiment, user equipment (UE) communicatively coupled with a network node is disclosed. The network node receives at least one procedure from one or more user equipments (UEs) and creates one or more application contexts corresponding to each of the received at least one procedure. The network node initiates a session audit timer corresponding to the created application context and releases the one or more application contexts upon expiry of the session audit timer if the one or more application contexts is not released before the expiry of the session audit timer.
[00109] While considerable emphasis has been placed herein on the preferred embodiments, it will be appreciated that many embodiments can be made, and 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.
[00110] The present disclosure provides technical advancement related to managing one or more application contexts within an IP Multimedia Subsystem (IMS) network. This advancement addresses the limitations of existing solutions by introducing a systematic method for creating, monitoring, and automatically releasing application contexts. By implementing a session audit timer initiated upon creating an application context and automatically releasing the context upon the session audit timer expiry, the present disclosure ensures efficient resource management, automatic error handling, and improved network performance. These inventive aspects enhance the handling of multimedia sessions and transactions, resulting in faster service response times, improved user experiences, and cost-effective network operations. Overall, the present disclosure offers significant improvements in performance, efficiency, and reliability within IMS networks.
ADVANTAGES OF THE PRESENT DISCLOSURE
[00111] The present disclosure described herein above has several technical advantages including, not limited to, releasing unused application context of a procedure by a network node, but also:
• running the session audit timer upon creation of the application context;
• releasing the application context upon the expiry of the session audit timer if the same is not released before the expiry of the session audit timer for an impending procedure;
• efficiently using application context in the IMS network;
• managing resources by clearing unused application context;
• automatically clearing application context which are no longer needed; and
• automatically clearing application context when the application context was not cleared due to a programming fault or error caused in the network node.

,CLAIMS:CLAIMS
We claim:
1. A method (500) for managing one or more application contexts in a network (106), the method (500) comprising:
receiving (502), by a network node (212), at least one procedure from one or more user equipments (UEs) (104);
creating (504), by the network node (212), the one or more application contexts corresponding to each of the received at least one procedure;
initiating (506), by the network node (212), a session audit timer corresponding to the created one or more application contexts; and
releasing (508), by the network node (212), the one or more application contexts upon expiry of the session audit timer if the one or more application contexts are not released after execution of the received at least one procedure.

2. The method (500) as claimed in claim 1, further comprises releasing a plurality of associated contexts along with the created one or more application contexts.

3. The method (500) as claimed in claim 1, wherein the network node (212) is a serving call session control function (S-CSCF).

4. The method (500) as claimed in claim 1, wherein the at least one procedure includes a set of instructions defining how a task is to be performed by the network node (212).

5. The method (500) as claimed in claim 1, wherein the session audit timer is started simultaneously with the creation of the one or more application contexts.

6. The method (500) as claimed in claim 1, wherein the session audit timer has a configurable duration determined based on the type of the received at least one procedure.

7. The method (500) as claimed in claim 1, wherein the releasing of the one or more application contexts includes clearing all associated session resources allocated to the one or more application contexts.

8. A system (108) for managing one or more application contexts in a network (106), the system (108) comprising:
a processing unit (208) coupled to a network node (212), wherein the network node (212) is configured to:
receive (302), by the network node (212), at least one procedure from one or more user equipments (UEs) (104);
create (304), by the network node (212), the one or more application contexts corresponding to each of the received at least one procedure;
initiate (306), by the network node (212), a session audit timer corresponding to the created application context; and
release (308), by the network node (212), the one or more application contexts upon expiry of the session audit timer if the one or more application contexts are not released after execution of the received at least one procedure.

9. The system (108) as claimed in claim 8, further comprises releasing a plurality of associated contexts along with the created one or more application contexts.

10. The system (108) as claimed in claim 8, wherein the network node (212) is a serving-call session control function (S-CSCF).

11. The system (108) as claimed in claim 8, wherein the at least one procedure includes a set of instructions defining how a task is to be performed by the network node (212).

12. The system (108) as claimed in claim 8, wherein the session audit timer is started simultaneously with the creation of the one or more application contexts.

13. The system (108) as claimed in claim 8, wherein the session audit timer has a configurable duration determined based on the type of the received at least one procedure.

14. The system (108) as claimed in claim 8, wherein the releasing of the one or more application contexts includes clearing all associated session resources allocated to the one or more application contexts.

15. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of:
receiving (502), by a network node (212), at least one procedure from one or more user equipments (UEs) (104);
creating (504), by the network node (212), one or more application contexts corresponding to each of the received at least one procedure;
initiating (506), by the network node (212), a session audit timer corresponding to the created one or more application contexts; and
releasing (508), by the network node (212), the one or more application contexts upon expiry of the session audit timer if the one or more application contexts are not released after execution of the received at least one procedure.