Method and system for managing internet protocol address of user equipment in a network

Abstract

The disclosure provides a method for managing an internet protocol (IP) address of a user equipment (UE) 502 in a network 106. A first network element such as a control plane 506 assigns a first dynamic private IP address to the UE 502 upon session creation and creates session mapping between the first dynamic private IP and a static public IP address and a port address in a second network element, such as a Public Internet Protocol (IP) Gateway (PIG) 510. The session mapping is updated in real-time based on session events. The second network element routes uplink and downlink traffic according to the maintained mapping. Upon session termination, the mapping is deleted to release IP resources. This approach enables efficient reuse of static public IPs across multiple users, reduces signaling overhead, and improves IP address utilization without compromising session continuity or service quality.

Description

METHOD AND SYSTEM FOR MANAGING INTERNET PROTOCOL ADDRESS OF USER EQUIPMENT 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 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. More particularly, the present disclosure relates to a method and a system for managing an Internet Protocol (IP) address of a user equipment (UE) in a network.DEFINITION

[0003] As used in the present disclosure, the following terms are generally intended to have the meaning as set forth below, except to the extent that the context in which they are used to indicate otherwise.

[0004] The term "Control Plane", as used herein, refers to a part of a core network that is responsible for handling signaling traffic. The control plane facilitates network operations such as routing, session management, mobility management, authentication, and coordination between user equipment (UE) and various core network entities.

[0005] The term “PIG” used hereinafter in the specification refers to a public internet protocol (IP) gateway. The PIG is a network device or component that serves as an interface between a private network (typically using private IP addresses) and the public internet (using public IP addresses).

[0006] The term “Static public internet protocol (IP) address” used hereinafter in the specification refers to a fixed IP address assigned to a device or service that is directly accessible from the public internet. It is typically provided by an Internet Service Provider (ISP) or cloud service provider and remains constant.

[0007] The term “Static private internet protocol (IP) address” used hereinafter in the specification refers to an IP address assigned to a device within a private network that remains fixed and does not change. The static private IP addresses are reserved for use within private networks and are not routable over the public internet.

[0008] The term “Dynamic private internet protocol (IP) address” used hereinafter in the specification refers to an IP address that is automatically assigned to a device within a private network by a Dynamic Host Configuration Protocol (DHCP) server. The DHCP server is a network service that automatically assigns IP addresses and other network configuration parameters to devices (DHCP clients) within a local area network (LAN) or other network segments.

[0009] The term “NAT” used hereinafter in the specification refers to Network Address Translation. It is a method used in networking to modify network address information in the IP header of packets as they traverse a traffic routing device. The primary purpose of NAT is to improve security and decrease the number of IP addresses an organization needs by allowing multiple devices on a local network to access the internet using a single public IP address.

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

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

[0012] As wireless technologies are advancing, there is a need to cope with the fifth-generation (5G) requirements and deliver an elevated level of service to the subscribers. Static public Internet Protocol (IP) addresses are allocated to end-users to ensure consistent accessibility and functionality for specific applications, such as hosting application servers or surveillance systems. This allocation ensures that the assigned static public IP address remains unchanged over time, which is crucial for maintaining continuous service availability. The provision of the static public IP addresses to end-users serves critical purposes such as supporting dedicated services like security cameras and application servers. However, the static nature of these addresses can lead to challenges in IP address management and network architecture.

[0013] Conventional techniques as explained in detail with reference to FIG. 2 and FIG. 3 presents several drawbacks. For example, when the static public IP address is blocked due to misuse or security concerns, it becomes unusable for other users. This situation results in the wastage of the static public IP addresses. Moreover, providing static public IP addresses adds complexity to network management. Network administrators must carefully handle and monitor the static public IP address assignments, ensuring that each address is correctly allocated and managed. This complexity extends to maintaining accurate records of the static public IP address usage and ensuring compliance with security policies.

[0014] Additionally, the deployment of static public IP addresses may compromise network redundancy architectures that involve replication of critical network components to ensure uninterrupted service in the event of a failure. Moreover, static public IP addresses may restrict the flexibility needed to seamlessly reroute traffic or dynamically allocate resources in redundancy scenarios.

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

[0016] In an exemplary embodiment, a method for managing an internet protocol address (IP) of a user equipment (UE) in a network is described. The method includes receiving, by a first network element, a session creation request from the UE. The method includes creating, by the first network element, a session for the UE based on the received session creation request. The method includes assigning, by the first network element, a first dynamic private IP address to the UE based on the session creation request. The method includes creating, by the first network element, a session mapping of the assigned dynamic private IP address to a static public IP address and a port address in a second network element. The method includes determining, by the first network element, at least one event associated with the created session. The method includes performing, by the first network element and the second network element, one or more operations related to the created session mapping based on the at least one determined event.

[0017] In some embodiments, the at least one determined event is detecting one of a modification in the created session or a deletion of the created session.

[0018] In some embodiments, a second dynamic private IP address is assigned to the UE based on the determined event as the modification in the created session.

[0019] In some embodiments, the one or more operations include routing, by the second network element, an uplink communication traffic and a downlink communication traffic based on the created session mapping. The one or more operations further include updating, by the first network element, the created session mapping by replacing the first dynamic private IP address with the second dynamic private IP address. The one or more operations further include routing, by the second network element, the uplink communication traffic and the downlink communication traffic based on the updated session mapping. The one or more operations further include deleting, by the first network element, the created session mapping based on determining the deletion event of the created session.

[0020] In some embodiments, routing the uplink communication traffic associated with the UE based on the created session mapping includes receiving, by a data plane gateway, the uplink communication traffic from the UE, transmitting, by the data plane gateway, the uplink communication traffic to the second network element based on the first dynamic private IP address, translating, by the second network element, the first dynamic private IP address to the static public IP address and the port address; and forwarding, by the second network element, the uplink communication traffic to an external network, based on the translated static public IP address and the port address.

[0021] In some embodiments, routing the uplink communication traffic associated with the UE based on the updated session mapping includes receiving, by the data plane gateway, the uplink communication traffic from the UE, transmitting, by the data plane gateway, the uplink communication traffic to the second network element based on the second dynamic private IP address, translating, by the second network element, the second dynamic private IP address to the static public IP address and the port address and forwarding, by the second network element, the uplinkcommunication traffic to an external network, based on the translated static public IP address and the port address.

[0022] In some embodiments, routing the downlink communication traffic associated with the UE based on the created session mapping includes receiving, by the second network element, the downlink communication traffic associated to the static public IP address and the port address from the external network, translating, by the second network element, the static public IP address to the first dynamic private IP address, and forwarding, by the second network element, the downlink communication traffic to the UE via the data plane gateway based on the first dynamic private IP address.

[0023] In some embodiments, routing the downlink communication traffic associated with the UE based on the updated session mapping includes receiving, by the second network element, the downlink communication traffic associated to the static public IP address and the port address from the external network, translating, by the second network element, the static public IP address to the second dynamic private IP address, and forwarding, by the second network element, the downlink communication traffic to the UE via the data plane gateway based on the second dynamic private IP address.

[0024] In some embodiments, the first network element is a control plane element, and the second network element is a public IP gateway or a firewall.

[0025] In some embodiments, the port address in the session mapping identifies that the static public IP address is shared across one or more UEs.

[0026] In another exemplary embodiment, a system for managing an internet protocol address (IP) of a user equipment (UE) in a network is described. The system includes a first network element. The first network element is configured to receivea session creation request from the UE. The first network element is configured to create,a session for the UE based on the received session creation request. The first network element is configured to assign, a first dynamic private IP address to the UE based on the session creation request. The first network element is configured to create, a session mapping of the assigned dynamic private IP address to a static public IP address and a port address in a second network element. The first network element is configured to determine, at least one event associated with the created session. The first network element and the second network element is configured to perform, , one or more operations related to the created session mapping based on the at least one determined event.

[0027] In an exemplary embodiment, the present disclosure discloses a User Equipment (UE). The UE includes a processor. The processor is configured to transmit a session creation request to a first network element for managing an internet protocol (IP) address of the UE in a network. The first network element is configured to assign a first dynamic private IP address to the UE based on the created session request. The first network element is further configured to create a session mapping of the assigned dynamic private IP address to a provisioned static public IP address and a port address in a second network element. The static public IP address is provisioned when the UE requests for a public address. The first network element is further configured to determine at least one event associated with the created session. The first network element is further configured to perform one or more operations related to the created session mapping at the second network element based on the at least one determined event.

[0028] In an exemplary embodiment, the present disclosure discloses 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 perform a method for managing an internet protocol address (IP) of a user equipment (UE) in a network is described. The method includes receiving, bya first network element, a session creation request from the UE. The method includes creating, by the first network element, a session for the UE based on the received session creation request. The method includes assigning, by the first network element, a first dynamic private IP address to the UE based on the session creation request. The method includes creating, by the first network element, a session mapping of the assigned dynamic private IP address to a static public IP address and a port address in a second network element. The method includes determining, by the first network element, at least one event associated with the created session. The method includes performing, by the first network element and the second network element, one or more operations related to the created session mapping based on the at least one determined event.

[0029] 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 PRESENT DISCLOSURE

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

[0031] An objective of the present disclosure is to provide a method and a system for managing Internet Protocol (IP) address of a user equipment (UE) in a network.

[0032] Another objective of the present disclosure is to provide a method and a system that facilitates the sharing of the same static public IP address across multiple UEs (customers).

[0033] Another objective of the present disclosure is to provide a method and a system that facilitates a mapping of a user’s dynamic IP address provided by thenetwork to the public IP address and port, thereby enabling session-aware and efficient network address translation (NAT), ultimately optimizing public IP resource utilization and maintaining seamless connectivity for IP-based services.

[0034] Another objective of the present disclosure is to provide a method and a system that results in optimizing the utilization of scarce IP resources in the network without compromising service quality.

[0035] Another objective of the present disclosure is to provide a method and a system that enhances redundancy in the network architecture by eliminating the need for rigid IP address assignments tied to specific user planes.

[0036] Another objective of the present disclosure is to provide a method and a system that ensures seamless failover and improved service continuity and also reduces network architecture complexity.

[0037] 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

[0038] 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 ofelectrical components, electronic components, or circuitry commonly used to implement such components.

[0039] FIG. 1 illustrates an exemplary network architecture in which or with a system configured for managing an internet protocol (IP) address of a user equipment (UE) in a network may be implemented, in accordance with embodiments of the present disclosure.

[0040] FIG. 2 illustrates an exemplary system architecture of a conventional system for managing the IP address of the UE in the network .

[0041] FIG. 3 illustrates another exemplary system architecture of a conventional system for managing the IP address of the UE in the network.

[0042] FIG. 4 illustrates an exemplary block diagram of the system for managing the IP address of the UE in the network, in accordance with an embodiment of the present disclosure.

[0043] FIG. 5 illustrates an exemplary system architecture for managing the IP address of the UE in the network, in accordance with an embodiment of the present disclosure.

[0044] FIG. 6 illustrates an exemplary process flow for managing the IP address of the UE in the network, in accordance with an embodiment of the present disclosure.

[0045] FIG. 7 illustrates an exemplary flow diagram of a method for managing the IP address of the UE in the network, in accordance with an embodiment of the present disclosure.

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

[0047] 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 - System200 - Convention system architecture300 - Convention system architecture500 - System architecture202, 302, 502- User equipment (UE)204, 304, 504 - Core Network206, 306, 506 - Control Plane208, 308, 508 - Gateway210, 312, 512 - Internet310 - Firewall400 -Block Diagram402 - Processor(s)404 - Memory406 - Interface(s)408 - Processing Engine410 - Database510 - Public internet protocol (IP) Gateway (PIG)600 - Process Flow Diagram700 - Method Flow Diagram800 - Computer system810 - External storage device820 - Bus830 - Main memory840 - Read only memory850 - Mass storage device860 - Communication port(s)870 - ProcessorDETAILED DESCRIPTION

[0048] 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 theproblems 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.

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

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

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

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

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

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

[0055] While considerable emphasis has been placed herein on the components and component parts of the preferred embodiments, it will be appreciated that many embodiments can be made and that many changes can be made in the preferred embodiments without departing from the principles of the disclosure. These and other changes in the preferred embodiment as well as other embodiments of the disclosure will be apparent to those skilled in the art from the disclosure herein, whereby it is to be distinctly understood that the foregoing descriptive matter is to be interpreted merely as illustrative of the disclosure and not as a limitation.

[0056] Traditionally, static public IP addresses have been assigned to end users to support specific use cases such as remote access, hosting services, or enhanced security monitoring. However, conventional approaches to such assignments introduce several limitations. For example, if a static public IP address is blocked due to security incidents or misuse, it becomes permanently unusable for other users, resulting in inefficient utilization of the limited public IP address space. Additionally, assigning static public IPs increases operational complexity, as network administrators are required to manually allocate and track these addresses, maintain detailed assignment records, and ensure compliance with evolving security policies.

[0057] Moreover, the use of static public IP addresses can adversely affect the design and efficiency of network redundancy architectures. Such architectures rely on dynamic routing and flexible resource allocation to ensure high availability and fault tolerance. However, the fixed nature of static public IP addresses limits the ability to seamlessly reroute traffic or dynamically reassign resources during failover events, thereby reducing the overall agility and resilience of the network infrastructure.

[0058] In order to address the challenges associated with conventional static public IP address allocation methods, the present disclosure introduces a method and a system for managing the IP address of a user equipment (UE) in a network environment. Specifically, the method enables the sharing of a single static public IP address among multiple end users. This efficient reuse of IP resources enhances IP address utilization while maintaining service quality. Unlike traditional methods that enforce fixed user plane associations, the system eliminates rigid bindings, thereby simplifying network design and improving failover capabilities. As a result, the system supports seamless service continuity and reduced architectural complexity. Moreover, the solution is adaptable across multiple access technologies, including wireline networks and wireless standards such as 4G, 5G, 6G, and Wi-Fi.

[0059] Hereinafter, exemplary embodiments of the present disclosure will be described with reference to the accompanying drawings.

[0060] FIG. 1 illustrates an exemplary network architecture 100 in which or with which a system 108 configured for managing an internet protocol (IP) address of a user equipment (UE) 104 in a network 106 may be implemented, in accordance with embodiments of the present disclosure.

[0061] 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 willY1 understand that one or more users 102-1, 102-2... 102-N may be collectively referred to as the users 102. Similarly, a person of ordinary skill in the art will understand that one or more UEs 104-1, 104-2... 104-N may be collectively referred to as the UE 104 or the UEs 104. Although only three UE 104 are depicted in FIG. 1, however, any number of the UE 104 may be included without departing from the scope of the ongoing description.

[0062] 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 are not limited to, smartphones, smart watches, smart sensors (e.g., a mechanical, a thermal, an electrical, a magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, a smart television (TV), computers, a smart security system, a smart home system, other devices for monitoring or interacting with or for the users 102 and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE 104 may include, but not limited to, intelligent, multisensing, network- connected devices, that may integrate seamlessly with each other and / or with a central server or a cloud- computing system or any other device that is network-connected.

[0063] Additionally, in some embodiments, the UE 104 may include, but not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), 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 mayinclude, but are 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, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, the UE 104 may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user 102 or an entity such as a touchpad, a touch-enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE 104 may not be restricted to the mentioned devices and various other devices may be used.

[0064] In an embodiment, the UE 104 may be deployed as a home gateway (HGW) device or a customer premise equipment (CPE) for use in a Fixed Wireless Access (FWA) environment. In an example, the UE 104 may be statically located at a fixed customer premises and connected to the core network via a wireless access network.

[0065] In FIG. 1 , the UE 104 may communicate with the system 108 through a network 106. The UE 104 may be communicatively coupled with the network 106. The communicative coupling comprises receiving, from the UE 104, a connection request by the network 106, sending an acknowledgment of the connection request to the UE 104, and transmitting a plurality of signals in response to the connection request. In an aspect, the system 108 may be implemented or embedded within a control plane element, core network nodes i.e., combination of control plane and data plane gateway, a public IP gateway or a firewall.

[0066] In an embodiment, upon receiving the connection request, the system 108 creates a user session in a core network, and the IP address is allocated to UE 104. Subsequently, the system 108 creates a mapping of a private IP address to a public IP address and a port. Further, when the system 108 determines the user session is updatedin the core network, the system 108 allocates a new IP address to the UE 104 and subsequently, the system 108 updates the mapping of the private IP address to the public IP address and port. Similarly, when the system 108 determines that the user session is deleted in the core network, the system 108 deletes the mapping of the private IP address to the public IP address and port. The detailed explanation and flow for managing the IP address of the UE 104 are described further with reference to FIG. 2 to FIG. 8.

[0067] In an embodiment, the network 106 may include at least one of a Fourth Generation (4G) network, a Fifth Generation (5G) network, a 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 may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network 106 may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

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

[0069] Although FIG. 1 shows exemplary components of the network architecture 100, in other embodiments, the network architecture 100 may include fewer components, different components, differently arranged components, or additional functional components than depicted in FIG. 1. Additionally, or alternatively, one or more components of the network architecture 100 may perform functions described as being performed by one or more other components of the network architecture 100.

[0070] FIG. 2 illustrates an exemplary system architecture 200 of a conventional system for managing the IP address of the UE 202 in the network 106.

[0071] The system architecture 200 includes a user equipment (UE) 202, a core network 204, and an internet 210. The UE 202 is connected to the core network 204 through the internet 210. The core network 204 may include a control plane 206 that manages and maintains the overall operation of the core network 204. The control plane 206 is responsible for making decisions about how data should flow through the core network 204 and for configuring devices such as routers and switches. The control plane 206 defines policies and rules for assigning a static public IP address to the UE 202. These policies dictate which user devices are eligible for static IP assignment, the criteria for allocation (e.g., based on device type and service requirements), and how conflicts or overlaps in the static public IP addresses are resolved. The core network 204 may include a gateway 208 that acts as an interface between different networks, forwarding data packets from one network to another. The gateway 208 often incorporate a Network Address Translation (NAT) functionality that modifies the static IP address information in IP packet headers while they are in transit across a router or a firewall. NAT enables devices within a private network to communicate with devices and services on the public internet using a limited number of static public IP addresses.

[0072] The conventional system is configured to statically assign a static public IP address directly to the UE 202 whenever a static public IP address (and a portaddress) is dedicated for the user. The static public IP address is allocated every time to the UE 202. Further, the allocated static public IP address is accessible to the other users through the internet 210. However, the conventional approach of statically assigning the static public IP addresses carries several disadvantages that can impact network management and operational efficiency. For example, statically assigning static public IP addresses means that each user or UE retains a dedicated IP address regardless of whether it is actively in use or not. This can lead to underutilization of valuable IP resources, especially in environments where IP addresses are limited or expensive to acquire. Additionally, static public IP assignments can complicate network scalability and flexibility. As the number of users or UEs requiring external connectivity grows, managing a large pool of static IP addresses becomes increasingly cumbersome. Further, the conventional system may hinder agility in network design and configuration updates, as it requires planning to ensure that IP addresses are assigned and maintained correctly across evolving network infrastructures. From a security perspective, static public IP addresses pose challenges as well. They provide consistent targets for potential attackers, who may exploit predictable address schemes to target specific services or devices.

[0073] FIG. 3 illustrates another exemplary system architecture 300 of a conventional system for managing the IP address of the UE 302 in the network 106.

[0074] The system architecture 300 may include a user equipment (UE) 302, a core network 304, a firewall 310, and an internet 312. The UE 302 is connected to the core network 304 through the internet 312. The core network 304 may include a control plane 306 and a gateway 308. The system is configured to allocate / assign a static private IP address every time to the UE 302 whenever the static private IP address (and a port address) is dedicated for a user. Further, when the static private IP address is allocated to the UE 302 the mapping of this static private IP address to a public IP address and the port address (in case of shared public IP address) is managed withinthe firewall 310. However, in the conventional system, the static private IP address assignments can constrain flexibility in network design and expansion, particularly in dynamic environments where devices frequently connect and disconnect or where there is a need to scale infrastructure rapidly. Further, managing a large pool of static IP addresses requires meticulous planning to prevent address conflicts and ensure efficient resource allocation, which can become increasingly complex and time-consuming as the network grows. Further, the conventional system results in increased complexity of network configuration and maintenance. Maintaining accurate mappings between the static private IP address and the public IP address within the firewall 310 requires monitoring and updates. The misconfigurations or outdated mappings can lead to connectivity issues, affecting service availability and user experience.

[0075] FIG. 4 illustrates an exemplary block diagram 400 of the system 108 for managing the IP address of the UE 104 in the network 106, in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIG. 1.

[0076] In an aspect, the system 108 may include one or more processor(s) 402, a memory 404, one or more interface(s) 406, a processing engine 408, and a database 410 for executing programming instructions for managing the IP address of the UE 104. The one or more processor(s) 402 may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) 402 may be configured to fetch and execute computer-readable instructions stored in a memory 404 of the system 108. The memory 404 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 404 may include any non-transitory storage device including, for example, volatile memory such as RandomAccess Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.

[0077] The interface(s) 406 may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) 406 may facilitate communication to / from the system 108. The interface(s) 406 may also provide a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, processing engine(s) 408 and a database 410.

[0078] In an embodiment, the processing engine(s) 408 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) 408. In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) 408 may be processor-executable instructions stored on a non- transitory machine-readable storage medium, and the hardware for the processing engine(s) 408 may include a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine- readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) 408. In such examples, the system 108 may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system 108 and the processing resource. In other examples, the processing engine(s) 408 may be implemented by electronic circuitry. In another example, the processing engine(s) 408 may be implemented by a first network element.

[0079] In an embodiment, the first network element is configured to receive a session creation request from the UE 104. The first network element is a control planeelement located within a core network. The control plane element is responsible for handling signaling, session management, and mobility procedures. In the 5G network, the control plane element may include entities such as a Session Management Function (SMF), an Access and Mobility Management Function (AMF), or any other equivalent control entity responsible for IP session establishment and policy control. In the 4G network, the control plane element may include entities such as a mobility management entity (MME), a serving gateway control plane (SGW-C), a packet gateway control plane (PGW-C) or any other equivalent control entity responsible for IP session management and policy control. The session creation request refers to a signaling message initiated by the UE 104 to establish an IP-based data connectivity session in the network. The session creation request is triggered when the UE 104 powers on, attaches to the network, or initiates a data service that requires IP connectivity. The session creation request may include relevant information such as UE identifiers (e.g., International Mobile Subscriber Identity (IMSI)), requested Quality of Service (QoS) parameters, network slice information, and an indication of whether a static IP address is required. For example, when the user 102 switches on their UE 104 (e.g., smartphone) and starts using an internet-based application such as a video streaming app, the UE 104 sends the session creation request to the first network element, such as the SMF, in the core network for initiating the IP session.

[0080] In an embodiment, the first network element is configured to create a session for the UE 104 based on the received session creation request. Upon receiving the session creation request from the UE 104, the first network element initiates a process to create an IP session for the UE. This session, referred to as a Packet Data Unit (PDU) session, represents an end-to-end logical connection between the UE 104 and a data network (DN), such as the Internet. The session creation process involves several internal procedures, including authentication and authorization of the UE, selection of an appropriate User Plane Function (UPF) to handle user data traffic, and establishment of policy and charging rules via interaction with the Policy ControlFunction (PCF). The session may be created by using key parameters such as the session ID, access type, network slice information, QoS profile, etc. Additionally, based on the UE request, the first network element may determine whether the created session should support static or dynamic IP addressing. The session creation ensures that the UE 104 is granted a valid logical path through which its IP packets can traverse in the network securely and in compliance with assigned QoS and routing rules.

[0081] In an embodiment, the first network element (the control plane element) is configured to assign a first dynamic private IP address to the UE 104 based on the session creation request. The first dynamic private IP address refers to a non-public IP address that is temporarily allocated to the UE 104 in the network. The first dynamic private IP is used for internal communication within the network and is not globally routable on the public Internet. The first dynamic private IP address may be selected from a predefined IP address pool that is managed by the network for temporary allocation. The term dynamic indicates that the IP address is assigned to the UE on demand for the duration of a session and can be reused for other UEs once the session ends. The dynamic assignment ensures that the IP address is not permanently bound to the UE 104, but instead it is associated for the duration of the session or until a specific event occurs. This dynamic assignment improves IP address utilization efficiency and reduces the need for maintaining large pools of static IP addresses. The assignment process may involve interaction with an IP Address Management (IP AM) system, such as a Dynamic Host Configuration Protocol (DHCP) server, that manages the IP pool. The first dynamic private IP address may be allocated to the UE 104 based on various factors such as the UE’s location, access type, requested services, and operator-defined policies. For example, when the UE 104 initiates a session for accessing an online video platform, the first network element assigns the first dynamic private IP address 10.15.23.89 from the available pool for that session, enabling the UE 104 to communicate with external servers via network translation mechanisms.

[0082] In an embodiment, the first network element is configured to create a session mapping of the assigned dynamic private IP address to a static public IP address and a port address in a second network element. The second network element is a public IP gateway (interchangeably referred to as PIG) or a firewall. In an aspect, the PIG is a firewall with enhanced support for updating the mapping of the dynamic private IP addresses to the static public IP addresses and the port addresses. The static public IP address refers to a fixed IP address assigned to the UE 104 that is directly accessible from the public internet.

[0083] In an aspect, the first network element is provisioned with information about available static public IP addresses and corresponding port addresses. When a session is established for the UE 104, the first network element selects a static public IP address and assigns a unique port address from the available pool associated with that static public IP address. The port address in the session mapping identifies that the static public IP address is shared across one or more UEs, allowing differentiation of traffic originating from or destined to multiple UEs using the same public IP.

[0084] Once the mapping is determined, the first network element transmits a mapping instruction to the second network element to provision and enforce the mapping in its address translation table. The instruction includes the UE’s dynamic private IP address, the selected static public IP address, the allocated port address, and any associated metadata such as session identifiers, expiration timers, or policy parameters. The second network element stores and applies the mapping as directed by the first network element. The mapping ensures that the UE 104 assigned with the first dynamic private IP address may securely communicate with external networks or services while appearing under the static public IP address.

[0085] In an embodiment, the first network element is configured to determine at least one event associated with the created session. The at least one event associated with the created session includes detecting one of a modification in the created sessionor a deletion of the created session. Once the session is created in the network 106, the first network element continuously monitors and manages the session to determine any event that may arise. In an embodiment, modification in the created session may involve events such as handover between access networks, change in the data network selection, policy re-evaluation, or reallocation of IP resources. These events may require updating the existing session parameters or reassigning IP addresses to ensure continued connectivity and compliance with updated network conditions. On the other hand, deletion of the created session involves terminating the session context altogether. This may occur when the UE 104 logs out, moves out of network coverage, or completes its session usage. By deleting the session, the first network element releases allocated resources such as IP addresses, bandwidth allocations, and security parameters, ensuring efficient resource utilization across the network.

[0086] In an aspect, when the first network element detects the at least one event as the modification in the created session, the first network function assigns a second dynamic private IP address to the UE 104 by replacing the previously assigned first dynamic private IP address. For example, if the user 102 moves from a Wi-Fi network to a cellular 5G network, the UE 104 undergoes a handover and establishes a new session with updated access type and network parameters. During this process, the first network element assigns a new dynamic private IP address, for e.g., 10.2.45.78, to the UE 104 due to changes in routing or policy.

[0087] In an embodiment, based on the at least one determined event, the first network element and the second network element are configured to perform one or more operations related to the created session mapping. The one or more operations include routing an uplink communication traffic and downlink communication traffic associated with the UE 104 by the first network element, based on the created session mapping. The uplink communication traffic refers to data sent from the UE 104 to an external server or application (e.g., uploading a file, sending a message, or making arequest). The downlink communication traffic refers to data sent from the external server or application to the UE 104 (e.g., downloading a file, receiving a message, streaming video).

[0088] In order to route the uplink communication traffic based on the created session mapping, a data plane gateway (e.g., User Plane Function (UPF)), receives the uplink communication traffic from the UE 104 and transmits the received uplink communication traffic to the second network element (e.g., PIG) based on the first dynamic private IP address of the UE 104. Further, as per the mapping previously created and stored, the second network element translates the first dynamic private IP address to the static public IP address and the associated port address and forwards this translated uplink communication traffic to an external data network (e.g., Internet, enterprise cloud, etc.). For example, when the UE 104 sends a packet, the data plane gateway forwards it to the second network element (PIG). The second network element (PIG) uses the created session mapping to translate the dynamic private IP address to the assigned static public IP address and port address and routes it to the external destination.

[0089] In order to route the downlink communication traffic based on the created session mapping, the second network element is configured to receive the downlink communication traffic, such as video, messages, etc., as addressed to the static public IP address and the port address from the external network. Further, the second network element translates the static public IP address to the first dynamic private IP address and forwards the received downlink communication traffic to the UE 104 via the data plane gateway based on the first dynamic private IP address. For example, when a packet is received from the external server, addressed to the UE’s static public IP address and the port address, the second network element (i.e., the PIG) may access the created session mapping to translate the static public IP address backto the UE’s first dynamic private IP address, and sends it back to the UE 104 via the data plane gateway.

[0090] In an embodiment, the one or more operations also involve updating the created session mapping by the first network element, by replacing the first dynamic private IP address with the second dynamic private IP address. In an example, when the first network element detects that the at least one event such as a modification in the created session has occurred, the first network element updates the session mapping in the second network element (PIG) to reflect the assigned second dynamic private IP address while maintaining external session continuity, ensuring that ongoing services like video streaming or secure connections are not disrupted.

[0091] In an embodiment, the one or more operations further involve routing the uplink communication traffic and the downlink communication traffic to the UE by the second network element based on the updated session mapping. In order to route the uplink communication traffic associated with the UE 104 based on the updated session mapping, the data plane gateway (e.g., UPF), is configured to receive the uplink communication traffic from the UE 104 and transmit the received uplink communication traffic to the second network element (e.g., PIG) based on the second dynamic private IP address of the UE 104. Further, as per the updated mapping, the second network element translates the second dynamic private IP address to the static public IP address and the associated port address and forwards this translated uplink communication traffic to an external data network (e.g., Internet, enterprise cloud, etc.). For example, when the UE 104 sends a packet, the data plane gateway forwards it to the second network element (PIG). The second network element (PIG) uses the updated session mapping to translate the second dynamic private IP address to the assigned static public IP address and port address and routes it to the external destination.

[0092] In order to route the downlink communication traffic based on the updated session mapping, the second network element is configured to receive thedownlink communication traffic, such as video, messages, etc., as addressed to the static public IP address and the port address from the external network. Further, the second network element translates the static public IP address to the second dynamic private IP address and forwards the received downlink communication traffic to the UE 104 via the data plane gateway based on the second dynamic private IP address. For example, when a packet is received from the external server, addressed to the UE’s static public IP address and the port address, the second network element (i.e., the PIG) access the updated session mapping to find and translate the static public IP address back to the UE’s second dynamic private IP address, and sends it back to the UE via the data plane gateway.

[0093] In an embodiment, the one or more operations further involve deleting the created session mapping based on detecting deletion of the created session. The first network element monitors the session lifecycle. Upon detecting session deletion (such as UE detach, session release message, timeout, or access network signaling) as the at least one event, the first network element initiates a mapping deletion command. This command is sent to the second network element (PIG), which then removes the created session mapping entry from its NAT or mapping table. The static public IP address and port address are now freed up and returned to the available pool for assignment to other users.

[0094] In an exemplary scenario, the user 102 is streaming a video on their phone, i.e., the UE 104, while initially connected to a Wi-Fi network. The UE 104 is assigned a first dynamic private IP address of 10.10.1.2, and the corresponding static public IP address and port address of 203.0.113.5:49000 are allocated for external communication. The first network element (control plane element) establishes the mapping between the first dynamic private IP address and the corresponding static public IP address and the port address in the second network element (PIG) and uses this mapping to correctly route uplink and downlink communication traffic associatedwith the UE’s ongoing video session. Subsequently, the user 102 switches from Wi-Fi to a mobile 5G network. The first network element detects this network change and assigns a second dynamic private IP address, such as 10.20.2.3, to the UE 104. The first network element then updates the existing session mapping in the second network element to reflect the second dynamic private IP address while retaining the same static public IP address and port address. This enables the video streaming session to continue seamlessly without requiring any change from the user’s perspective. Eventually, when the user 102 stops streaming and powers off the UE 104, the first network element detects the session termination and deletes the corresponding mapping, thereby releasing the static public IP address and port address.

[0095] Although FIG. 4 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. 4. 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.

[0096] FIG. 5 illustrates an exemplary system architecture 500 for managing the IP address of the UE 502 in the network 106, in accordance with an embodiment of the present disclosure.

[0097] The system architecture 500 includes the user equipment (UE) 502, the core network 504, the control plane 506, the gateway 508, the PIG 510 and the internet 512. The UE 502 is connected to the core network 504 through the Internet 512. The core network 504 includes the control plane 506 and the gateway 508.

[0098] In an embodiment, the system 500 for managing the IP address of the UE 502, reduces the network complexity. For example, when the user 102 opts for a static public IP address, the control plane 506 of the core network 504 may getprovisioned with the user identity and the static public IP address (and port address in case the static public IP address is shared across multiple users) details. The user session is established in the core network 504, and a first dynamic private IP address is allocated to the UE 502. Further, the first dynamic private IP address to static public IP address (and port address) mapping is created in the PIG 510 by the control plane 506. Thus, when the user session is updated in the core network 504, a second dynamic private IP address is allocated to UE 502. Further, the dynamic private IP address to the static public IP address (and port address), mapping may get updated in the PIG 510 by the control plane 506. Further, when the user session is deleted in the core network 510, the dynamic private IP address to static public IP address (and port address) mapping may get deleted in the PIG 510 by the control plane 506. In this way, in the core network 504, the dynamic private IP address assignment to the UE 502 is continuously performed.

[0099] In an aspect, the control plane 506 updates the session mapping in the PIG 510 every time the control plane 506 detects the at least one event occurring in the network for the UE 502. The at least one may be the modification in the created session or deletion of the created session. The PIG 510 routes the uplink communication traffic and the downlink communication traffic to the UE 502 based on the updated session mapping.

[0100] In an aspect, when the gateway 508 receives the uplink communication traffic from the UE 502, it transmits to the PIG 510 based on the second dynamic private IP address. The PIG 510 translates the second dynamic private IP address to the static public IP address and the port address by using the updated session mapping and forwards the uplink communication traffic to the internet 512. Similarly, when the PIG 510 receives the downlink communication traffic from the internet 512, it 510 translates the static public IP address to the second dynamic IP address and forwards the downlink communication traffic to the UE 502 via the gateway 508.

[0101] FIG. 6 illustrates an exemplary process flow 600 for managing the IP address of the UE 502 in the network 106, in accordance with an embodiment of the present disclosure. FIG. 6 is explained in conjunction with FIG. 5.

[0102] As shown in FIG. 6, the communication between the UE 502, the core network 504, the PIG and the Internet 512 is described for managing the IP address of the UE 502 in the network 106. The core network 504 includes the control plane 506 and the data plane gateway 508.

[0103] At step 602, the control plane 506 receives the session creation request from the UE 502 to establish the UE session. Based on the session creation request, the control plane 506 creates the UE’s session. The control plane 506 may authenticate the UE’s credentials to verify its identity and authorization to access network services. The control plane 506 further allocates necessary resources and establishes a session context according to the UE’s requirements, such as assigning the IP addresses and setting up security parameters.

[0104] At step 604, the control plane 506 assigns the first dynamic private address to the UE 502 based on the session creation request.

[0105] At step 606, the control plane 506 creates the mapping of the assigned dynamic private IP address to a static public IP address and a port address in the PIG 510. The created session mapping is stored in a translation or NAT table within the PIG 510, enabling bi-directional traffic routing between the UE 502 and the Internet 512.

[0106] At step 608, the gateway 508 receives the uplink communication traffic from the UE 502. The uplink communication traffic refers to the aggregate of data packets, control signals, and protocol messages transmitted by the UE 502 to the core network 504.

[0107] At step 610, the gateway 508 forwards the received uplink communication traffic to the PIG 510 based on the first dynamic private IP address. Upon receiving, the PIG 510 translates the first dynamic private IP address to the static public IP address and the port address by using the stored mapping. Further, at step 612, the PIG 510 forwards the received uplink communication traffic Internet 512 based on the static public IP address and the port address.

[0108] At step 614, the PIG 510 receives the downlink communication traffic associated with the static public IP address and the port address from the Internet 512.

[0109] The PIG 510 translates the static public IP address and the port address to the first dynamic private IP address by using the stored mapping. Further, at step 616, the PIG 510 forwards the downlink communication traffic to the UE 502 based on the first dynamic private IP address..

[0110] At step 618, the control plane 506 assigns the second dynamic private IP address to the UE 104 upon detecting the at least one event such as a modification in the UE’s session.

[0111] Consequently, at step 620, the control plane 506 updates the stored mapping the PIG 510 by replacing the first dynamic private IP address with the second dynamic private IP address.

[0112] At step 622, the gateway 508 receives the uplink communication traffic from the UE 502. Further, at step 624, the gateway 508 forwards the received uplink communication traffic to the PIG 510 based on the second dynamic private IP address.

[0113] Upon receiving, the PIG 510 translates the second dynamic private IP address to the static public IP address and the port address by using the updated stored mapping. Further, at step 626, the PIG 510 forwards the received uplinkcommunication traffic to the Internet 512 based on the static public IP address and the port address.

[0114] At step 628, the PIG 510 receives the downlink communication traffic associated with the static public IP address and the port address from the Internet 512.

[0115] At step 630, the PIG 510 forwards the downlink communication traffic to the UE 502 based on the second dynamic private IP address after translating the static public IP address and the port address to the second dynamic private IP address by using the updated stored mapping.

[0116] Further, at step 632, the PIG 510 deletes the stored mapping in the PIG 510 upon detecting the at least one event, such as the deletion of the session. For example, when the UE 502 initiates a session release request or moves out of coverage, leading to session termination, the session associated with the UE, prompting the PIG 510 to remove the corresponding mapping.

[0117] FIG. 7 illustrates an example of a flow diagram 700 of a method for managing the IP address of the UE 104 in the network 106, in accordance with an embodiment of the present disclosure.

[0118] At step 702, the method 700 includes receiving, by a first network element, a session creation request from the UE 104. The first network element is a control plane element. At step 704, the method 700 includes creating, by the first network element, a session for the UE based on the received session creation request. When the UE 104 sends the session creation request to the first network element, the first network element performs a series of critical tasks to ensure the successful establishment of the session. Initially, the first network element validates the UE’s authentication credentials to verify its identity and authorization to access network services. The first network element further allocates necessary resources and establishes a session context according to the UE’s requirements, such as assigning theIP addresses and setting up security parameters. Additionally, the first network element negotiates Quality of Service (QoS) parameters to guarantee optimal network performance based on the UE’s service needs. Further, the first network element confirms the session establishment, and provides the UE 104 with access to network resources.

[0119] At step 706, the method 700 includes assigning, by the first network element, a first dynamic private IP address to the UE 104 based on the session creation request. The first network element may interacts with a DHCP sever or, IP address management function (IP AM), or internal IP pool manager to allocate an available private IP address from a predefined dynamic IP address pool. The dynamic private IP address is selected based on factors such as UE location, access type, network slice, or policy rules.

[0120] At step 708, the method 700 includes creating, by the first network element, a session mapping of the assigned dynamic private IP address to a static public IP address and a port address in a second network element. The second network element is a public IP gateway (PIG) or a firewall. The port address in the session mapping identifies that the static public IP address is shared across one or more UEs.

[0121] In order to create the session mapping, the first network element selects a static public IP address and the port address from a preconfigured pool and sends a mapping instruction to the second network element (e.g., PIG). This instruction includes the UE’s assigned dynamic private IP address, the selected static public IP address and the port address, and relevant session metadata. Upon receiving this instruction, the second network element stores the mapping in its translation or NAT table, enabling bi-directional traffic routing between the UE 104 and the external network, such as the Internet.

[0122] At step 710, the method 700 includes determining, by the first network element, at least one event associated with the created session. In an embodiment, the at least one event associated with the created session includes one of a modification in the created session or a deletion of the created session. In an aspect, a second dynamic private IP address is assigned to the UE based on the detected modification in the created session.

[0123] In an embodiment, modification in the created session occurs when there is a need to modify session parameters to adapt to new service demands or network configurations. For example, if the UE 104 requires additional bandwidth or QoS parameters due to increased data traffic or application requirements, the first network element can dynamically adjust these settings within the session context. On the other hand, deletion of the created session involves terminating the session context altogether. This may occur when the UE 104 logs out, moves out of network coverage, or completes its session usage. By deleting the session, the first network element releases allocated resources such as IP addresses, bandwidth allocations, and security parameters, ensuring efficient resource utilization across the network. In an aspect, a second dynamic private IP address is assigned to the UE 104 based on the detected modification in the created session.

[0124] At step 712, the method 700 includes performing, by the first network element and the second network element, one or more operations related to the created session mapping based on the at least one determined event. The one or more operations include routing, by the second network element, an uplink communication traffic and a downlink communication traffic to the UE 104 based on the created session mapping, updating, by the first network element, the created session mapping by replacing the first dynamic private IP address with the second dynamic private IP address, routing, by the second network element, the uplink communication traffic and the downlink communication traffic to the UE 104 based on the updated sessionmapping and deleting, by the first network element, the created session mapping based on detecting deletion of the created session.

[0125] In an aspect, routing the uplink communication traffic associated with the UE 104 based on the created session mapping includes receiving, by a data plane gateway, the uplink communication traffic from the UE 104, transmitting, by the data plane gateway, the uplink communication traffic to the second network element based on the first dynamic private IP address, translating, by the second network element, the first dynamic private IP address to the static public IP address and the port address and based on the translated static public IP address and the port address forwarding, by the second network element, the uplink communication traffic to an external network.

[0126] In an aspect, routing the uplink communication traffic associated with the UE 104 based on the updated session mapping includes receiving, by the data plane gateway, the uplink communication traffic from the UE 104. transmitting, by the data plane gateway, the uplink communication traffic to the second network element based on the second dynamic private IP address, translating, by the second network element, the second dynamic private IP address to the static public IP address and the port address and based on the translated static public IP address and the port address forwarding, by the second network element, the uplink communication traffic to the external network.

[0127] In an aspect, routing the downlink communication traffic associated with the UE 104 based on the created session mapping includes receiving, by the second network element, the downlink communication traffic addressed to the static public IP address and the port address from the external network, translating, by the second network element, the static public IP address to the first dynamic private IP address; and forward the received downlink communication traffic to the UE 104 via the data plane gateway based on the first dynamic private IP address.

[0128] In an aspect, routing the downlink communication traffic associated with the UE 104 based on the updated session mapping includes receiving, by the second network element, the downlink communication traffic addressed to the static public IP address and the port address from the external network, translating, by the second network element, the static public IP address to the second dynamic private IP address and forwarding the downlink communication traffic to the UE 104 via the data plane gateway based on the second dynamic private IP address.

[0129] In an exemplary embodiment, the present disclosure discloses a user equipment (UE) 104. A processor in the UE 104 is configured to transmit a session creation request to a first network element for managing an internet protocol (IP) address of the UE 104 in a network 106. The first network element is configured to assign a first dynamic private IP address to the UE 104 based on the created session request. The first network element is configured to create a session mapping of the assigned dynamic private IP address to a provisioned static public IP address and a port address in a second network element. The static public IP address is provisioned to the UE 104 if the UE 104 requests or opts for a public IP address. The first network element is configured to determine at least one event associated with the created session and perform one or more operations related to the created session mapping at the second network element based on the at least one determined event.

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

[0131] As shown in FIG. 8, the computer system 800 may include an external storage device 810, a bus 820, a main memory 830, a read only memory 840, a mass storage device 850, a communication port 860, and a processor 870. A person skilled in the art will appreciate that the computer system 800 may include more than one processor 870 and communication ports 860. Processor 870 may include various modules associated with embodiments of the present disclosure.

[0132] In an embodiment, the communication port 860 may be any of an RS- 232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication port 860 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 800 connects.

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

[0134] In an embodiment, the mass storage device 850 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).

[0135] In an embodiment, the bus 820 communicatively couples the processor(s) 870 with the other memory, storage, and communication blocks. The bus 820 may be, e.g., a Peripheral Component Interconnect (PCI) / PCI Extended (PCI-X) bus, Small Computer System Interface (SCSI), Universal Serial Bus (USB) or the like, for connecting expansion cards, drives and other subsystems as well as other buses, such a front side bus (FSB), which connects the processor 870 to the computer system 800.

[0136] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and a cursor control device, may also be coupled to the bus 820 to support direct operator interaction with the computer system 800. Other operator and administrative interfaces may be provided through network connections connected through the communication port 860. The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 800 limit the scope of the present disclosure.

[0137] The present disclosure provides a method for static to dynamic IP address mapping for providing static IP address to broadband user. The control plane node updates the Network address translation (NAT) mapping in public IP gateway (PIG) every time there is an IP change event in the network for the UE. The user session is created in the core network, IP address is allocated to UE and private IP address to public IP address (and port) mapping is created in the PIG by the control plane element. The user session is updated in the core network, new IP address is allocated to UE and private IP address to public IP address (and port) mapping is updated in the PIG by the control plane element. The user session is deleted in the core network, private IP address to public IP address (and port) mapping is deleted in the PIG by the control plane element.

[0138] The present disclosure provides a technical advancement in the field of IP address management and network resource optimization. By introducing a session- aware mechanism for dynamically mapping a UE’s private IP address to a static public IP address (and port), the system enables multiple user sessions to share the same static public IP resource without compromising service continuity or reachability. This mapping is maintained and updated in real-time by the network’s control plane based on session events, such as handovers or IP reassignments. This approach minimizes wastage of scarce public IP resources, reduces network complexity, and supports seamless user mobility.

[0139] While the foregoing describes various embodiments of the invention, other and further embodiments of the invention may be devised without departing from the basic scope thereof. The scope of the invention is determined by the claims that follow. The invention is not limited to the described embodiments, versions or examples, which are included to enable a person having ordinary skill in the art to make and use the invention when combined with information and knowledge available to the person having ordinary skill in the art.

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

[0141] 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 to be implemented merely as illustrative of the disclosure and not as limitation.ADVANCEMENTS OF THE PRESENT DISCLOSURE

[0142] The present disclosure described herein above has several technical advantages as follows:

[0143] The present disclosure provides a method and a system for managing an internet protocol (IP) address of a user equipment (UE) in a network.

[0144] The present disclosure facilitates sharing of the same static public IP address across multiple UEs.

[0145] The present disclosure provides optimizes the utilization of scarce IP resources in the network without compromising service quality.

[0146] The present disclosure enhances redundancy in the network architecture by eliminating the need for rigid IP address assignments tied to specific user planes.

[0147] The present disclosure ensures seamless failover and improved service continuity, and also reduces network architecture complexity.

[0148] The present disclosure enables dynamic creation, update, and deletion of IP address mappings in the control plane, which allows loT devices and devices in a private network to efficiently handle mobility and IP reassignment scenarios without service interruption.

Claims

CLAIMS1. A method (700) for managing an internet protocol (IP) address of a user equipment (UE) (104) in a network, the method (600) comprising: receiving (702), by a first network element, a session creation request from the UE (104); creating (704), by the first network element, a session for the UE (104) based on the received session creation request; assigning (706), by the first network element, a first dynamic private IP address to the UE (104) based on the session creation request; creating (708), by the first network element, a session mapping of the assigned dynamic private IP address to a static public IP address and a port address in a second network element; determining (710), by the first network element, at least one event associated with the created session; and performing (712), by the first network element and the second network element, one or more operations related to the created session mapping based on the at least one determined event.

2. The method (700) as claimed in claim 1, wherein the at least one determined event is detecting one of a modification in the created session or a deletion of the created session.

3. The method (700) as claimed in claim 2, wherein a second dynamic private IP address is assigned to the UE (104) based on the determined event as the modification in the created session.

4. The method (700) as claimed in claim 1, wherein the one or more operations comprising:routing, by the second network element, an uplink communication traffic and a downlink communication traffic based on the created session mapping; updating, by the first network element, the created session mapping by replacing the first dynamic private IP address with the second dynamic private IP address; routing, by the second network element, the uplink communication traffic and the downlink communication traffic based on the updated session mapping; and deleting, by the first network element, the created session mapping based on determining the deletion event of the created session.

5. The method (700) as claimed in claim 4, wherein routing the uplink communication traffic associated with the UE (104) based on the created session mapping comprising; receiving, by a data plane gateway, the uplink communication traffic from the UE (104) ; transmitting, by the data plane gateway, the uplink communication traffic to the second network element based on the first dynamic private IP address; translating, by the second network element, the first dynamic private IP address to the static public IP address and the port address; and based on the translated static public IP address and the port address forwarding, by the second network element, the uplink communication traffic to an external network.

6. The method (700) as claimed in claim 4, wherein routing the uplink communication traffic associated with the UE (104) based on the updated session mapping comprising: receiving, by the data plane gateway, the uplink communication traffic from the UE (104) ; transmitting, by the data plane gateway, the uplink communication traffic to the second network element based on the second dynamic private IP address; translating, by the second network element, the second dynamic private IP address to the static public IP address and the port address; and based on the translated static public IP address and the port address, forwarding, by the second network element, the uplink communication traffic to the external network.

7. The method (700) as claimed in claim 4, wherein routing the downlink communication traffic associated with the UE (104) based on the created session mapping comprising: receiving, by the second network element, the downlink communication traffic addressed to the static public IP address and the port address from the external network; translating, by the second network element, the static public IP address to the first dynamic private IP address; and forwarding the received downlink communication traffic to the UE (104) via the data plane gateway based on the first dynamic private IP address.

8. The method (700) as claimed in claim 4, wherein routing the downlink communication traffic associated with the UE (104) based on the updated session mapping comprising:receiving, by the second network element, the downlink communication traffic addressed to the static public IP address and the port address from the external network; translating, by the second network element, the static public IP address to the second dynamic private IP address; and forwarding the downlink communication traffic to the UE (104) via the data plane gateway based on the second dynamic private IP address.

9. The method (700) as claimed in claim 1, wherein the first network element is a control plane element, and the second network element is a public IP gateway or a firewall.

10. A system (108) for managing an internet protocol (IP) address of a user equipment (UE) (104) in a network (106), the system (108) comprising: a first network element, wherein the first network element is configured to: receive a session creation request from the UE (104); create a session for the UE (104) based on the received session creation request; assign a first dynamic private IP address to the UE (104) based on the session creation request; create a session mapping of the assigned dynamic private IP address to a static public IP address and a port address in a second network element; determine at least one event associated with the created session; and wherein the first network element and the second network element is configured to perform one or more operations related to the created session mapping based on the at least one determined event.

11. The system (108) as claimed in claim 11, wherein the at least one determined event is detecting one of a modification in the created session or a deletion of the created session.

12. The system (108) as claimed in claim 12, wherein a second dynamic private IP address is assigned to the UE (104) based on the determined event as the modification in the created session.

13. The system (108) as claimed in claim 12, wherein the one or more operations comprising: routing, by the second network element, an uplink communication traffic and a downlink communication traffic based on the created session mapping; updating, by the first network element, the created session mapping by replacing the first dynamic private IP address with the second dynamic private IP address; routing, by the second network element, the uplink communication traffic and the downlink communication traffic based on the updated session mapping; and deleting, by the first network element, the created session mapping based on determining the deletion event of the created session.

14. The system (108) as claimed in claim 14, wherein routing the uplink communication traffic associated with the UE (104) based on the created session mapping comprising: receiving, by a data plane gateway, the uplink communication traffic from the UE (104);transmitting, by the data plane gateway, the uplink communication traffic to the second network element based on the first dynamic private IP address; translating, by the second network element, the first dynamic private IP address to the static public IP address and the port address; and based on the translated static public IP address and the port address forwarding, by the second network element, the uplink communication traffic to an external network.

15. The system (108) as claimed in claim 14, wherein routing the uplink communication traffic associated with the UE (104) based on the updated session mapping comprising: receiving, by the data plane gateway, the uplink communication traffic from the UE (104); transmitting, by the data plane gateway, the uplink communication traffic to the second network element based on the second dynamic private IP address; translating, by the second network element, the second dynamic private IP address to the static public IP address and the port address; and based on the translated static public IP address and the port address forwarding, by the second network element, the uplink communication traffic to the external network.

16. The system (108) as claimed in claim 14, wherein routing the downlink communication traffic associated with the UE (104) based on the created session mapping comprising:receiving, by the second network element, the downlink communication traffic addressed to the static public IP address and the port address from the external network; translating, by the second network element, the static public IP address to the first dynamic private IP address; and forwarding the received downlink communication traffic to the UE (104) via the data plane gateway based on the first dynamic private IP address.

17. The system (108) as claimed in claim 14, wherein routing the downlink communication traffic associated with the UE (104) based on the updated session mapping comprising: receiving, by the second network element, the downlink communication traffic addressed to the static public IP address and the port address from the external network; translating, by the second network element, the static public IP address to the second dynamic private IP address; and forwarding the downlink communication traffic to the UE (104) via the data plane gateway based on the second dynamic private IP address.

18. The system (108) as claimed in claim 11 , wherein the first network element is a control plane element, and the second network element is a public IP gateway or a firewall.

19. A user equipment (UE) (104) comprising: a processor configured to transmit a session creation request to a first network element for managing an internet protocol (IP) address of the UE (104) in a network, wherein the first network element is configured to:assign a first dynamic private IP address to the UE based on the created session request; create a session mapping of the assigned dynamic private IP address to a provisioned static public IP address and a port address in a second network element, wherein the static public IP address is provisioned when the UE (104) requests for a public IP address determine at least one event associated with the created session; and perform one or more operations related to the created session mapping at the second network element based on the at least one determined event.

20. 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 perform a method (700) for managing an internet protocol (IP) address of a user equipment (UE) (104) in a network (106), the method (700) comprising: receiving (702), by a first network element, a session creation request from the UE (104); creating (704), by the first network element, a session for the UE (104) based on the received session creation request; assigning (706), by the first network element, a first dynamic private IP address to the UE (104) based on the session creation request; creating (708), by the first network element, a session mapping of the assigned dynamic private IP address to a static public IP address and a port address in a second network element; determining (710), by the first network element, at least one event associated with the created session; andperforming (712), by the first network element and the second network element, one or more operations related to the created session mapping based on the at least one determined event.

Images