Method and system for maintaining one or more sessions in a network

Abstract

The present disclosure provides a system (108) and a method (500) for maintaining one or more sessions in a network (106). The method (500) includes receiving a policy create request from a Session Management Function (SMF) (302). Further, the method (500) includes extracting a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI) from the received policy create request. The method (500) further includes identifying if a combination of the SUPI, the DNN and the S-NSSAI is a unique combination. Based on identification, the method (500) includes determining if an interface between the PCF (304) and a Traffic Detection Function (TDF) (306) is enabled. Based upon the determination, the method (500) includes creating a session for the unique combination and transmitting a TDF session request (TSR) towards the TDF (306) for maintaining the created session for the unique combination.

Description

METHOD AND SYSTEM FOR MAINTAINING ONE OR MORE SESSIONS IN A NETWORKRESERVATION 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.TECHNICAL FIELD

[0002] The present disclosure relates to a field of telecommunications network.In particular, the present disclosure relates to a method and a system for maintaining one or more sessions in a network.DEFINITION

[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 term ‘Subscription Permanent Identifier (SUPI)’ used herein in the specification refers to a permanent, unique identifier assigned to a user in fifth generation (5G) networks. The SUPI is used to identify the user across various network operations and services.

[0005] The term ‘Data Network Name (DNN)’, as used herein in the specification refers to an identifier of a data network that a user equipment (UE) connects to in the 5G network. The DNN specifies the data network that a user wishes to connect to within the 5G network. The DNN is equivalent to the AccessPoint Name (APN) in 4G systems. The DNN is crucial for directing user traffic to the appropriate external network, like the internet or an enterprise network.

[0006] The term ‘Policy Control Function (PCF)’, as used herein in the specification refers to a core network component of the 5G network architecture. The PCF in the 5G network is responsible for managing and enforcing policies that control network behaviour, such as Quality of Service (QoS), bandwidth allocation, and session management. The PCF communicates with other core network functions to ensure that user sessions are handled according to predefined rules.

[0007] The term ‘Traffic Detection Function (TDF)’, as used herein in the specification refers to a core network component of the 5G network architecture. The TDF is used in telecommunication networks to monitor and detect specific types of traffic flows. The TDF applies predefined rules to identify, manage, and steer traffic in real time, ensuring optimal use of network resources.

[0008] The term ‘TDF session request (TSR)’, as used herein in the specification refers to a message involved in the process of managing traffic detection and steering within the network. This message is sent by the PCF or other control-plane network functions to the TDF.

[0009] The term ‘User Plane Function (UPF)’, as used herein in the specification refers to a core network component of the 5G network architecture. The UPF is responsible for handling user traffic in 5G network. The UPF plays a key role in routing and forwarding data between the user equipment and external networks. The UPF also handles data path selection, QoS enforcement, and traffic steering based on policies set by the PCF.

[0010] The term ‘Session Management Function (SMF)’, as used herein in the specification refer to a core network component of the 5G network architecture. The SMF handles session-related functions in the 5G networks, such as session establishment, modification, and termination. The SMF also manages internet protocol (IP) address allocation, QoS, and interacts with the UPF for routing data.

[0011] The term ‘network slicing’, as used herein in the specification allows plurality of logical networks to be created on top of a shared physical infrastructure. Each slice is isolated and optimized for specific use cases, such as enhanced mobile broadband (eMBB), massive machine-type communication (mMTC), or ultrareliable low latency communication (URLLC).

[0012] The term ‘Slice Identifier (SID)’ as used herein in the specification refer to a key component used to distinguish different network slices. The SID may consist of a Slice / Service Type (SST) and a Slice Differentiator (SD). The SST indicates the type of service, such as eMBB, URLLC, mMTC and the SD indicates an optional 3 -octet field that differentiates slices with the same SST.

[0013] These definitions are in addition to those expressed in the art.BACKGROUND

[0014] 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.

[0015] In the evolution of 5th generation (5G) networks, a Policy Control Lunction (PCL) serves as a central component responsible for policy enforcement and session management. The PCL is crucial in managing how data traffic is handled across the network, ensuring that data packets are directed to an appropriate User Plane Lunctions (UPLs) based on predetermined policies. One of the mechanisms employed by the PCL to achieve this is through Traffic Detection Lunction (TDF) Session Request (TSR) messages, which are utilized for traffic steering. The TSR messages instruct the network on how to route traffic based on various criteria, such as service requirements, quality of service (QoS) levels, and the characteristics of the data being transmitted.

[0016] However, the conventional implementation of the session management mechanism within the PCF is limited by its inability to maintain plurality of concurrent sessions in the 5G network. When a new TSR message is initiated for a particular user, the existing session associated with that user is overwritten. The conventional approach results in the loss of the previous session's context and leads to inefficiencies in resource allocation. For instance, the need to manage plurality of sessions become apparent, when different types of services or applications are being used simultaneously by the user. However, the conventional system’s inability to support plurality of concurrent sessions means that only one service can be managed effectively at any given time, impacting the granularity of traffic steering within the network.

[0017] There is, therefore, a need in the art to provide a method and a system that can mitigate the disadvantages of the prior art.SUMMARY OF THE DISCLOSURE

[0018] In an exemplary embodiment, a method for maintaining one or more sessions in a network is described. The method includes receiving a policy create request from a Session Management Function (SMF). Further, the method includes extracting a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI) from the received policy create request. The method further includes identifying if a combination of the SUPI, the DNN and the S-NSSAI is a unique combination. Based upon the identification, the method includes determining if an interface between the PCF and a Traffic Detection Function (TDF) is enabled. Based upon the identification, the method further includes creating a session for the unique combination and transmitting a TDF session request (TSR) towards the TDF for maintaining the created session for the unique combination.

[0019] In an embodiment, the method further includes overwriting an existing session at the PCF using the SUPI, the DNN and the S-NSSAI when the identified combination is not a unique combination.

[0020] In another embodiment, the unique combination is identified by comparing the combination of the SUPI, the DNN and the S-NSSAI with an existing combination at the PCF.

[0021] In another embodiment, the method further includes receiving a traffic session answer from the TDF in response to the TSR.

[0022] In another embodiment, the method further includes receiving a success response message from the PCF in response to the policy create request.

[0023] In another exemplary embodiment, a system for maintaining one or more sessions in a network is described. The system includes a Policy Control Function (PCF). The PCF is configured to receive a policy create request from a Session Management Function (SMF). Further, the PCF is configured to extract a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI) from the received policy create request. The PCF is configured to identify if a combination of the SUPI, the DNN and the S-NSSAI is a unique combination. Based upon the identification, the PCF is configured to determine if an interface between the PCF and a Traffic Detection Function (TDF) is enabled. Based on the determination, the PCF is configured to create a session for the unique combination and transmit a TDF session request (TSR) towards the TDF for maintaining the created session for the unique combination.

[0024] In another exemplary embodiment, a computer program product including a non-transitory computer-readable medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for maintaining one or more sessions in a network. The method includes receiving a policy create request from a Session Management Function (SMF). Further, the method includes extracting a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI) from the received policy create request. The method further includes identifying if a combination of the SUPI, the DNN and theS-NSSAI is a unique combination. Based upon the identification, the method includes determining if an interface between the PCF and a Traffic Detection Function (TDF) is enabled. Based upon the identification, the method further includes creating a session for the unique combination and transmitting a TDF session request (TSR) towards the TDF for maintaining the created session for the unique combination.OBJECTIVES OF THE PRESENT DISCLOSURE

[0025] Some of the objects of the present disclosure, which at least one embodiment herein satisfies, are as follows:

[0026] An objective of the present disclosure is to provide a method and a system to enable a Policy Control Function (PCF) in a 5th Generation (5G) network to maintain more than one session based on a combination of a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Slice Identifier (SID).

[0027] Another objective of the present disclosure is to provide a method and a system to enhance the traffic steering within the 5G network, ensuring that the network effectively manage and allocate resources for various services and applications used by a user.

[0028] Another objective of the present disclosure is to improve the overall performance of the 5G network by enabling the PCF to manage plurality of concurrent sessions for a single user, each tailored to different services, applications, or slices.

[0029] Another objective of the present disclosure is to support the scaling of PCF deployments to accommodate a large number of users and diverse service offerings without compromising resource efficiency or performance of the network.

[0030] Another objective of the present disclosure is to ensure that users receive the best quality of service (QoS), regardless of the number of concurrentservices they are accessing, by maintaining plurality of sessions based on the combination of the SUPI, the DNN, and the SID.

[0031] Other objectives 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.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWINGS

[0032] 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.

[0033] FIG. 1 illustrates an exemplary network architecture of a system configured for maintaining one or more sessions in a network, in accordance with an embodiment of the present disclosure.

[0034] FIG. 2 illustrates an exemplary block diagram of the system configured for maintaining one or more sessions in the network, in accordance with an embodiment of the present disclosure.

[0035] FIG. 3 illustrates an exemplary system architecture for maintaining one or more sessions in the network, in accordance with an embodiment of the present disclosure.

[0036] FIG. 4 illustrates an exemplary process flow of a method for maintaining one or more sessions in the network, in accordance with an embodiment of the present disclosure.

[0037] FIG. 5 illustrates a flow diagram of a method for maintaining one or more sessions in the network, in accordance with an embodiment of the present disclosure.

[0038] FIG. 6 illustrates an exemplary computer system in which or with which the embodiments of the present disclosure may be implemented.

[0039] The foregoing shall be more apparent from the following detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - User(s)104 -User Equipments (UEs)106 - Network108 - System200 - Block diagram202 - Processor(s)204 - Memory206 -Interface(s)208 - Processing engine210 - Database12 - Receiving module214 - Extracting module216 -Identifying module218 - Traffic Detection Function (TDF) interface module220 - Session module300 - System Architecture302 - Session Management Function (SMF)304 - Policy Control Function (PCF)306 - Traffic Detection Function (TDF)400 - Process Flow500 - Method600 - A computer system610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION

[0040] 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.

[0041] 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.

[0042] 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.

[0043] Also, it is noted that individual embodiment may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, astructure 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.

[0044] 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.

[0045] 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.

[0046] 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.

[0047] 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 fimction / 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 IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, 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, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer,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.

[0048] 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 Signalling Processing (DSP) core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input / output processing, and / or any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor is a hardware processor.

[0049] While considerable emphasis has been placed herein on the components and component parts of 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 embodiment, as well as other 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 interpreted merely as illustrative of the disclosure and not as a limitation.

[0050] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog, offering only voice services. Further, text messaging and data services became possible when the second-generation (2G) technology was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technology revolutionized wireless communication with faster data speeds, improved network coverage, and security. Currently, fifth generation (5G)technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devices simultaneously. These advancements represent a significant leap forward from previous generations, enabling enhanced mobile broadband, improved Internet of Things (loT) connectivity, and more efficient use of network resources. 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 to connect and interact with technology.

[0051] In a 5th Generation (5G) network, a Policy Control Function (PCF) plays an important role in enforcing policies related to network usage and managing sessions for users. The session refers to a specific communication instance between a user's device and the 5G network, governed by certain policies such as Quality of service (QoS), resource allocation, and traffic steering. Ideally, the PCF should be capable of maintaining and managing plurality of sessions for a single user, each tailored to specific services, applications, or network slice to enable more efficient use of network resources. Moreover, it may enhance the overall performance of the network, ensuring that users receive the quality of service they expect, regardless of the number of concurrent services they are accessing.

[0052] However, in conventional techniques, the PCF limits the traffic steering, as only one session based on a combination of a Subscription Permanent Identifier (SUPI) and a Data Network Name (DNN) is maintained. The SUPI uniquely identifies a user, while the DNN specifies the particular data network the user wants to access. Conventionally, the PCF overwrites existing sessions when initiating new Traffic Detection Function (TDF) Session Request (TSR) messages, resulting in inefficient resource allocation. All traffic for the user is handled through a single session. The conventional approach limits the network's ability to steer traffic based on the specific needs of different services or applications, resulting in suboptimal performance and underutilization of available resources.

[0053] There is, therefore, a need for a method and a system that maintain plurality of concurrent sessions for a single user. The present disclosure provides an improved method and a system that maintains plurality of sessions for the single user based on a combination of the SUPI, the DNN, and a Slice Identifier (SID). The SID helps in distinguishing different network slices accessed by the user simultaneously, without overwriting the current session. The present disclosure provides a method and a system that introduces the capability for the PCF to maintain plurality of concurrent sessions for the same user, differentiated by the combination of the SUPI, the DNN, and the SID. The combination allows the network to manage distinct traffic flows independently, providing tailored QoS for each session. For example, a user may have separate sessions for video streaming, gaming, and internet of things (loT) device management, each optimized according to the specific needs. By allowing plurality of sessions, the network may allocate resources more precisely, ensuring that each service receives the appropriate level of resources based on its demands and resources are utilized efficiently, improving the overall quality of service provided to the user.

[0054] The present disclosure provides a solution to differentiate between the specific needs of different services or applications. The present disclosure provides a method and a system that prevents session overwriting by allowing plurality of concurrent sessions, ensuring that all active services for a user continue without interruption, maintaining service continuity and improving the overall reliability of the network. Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0055] The various embodiments throughout the disclosure will be explained in more detail with reference to FIG. 1- FIG. 6.

[0056] FIG. 1 illustrates an exemplary network architecture 100 of a system 108 for maintaining one or more sessions in a network 106, in accordance with an embodiment of the present disclosure. As illustrated in FIG. 1, the network architecture 100 may include one or more 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 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 collectively referred to as the UE 104 or the UEs 104. Although only three UE 104 are depicted in FIG. 1, however, any number of the UE 104 may be included without departing from the scope of the ongoing description.

[0057] In an embodiment, the UE 104 may include smart devices operating in a smart environment, for example, loT system. In such an embodiment, the UE 104 may include, but are not limited to, smartphones, smart watches, smart sensors (e.g., a mechanical, a thermal, an electrical, a magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, a smart television (TV), computers, a smart security system, a 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 UE 104 may include, but not limited to, intelligent, multisensing, network-connected devices, that may integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0058] Additionally, in some embodiments, the UE 104 may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), awearable computer device (e.g., aheadmounted 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 are not limited to, any electrical, electronic, electromechanical, orequipment, 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 such as a touchpad, 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.

[0059] In FIG. 1, the UE 104 may communicate with the system 108 through the network 106 for sending or receiving various types of data. In an embodiment, the network 106 may include at least one of a 5th Generation (5G) network, a 6th Generation (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), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0060] In an embodiment, the network 106 may include, 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. The network 106 may also include, by way of example but not limitation, one or more of, a wireless network, a wired network, an internet, an intranet, a public network, a private network, a packet-switched network, a circuit-switched network, an ad hocnetwork, an infrastructure network, the PSTN, a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0061] In an embodiment, the system 108 may include a Policy Control Function (PCF). The PCF is a network element that manages and enforces policies for various network functionalities. The PCF may act as a central control point for defining and applying rules that govern how users and UEs interact with the network, ensuring optimal performance, security, and resource allocation. Further, the PCF ensures the network behaves as intended, based on predefined rules and the specific needs of different services and applications. In some embodiments the PCF may receive a policy create request from a Session Management Function (SMF). The PCF may then extract a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI) from the received policy create request. The PCF may further identify if a combination of the SUPI, the DNN and the S-NSSAI is a unique combination. Based on the identification, the PCF may determine if an interface between the PCF and a Traffic Detection Function (TDF) is enabled. Based on the determination, the PCF may create a session for the unique combination and transmitting a TDF session request (TSR) towards the TDF for maintaining the created session for the unique combination.

[0062] In an embodiment, the UE 104 is communicatively coupled with the network 106. The network 106 may receive a connection request from the UE 104. The network 106 may send an acknowledgment of the connection request to the UE 104. The UE 104 may transmit a plurality of signals in response to the connection request.

[0063] 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 performfunctions described as being performed by one or more other components of the network architecture 100.

[0064] FIG. 2 illustrates an exemplary block diagram 200 of the system 108 configured for maintaining one or more sessions in the network 106, in accordance with an embodiment of the disclosure.

[0065] In an embodiment, 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, 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 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.

[0066] In an embodiment, 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 (RO), storage devices, and the like. The interface(s) 206 may facilitate communication through 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, a processing engine 208 and a database 210.

[0067] In an embodiment, the system 108 may include a processing engine 208 that may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine 208. In examples described herein, such combinations ofhardware and programming may be implemented in several different ways. For example, the programming for the processing engine 208 may be processorexecutable instructions stored on a non-transitory machine -readable storage medium and the hardware for the processing engine 208 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 engine 208. 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 engine 208 may be implemented by electronic circuitry. In an embodiment, the processing engine 208 may be implemented within the PCF. Further, the processing engine 208 may include a receiving module 212, an extracting module 214, an identifying module 216, a Traffic Detection Function (TDF) interface module 218 and a session module 220.

[0068] In an embodiment, the receiving module 212 may be configured to receive a policy create request from a Session Management Function (SMF). The policy create request may be a SM policy control create request. The SM policy control create request initiates the establishment of a policy control session for a specific PDU session associated with the UE 104. The SM policy control create request may include a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), a Single Network Slice Selection Assistance Information (S- NSSAI), UE IP address, Access Type, and Session Identifier. In an embodiment, the SUPI may be a unique identifier used to represent a subscriber's permanent identity in the 5G network 106. The DNN may be a unique identifier that specifies which external data network the UE 104 should connect to. Further, the S-NSSAI may be a key identifier used in the 5G network 106 to uniquely identify and select a specific network slice. The S-NSSAI consists of two main parts a Slice / Service Type (SST) and an optional Slice Differentiator (SD). The SST defines the generalcharacteristics and purpose of the slice (e.g., eMBB, URLLC), while the SD provides further differentiation within the same SST.

[0069] In an embodiment, the extracting module 214 may be configured to extract the SUPI, the DNN, and the S-NSSAI from the received SM policy control create request. The extracting module 214 is configured to process the SM policy control create request received by the receiving module 212, and to extract key identifiers from the SM policy control create request. The extraction may enable the PCF to maintain session-specific granularity, which is critical in scenarios where the single UE 104 may engage in multiple concurrent sessions, each associated with a different DNN or slice. The extraction also facilitates correct policy binding and event trigger configuration aligned with 5G's service-based architecture.

[0070] The identifying module 216 may be configured to identify if a combination of the SUPI, the DNN and the S-NSSAI is a unique combination. The unique combination is identified by comparing the combination of the SUPI, the DNN and the S-NSSAI with an existing combinations configured at the PCF. Upon receiving the extracted identifiers from the extracting module 214, the identifying module 216 performs a lookup operation against an internal session context repository or registry maintained by the PCF. The repository may store previously instantiated policy sessions, where each session is indexed using the combination of the SUPI, the DNN, and the S-NSSAI. Further, the identifying module 216 compares the newly received combination (SUPI+DNN+S-NSSAI) to the existing entries.

[0071] In an embodiment, if no existing combination (SUPI+DNN+S-NSSAI) matching with the new combination is found at the PCF, the identifying module 216 may classify the current session as a unique combination. The determination triggers the creation of a new policy session context specifically associated with the SUPI+DNN+S-NSSAI tuple. Conversely, if a matching combination (SUPI+DNN+S-NSSAI) already exists, the PCF may either update the existing1 session, reject the duplicate request, depending on configuration policies or servicespecific rules.

[0072] The TDF interface module 218 may be configured to identify if an interface between the PCF and a Traffic Detection Function (TDF) is enabled. The interface may refer to a logical or service-based connection that facilitates communication and coordination between the PCF and the TDF for purposes such as traffic classification, steering, or enhanced policy enforcement. The interface may be a Sd interface. In an embodiment, the TDF interface module 218 performs a configuration status check, which may include evaluating an internal policy flag or operational parameter, such as “isToEnableSdlnterface”. The “isToEnableSdlnterface” flag may be predefined by network operators via an Operations, Administration, and Maintenance (0AM) system. Further, the “isToEnableSdlnterface” flag may be provisioned during initial network deployment or updated at runtime through a network function orchestration. The activation of the Sd interface allows the PCF to extend the granularity of control beyond static session attributes to the actual traffic behaviour observed in real time.

[0073] In some embodiments, if the Sd interface is determined to be enabled, the TDF interface module 218 may allow the PCF to proceed with establishing a session-level interaction with the TDF. Further, if the Sd interface is not enabled, the PCF may bypass the TDF interaction and manage the policy enforcement entirely within its own logic and coordination with the SMF. The ability to conditionally enable or disable the PCF and the TDF interface allows the system 108 to remain flexible and scalable, ensuring that the TDF resources are used only when needed such as in advanced traffic steering use cases and multi-slice environments.

[0074] The session module 220 may be configured to create a session for the unique combination (SUPI+DNN+S-NSSAI) and transmitting a TDF session request (TSR) towards the TDF for maintaining the created session for the unique combination. Upon identification the unique combination (SUPI+DNN+S-NSSAI)by the identifying module 216, the session module 220 may generate and stores a distinct session context within the PCF’s session management database. The created session context may include Quality of Service (QoS) parameters, charging and usage reporting configurations, event triggers, and session specific traffic detection policies.

[0075] Further, the session module 220 may initiate a Traffic Detection Function (TDF) session corresponding to the same unique identifier combination. To create the TDF session, the session module 220 may transmits the TSR message toward the TDF. The TSR message may serve as the control plane handshake that activates TDF-based support for the created session. The TSR message may include relevant information about the session, such as unique SUPI+DNN+S-NSSAI combination, traffic filters and detection rules, service category, application type, policy enforcement requirements, session identifiers, and reporting instructions. The TSR message may enable the TDF to establish a traffic monitoring or steering context. In an example, any data flow corresponding to the created session may be detected and classified in real time, mapped to appropriate user plane treatment, and controlled according to slice specific or application specific policies.

[0076] In an embodiment, the PCF maintains multiple concurrent sessions per UE 104, each based on a unique SUPI+DNN+S-NSSAI combination. For each session, the PCF selectively engages the TDF through the Sd interface, triggering separate and isolated traffic detection sessions. Thus, the TDF is reused dynamically, not statically, and is context-aware per session, aligned with network slices or application-specific requirements.

[0077] In an embodiment, the processing engine 208 may be configured to overwrite an existing session at the PCF using the SUPI, the DNN and the S-NSSAI when the identified combination is not a unique combination, when a new SM policy control create request is received and the combination of the SUPI, the DNN, and the S-NSSAI is determined to be not unique by the identifying module 216, the processing engine 208 may initiate a controlled session overwrite operation. In anembodiment, the processing engine 208 compares the received combination (SUPI+DNN+S-NSSAI) with existing entries in the session context database. If an exact match is found, indicating that a session with the same SUPI, DNN, and slice already exists, the processing engine may proceed to invalidate and terminate the existing session context, delete the associated policy rules, traffic steering instructions, and QoS configurations, and replace the old session with the new session instance that reflects the updated parameters received from the SMF in the SM policy control create request. The overwrite operation ensures that the PCF always maintains the most current policy state for a given session combination (SUPI+DNN+S-NSSAI).

[0078] In an embodiment, the processing engine 208 may be configured to receive a traffic session answer from the TDF in response to the TSR. The traffic session answer may be a TDF session Acknowledgement (TSA). The TSA may serve as a confirmation from the TDF that the requested session-specific traffic detection and monitoring context has been successfully established. The TSA may include a status code indicating success or failure, a session identifier for reference by the PCF and other functions, configuration parameters or response attributes such as traffic classification results, detection status, and usage reporting settings. Upon receiving the TSA, the processing engine 208 may update the PCF to reflect that TDF-level support is now active for the given policy session. The processing engine 208 may store the received TSA in the session context, enabling policy enforcement that rely on real-time traffic classification.

[0079] Further, the processing engine 208 may be configured to transmit a success response message to the SMF in response to the policy create request. The success response may be a SM policy control create response. The SM policy control create response is sent once the policy session creation has been successfully completed at the PCF. The SM policy control create response may serve as an acknowledgment indicating that the policy control context has been successfully established for the requested PDU session. By transmitting the SM policy control create response to the SMF, the PCF enables the SMF to proceedwith completing the PDU session establishment procedure including the UPF selection, resource allocation, and initiating subsequent interactions with other control plane functions.

[0080] In an embodiment, the system 108 may include a database 210 that includes data (e.g., the SUPI, the DNN, the SID, flags, TSR, etc.) 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 engine 208.

[0081] FIG. 3 illustrates an exemplary system architecture 300 for maintaining one or more sessions in the network 106, in accordance with an embodiment of the present disclosure. FIG. 3 is explained in conjunction with FIGs. 1 and 2.

[0082] In FIG. 3, a communication flow between the SMF 302, the PCF 304, and the TDF 306 is depicted. The SMF 302 may interact with the PCF 304 and vice versa via a first interface. The PCF 304 may interact with the TDF 306 and vice versa via a second interface. In some embodiments, the TDF 306 may interact with network functions of the network other than PCF, such as Access and Mobility Management Function (AMF), Network Repository Function (NRF), etc. The PCF 304 may define policies and rules for the network based on the application and desired use of the network. In an embodiment, the PCF 304 may stream the policies for the network to the SMF 302 via the first interface. The SMF 302 may be responsible for implementing policies defined by the PCF 304 to manage communication between user equipment 104 and the network. Further, The SMF 302 enforces the policies by configuring the UPFs according to the policy received from the PCF 304.

[0083] In an embodiment, the PCF 304 may stream the policies for the network to the TDF 306 via the second interface. The TDF 306 is responsible for identifying, analysing, and managing specific types of traffic flows within the network. The TDF 306 may be responsible for service differentiation, traffic management, and policy enforcement by detecting and classifying traffic based on various criteria like application type, user behaviour, service requirements, and number of sessions peruser. Further, the TDF 306 may direct user traffic across the network using plurality of sessions based on the combination of SUPI, DNN, and SID for efficient resource usage and low latency delivery of services.

[0084] In an embodiment, the TDF 306 may provide dynamic visibility and control over traffic flows associated with each unique session. Upon receiving a TDF session Request (TSR) from the PCF 304, the TDF 306 is capable of detecting application flows such as HTTP, video, enterprise VPN, loT telemetry in real time and mapping them to the appropriate session context. The mapping may allow the TDF to apply service-specific rules, such as redirection, filtering, or bandwidth shaping. Further, the TDF may support multi-slice traffic handling, where different flows are directed to distinct user plane functions (UPFs) or core slices based on their policy bindings. The TDF may acts as an intermediary control anchor between the PCF 304 and the user plane, ensuring that the multi-session are not only instantiated at the policy level but also realized in traffic flow treatment.

[0085] FIG. 4 illustrates an exemplary process flow of a method 400 for maintaining one or more sessions in the network 106, in accordance with an embodiment of the present disclosure. The method 400 may be implemented by the processing engine 208 implemented within the PCF 304, the SMF 302, and the TDF 306. FIG. 4 is explained in conjunction with FIGs. 1, 2 and 3.

[0086] At step 402, the SMF 302 sends a Session Management (SM) policy control create request to the PCF 304. The SM policy control create request includes parameters such as the SUPI, the DNN, and the SID. In an embodiment, the SM policy control create request may include a “Npcf_SMPolicyControl_Create” request. The “Npcf_SMPolicyControl_Create” request is sent from the SMF 302 to the PCF 304 to create an SM Policy associated with the PCF 304 to receive the policy for a Protocol Data Unit (PDU) session. The PDU session establishment procedure in the 5G network is essential for setting up a data session between UE 104 and the network 106. The PDU session ensures efficient and secure data transfer, catering to the diverse requirements of 5G services. The SM policy control1 create request provides means for the SMF 302 to request the creation of a corresponding SM Policy Association with PCF 304.

[0087] Upon receiving the SM policy control create request, at step the PCF 304 may check an internal configuration flag named isToEnableSdlnterface, which indicates whether the TDF’s 306 interface is to be enabled for the corresponding session. If the “isToEnableSdlnterface” flag is set to True, the PCF 304 proceeds to initiate the PDU session with the TDF 306. If the “isToEnableSdlnterface” flag is set to False, the PCF 304 may fall back to a standard session handling mechanism such as using the SUPI and the DNN to create the PDU session.

[0088] If the “isToEnableSdlnterface” flag is set to True, at step 406, the PCF 304 may maintain multiple concurrent sessions for the same SUPI+DNN, differentiated by slice identifiers, enabling fine-grained traffic steering, allowing each service flow such as video, loT, enterprise Virtual Private Network (VPN) to be treated as a separate session even if originating from the same subscriber and DNN. In an embodiment, the PCF 304 manages plurality of sessions based on the combination of SUPI, DNN, and SID extracted from the SM policy control create request.

[0089] In an embodiment, the PCF 304 may be configured to maintain multiple concurrent policy sessions for a single UE 104 by utilizing a compound session identifier derived from a combination of key attributes, such as the SUPI which uniquely identifies the user, the DNN which specifies the data network the session is connected to and the slice ID which defines the network slice. The PCF 304 may maintain a session context table, where each entry is indexed using the combination (SUPI + DNN + Slice ID). When a new SM policy control create request is received from the SMF 302, the PCF 304 may evaluate whether an existing session with the same combination (SUPI+DNN+Slice ID) exists. If the existing session with the same combination (SUPI+DNN+Slice ID) do not exist, a new session is instantiated. If a session with a matching SUPI and DNN already exists but with a different Slice ID, the PCF 304 creates and stores a separate session context,enabling parallel enforcement of policies across network slices. Further, the PCF 304 may allocate a unique session context ID such as pcfSessionlD for each combination (SUPI+DNN+Slice ID), ensuring context isolation between concurrent sessions.

[0090] Once the multiple sessions are created, at step 408, the PCF 304 sends a TDF Session Request (TSR) message to the TDF 306. The TSR message informs the TDF 306 about the traffic flow characteristics, service classification rules, and associated policy data, enabling it to apply detection and enforcement logic for the new sessions. The TSR messages are crucial for steering traffic by directing data packets to the appropriate UPFs based on specific criteria. Further, the TDF 306 allows traffic steering, shaping, or redirection at a per-session granularity, particularly useful when the UE 104 is engaging multiple services that require distinct treatment paths such as AR / VR vs. standard browsing.

[0091] Once the TSR message is sent, at step 410, the TDF 306 processes the TSR message and returns a TDF-Session Acknowledgement (TSA) message towards the PCF 304. The TSA message indicates that the traffic steering configuration is successfully applied, confirming that the session setup is complete.

[0092] Upon receiving the TSA message, at step 412, the PCF 304 sends a success response (SM policy control create response) back to the SMF 302 indicating that the policy control context and TDF interaction have been successfully established for the session. In an embodiment, the success response may include a 201 created / served success codes and the PCC rules may get send accordingly to the SMF 302 from the PCF 304 along with the 201 success code. The TSA message marks the successful establishment of the session with the enhanced multi-session support in the network.

[0093] FIG. 5 illustrates a flow diagram of a method 500 for maintaining one or more sessions in the network 106, in accordance with an embodiment of the present disclosure. The method 500 may be implemented by the processing engine208 implemented within the PCF 304, the SMF 302, and the TDF 306. FIG. 5 is explained in conjunction with FIGs. 1, 2, 3 and 4.

[0094] At step 502, the PCF 304 may receive a policy create request from the SMF 302. The policy create request may be the SM policy control create request triggered during the establishment of a PDU session by the UE 104. The SM policy control create request may include the SUPI, the DNN, the S-NSSAI, the UE IP address, access type, and session identifier.

[0095] At step 504, the PCF 304 may extract the SUPI, the DNN and the S- NSSAI from the received policy create request. The combination of the SUPI, the DNN and the S-NSSAI form the session's unique signature and are used for indexing and managing concurrent sessions.

[0096] At step 506, the PCF 304may identify if a combination of the SUPI, the DNN and the S-NSSAI is a unique combination. The PCF 304 may query the session database 210 to check for any existing session that matches the exact same SUPI+DNN+S-NSSAI tuple. If a matching session already exists for the SUPI+DNN+S-NSSAI tuple, the PCF 304 may overwrite the existing session or maintain it based on preconfigured logic or operator policies. Further, if a matching session do not exist for the SUPI+DNN+S-NSSAI tuple, the PCF 304 may classify the current session as a unique combination.

[0097] At step 508, the PCF 304 may determine if an interface between the PCF and the TDF 306 is enabled. The PCF 304 may evaluate a preconfigured flag, such “isToEnableSdlnterface”, which indicates whether the service detection (Sd) interface with the TDF 306 should be active for the current session. If the “isToEnableSdlnterface” is determined to be enabled, the PCF 304 may transmit the TSR to establish a traffic detection context for the session. Further, if the “isToEnableSdlnterface” is determined to be disabled, the PCF 304 may bypass the TDF 306 interaction and apply local policy enforcement only.

[0098] At step 510, the PCF 304 may create a session for the unique combination and transmit the TSR towards the TDF 306 for maintaining the created session for the unique combination. The PCF 304 creates a new session context corresponding to the unique SUPI+DNN+S-NSSAI combination. The new session is maintained within the PCF’s 304 internal session management database. Upon receiving the TSR, the TDF 306 establishes a corresponding session on its side to detect, classify, and apply control policies to the traffic flows associated with the session. The TSR handshake ensures that the session is jointly maintained by both the PCF 304 and the TDF 306.

[0099] Further, the PCF 304 may receive a traffic session answer from the TDF in response to the TSR. The traffic session answer may be a TSA. The TSA may confirm the successful setup and acceptance of the traffic detection session corresponding to the policy context previously created for a unique SUPI+DNN+S- NSSAI combination. Further, the PCF 304 may transmit a success response message to the SMF in response to the policy create request. Upon successful creation and activation of the session, the PCF 304 is configured to transmit a success response message to the SMF in response to the previously received SM policy control create request. The success response may serve as a confirmation that the requested policy control session has been successfully established and integrated with the TDF 306.

[0100] In an exemplary embodiment, a manufacturing plant may use ultrareliable low-latency communication (URLUC) slices for real-time robotic control, enhanced mobile broadband (eMBB) slices for high-definition video surveillance, and massive machine-type communication (mMTC) slices for sensor telemetry. All of the services may originate from the same device and use the same Data Network Name (DNN), but each is associated with a different Slice ID (S-NSSAI). The present disclosure enables the Policy Control Function (PCF) to maintain multiple concurrent policy sessions for the single UE by treating each SUPI+DNN+S- NSSAI combination as unique. Conventionally, the PCF support only one session per SUPI+DNN, resulting in session overwrites or policy mismatches. With thepresent disclosure, the PCF creates a separate policy context for each service, ensuring accurate and isolated enforcement based on the combination of the SUPI, the DNN and the S-NSSAI. Further, if the TDF interface is enabled, the PCF sends a Traffic Service Request (TSR) to the TDF for each session. The TDF detects and classifies traffic in real-time, enabling fine-grained enforcement, such as low- latency handling for robotic traffic or bandwidth control for video streams.

[0101] 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 computer system 600 may include an external storage device 610, a bus 620, a main memory 630, a read-only memory 640, a mass storage device 650, communication port(s) 660, and a processor 670. A person skilled in the art will appreciate that the computer system 600 may include more than one processor and communication ports. The processor 670 may include various modules associated with embodiments of the present disclosure. The communication port(s) 660 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) 660 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 600 connects.

[0102] The main memory 630 may be a Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory 640 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 670. The mass storage device 650 may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage device 650 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., havingUniversal 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.

[0103] The bus 620 communicatively couples the processor 670 with the other memory, storage, and communication blocks. The bus 620 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 670 to the computer system 600.

[0104] Optionally, operator and administrative interfaces, e.g. a display, keyboardjoystick, and a cursor control device, may also be coupled to the bus 620 to support direct operator interaction with the computer system. Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) 660. Components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 600 limit the scope of the present disclosure.

[0105] In an embodiment, the disclosure provides a method for maintaining one or more sessions in a network. The method include receiving a policy create request from a Session Management Function (SMF). Further, the method may include extracting a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S- NSSAI) from the received policy create request. Further, the method may include identifying if a combination of the SUPI, the DNN and the S-NSSAI is a unique combination. Based on identification, the method may include determining if an interface between the PCF and a Traffic Detection Function (TDF) is enabled. Based on the determination, the method may include creating a session for the unique combination and transmitting a TDF session request (TSR) towards the TDF for maintaining the created session for the unique combination.

[0106] In an embodiment, the disclosure provides a system for maintaining one or more sessions in a network. The system includes a Policy Control Function(PCF). The PCF is configured to receive a policy create request from a Session Management Function (SMF). Further, the PCF is configured to extract a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI) from the received policy create request. The PCF may be configured to identify if a combination of the SUPI, the DNN and the S-NSSAI is a unique combination. Further, the PCF is configured to determine if an interface between the PCF and a Traffic Detection Function (TDF) is enabled, based upon the identification. The PCF is further configured to create a session for the unique combination and transmit a TDF session request (TSR) towards the TDF for maintaining the created session for the unique combination, based upon the determination.

[0107] In an embodiment, the disclosure provides a computer program product comprising a non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to execute a method for maintaining one or more sessions in a network. The method includes receiving a policy create request from a Session Management Function (SMF). Further, the method may include extracting a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI) from the received policy create request. Further, the method may include identifying if a combination of the SUPI, the DNN and the S-NSSAI is a unique combination. Based on identification, the method may include determining if an interface between the PCF and a Traffic Detection Function (TDF) is enabled. Based on the determination, the method may include creating a session for the unique combination and transmitting a TDF session request (TSR) towards the TDF for maintaining the created session for the unique combination.

[0108] 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 orexamples, 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.

[0109] 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.

[0110] 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.TECHNICAL ADVANCEMENTS[oni] Enhanced Session Management: The present disclosure introduces a method and a system capable of maintain plurality of sessions based on a combination of a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Slice Identifier (SID) in a network, allowing more control over session management.

[0112] Improved Traffic Steering: The present disclosure allows more precise traffic steering, ensuring that data packets are directed to the appropriate User Plane Functions (UPFs) based on specific criteria and optimizing network performance, by supporting plurality of sessions for a single user.

[0113] Optimized Resource Utilization: The present disclosure manages separate sessions for different traffic flows within the same user context leads to more efficient allocation of network resources, preventing underutilization and ensuring optimal performance.

[0114] Prevention of Session Overwrite: The present disclosure addresses the issue of session overwriting in current systems, where initiating new Traffic Detection Function (TDF) Session Request (TSR) messages may overwrite existing sessions, leading to inefficiencies.

[0115] Enhanced Quality of Service (QoS): By enabling the management of plurality of concurrent sessions for the single user, the present disclosure ensures that users receive consistent and high-quality service, even when accessing plurality of services simultaneously.

Claims

We claim:

1. A method (500) for maintaining one or more sessions in a network (106), the method (500) comprising: receiving (502), by a Policy Control Function (PCF) (304), a policy create request from a Session Management Function (SMF) (302); extracting (504), by the PCF (304), a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI) from the received policy create request; identifying (506), by the PCF (304), if a combination of the SUPI, the DNN and the S-NSSAI is a unique combination; based upon the identification, determining (508), by the PCF (304), if an interface between the PCF (304) and a Traffic Detection Function (TDF) (306) is enabled; and based upon the determination, creating (510), by the PCF (304), a session for the unique combination and transmitting a TDF session request (TSR) towards the TDF (306) for maintaining the created session for the unique combination.

2. The method (500) as claimed in claim 1, further comprising overwriting an existing session at the PCF (304) using the SUPI, the DNN and the S-NSSAI when the identified combination is not a unique combination.

3. The method (500) as claimed in claim 1, wherein the unique combination is identified by comparing the combination of the SUPI, the DNN and the S-NSSAI with an existing combination at the PCF (304).

4. The method (500) as claimed in claim 1, further comprising receiving, by the PCF (304), a traffic session answer from the TDF (306) in response to the TSR.

5. The method (500) as claimed in claim 1, further comprising receiving, by the SMF (302), a success response message from the PCF (304) in response to the policy create request.

6. A system (108) for maintaining one or more sessions in a network (106), the system (108) comprising a Policy Control Function (PCF) (304) configured to: receive a policy create request from a Session Management Function (SMF) (302); extract a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI) from the received policy create request; identify if a combination of the SUPI, the DNN and the S-NSSAI is a unique combination; based upon the identification, determine if an interface between the PCF (304) and a Traffic Detection Function (TDF) (306) is enabled; and based upon the determination, create a session for the unique combination and transmit a TDF session request (TSR) towards the TDF (306) for maintaining the created session for the unique combination.

7. The system (108) as claimed in claim 6, further configured to overwrite an existing session at the PCF (304) using the SUPI, the DNN and the S-NSSAI when the identified combination is not a unique combination.

8. The system (108) as claimed in claim 6, wherein the unique combination is identified by comparing the combination of the SUPI, the DNN and the S-NSSAI with an existing combination at the PCF (304).

9. The system (108) as claimed in claim 6, further configured to receive, by the PCF (304), a traffic session answer from the TDF (306) in response to the TSR.

10. The system (108) as claimed in claim 6, further configured to receive, by the SMF (302), a success response message from the PCF (304) in response to the policy create request.

11. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (500) for maintaining one or more sessions in a network (106), the method (500) comprising: receiving (502), by a Policy Control Function (PCF) (304), a policy create request from a Session Management Function (SMF) (302); extracting (504), by the PCF (304), a Subscription Permanent Identifier (SUPI), a Data Network Name (DNN), and a Single Network Slice Selection Assistance Information (S-NSSAI) from the received policy create request; identifying (506), by the PCF (304), if a combination of the SUPI, the DNN and the S-NSSAI is a unique combination; based upon the identification, determining (508), by the PCF (304), if an interface between the PCF (304) and a Traffic Detection Function (TDF) (306) is enabled; and based upon the determination, creating (510), by the PCF (304), a session for the unique combination and transmitting a TDF session request (TSR) towards the TDF (306) for maintaining the created session for the unique combination.

Images