System and method for managing connections in a network

Abstract

A system (108) and a method (500) for managing at least one connection in a network (106) is described. A network function (110) communicates at least one first session create request towards a network entity (112) on receiving at least one request from a user equipment (104). At least one create session request having a tunnel endpoint identifier (TEID) is communicated from the network entity by the NF. The received TEID is validated based on a set of validation rules by the network entity (402). Based on the validation of the TEID, the network entity communicates at least one create session response to the NF. Upon receiving the create session response by the NF, the NF (308) terminates at least one stale session attached to the TEID and transmits a trigger message to the UE for detaching / re-attaching with the network entity by the NF.

Description

SYSTEM AND METHOD FOR MANAGING CONNECTIONS 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 generally to the field of telecommunications. In particular, it relates to a system and a method for managing connections 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 indicates otherwise.

[0004] The term “Network Function (NF)” used hereinafter in the specification refers to a component within the 5G network architecture that performs specific roles and services. The design of NFs in 5G allows for greater flexibility, scalability, and efficiency compared to previous generations of mobile networks. Each NF operates independently but can interconnect with other NFs to support a wide range of services. Examples of the network functions (NFs) include a User Plane Function (UPF), an Access and Mobility Management Function (AMF), a Session Management Function (SMF), a Network Exposure Function (NEF), and a Policy Control Function (PCF).

[0005] The term “Packet Data Network Gateway (PGW)” used hereinafter in the specification refers to a component that manages data traffic between the user equipment (UE) and the network. The PGW is responsible for assigning IP addresses to the UE during the connection establishment in the network. The PGW interacts with a serving gateway (SGW) and a mobility management entity (MME) to establish and maintain sessions for the user data traffic.

[0006] The term “Serving Gateway (SGW)” used hereinafter in the specification refers to a component that serves as a crucial link between a radio access network (RAN) and the network. The SGW enables routing of the user data packets between the evolved NodeB (eNB) and the PGW. The SGW involves creation, maintenance, and termination of data tunnels that facilitate the transport of user data packets between the UE, the evolved NodeB (eNB), and the Packet Data Network Gateway (PGW).

[0007] The term “Tunnel Endpoint Identifier (TEID)” used hereinafter in the specification refers to a unique value assigned to a General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnel that serves as an identifier for the endpoints (between the user equipment and the network) of the tunnel. The TEID distinguishes one tunnel from another within the same GTP connection. The TEID values are exchanged between tunnel endpoints using a control plane message.

[0008] The term “General Packet Radio Service (GPRS)” used hereinafter in the specification refers to a packet-oriented mobile data standard that enables the UE to transmit data efficiently over cellular networks, allowing for services such as internet access, multimedia messaging, and other applications.

[0009] The term “GPRS tunneling protocol (GTP)” used hereinafter in the specification refers to a protocol that is responsible for carrying data between network nodes and managing the tunnel for user data and signaling information. For example,GTP-C (Control) is used for signaling and control messages, such as session management, which establishes and modifies tunnels.

[0010] The term “tunnel” used hereinafter in the specification refers to a process of encapsulating data packets for secured transmission over the network. The tunnel provides privacy, security, or communication across an incompatible network.

[0011] The term “evolved NodeB (eNodeB)” used hereinafter in the specification refers to a component that serves as the base station responsible for managing the radio communication between the UE and the network. The eNodeB transmits and receives radio signals to and from UE, enabling voice and data transmission. The eNodeB allocates radio resources to users based on demand and quality of service (QoS) requirements.

[0012] The term “Mobility Management Entity (MME)” used hereinafter in the specification refers to a component in the long-term evolution (LTE) core network that manages user mobility and session management. The MME helps in authentication, session management, and signaling in the network. The MME initiates and terminates data paths for user sessions coordinating with the SGW and PGW.

[0013] The term “Evolved Universal Terrestrial Radio Access Network (E- UTRAN)” used hereinafter in the specification refers to radio technology that is used between the user equipments and the base stations of Third Generation Partnership Project (3 GPP) systems. The E-UTRAN supports seamless handovers as users move between different cells, ensuring continuous service without interruption.

[0014] The term “Home Subscriber Server (HSS)” used hereinafter in the specification refers to a component that acts as a central repository for subscriber- related information and manages user identities and services. The HSS handles authentication requests from network elements like MME and provides credentials to verify a user's identity and authorization for service access.

[0015] The term “Policy and Charging Rules Function (PCRF)” used hereinafter in the specification refers to a component that manages network policies and charging for services. The PCRF manages and enforces policy decisions based on subscriber profiles, service requirements, and network conditions. The PCRF ensures that the appropriate Quality of Service (QoS) is applied to user sessions.

[0016] The term “Evolved Packet Core (EPC)” used hereinafter in the specification refers to a component that is responsible for managing data transmission and network connectivity. The EPC supports seamless handovers as the users move across different network cells. The EPC establishes, modifies, and terminates data sessions for users.

[0017] The expression “Stale Session” used hereinafter in the specification refers to a session that has become outdated or inactive in the network due to one or more reasons. The one or more reasons include a lack of activity, a network failure, a device issue, etc.

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

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

[0020] In a 4G network architecture, user sessions are typically established through the interaction of various network components, including a Mobility Management Entity (MME), a serving gateway (SGW), and a packet data networkgateway (PGW). When a UE initiates a session with a specific access point name (APN), the SGW allocates a GPRS Tunneling Protocol version 2 - Control Plane (GTPv2-C) tunnel endpoint identifier (TEID) to manage the session. The TEID serves as a unique identifier for the session, enabling efficient data routing and session management. However, complications may arise during the session release process. Specifically, when a session corresponding to the specific APN is terminated by a session management function (SMF) and the PGW, the release request may fail to reach the MME from the SGW. The SGW deletes the TEID associated with that session. However, the MME retains the session, including the deleted TEID.

[0021] In such a scenario, when the UE subsequently issues another connectivity request for a different APN, such as an IP Multimedia Subsystem (IMS) APN. The MME, still holding the TEID associated with the specific APN, attempts to create a new session by sending a Create Session Request to the SGW, including the deleted TEID in the header. Since the TEID has already been deleted from the SGW, the SGW responds with a "Context Not Found" error.

[0022] As a result, the UE may repeatedly send PDN connectivity requests for the IMS APN, each meeting with the same rejection from the SGW due to the unknown TEID (deleted TEID). This cycle of failed requests leads to significant latency. It adversely affects user experience and key performance indicators (KPIs) for the network, such as connection success rates and overall service availability.

[0023] Hence, a method and system that can address the shortcomings of existing solutions are needed.SUMMARY OF THE DISCLOSURE

[0024] In an exemplary embodiment, a method for managing at least one connection in a network is described. The method includes communicating, by a network function at least one first session request towards a network entity on receivingat least one request from a user equipment. The method includes extracting, by the network entity, at least one first identifier value from the at least one first session create request. The method includes validating, by the network entity, the at least one first session create request by mapping the at least one extracted first identifier value with a configured value stored in a memory associated with the network entity. The method includes in case of unsuccessful mapping, communicating, by the network entity, at least one first session create response towards the NF and upon receiving the at least one first session create response, managing, by the NF, the at least one connection by releasing at least one stale session associated with the at least one first identifier value.

[0025] In some embodiments, for performing mapping, the method includes detecting, by the network entity, whether the at least one extracted first identifier value is matched with the configured value stored in the memory. Further, the method includes upon receiving the at least one first session create response, managing, by the NF, the at least one connection by releasing at least one stale session associated with the at least one first identifier value. The method includes marking, by the network entity, the mapping as a successful mapping and storing, by the network entity, the at least one extracted first identifier value. The method includes upon detecting that the one extracted first identifier value is not matched with the configured value, marking, by the network entity, the mapping as the unsuccessful mapping. The method further includes sending, by the network entity, the at least one extracted first identifier value as zero to the NF.

[0026] In some embodiments, the method includes on successful mapping, retrieving, by the network entity, the previously established session between the UE and the network entity based on the mapped first identifier value and attaching, by the network entity, at least one communication information to the previously established session.

[0027] In some embodiments, at least one create session response includes at least one default identifier value and at least one cause message.

[0028] In some embodiments, at least one first identifier value is associated with a previously established session between the UE and the network entity.

[0029] In some embodiments, the method includes transmitting, by the NF, at least one trigger message to the UE to perform at least one operation and the at least one operation further includes a re-attaching operation and a detaching operation.

[0030] In some embodiments, the method includes receiving, by the NF, at least one second session create request from the UE to establish a new session connection with the network entity on receiving at least one trigger message by the UE. Where, the at least one second session create request is one of an attach request and a detach request. The method further includes forwarding, by the NF, the at least one second session create request to the network entity and assigning, by the network entity, at least one second identifier value corresponding to the UE based on the new established session.

[0031] In another exemplary embodiment, a system includes a network function configured to communicate at least one first session create request towards a network entity on receiving at least one request from a user equipment. The network entity is configured to cooperate with the NF to receive the at least one first session create request and is further configured to extract at least one first identifier value from the at least one first session create request, validate the at least one first session create request by mapping the at least one extracted first identifier value with a configured value stored in a memory associated with the network entity. In case of unsuccessful mapping, the network entity is configured to communicate at least one first session create response towards the NF. The network function is further configured to manage the at least one connection by releasing at least one stale session associated with the atleast one first identifier value upon receiving the at least one first session create response.

[0032] In yet another exemplary embodiment, a user equipment (UE) communicatively coupled with a network, the coupling comprises steps of: transmitting, by the UE, at least one request to a network function (NF). At least one connection is managed in the network by a method for managing secure communication between network functions. The method includes communicating, by a network function at least one first session request towards a network entity on receiving at least one request from a user equipment. The method includes extracting, by the network entity, at least one first identifier value from the at least one first session create request. The method includes validating, by the network entity, the at least one first session create request by mapping the at least one extracted first identifier value with a configured value stored in a memory associated with the network entity. The method includes in case of unsuccessful mapping, communicating, by the network entity, at least one first session create response towards the NF and upon receiving the at least one first session create response, managing, by the NF, the at least one connection by releasing at least one stale session associated with the at least one first identifier value.

[0033] In yet another exemplary embodiment, a computer program product includes 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 for managing at least one connection in a network, the method further includes communicating, by a network function (NF), at least one first session create request towards a network entity on receiving at least one request from a user equipment. The method includes extracting, by the network entity, at least one first identifier value from the at least one first session create request. The method includes validating, by the network entity, the at least one first session create request by mappingthe at least one extracted first identifier value with a configured value stored in a memory associated with the network entity. In case of unsuccessful mapping, communicating, by the network entity, at least one first session create response towards the NF and upon receiving the at least one first session create response, managing, by the NF, the at least one connection by releasing at least one stale session associated with the at least one first identifier value.

[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.OBJECTIVES OF THE DISCLOSURE

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

[0036] An objective of the present disclosure is to provide a system and a method for managing at least one connection in a network.

[0037] Another objective of the present disclosure is to handle one or more requests in the network.

[0038] Another objective of the present disclosure is to retrieve a User Equipment (UE) trapped in a cycle of continuous rejection of one or more create session requests in the network.

[0039] Another objective of the present disclosure is to clear stale sessions within a Mobility Management Entity (MME).

[0040] Another objective of the present disclosure is to reduce the impact on network Key Performance Indicators (KPIs) by clearing stale sessions in the network.

[0041] Another objective of the present disclosure is to detect stale Packet DataNetwork (PDN) sessions in the network.

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

[0043] 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 is instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components, electronic components, or circuitry commonly used to implement such components.

[0044] FIG. 1 illustrates an exemplary network architecture of a system for managing at least one connection in a network, in accordance with an embodiment of the present disclosure.

[0045] FIG. 2 illustrates an exemplary block diagram of the system for managing the at least one connection in the network, in accordance with an embodiment of the present disclosure.

[0046] FIG. 3 illustrates an exemplary system architecture, in accordance with an embodiment of the present disclosure.

[0047] FIG. 4 illustrates an exemplary flow diagram of a method for managing the at least one connection in the network, in accordance with an embodiment of the present disclosure.

[0048] FIG. 5 illustrates an exemplary flow diagram of a method for managing the at least one connection in the network, in accordance with an embodiment of the present disclosure.

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

[0050] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102 - User(s)104 - User Equipments (UEs)106 - Network108 - System110 - Network Function (NF)112 - Network Entity200 - Block diagram202 - Processor204 - Memory206 - Interface(s)208 - Processing Engine210 - Database 300 - Exemplary system302 - Evolved Universal Terrestrial Radio Access Network (E-UTRAN)304 - eNodeB (eNB)306 - Evolved Packet Core (EPC)308- Mobility management entity (MME) 310 - Serving gateway (SGW)312 - Home subscriber server (HSS)314 - Policy and Charging Rules Function (PCRF)316 - Packet Data Network Gateway (PGW)400 - Flow Diagram 402 - SGW / PGW / PGW Control Plane (PGW-C)+Session Management Function(SMF)500 - Flow Diagram600 - Computer system610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port670 - ProcessorDETAILED DESCRIPTION

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

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

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

[0054] Also, it is noted that individual embodiments may be described as a process that is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations can be performed in parallel or concurrently. In addition, the order of the operations may be re-arranged. A process is terminated when its operations are completed but could have additional steps not included in a figure. A process may correspond to a method, a function, a procedure, a subroutine, a subprogram, etc. When a process corresponds to a function, its termination can correspond to a return of the function to the calling function or the main function.

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

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

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

[0058] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that manyembodiments 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.

[0059] 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 the 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. Further, 6G successor to 5G is expected to provide significantly high data speed with reduced latency, which may offer improved connectivity for a vast number of devices concurrently. The capabilities of 6G enable new types of applications and services, such as advanced augmented reality (AR) and virtual reality (VR), holographic communications, and more immersive digital experiences. 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 of connecting and interacting with technology.

[0060] In wireless networks, when a user equipment (UE) powers on or enters a coverage area, the UE transmits an attach request to a base station (eNodeB). A Mobility Management Entity (MME) receives the attach request via the eNodeB for network connection and verifies the UE using identifiers such as the International Mobile Equipment Identity (IMEI) and the International Mobile Subscriber Identity (IMSI). This verification involves comparing the received details (IMEI, IMSI) with the details stored in a home subscriber server (HSS). The HSS maintains user identities alongside additional information like session IDs, access point names, and network types.

[0061] Upon successful verification of the UE, the MME initiates a packet data network (PDN) session request to a serving gateway (SGW) / packet data network gateway (PGW). The SGW establishes a GPRS tunneling protocol (GTP) tunnel with a network and assigns a tunnel endpoint identifier (TEID) to manage user data flow for a PDN session corresponding to the attach request. The TEID will be common for all PDN connections of the single UE in the network, facilitating efficient routing and resource allocation.

[0062] Once the session is established, the SGW facilitates data packet transfer between the UE and the network via the PGW and enforces policies applicable to the UE during data transmission. Sessions may be released by the SGW, PGW, or session management function (SMF) for various reasons, including user-initiated releases, network conditions, service changes, errors, or administrative actions. If a session release request fails to reach the MME, the SGW deletes the TEID, but the MME retains the session.

[0063] When the UE subsequently sends another PDN connectivity request for an IP Multimedia Subsystem Access Point Name (IMS APN), the MME triggers a create session request with the previously assigned TEID, which the SGW no longer recognizes. Consequently, the SGW rejects the create session request with an errormessage indicating “Context not found”. This leads to the UE repeatedly sending the PDN connectivity requests for the IMS APN, all of which are rejected by the SGW due to the unknown TEID. Such rejections result in latency, performance degradation, and overall disruption in network operations.

[0064] Hence, there is a need to provide a method and a system that can address the shortcomings of existing solutions.

[0065] The present disclosure relates to a method and system for managing at least one connection in a network. The UE may send a PDN connectivity request to the MME via the eNodeB. Upon receipt of the PDN connectivity request, the MME generates a Create Session Request, incorporating a non-zero GPRS Tunneling Protocol version 2 - Control Plane (GTPv2-C) tunnel endpoint identifier (TEID) within the GTPv2-C header, which is associated with a prior PDN establishment session. The SGW processes the create session request and subsequently responds with a Create Session Response. The SGW is configured to set the TEID to zero in the GTPv2-C header and send it along with the Create Session Response. The Create Session Response is accompanied by an error cause indicating "Context Not Found”. This response signifies that the session context associated with the requested TEID is no longer valid. Upon receiving the Create Session Response from the SGW, the MME removes the TEID and all associated PDN connections linked to that TEID. After removing the TEID and associated PDN connections, the MME initiates a detach procedure, followed by a Re-attach request directed to the UE.

[0066] After the TEID clearing process, new attach or PDN connectivity requests received by the MME are processed successfully. The MME sends the create session request to the SGW, utilizing the GTPv2-C TEID set to zero. In response, the SGW assigns a new, fresh TEID for the UE, thus facilitating the establishment of a valid session and ensuring continuity in network connectivity. This method effectivelymitigates issues arising from stale contexts and enhances the overall efficiency of connection management within the network.

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

[0068] FIG. 1 illustrates an exemplary network architecture (100) of a system (108) for managing at least one connection in a network (106), in accordance with an embodiment of the present disclosure.

[0069] 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 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). Although only three UEs (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.

[0070] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE (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 UE (104) may include, but not limited to, intelligent, multi-sensing, 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.

[0071] Additionally, in some embodiments, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a tablet device, and so on), a wearable computer device (e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but is not limited to, any electrical, electronic, electromechanical, or 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, wherein 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 the entity such as touchpad, touch-enabled screen, 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.

[0072] Referring to FIG. 1, the UE (104) may communicate with the system (108) through the network (wireless communication network) (106) for sending or receiving various types of data. In an embodiment, the network (106) may include at least one of a fifth generation (5G) network, sixth 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) mayinclude 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.

[0073] 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 hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof.

[0074] The system (108) comprises a network function (NF) (110) and a network entity (112). In an example, the network entity (112) may include a serving gateway (SGW), a packet data network gateway (PGW), a base station (evolved NodeB (eNodeB)) and a Packet data network Gateway- Control + session management function (PGW-C+SMF). The SGW is the primary data transfer point between the UE and the data networks. The SGW routes user data packets and manages the mobility of the UE within the network. The PGW connects the LTE network to the data networks, like the Internet. The PGW also handles IP address allocation and QoS (Quality of Service) management. The eNodeB is the radio access network component that connects user equipment to the core network. The eNodeB manages radio resources and performs functions like handover between cells. In 5G architecture, the PGW-Chas evolved into the SMF, which manages session establishment, modification, and release. It also handles the control plane functions of the gateway, coordinating with other network elements for session management. In an aspect, the PGW-C+ SMF may be configured to manage data sessions, policy control, user authentication, and resource management in an Evolved Packet Core (EPC). The PGW-C+SMF may be configured to dynamically allocate and adjust network policy based on real-time network conditions. Further, the system (108) may comprise the network function (110). For example, the network function (110) comprises a mobility management entity (MME), a home subscriber server (HSS), and a policy and charging rules function (PCRF). In an aspect, the MME controls the establishment and management of the user’s evolved packet system (EPS) bearer, handles authentication, and coordinates with other core nodes to maintain the connection. The HSS provides the user’s subscription profile and authentication credentials to support packet data network (PDN) connectivity and determines the allowed services and PDN access. The PCRF sets the policy rules for the session, including QoS levels and charging parameters, ensuring appropriate data handling and billing during the user’s session.

[0075] 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. The network (106) is configured to perform a method for managing at least one connection in the network (106), as explained in detail in FIGs. 2-5.

[0076] 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).

[0077] FIG. 2 illustrates an exemplary block diagram (200) of the system (108) for managing the at least one connection in the network (106), in accordance with an embodiment of the present disclosure.

[0078] The system comprises a processor (202), a memory (204), an interface(s) (206), a processing engine (208) and a database (210).

[0079] Referring to FIG. 2, in an embodiment, the system (108) may include one or more processors (202). The processors (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 processors (202) may be configured to fetch and execute computer-readable instructions stored in the 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.

[0080] 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 (VO), 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, the processing engine (208) and the database (210).

[0081] In an embodiment, the processing engine (208) 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 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 (208) may be processor-executable 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 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 and the processing resource. In other examples, the processing engine (208) may be implemented by electronic circuitry.

[0082] In an embodiment, the network function (110) may be configured to receive at least one request from the UE (104). The at least one request may include an attach request, a modification request, a context request, and a release request. For example, the attach request may include a user identity, an attach type, and a network parameter. In an example, the user identity may be an International Mobile Equipment Identity (IMEI). The network parameter may be latency, bandwidth, a bit rate, an access point name (APN), or a frequency. The attach type may include a normal attach, a re-attach, an update attach, and an emergency attach. For example, the normal attachmay be a regular network service attach that enables the user to connect to the network (106).

[0083] In an aspect, the modification request may allow the UE to adjust connection parameters during an active session. Adjusting the connection parameters may involve changing QoS settings or bandwidth requirements to suit the current needs of the applications being utilized. The context requests are processed to retrieve or update information about the UE’s current session, such as active services or QoS profiles, facilitating effective resource management by the network. The release requests are initiated by the UE when disconnection from the network is desired. This may occur due to user action, such as turning off the device or after completing a service. Release requests are vital for freeing up network resources that were previously allocated to the UE, thus optimizing overall network performance.

[0084] In an embodiment, the processing engine (208) may be configured to process the received at least one request from the UE (104). In an embodiment, the processing engine (208) may be configured to initiate at least one session create request to establish a session between the UE and the network. In another embodiment, the processing engine (208) may be configured to trigger the network function (e.g., MME) (110) to generate the at least one session create request to establish the session between the UE and the network. The session may be a packet data network (PDN) session. The processing engine (208) may receive the at least one request from the UE (104) to establish the session in the network (106). The at least one request may be forwarded using the eNB to the system (108). The system (108) may authenticate the UE (104) by checking the user identity parameter.

[0085] In an aspect, the network function (110) (e.g., MME) may authenticate the UE (104) to ensure secure access to the network (106) by utilizing various user identity parameters, one of which is the IMEI. The IMEI serves as a unique identifier assigned to the UEs, allowing the network to distinguish between different devices andmanage access accordingly. During the authentication process, the network function (e.g., MME) (110) first receives the attach request from the UE, which includes the EMEI. The MME then cross-references this information against a database, typically located in the HSS, where user identities and associated details are securely stored. This comparison ensures that the UE attempting to connect is authorized for network access.

[0086] The MME may verify additional identity parameters, such as the International Mobile Subscriber Identity (IMSI), which identifies the subscriber's mobile account. By validating both the IMEI and IMSI, the MME enhances the security of the authentication process, ensuring that the network recognizes both the device and the subscriber.

[0087] In an embodiment, the network function (110) may be configured to communicate at least one first session create request with a tunnel endpoint identifier (TEID). The at least one first session create request may be sent from the MME to the network entity to set up the necessary tunnels for data transfer in the network (106). The at least one first session create request may be directed from the MME towards the network entity, including components such as the HSS, the SGW, the PGW, and the PGW-C+SMF. The processing engine (208) plays a critical role in triggering the network function (e.g., MME) (110) to initiate the at least one first session create request. The at least one first session create request may comprise multiple headers that encapsulate vital information for session management. These headers include the TEID, which is essential for uniquely identifying the data flow associated with each user session. The TEID is particularly important as it allows for precise routing and management of data packets within the network. The TEID may be assigned by the network entity (112) for each specific UE (104). By using the TEID, the network may efficiently route data packets to the correct destinations, ensuring seamless communication and data transfer. In addition to the TEID, the headers within the create1 session request may include a message type, which specifies the nature of the request, as well as an Access Point Name (APN) that defines the network access point for the UE. The request also contains a user identity, which may include identifiers such as the IMEI or IMSI, and an Internet Protocol (IP) address assigned to the UE.

[0088] In an aspect, the TEID may be assigned by the network entity (112) for each UE (104). In an embodiment, the TEID is assigned by the SGW during the session establishment process. The TEID is critical for managing data flows between the various components of the mobile network. Once the SGW assigns the TEID, it is subsequently shared with the network function (110) (e.g., MME). The exchange of information is crucial for maintaining a consistent and efficient communication pathway for user sessions. By retaining this information, the MME may facilitate further communication for the same user without repeated session establishment procedures. This capability enhances the efficiency of the network, as it allows the MME to quickly reference the TEID during subsequent data transfers, ensuring that packets are routed correctly to and from the appropriate UE. When the MME receives the TEID from the SGW, the MME integrates the shared information into session management protocols. The stored TEID serves as a key identifier that allows the MME to track and manage user sessions seamlessly. As user data flows through the network, the MME utilizes the stored TEID to ensure that data packets are delivered accurately and efficiently, maintaining the integrity of the user experience.

[0089] In an embodiment, the network entity (112) may be configured to cooperate with the network function (110) to receive the at least one first session create request. The network entity (112) may be configured to extract at least one first identifier value from the at least one first session create request and validate the at least one first session create request. The at least one first identifier value is associated with a previously established session between the UE (104) and the network entity (112).

[0090] Further, the network entity (112) is configured to validate the at least one first session create request by mapping the at least one extracted first identifier value with a configured value stored in a memory associated with the network entity (H2).

[0091] In an aspect, the mapping comprises the following steps to be performed by the network entity (112).

[0092] The network entity (112) is configured to detect whether the at least one extracted first identifier value (i.e., TEID) is matched with the configured value (TEID value) stored in the memory.

[0093] Upon detecting that the at least one extracted first identifier value is matched with the configured value, the network entity (112) is configured to validate the at least one extracted first identifier value.

[0094] After validating the at least one extracted first identifier value, the network entity (112) is configured to mark the mapping as a successful mapping and store the at least one extracted first identifier value. In an aspect, on successful mapping, the network entity is configured to retrieve the previously established session between the UE and the network entity and attach at least one communication information to the previously established session.

[0095] Further, upon detecting that the one extracted first identifier value is not matched with the configured value, the network entity (112) is configured to mark the mapping as the unsuccessful mapping. The network entity (112) is configured to send the at least one extracted first identifier value as zero to the network function (110) for the unsuccessful mapping.

[0096] In an aspect, the network entity (112) may be configured to validate the received TEID based on a set of validation rules. The network entity (112) may parsethe create session request received from the MME. The set of validation rules may comprise a format verification, a range check, an associated session verification, a flag verification and a routing verification. For example, the format verification involves parsing the TEID and verifying the size of the TEID. The size of the TEID may be 32- bit. Also, the network entity may check the TEID value to determine whether the TEID is a non-zero value. For example, if the TEID is a zero value, the TEID may not be a valid ID. In an exemplary aspect, the network entity may parse the TEID value in the TEID header. The TEID header may be a part of the GPRS Tunneling Protocol (GTP). The TEID may be used to identify tunnels in the user plane. The TEID header may comprise a size, a value and a flag. In an exemplary aspect, the set of validation rules may be based on the status of the flag in the TEID header. For example, if the TEID header may include a flag. If the flag is set to 1, the TEID header has a valid value. Conversely, if the flag is set to 0, the TEID header may have an invalid value. To prevent data misrouting, the TEID values are unique for each UE (104) in the network (106). In an aspect, the memory of the network entity (112) may store a list of TEID values assigned to each UE (104). The network entity (112) may be configured to perform a matching operation of the value with the list of TEID values. For example, the network entity (112) may read the TEID value and check whether the value is nonzero value. In an example, the TEID value may be a hexadecimal value. If the TEID is found in the list of TEID values stored in the memory, then it is a valid TEID. Otherwise, the network entity (112) determines the TEID value as invalid TEID. In an embodiment, the network entity (112) may communicate with the network function (110) (e.g., MME) based on the validation of the TEID.

[0097] In case of the unsuccessful mapping, the network entity (112) may be configured to communicate at least one first session create response to the network function (110). The processing engine (208) of the system (108) may receive the at least one first session create response from the network entity (112) and forward the at least one received first session create response.

[0098] The at least one first session create response comprises at least one default identifier and at least one cause message. For example, the at least one first session create response may comprise, but is not limited to, a message type, a TEID, a length, and a status indication. For example, if the TEID is valid, the create session response may indicate a status of success to the MME. Conversely, if the TEID is not found in the network entity, the status may reflect “context not found.”

[0099] Upon receiving the at least one first session create response from the network entity (112), the network function (110) is further configured to manage the at least one connection by releasing at least one stale session associated with the at least one first identifier value.

[0100] In an aspect, the network entity (112) may be configured to send a message (response) to the network function (110) (e.g., MME) to terminate the session by setting the TEID value to zero (“0000”). This action serves as an indication that the session associated with that TEID is no longer active, allowing the network entity (112) (e.g., MME) to properly manage resources and update session states accordingly. By utilizing this specific TEID value, the network (106) ensures that any ongoing data flows are effectively terminated, preventing any further communication on that session. For example, the network entity may be configured to terminate the session based on various reasons, which may include an abrupt disconnection, a UE issue, and a network failure.

[0101] In an embodiment, the processing engine (208) may be configured to terminate at least one stale session attached with the TEID based upon the received at least one create session response. In an aspect, the stale session refers to a session that is no longer active in the network (106) due to various reasons. A stale session refers to a session that is no longer active within the network (106). When the create session response indicates a status of “context not found”, and the TEID is set to zero, the processing engine identifies this as a signal to clear the stale session. Upon recognizingthe stale session, the processing engine (208) may remove the corresponding session details from memory or the associated database (210). These session details typically include a session ID, the TEID, the user identity, the Access Point Name (APN), and the Internet Protocol (IP) address. By effectively managing the lifecycle of these sessions, the processing engine ensures that inactive sessions do not occupy valuable network resources, thereby maintaining optimal performance and operational efficiency within the network.

[0102] In an embodiment, the network function (110) may be configured to clear at least one stale session attached, which has the TEID and one or more PDN sessions associated with the UE (104). The network function (110) may clear the session details having the invalid TEID value from the memory or database (210). Based on the determination of the validity of the TEID value, the network entity (112) (e.g., MME) clears the one or more PDN session information associated with the UE (104) from the database (210).

[0103] In an embodiment, the network function (110) is configured to transmit at least one trigger message to the UE (104) to perform at least one operation. The at least one operation comprises a re-attaching operation and a detaching operation. The processing engine (208) may be configured to transmit the trigger message from the network function (110) to the UE (104) for detaching / re-attaching with the network entity. In an exemplary aspect, the trigger message may be a signaling message between the UE (104) and the network function (110). The trigger message may be initiated by the network function (110) to initiate an attempt request for establishing a session with the network (106) as the TEID is already invalid. The trigger message may include a reason for detachment and the invalid TEID. The UE (104) may clear all the session data from the memory and initiate a fresh request for session establishment with the network (106).

[0104] In an aspect, the network function (110) is configured to receive at least one second session create request from the UE (104) to establish a new session connection with the network entity (112) based on the received at least one trigger message. The at least one second session create request is one of an attach request and a detach request.

[0105] Further, the network function (110) is configured to forward the at least one second session create request to the network entity. The network function (110) is configured to obtain at least one second identifier value (e.g., TEID) for the UE (104) assigned by the network entity (112) based on the new established session.

[0106] In an embodiment, the present disclosure may be configured to:• UE sends an Attach Request / PDN connectivity request to the MME, thereby establishing one PDN session end-to-end.• For any reason, the PDN session gets released at the SGW / PGW / PGW- C+SMF end but cannot be communicated to MME, resulting in a stale PDN context being created at MME.• UE sends another PDN Connectivity request to the MME.• MME sends Create Session Request towards the SGW with non-zero SGW GTPv2-C TEID in the GTPv2-C header (which was assigned during the establishment of an earlier PDN session). The SGW rejects the Create Session Request and responds with TEID as Zero in the GTPv2-C header and status indication (Cause): Context Not Found.• MME clears the SGW GTPv2-C TEID and all PDN connections corresponding to the TEID, and initiates Detach with Re-attach Required to the UE.• Further, UE sends fresh attach / PDN connectivity requests for all APNs.• All sessions will be established successfully.

[0107] In an embodiment, the database (210) includes data (e.g., user information, provisioning details, error logs, network configuration parameters, historical user data, 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).

[0108] Although FIG. 2 shows exemplary components of the system (108), in other embodiments, the system (108) may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 2. Additionally, or alternatively, one or more components of the system (108) may perform functions described as being performed by one or more other components of the system (108).

[0109] FIG. 3 illustrates an exemplary system architecture (300), in accordance with an embodiment of the present disclosure.

[0110] In an embodiment, the system architecture (300) may include the UE (104), an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) (302), an Evolved Packet Core (EPC) (306), and the network (106).

[0111] In an embodiment, the E-UTRAN (302) may comprise one or more base stations that connect the UE (104) with the network (106). The one or more base stations may include one or more eNodeB (eNB) (304-1, 304-2... 304-N). The E- UTRAN (302) may be configured to enable high-speed data transmission and low latency in the network (106). The E-UTRAN (302) may handle radio communication, resource allocation and user mobility in the network (106).

[0112] In an embodiment, the eNB (304-1, 304-N) (collectively referred to as 304) may handle radio communication with the UE, managing the network interface using radio protocols. The eNB (304) facilitates the transmission of both control and user data between the UE (104) and the network (106). The eNB (304) enableshandovers as the UEs move between a plurality of network cells, allowing the user to maintain the connection with the network (106) while moving through different coverage areas. The E-UTRAN (302) and the MME (308) may communicate using a reference point. The reference point may be an S 1 -MME reference point.

[0113] In an embodiment, the EPC (306) comprises an MME (308), an SGW (310), an HSS (312), a PCRF (314), and a PGW (316). The EPC verifies user identity before granting network access. The EPC (306) supports high-speed data transfer, efficient resource management, and seamless connectivity. The EPC (306) enables efficient voice and data traffic handling over the network.

[0114] In an embodiment, the MME (308) may be configured to manage signals and user sessions in the network (106). The MME (308) handles UE registration when the UEs connect to the network, ensuring that each UE is authenticated and authorized for access. The MME is also responsible for establishing, modifying, and terminating data channel sessions, playing a crucial role in session management. By overseeing these processes, the MME ensures that users experience seamless connectivity and can access network services without interruption.

[0115] To facilitate data sessions, the MME (308) communicates with the SGW (310), establishing a vital connection for data transfer. The SI 1 interface serves as a key reference point between the MME and the SGW, enabling the exchange of control messages related to session establishment and management. This interaction ensures that data flows efficiently between the network and the UE, while also allowing the MME to coordinate actions such as session modifications or terminations as needed.

[0116] In an embodiment, the SGW (310) may be configured to handle session establishment, session modification and session termination requests related to user data sessions. The SGW (310) serves as the data path for user traffic between the UE(104) and PGW (316). The SGW (310) routes and forwards user data packets, ensuring efficient transmission.

[0117] In an embodiment, the HSS (312) may be configured to manage the user information and authentication processes. The HSS (312) stores the user information such as a subscriber profile, a service detail, and an authentication detail that helps to manage network service for the user. The HSS (312) authenticates the users when they connect to the network (106) and validates the user identity to ensure secure access to the network.

[0118] In an embodiment, the PCRF (314) may be configured to manage and allocate resources based on user information, network conditions, and network service requirements. The PCRF (314) enforces policies related to QoS to ensure that the UE (104) receives the necessary bandwidth and latency.

[0119] In an embodiment, the PGW (316) may be configured to manage and configure UEs (104) in the network (106). The PGW (316) enables deployment, updates, and management of UE settings and policies. The PGW (316) may retrieve the appropriate configuration settings and policies from the database (210). The PGW (316) manages IP address allocation and enforces network data usage policies.

[0120] In an embodiment, the UE (104) may be configured to send one or more connection requests to the E-UTRAN (302) to establish a connection with the network (106). The one or more connection requests may include a radio resource control connection (RCC) request, an attach request, a service request, a handover request, a detach request, and a context request. For example, the connection request may comprise at least one message that may be used by the UE (104) to establish a connection with the eNB (304). The eNB (304) forwards the one or more messages to the SGW (310). The at least one message may be a GTP message. The GTP message is used for managing sessions and data flow in the network (106). The GTP messagemay include a version, a message type, the TEID, and a sequence number. For example, the GTP message may include a create session request to establish a PDN session in the network (106). The SGW (310) manages the routes the data sessions for the UE (104). The SGW (310) may send the GTP message to the PGW (316). The PGW (316) may provide the IP address to the UE (104). The MME (308) is responsible for signaling and managing the mobility of the UEs (104). The HSS is used to authenticate and authorize the user identity to enable latching into the network (106). The PCRF (314) manages the policy control and charging functions. The PCRF (314) controls the user plane and control plane based on the set policies. The PGW (316) establishes the connection with the UE (104) and the network (106).

[0121] In an embodiment, the create session request message may be sent using the SI 1 interface by the MME (308) to the SGW (310) and the S5 / S8 interface may be used by the SGW (310) to the PGW (316) as to initiate an E-UTRAN when a PDN connection is established between the SGW (310) and the PGW (316). The UE (104) may request a PDN connectivity when a PDN connection needs to be established using the SGW (310) and the PGW (316).

[0122] In an embodiment, if the TEID is not available at the SGW (310), the TEID may be set to 0. Also, the MME (308) receives a response message from the SGW (310). The TEID-C in the GTPv2 header in the received response message may state that "Context not found" corresponds to the UE (104). The TEID used in the GTPv2-C header in the response message may be set to zero.

[0123] In an embodiment, the system (108) is configured to recover the UE (104) from a request loop occurring within a telecommunications network (106). A request loop is defined as a situation wherein the UE repeatedly transmits one or more requests, such as attach requests, to the SGW. The request loop may be generated from a plurality of factors, including but not limited to improper session management, failedattach procedures, erroneous response messages, misconfigured network elements, and conditions of network congestion.

[0124] In one embodiment, improper session management by the SGW may lead to an inability to establish or maintain an active session for the UE. This inadequacy may result in the UE continuously attempting to initiate a session, generating a loop of requests. Furthermore, in scenarios where the attach procedure fails due to authentication errors or configuration discrepancies, the UE may resend attach requests in a repetitive manner.

[0125] The system (108) may be configured to detect the presence of the request loop and implement remedial actions to restore normal operational conditions for the UE. Such actions may include informing MME regarding the stale sessions, dynamic configuration adjustments, provision of feedback mechanisms to inform the UE of the prevailing conditions, or rerouting requests through alternative network pathways to mitigate the effects of congestion or errors. The objective is to facilitate the successful attachment of the UE to the network, thereby ensuring uninterrupted service delivery and enhanced user experience.

[0126] FIG. 4 illustrates an exemplary flow diagram of a method (400) for managing the at least one connection in the network (106), in accordance with an embodiment of the present disclosure.

[0127] At step 404, the UE (104) may send one or more request messages, such as the attach request to SGW / PGW / PGW-C+SMF (402) (i.e., network entity (112)) through the eNB (304) for establishing the connection / session with the network (106). The session established between the UE (104) and the network (106) may be a packet data network (PDN) session, an Internet Protocol (IP) Multimedia Subsystem (IMS) session, a Multimedia Broadcast Multicast Service (MBMS) session, or a GPRS Tunneling Protocol (GTP) session. In an aspect, the attach request message sent to theeNodeB (304) may include the IMSI, the IMEI, the data access point name (APN), and the attach type. The data APN indicates the specific data service access that the UE (104) needs in the network (106). The specific data services include internet access, a voice over IP (VoIP), video calling, and a virtual private network (VPN). The eNB (304) forwards the attach request to the MME (308). The MME (308) (e.g., network function 110) authenticates the UE (104) and sends a create session request to the SGW / PGW / PGW-C+SMF (402). The SGW / PGW / PGW-C+SMF (402) establishes a session and a data transmission path for the UE (104) to send and receive data using the network (106).

[0128] In an aspect, the SGW / PGW / PGW-C+SMF (402) may assign the TEID when the connection is established with the UE (104). The SGW / PGW / PGW- C+SMF (402) uses the TEID to manage and forward packets through the data tunnels to ensure the QoS of the network (106). For example, the TEID is used in GPRS Tunneling Protocol version 2 - Control Plane (GTPv2-C) header in a GPRS Tunneling Protocol (GTP) message. The GTP message may be a create session request, a modify session request, a delete session request, and a bearer resource command. The GTPv2- C header comprises a version, a message type, a message length, a TEID, and a sequence number. The GTPv2-C header may include the signaling information necessary for managing sessions and bearers.

[0129] In an aspect, the GTP message may be sent from the MME (308) to the SGW / PGW / PGW-C+SMF (402). The SGW / PGW / PGW-C+SMF (402) may send a response to the MME (308) that includes the TEID for the UE (104). The TEID assigned by the SGW / PGW / PGW-C+SMF (402) is unique for each UE (104) in the network (104). The TEID may be used by the MME for all sessions.

[0130] At step 406, upon one or more reasons, the session, such as a PDN session, may be released at the SGW / PGW / PGW-C+SMF (402), and the same could not be communicated to the MME (308). The miscommunication between the MME(308) and the SGW / PGW / PGW-C+SMF (402) leaves the PDN session in a stale state at the MME (308). The stale state may refer to a session that has expired or is no longer active due to one or more reasons. The one or more reasons may include a user detach request, a timeout, a user inactivity, and a UE disconnection. These reasons release the PDN session between the UE (104) and the SGW / PGW / PGW-C+SMF (402).

[0131] At step 408, the UE (104) may re-initiate at least one request to the MME (308) for the second time due to the release of the PDN session at the SGW / PGW / PGW-C+SMF (402). The at least one request may be a PDN session request. The PDN session request includes an access point name (APN), a user authentication, a session duration, a session management information, and a TEID. The TEID may be reused from the previous session establishment. The TEID may be assigned to identify the specific tunnel between the UE and the network. The TEID facilitates the management of data flows, enabling QoS parameters to be applied based on the associated tunnel. For example, the GTP tunnels are primarily in the mobile networks to tunnel user data and signaling messages.

[0132] At step 410, the MME (308) may trigger a create session request to the SGW / PGW / PGW-C+SMF (402). The create session request may be a GTPv2-C message with one or more headers, such as a TEID header. For example, the MME (308) sends GTPv2-C message with a TEID header to the SGW / PGW / PGW-C+SMF (402). The TEID header may have a non-zero value. The non- zero value may be the TEID value assigned for the previous PDN session. The TEID may be the same for the UE (104) for all sessions in the network (106).

[0133] At step 412, the SGW / PGW / PGW-C+SMF (402) sends a response to the MME (308). The response may be a create session response with the TEID header set as zero in the GTPv2-C message and with a status indication indicating context not found. For example, the TEID header set as zero indicates that the session is released at the network entity (402). There is no session related to the given TEID in the SGW / PGW / PGW-C+SMF (402). Upon receiving this response, the MME (308) may clear the TEID and all PDN sessions corresponding to the UE (104) from the memory (204) or database (210).

[0134] At step 414, the MME (308) may prompt the UE (104) to send a detach / re-attach request to the network (106). The request includes a detach type, a user identity, a detach status indication, a session ID, and an APN. For example, the MME (308) initiates a detach / a re-attach request to the UE (104) after clearing the TEID and all PDN sessions from the memory (204) or database (210). The UE (104) responds with a detach accept message to confirm successful detachment. This request enables proper session and resource management in the network (106).

[0135] At step 416, again the UE (104) may initialize a fresh attach request to the SGW / PGW / PGW-C+SMF (402) using the MME (308).

[0136] FIG. 5 illustrates an exemplary flow diagram of a method (500) for managing the at least one connection in the network (106), in accordance with an embodiment of the present disclosure.

[0137] At step 502, the method (500) includes communicating, by the network function (110), at least one first session create request towards the network entity (112) on receiving at least one request from the UE (104). initiates when a request is generated and forwarded from the user equipment, and the request is received by the network entity. Accordingly, the network function (110) (e.g., MME) initiates communication with the network entity (112) (e.g., SGW / PGW / PGW-C+SMF) for generating a first session create request.

[0138] At step 504, the method (500) includes extracting, by the network entity (112), at least one first identifier value from the first session create request. The first identifier value is associated with a previously established session between the UE and the network entity (112).

[0139] At step 506, the method (500) further includes validating, by the network entity (112), the first session create request by initiating mapping of the one extracted first identifier value with the configured value, stored in the memory associated with the network entity.

[0140] The mapping initiates to detect whether the at least one extracted first identifier value is matched with the configured value stored in the memory. When the network entity (112) detects that the one extracted first identifier value successfully matches with stored configured value in the memory. Upon successful matching, the network entity further validates the one first extracted identifier value and marks the mapping as successful mapping. Followed by marking the matched identifier value and accordingly storing the marked first identifier value. Further, on the basis of the mapped first identifier value, the network entity retrieves the previously established session between the user equipment (104) and network entity (112) and accordingly, the network entity (112) attaches the one communication information with the previously established session between the user equipment and the network entity (H2).

[0141] Further, upon detecting that the one first extracted identifier value does not matched with the configured value, the network entity (112) marks the mapping as the unsuccessful mapping. For the unsuccessful mapping, the network entity (112) sends the at least one extracted first identifier value as zero to the network function (HO).

[0142] At step 508, the method (500) includes a condition where in case, the network entity detects that the unsuccessful mapping of the one extracted first identifier value with the stored configured value, the network entity (112) communicates the unsuccessful match in the form of first session create response for the network function. In an aspect, the at least one create session response comprises at least one default identifier value and at least one cause message.

[0143] At step 510, based on receiving the at least one first session create response, the network function (110) manages the one connection by releasing one stale session linked with the extracted first identifier value. After the removal of the stale session from the extracted first identifier value, the network function transmits one trigger message to the user equipment (104) for initiating one operation that comprises of a re-attaching and a detaching operation. Accordingly, the network function (110) receives one second session create request that constitutes an attach request and a detach request, from the user equipment (104) for generating a new session with the network entity (112) on receiving one trigger message by the user equipment (104).

[0144] Based on the generated one session second request, the network function (110) forwards the request to the network entity (112) and accordingly as per the new established session, the network entity (112) assigns the one second identifier value corresponding the user equipment (104).

[0145] In an aspect, user equipment (UE) (104) is communicatively coupled with the network (106). The coupling comprises steps of transmitting, by the UE (104), at least one request to the network function (NF) (110). The method comprises managing at least one connection in the network (106). The method comprises communicating, by the network function (NF) (110), at least one first session create request towards a network entity (112) on receiving at least one request from the UE (104). The method comprises extracting, by the network entity (112), at least one first identifier value from the at least one first session create request. The at least one first identifier value is associated with a previously established session between the UE (104) and the network entity (112). The method comprises validating, by the network entity (112), the at least one first session create request by mapping the at least one extracted first identifier value with a configured value stored in the memory associated with the network entity (112). The method comprises, on successful mapping,retrieving, by the network entity (112), the previously established session between the UE (104) and the network entity (112) based on the mapped first identifier value and attaching, by the network entity (112), at least one communication information to the previously established session. The method comprises in case of unsuccessful mapping, communicating, by the network entity (112), at least one first session create response towards the NF (110). The at least one create session response comprises at least one default identifier value and at least one cause message. The method comprises upon receiving the at least one first session create response, managing, by the NF (110), the at least one connection by releasing at least one stale session associated with the at least one first identifier value. The method comprises transmitting, by the NF (110), at least one trigger message to the UE (104) to perform at least one operation. The UE (104) is configured to receive the at least one trigger message from the NF (110) to perform at least one operation. The at least one operation comprises a re-attaching operation and a detaching operation. Upon receiving the at least one trigger message, the UE (104) is configured to transmit at least one second session create request to the NF (110) to establish a new session connection with a network entity (112). The at least one second session create request is one of an attach request and a detach request. The method comprises forwarding, by the NF (110), the at least one second session create request to the network entity (112) and assigning, by the network entity (112), at least one second identifier value corresponding to the UE (104) based on the new established session.

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

[0147] 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), a communication port (660), and a processor (670). A person skilled in the art will appreciate that the computer system (600) may includemore than one processor (670) and communication ports (660). The processor (670) may include various modules associated with embodiments of the present disclosure.

[0148] In an embodiment, the communication port (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 fibre, a serial port, a parallel port, or other existing or future ports. The communication port (660) may be chosen depending on the network (106), such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (600) connects.

[0149] In an embodiment, the memory (630) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. 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).

[0150] In an embodiment, the mass storage device (650) may be any current or future mass storage solution, which may be 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 Lirewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks (e.g., SATA arrays).

[0151] In an embodiment, the bus (620) communicatively couples the processor(s) (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 otherbuses, such a front side bus (FSB), which connects the processor (670) to the computer system (600).

[0152] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and cursor control device, may also be coupled to the bus (620) to support direct operator interaction with the computer system (600). Other operator and administrative interfaces may be 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 computer system (600) limit the scope of the present disclosure.

[0153] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to perform a method for managing at least one connection in a network is described. The method includes communicating, by a network function at least one first session request towards a network entity on receiving at least one request from a user equipment. The method includes extracting, by the network entity, at least one first identifier value from the at least one first session create request. The method includes validating, by the network entity, the at least one first session create request by mapping the at least one extracted first identifier value with a configured value stored in a memory associated with the network entity. The method includes in case of unsuccessful mapping, communicating, by the network entity, at least one first session create response towards the NF and upon receiving the at least one first session create response, managing, by the NF, the at least one connection by releasing at least one stale session associated with the at least one first identifier value.

[0154] 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 thatfollow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

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

[0156] The present disclosure provides a technical advancement related to a system and method for managing packet data network (PDN) connections in a telecommunications network. This advancement addresses the challenge of the SGW repeatedly rejecting PDN connectivity requests sent by the UE for the IMS APN. Specifically, the UE initiates an Attach Request or PDN connectivity request to the MME, thereby establishing an end-to-end PDN connection. If the PDN connection is released at the SGW / PGW / PGW-C+SMF end without notification to the MME, a stale PDN context remains at the MME. When the UE subsequently sends a PDN connectivity request for a second APN, the MME forwards a Create Session Request to the SGW using the previously assigned non-zero SGW GTPv2-C TEID. If the SGW rejects this request with a TEID set to zero in the GTPv2-C header and the cause 'Context Not Found,' the MME then clears the SGW GTPv2-C TEID and allcorresponding PDN connections and initiates a detach procedure with re-attach required for the UE. Afterward, the UE sends fresh attach or PDN connectivity requests for all APNs, resulting in successful establishment of all sessions.

[0157] 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 ADVANTAGES

[0158] The present disclosure, as described above, offers several significant technical advantages that enhance the functionality and efficiency of the network, including, but not limited to:• effectively managing at least one connection, ensuring that user interactions with the network are processed efficiently and without delay. This capability supports a wide range of network operations and enhances overall responsiveness;• identifying and retrieving User Equipment (UE) that may be stuck in a cycle of repeated rejections of create session requests. This feature allows for timely intervention, enabling users to regain access to network services and preventing frustration associated with connectivity issues;• identifying and clearing stale sessions within the MME. This process helps maintain an up-to-date session database, ensuring that only active sessions consume resources;• managing sessions and requests proactively to minimize negative impacts on critical KPIs, such as latency, throughput, and user satisfaction. Byaddressing issues promptly, the network may maintain high performance levels;• removing stale sessions continuously contributing to the overall performance of the network by freeing up resources that would otherwise be occupied by inactive connections; and• providing a seamless user experience, uninterrupted service and reliable connectivity in the network. This focus on user-centric design enhances overall satisfaction and promotes greater utilization of network resources.

Claims

We Claim:

1. A method (500) for managing at least one connection in a network (106), the method (500) comprising: communicating (502), by a network function (NF) (110), at least one first session create request towards a network entity (112) on receiving at least one request from a user equipment (UE) (104); extracting (504), by the network entity (112), at least one first identifier value from the at least one first session create request; validating (506), by the network entity (112), the at least one first session create request by mapping the at least one extracted first identifier value with a configured value stored in a memory associated with the network entity (112); in case of unsuccessful mapping, communicating (508), by the network entity (112), at least one first session create response towards the NF (110); and upon receiving the at least one first session create response, managing (510), by the NF (110), the at least one connection by releasing at least one stale session associated with the at least one first identifier value.

2. The method (500) as claimed in claim 1, wherein the mapping comprising: detecting, by the network entity (112), whether the at least one extracted first identifier value is matched with the configured value stored in the memory; upon detecting that the one extracted first identifier value is matched with the configured value, validating, by the network entity (112), the at least one extracted first identifier value; marking, by the network entity (112), the mapping as a successful mapping; and storing, by the network entity (112), the at least one extracted first identifier value, wherein upon detecting that the one extracted first identifiervalue is not matched with the configured value, marking, by the network entity (112), the mapping as the unsuccessful mapping; and sending, by the network entity (112), the at least one extracted first identifier value as zero to the NF (110).

3. The method (500) as claimed in claim 1, further comprising: on successful mapping, retrieving, by the network entity (112), the previously established session between the UE (104) and the network entity (112) based on the mapped first identifier value; and attaching, by the network entity (112), at least one communication information to the previously established session.

4. The method (500) as claimed in claim 1, wherein the at least one create session response comprises at least one default identifier value and at least one cause message.

5. The method (500) as claimed in claim 1, wherein the at least one first identifier value is associated with a previously established session between the UE (104) and the network entity (112).

6. The method (500) as claimed in claim 1, further comprising: transmitting, by the NF (110), at least one trigger message to the UE (104) to perform at least one operation, wherein the at least one operation comprises a re-attaching operation and a detaching operation.

7. The method (500) as claimed in claim 4, further comprising: receiving, by the NF (110), at least one second session create request from the UE (104) to establish a new session connection with the network entity(112) on the receiving the at least one trigger message by the UE (104), wherein the at least one second session create request is one of an attach request and a detach request; forwarding, by the NF (110), the at least one second session create request to the network entity (112); and assigning, by the network entity (112), at least one second identifier value corresponding to the UE (104) based on the new established session.

8. A system (108) for managing at least one connection in a network (106), the system (108) comprising: a network function (NF) (110) configured to communicate at least one first session create request towards a network entity (112) on receiving at least one request from a user equipment (UE) (104); and the network entity (112) is configured to cooperate with the NF (110) to receive the at least one first session create request and is further configured to: extract at least one first identifier value from the at least one first session create request; validate the at least one first session create request by mapping the at least one extracted first identifier value with a configured value stored in a memory associated with the network entity (112); in case of unsuccessful mapping, communicate at least one first session create response towards the NF (110); and the NF (110) is further configured to manage the at least one connection by releasing at least one stale session associated with the at least one first identifier value upon receiving the at least one first session create response.

9. The system (108) as claimed in claim 8, wherein the mapping comprising:the network entity (112) configured to detect whether the at least one extracted first identifier value is matched with the configured value stored in the memory; and upon detecting that the at least one extracted first identifier value is matched with the configured value, the network entity (112) configured to: validate the at least one extracted first identifier value; mark the mapping as a successful mapping; and store the at least one extracted first identifier value, wherein upon detecting that the one extracted first identifier value is not matched with the configured value, the network entity (112) is configured to: mark the mapping as the unsuccessful mapping; and send the at least one extracted first identifier value as zero to the NF (110).

10. The system (108) as claimed in claim 8, wherein, on successful mapping, the network entity (112) is configured to: retrieve the previously established session between the UE (104) and the network entity (112); and attach at least one communication information to the previously established session.

11. The system (108) as claimed in claim 8, wherein the at least one create session response comprises at least one default identifier and at least one cause message.

12. The system (108) as claimed in claim 8, wherein the at least one first identifier value is associated with a previously established session between the UE and the network entity (112).

13. The system (108) as claimed in claim 8, wherein the NF (110) is configured to transmit at least one trigger message to the UE (104) to perform at least one operation, wherein at least one operation comprises a re-attaching operation and a detaching operation.

14. The system (108) as claimed in claim 13, wherein the NF (110) is configured to: receive at least one second session create request from the UE (104) to establish a new session connection with the network entity (112) on receiving the at least one trigger message by the UE (104), wherein the at least one second session create request is one of an attach request and a detach request; forward the at least one second session create request to the network entity (112); and obtain at least one second identifier value for the UE (104) assigned by the network entity (112) based on the new established session.

15. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of: transmitting, by the UE (104), at least one request to a network function (NF) (110), wherein at least one connection is managed in the network (106) by a method (500) as claimed in claim 1.

16. The UE (104) as claimed in claim 15, comprising steps of:receiving, by the UE (104), at least one trigger message from the NF (110) to perform at least one operation, wherein the at least one operation comprises a re-attaching operation and a detaching operation; and upon receiving the at least one trigger message, transmitting, by the UE (104), at least one second session create request to the NF (110) to establish a new session connection with a network entity (112), wherein the at least one second session create request is one of an attach request and a detach request.

17. 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 managing at least one connection in a network (106), the method (500) comprising: communicating (502), by a network function (NF) (110), at least one first session create request towards a network entity (112) on receiving at least one request from a user equipment (UE) (104); extracting (504), by the network entity (112), at least one first identifier value from the at least one first session create request; validating (506), by the network entity (112), the at least one first session create request by mapping the at least one extracted first identifier value with a configured value stored in a memory associated with the network entity (112); in case of unsuccessful mapping, communicating (508), by the network entity (112), at least one first session create response towards the NF (110); and upon receiving the at least one first session create response, managing (510), by the NF (110), the at least one connection by releasing at least one stale session associated with the at least one first identifier value.

Images