System and method for managing one or more home gateways in a network

Abstract

The present disclosure relates to a system (108) and a method (400) for Internet Protocol (IP) address allocation for network equipments (212) in a network (106). The method (400) comprises receiving, by a User Plane Function (UPF) (218), an IP address discovery message. The method (400) comprises transmitting, by the UPF (218), an IP address offer message. The method (400) comprises receiving, by the UPF (218), an IP address request message for allocation of the offered IP address. The method (400) comprises transmitting, by the UPF (218), an IP address acknowledgment message. The method (400) comprises renewing, by the UPF (218), the allocated IP address upon receiving a lease renewal message prior to expiration of a lease timer. The method (400) comprises reassigning, by the UPF (218), a previously allocated IP address upon receiving the IP address discovery message associated with the at least one network equipment.

Description

SYSTEM AND METHOD FOR MANAGING ONE OR MORE HOME GATEWAYS IN A NETWORKRESERVATION OF RIGHTS

[0001] A portion of the disclosure of this patent document contains material, which is subject to intellectual property rights such as, but are not limited to, copyright, design, trademark, Integrated Circuit (IC) layout design, and / or trade dress protection, belonging to Jio Platforms Limited (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.FIELD OF DISCLOSURE

[0002] The embodiments of the present disclosure generally relate to communication networks. In particular, the present disclosure relates to a system and a method for Internet Protocol (IP) address allocation for network equipments in a network.DEFINITIONS

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

[0004] The term ‘Customer Premise Equipment (CPE)’ used hereinafter in the specification refers to a network equipment deployed indoors or outdoors, depending on the network design and signal requirements. The CPE is wirelessly connected to base station or gNodeB.

[0005] The term ‘network element’ used hereinafter in the specification refers to a Home Gateway (HGW) which is a type of Residential Gateway (RG), which is a device configured to provide communication services such as voice, data, broadcast video, and video on demand to other devices within a home. The HGW acts as an interface between the Wide Area Network (WAN) and the Local Area Network (LAN) IP environment for a consumer broadband customer, capable of routing or bridging traffic depending on its configuration. In the context of the 5G Core Network, the HGW device may function as a User Equipment (UE) or communicate via the CPE, holding a secure element and exchanging Non-Access Stratum (NAS) signalling with the core network (e.g., 5G or 4G) to establish connectivity.

[0006] The term “Dynamic Host Configuration Protocol (DHCP)” used hereinafter in the specification refers to a network management protocol used for dynamically assigning IP addresses and other configuration parameters to devices on a network.

[0007] The term “Dynamic Host Configuration Protocol Version 4 (DHCPv4)” used hereinafter in the specification refers to the standard for assigning IPv4 addresses to devices.

[0008] The term “Dynamic Host Configuration Protocol Version 6 (DHCPv6)” used hereinafter in the specification refers to the standard for assigning IPv6 addresses to devices.

[0009] The term “Internet Protocol version 4 (IPv4)” used hereinafter in the specification refers to a connectionless network protocol that uses a 32-bit address format to identify devices on a network.

[0010] The term “Internet Protocol version 6 (IPv6)” used hereinafter in the specification refers to a network protocol that uses a 128 -bit address format to support a larger number of devices with unique IP addresses.

[0011] The term “Negative Acknowledgment (NACK)” used hereinafter in the specification refers to a message from a receiver indicating that data or a request was not accepted or was invalid.

[0012] The term “Identity Association for Non-temporary Address (IA_NA)” used hereinafter in the specification refers to a DHCPv6 parameter that identifies a group of non-temporary IPv6 addresses assigned to an interface.

[0013] The term “Identity Association for Prefix Delegation (IA PD)” used hereinafter in the specification refers to a DHCPv6 parameter that identifies a group of IPv6 prefixes delegated to a device.

[0014] The term “Router Solicitation (RS)” used hereinafter in the specification refers to a message sent by a host to a router to request a router advertisement.

[0015] The term “Router Advertisement (RA)” used hereinafter in the specification refers to a message sent by a router to provide hosts with network configuration information, such as available prefixes and router addresses.

[0016] The expression ‘session’ used hereinafter in the specification refers to a connection established between the HGW and the network. This session allows data to flow between the HGW and the network.

[0017] The expression ‘ethernet session’ used hereinafter in the specification refers to a type of data connection established over an ethernet cable for communication between the HGW and the network.

[0018] The expression ‘International Mobile Subscriber Identity (IMSI)’ used hereinafter in the specification refers to a unique identifier associated with the network element on a network.

[0019] The expression ‘User Plane Function (UPF)’ used hereinafter in the specification refers to a core network function responsible for processing user data traffic. The UPF includes functionalities such as packet forwarding, routing, aDynamic Host Configuration Protocol (DHCP) server, and policy enforcement. It may also involve Quality of Service (QoS) management and security features.

[0020] The expression ‘Session Management Function (SMF)’ used hereinafter in the specification refers to a network function responsible for managing user sessions, including session establishment, modification, and termination. The SMF handles mobility management and resource allocation for user sessions.

[0021] The expression ‘Policy Control Function (PCF)’ used hereinafter in the specification refers to a network function responsible for defining and enforcing network policies. The PCF determines authorized services, resource allocations, and traffic prioritization.

[0022] The expression ‘gNodeB’ used hereinafter in the specification refers to a 5G network base station that provides connectivity between the CPE and the core network. The gNodeB handles radio resource management and radio interface protocols.

[0023] The expression ‘Broadband Network Gateway (BNG)’ used hereinafter in the specification refers to a network device that connects broadband customers to the internet. It handles tasks like user authentication, assigning IP addresses, managing network traffic, and ensuring service quality.

[0024] The term “Network Time Protocol (NTP)” used hereinafter in the specification refers to a protocol used for synchronizing computer clock times.

[0025] The term “Domain Name System (DNS)” used hereinafter in the specification refers to a system that translates domain names into IP addresses.

[0026] These definitions are in addition to those expressed in the art.BACKGROUND OF DISCLOSURE

[0027] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section mayinclude 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.

[0028] In Fifth Generation (5G) communication networks, the provisioning of IP addresses to a Customer Premises Equipment (CPE) that plays a vital role in ensuring seamless connectivity and access to services. Traditionally, IP address assignment for devices behind a CPE is managed by invoking a centralized DHCP (Dynamic Host Configuration Protocol) server, typically located outside the user plane path. While functional, this approach introduces multiple inefficiencies.

[0029] Firstly, every time a Home Gateway (HGW) connects behind the CPE, the network must rely on signalling between the User Plane Function (UPF) and the DHCP server, often involving multiple hops and increased latency. This centralized dependency leads to additional signalling overhead, increased setup delay, and potential single points of failure, especially when the DHCP server becomes a bottleneck. Moreover, in multi-Home Gateway (HGW) deployments where multiple gateways are connected behind the same CPE, conventional DHCP solutions do not support session-specific differentiation or address reuse optimally.

[0030] Additionally, centralized DHCP processing lacks contextual awareness of the user plane traffic, making it inefficient in identifying session reuse opportunities or maintaining per-device IP continuity during network transitions or gateway reboots. These limitations result in unnecessary session tear-down and recreation cycles, adversely affecting user experience and wasting network resources.

[0031] Therefore, there exists a need for a more efficient and distributed IP address allocation mechanism that reduces reliance on centralized DHCP servers, enables session-aware IP assignment directly from the UPF, and supports continuity and reuse of IP addresses without incurring additional signalling or delays.

[0032] Therefore, there is a need for a system and method that overcomes the limitations of the existing state of the art.OBJECTS OF THE PRESENT DISCLOSURE

[0033] Some of the objects of the present disclosure, which at least one embodiment herein satisfies are as listed herein below.

[0034] An objective of the present disclosure is to provide a system and a method to enable the User Plane Function (UPF) to autonomously allocate Internet Protocol version 4 (IPv4) and / or Internet Protocol version 6 (IPv6) addresses to Home Gateways (HGWs), thereby reducing dependency on centralized Dynamic Host Configuration Protocol (DHCP) servers.

[0035] Another objective of the present disclosure is to provide a system and a method for supporting IP address renewal procedures for ongoing sessions directly at the UPF, ensuring timely lease extension without involving external DHCP infrastructure.

[0036] Another objective of the present disclosure is to provide a system and a method for providing a mechanism within the UPF to handle DHCP Discover (for IPv4) or DHCPv6 Solicit (for IPv6) messages received from an HGW with an already established session, such that the UPF reassigns the previously allocated IP address mapped to the same HGW.

[0037] Another objective of the present disclosure is to provide a system and a method to maintain session continuity by avoiding unnecessary teardown and re-establishment of sessions during IP renewal or HGW reboots, thus improving service reliability and reducing signalling overhead.

[0038] Another objective of the present disclosure is to provide a system and a method that simplifies network architecture by reducing the number of required network elements and interfaces.SUMMARY

[0039] In an exemplary embodiment, a method for Internet Protocol (IP) address allocation for network equipments in a network is described. The method includes receiving, by a User Plane Function (UPF), an IP address discovery message from at least one network equipment. The method includes transmitting, by the UPF, an IP address offer message to the at least one network equipment in response to the IP address discovery message. The method includes receiving, by the UPF, an IP address request message from the at least one network equipment, requesting allocation of the offered IP address. The method includes transmitting, by the UPF, an IP address acknowledgment message to the at least one network equipment, thereby allocating an IP address to the at least one network equipment, wherein the IP address is an Internet Protocol version 4 (IPv4) address or an Internet Protocol version 6 (IPv6) address. The method includes renewing, by the UPF, the allocated IP address upon receiving a lease renewal message from the at least one network equipment prior to expiration of a lease timer associated with the allocated IP address. The method includes reassigning, by the UPF, a previously allocated IP address to the at least one network equipment upon receiving the IP address discovery message that corresponds to an existing network session associated with the at least one network equipment.

[0040] In an embodiment, the IP address discovery message is at least one of a Dynamic Host Configuration Protocol Version 4 (DHCPv4) discover message or a Dynamic Host Configuration Protocol Version 6 (DHCPv6) solicit message.

[0041] In an embodiment, the DHCPv4 discover message comprises a first set of configuration parameters including a client address, a router, a subnet mask, a Network Time Protocol (NTP) server, and a Domain Name System (DNS) server and the DHCPv6 solicit message comprises a first set of configuration parameters including at least a client identifier, a DNS server, an Identity Association for Nontemporary Address (IA NA), or an Identity Association for Prefix Delegation (IA PD).

[0042] In an embodiment, the IP address offer message is at least one of a DHCPv4 Offer message or a DHCPv6 Advertisement message.

[0043] In an embodiment, the DHCPv4 Offer message comprises a second set of configuration parameters including the allocated IP address, a lease time, a DHCP server Identifier, at least one value for a requested router, a subnet mask, a NTP server, and a DNS server and the DHCPv6 Advertisement message comprises a second set of configuration parameters including the allocated IP address, a client identifier, a server identifier, a DNS server, an IA_NA, or an IA_PD

[0044] In an embodiment, the IP address request message is one of a DHCPv4 Request message and a DHCPv6 Request message.

[0045] In an embodiment, the IP address acknowledgment message is one of a DHCPv4 Acknowledgment message and a DHCPv6 Reply message.

[0046] In an embodiment, the UPF is configured to transmit the second set of configuration information along with the allocated IPv4 address and transmit a third set of configuration information along with the allocated IPv6 address, wherein the second set of configuration information comprises at least one value corresponding to each of the DNS server, a lease time, a rebind time, and a renew time.

[0047] In an embodiment, the UPF is configured to determine an allocation of the IP requested by the at least network equipment and transmit a Negative Acknowledgment (NACK) message if the requested IP cannot be allocated.

[0048] In an embodiment, the UPF processes an address renewal request or an address release request received from the at least one network equipment based on at least one of the assigned IP address and a lease timer.

[0049] In an embodiment, the lease timer is dynamically configured based on a type of service provided to the network equipment

[0050] In an embodiment, the UPF receives a Router Solicitation (RS) message from the at least one network equipment via a tunnel and transmit a Router Advertisement (RA) message to the at least one network equipment, the RA message includes a fourth set of configuration parameters.

[0051] In an embodiment, the UPF validates whether the network equipment is authorized to receive the requested IP address based on a set of preconfigured IP address allocation policies.

[0052] In an embodiment, the UPF interacts with a Session Management Function (SMF) over an N4 interface to obtain policy control information for IP address allocation and management.

[0053] In an embodiment, the UPF identifies a disconnected network equipment by detecting an absence of one of the IP address renewal request and the IP address release request for the allocated IP address within a predefined lease period or receiving a disconnection notification from the disconnected network equipment and releases the IP address associated with the disconnected network equipment to make the IP address available for reassignment to another network equipment.

[0054] In an embodiment, the plurality of network equipment comprises Home Gateways (HGWs) connected to a Customer Premises Equipment (CPE).

[0055] In an exemplary embodiment, a system for facilitating Internet Protocol (IP) address allocation for a plurality of network equipments in a network. The system includes a User Plane Function (UPF) configured to receive an IP address discovery message from at least one network equipment. The system transmits an IP address offer message to the at least one network equipment in response to the IP address discovery message. The system receives an IP address request message from the at least one network equipment, requesting allocation of the offered IP address. The system transmits an IP address acknowledgment message to the at least one network equipment, thereby allocating an IP address tothe at least one network equipment, wherein the IP address is an Internet Protocol version 4 (IPv4) address or an Internet Protocol version 6 (IPv6) address. The system renews the allocated IP address upon receiving a lease renewal message from the at least one network equipment prior to expiration of a lease timer associated with the allocated IP address. The system reassigns a previously allocated IP address to the at least one network equipment upon receiving the IP address discovery message that corresponds to an existing network session associated with the at least one network equipment

[0056] In an exemplary embodiment, a network equipment configured to transmit an Internet Protocol (IP) address discovery message to a User Plane Function (UPF). The network equipment configured to receive, from the UPF, a previously allocated Internet Protocol (IP) address that is reassigned upon the UPF receiving the Internet Protocol address discovery message corresponding to an existing network session associated with the network equipment. The network equipment configured to establish a data communication session with the UPF (218) using the previously allocated IP address for exchange of user plane data packets associated with the network equipment.

[0057] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for Internet Protocol (IP) address allocation for network equipments in a network is described. The method includes receiving, by a User Plane Function (UPF), an IP address discovery message from at least one network equipment. The method includes transmitting, by the UPF, an IP address offer message to the at least one network equipment in response to the IP address discovery message. The method includes receiving, by the UPF, an IP address request message from the at least one network equipment, requesting allocation of the offered IP address. The method includes transmitting, by the UPF, an IP address acknowledgment message to the at least one network equipment, thereby allocating an IP address to the at least one network equipment, wherein the IP address is anInternet Protocol version 4 (IPv4) address or an Internet Protocol version 6 (IPv6) address. The method includes renewing, by the UPF, the allocated IP address upon receiving a lease renewal message from the at least one network equipment prior to expiration of a lease timer associated with the allocated IP address. The method includes reassigning, by the UPF, a previously allocated IP address to the at least one network equipment upon receiving the IP address discovery message that corresponds to an existing network session associated with the at least one network equipment.BRIEF DESCRIPTION OF DRAWINGS

[0058] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Some drawings may indicate the components using block diagrams and may not represent the internal circuitry of each component. It will be appreciated by those skilled in the art that disclosure of such drawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0059] FIG. 1 illustrates an exemplary network architecture for implementing a system for Internet Protocol (IP) address allocation for network equipments in a network, in accordance with embodiments of the present disclosure.

[0060] FIG. 2A illustrates an exemplary system architecture for implementing the system for the IP address allocation for the network equipments in the network, in accordance with embodiments of the present disclosure.

[0061] FIG. 2B illustrates an exemplary block diagram of the system for implementing the system for the IP address allocation for the network equipments in the network, in accordance with embodiments of the present disclosure.

[0062] FIG. 3 illustrates a flowchart of a method for implementing the system for the IP address allocation for the network equipments in the network, in accordance with embodiments of the present disclosure.

[0063] FIG. 4 illustrates a flowchart of a method for implementing the system for the IP address allocation for the network equipments in the network, in accordance with embodiments of the present disclosure.

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

[0065] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102-1, 102-2, 102-N - Users104-1, 104-2, 104-N - User Equipments (UEs)112-1, 112-2, 112-N - Base stations106 - Network108 - System200A - System architecture212-1, 212-2 - One or more Home Gateways (HGWs)214 - Customer Premise Equipment (CPE)218 - User Plane Function (UPF)220 - Session Management Function (SMF)222 - Policy Control Function (PCF)226 - gNodeB228 - Internet200B - Block diagram230 - Receiving unit232 - Memory234 - Interface(s)236 - Processing engine238 - Other module(s)238 - Database300 - Flow diagram400 - Flow diagram500 - Computer system510 - External storage device520 - Bus530 - Main memory540 - Read only memory550 - Mass storage device560 - Communication port(s)570 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

[0066] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter can each be used independently of one another or with any combination of other features. An individual feature may not address all of the problems discussed above or might address only some of the problems discussed above. Some of the problems discussed above might not be fully addressed by any of the features described herein.

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

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

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

[0070] 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 techniquesknown to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

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

[0072] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any and all combinations of one or more of the associated listed items.

[0073] The present disclosure relates to a system and a method for Internet Protocol (IP) address allocation for network equipments in a network. Various embodiments throughout the disclosure will be explained in more detail with reference to FIGS. 1-5.

[0074] FIG. 1 illustrates an exemplary network architecture (100) for Internet Protocol (IP) address allocation for the network equipments (212) in the network (106), in accordance with embodiments of the present disclosure.

[0075] Referring to FIG. 1, the network architecture (100) may include one or more computing devices or user equipments (104-1, 104-2. . . 104-N) associated with one or more users (102-1, 102-2. .. 102-N) in an environment. The network architecture (100) may be applied on Fixed Wireless Access (FWA) deployments, where wireless cellular technology provides broadband connectivity to fixed subscriber locations. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2. .. 102-N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more user equipments (UE) (104-1, 104- 2... 104-N) may be individually referred to as the user equipment (104) and collectively referred to as the user equipment (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three user equipments (104) are depicted in FIG. 1, however, any number of the user equipments (104) may be included without departing from the scope of the ongoing description. In an embodiment, each of the user equipment (104) may have a unique identifier attribute associated therewith. In an embodiment, the unique identifier attribute may be indicative of Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, International Mobile Subscriber Identity (IMSI), Subscriber Permanent Identifier (SUPI) and the like.

[0076] In an embodiment, the user equipment (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the user equipment (104) may include, but is not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories,networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the user equipment (104) may include, but is not limited to, intelligent, multi-sensing, network-connected devices that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0077] In an embodiment, the user equipment (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a 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 user equipment (104) may include but is not limited to, any electrical, electronic, electromechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general -purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein the user equipment (104) may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user (102) or the entity such as touchpad, touch-enabled screen, electronic pen, and the like. A person of ordinary skill in the art will appreciate that the user equipment (104) may not be restricted to the mentioned devices and various other devices may be used.

[0078] As will be appreciated, the Home Gateway (HGW) may correspond to a UE. In an aspect, the users (110) are network operators or field engineers. Further, with each CPE, a set of HGW devices may be connected. A person of ordinary skill in the art will appreciate that the terms “CPE” and “UE” may be usedinterchangeably throughout the disclosure. As will be appreciated, the CPE is a network device that may be installed outdoors and indoors at customer locations to facilitate connectivity and network services. In an embodiment, examples of the CPE include a Fifth Generation (5G) or a Fourth Generation (4G) outdoor customer premise equipment which can provide a high throughput broadband connectivity to end users. The CPE can also have a functionality to connect to the 5G NonTerrestrial Network (NTN). In this context the CPE is no more dedicated to a customer premises but the set of HGWs in individual customers premise (i.e., homes) connects to a single CPE using a Multiple Dwelling Unit (MDU). In that sense the CPE is shared across multiple homes and the CPE becomes a network element for an FWA deployment serving multiple subscribers. In an embodiment, the UE 104 may be deployed as a home gateway device (HGW) connected to a customer premise equipment (CPE) for use in a 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.

[0079] Referring to FIG. 1, the user equipment (104) may communicate with the system (108) via the 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 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 user equipment (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 another 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 wirelessnetwork, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0080] In an embodiment, the UE (104) may be deployed as a home gateway device (HGW) connected to 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.

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

[0082] FIG. 2A illustrates a system architecture (200A) for implementing a system (108) for the Internet Protocol (IP) address allocation for the network equipments (212) in the network (106), in accordance with embodiments of the present disclosure.

[0083] In an embodiment, the system architecture (200A) further comprises of the network equipments (212). As will be appreciated, the network equipments (212) may be referred to as the one or more HGWs (212-1, 212-1) in the present disclosure. The system architecture (200A) further comprises of a Customer Premises Equipment (CPE) (214), gNodeB (226) a User Plane Function (UPF) (218), a Session Management Function (SMF) (220), and a Policy Control Function (PCF) (222) and the internet (228). A person of ordinary skill in the art will understand that the one or more HGW s (212-1, 212-1) may be individually referred to as the HGW (212) and collectively referred to as the HGWs (212).

[0084] In an aspect, the HGW (212) represents the end-user device, such as a router or modem, within residential or commercial premises. The HGW (212) is the interface between the UE (104) and the network (106). The HGW (212) represents an end-user device within residential or commercial premises, such as a router or modem. For instance, a home router is a common example of the HGW (212). In an aspect, when the HGW (212) is powered on, the HGW (212) sends a Dynamic Host Configuration Protocol (DHCP) Discover or DHCPv6 Solicit message to a DHCP server requesting an Internet Protocol (IP) address. The DHCP Discover message is broadcast on a local network to discover available DHCP servers that can assign the IP address to the HGW. The DHCP server then responds with a DHCP Offer message containing an available IP address and other network configuration details. The DHCPv6 Solicit message is a client-initiated request for IPv6 address configuration, carried over an Ethernet over a General Packet Radio Service (GPRS) Tunnelling Protocol (EoGRE) tunnel. The EoGRE allows Ethernet frames to be encapsulated within GPRS Tunnelling Protocol (GTP) tunnels. This encapsulation allows the DHCPv6 Solicit message to traverse the network infrastructure seamlessly. In an aspect, the message first reaches the gNodeB (226), which is the 5G radio access network element, where it is encapsulated within the GTP tunnel, enabling efficient data transfer across the core network. The gNodeB (226) forwards this encapsulated message to the UPF (218). The UPF (218) then terminates the GTP tunnel and processes the encapsulated DHCPv6 Solicit message, facilitating the allocation of an IPv6 address and other configuration parameters for the HGW (212).

[0085] In an aspect, the CPE (214) may be installed externally to connect with the HGW (212). The CPE (214) may be a central point for connecting the HGW (212) to the core network. The CPE (214) may include hardware for signal amplification, modulation, and multiplexing to efficiently handle the combined traffic from the HGW (212). The traffic originating from the HGW (212) residing at individual customer premises passes through the CPE (214). The CPE (214)creates the EoGRE tunnel with the core network and encapsulates the HGW traffic sent to the core network.

[0086] In an aspect, the gNodeB (226) supports both the CPE (214) and the HGW (212) sessions and manages the radio connection and initial processing of data traffic. From the CPE (214), the traffic reaches the gNodeB (226), creating the GTP tunnel for the packets and sending them towards the UPF (218) via a N3 interface endpoint. The N3 interface connects the UPF (218) to the Radio Access Network (RAN), specifically the gNodeB (226), which is the 5G base station. As part of the attach procedure, the gNodeB (226) learns the N3 interface endpoint and the associated GTP tunnel -ID. The GTP tunnel-ID is a unique identifier for a tunnel established between the gNodeB (226) and the UPF (218). The GTP tunnel encapsulates user data packets, allowing them to travel through the network while maintaining session information. This is similar to how a base station in a cellular network manages data traffic from the one or more UEs (104) and ensures it is correctly routed through the network (106). The gNodeB (226) ensures the data packets are appropriately formatted and transmitted, maintaining a stable connection between the CPE (214) and the core network.

[0087] In an aspect, the UPF (218) includes Broadband Network Gateway (BNG) functionality. The BNG functionality embedded within the UPF (218) facilitates the management of IP address assignments and data traffic routing, ensuring efficient broadband service delivery. Various functionalities performed by the UPF are described in detail conjunction of FIG. 2B

[0088] In an aspect, the HGW (212) may implement the DHCP client functionalities at its end (acting as a DHCP client), while the DHCP server in the network handles IP address allocation. By employing the DHCP functionalities, the system (108) automates obtaining IP addresses and network configuration from the DHCP server, facilitating seamless network connectivity for the HGWs (212).

[0089] To implement the BNG functionality, it is required that the BNG deployment match the throughput and sizing of the UPF clusters. Such an approachwould also incur additional Capital Expenditure (CAPEX) on IP fabric (in terms of additional routers / SFPs) to support the traffic movement from the UPF (218) to the BNG and then to the internet (228). To eliminate these extra capex and Operational Expenditure (OPEX) requirements and to provide a more optimized solution, the functionality of the BNG is integrated into the UPF (218), which acts as the anchor point. This integration allows for the processing of both the GTP payload (encapsulated data) and subsequently EoGRE payload (encapsulated data) in both uplink and downlink directions. This approach streamlines the network infrastructure and enhances efficiency by reducing the need for additional hardware and resource.

[0090] In an aspect, the SMF (220) is configured for establishing and managing sessions for the HGW (212). The SMF (220) communicates with the PCF (222) to enforce policies and the UPF (218) to manage session states and data reporting. For example, when the user (102) streams a video on a laptop, the SMF (220) may ensure that the session is properly established and maintained, allocating the necessary resources and enforcing network policies to provide a smooth streaming experience. The SMF (220) may also ensure that data usage is accurately tracked and reported for billing purposes.

[0091] In an aspect, the PCF (222) enforces network policies, including the authentication and authorization of the HGW (212). The PCF (222) checks the MAC address bindings and ensures that only authorized HGW can connect. For instance, in a corporate network, the PCF (222) would ensure that only authorized devices can access the network, providing an additional layer of security. The PCF (222) communicates with the SMF (220) to provide policy decisions and with the UPF (218) indirectly through the SMF (220) to manage sessions and enforce policies

[0092] In an aspect, the Internet (228) may provide external network connectivity, allowing the HGW (212) to access online resources and services. Once the HGW (212) is authenticated and authorized, it can access the internet(228) through the UPF (218), which routes the traffic appropriately. For example, when the user (102) browses a website on the UE (104), the HGW (212) may send a request to the UPF (218), which then routes it to the internet (228), retrieving the necessary data and delivering it back to the UE (104).

[0093] FIG. 2B illustrates an exemplary block diagram (200B) of the system(108) for implementing the system (108) for the Internet Protocol (IP) address allocation for the network equipments (212) in the network (106), in accordance with embodiments of the present disclosure.

[0094] The system (108) is configured for supporting the network equipments (212) including one or more Home Gateways (HGWs) (212-1, 212-2) connected via the Customer Premises Equipment (CPE) (214) and further comprises the User Plane Function (UPF) (218), the Session Management Function (SMF) (220), and the Policy Control Function (PCF) (222). The system (108) is adapted to receive, retrieve, and process encapsulated data packets associated with the HGWs (212), in accordance with a method and architecture that supports the integration of the Broadband Network Gateway (BNG) functionalities into the UPF (218).

[0095] It should be understood that the UPF (218) described herein and shown in the figures, such as Figure 2B, is a physical hardware component. The UPF (218) may be implemented as a dedicated hardware appliance, a virtualized network function (VNF) running on a server, or a combination of hardware and software. In such implementations, the UPF (218) comprises processor(s) (230), a memory (232), an interface (234), a processing engine (236) and a database (238) to perform the functions described herein.

[0096] Referring to FIG. 2B, the system (108) may include an interface(s) (234) that 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) (234) may facilitate communication to / from the system (108). The interface(s) (234) may also provide a communication pathway for one or morecomponents of the system (108). Examples of such components include, but are not limited to, the processing engine (236) and the database (238).

[0097] In an embodiment, the processing engine (236) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (236). 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 (236) may be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the processing engine (236) 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 (236). 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 (236) may be implemented by electronic circuitry.

[0098] Among other capabilities, the processing engine (236) may be configured to fetch and execute computer-readable instructions stored in a memory (232) of the system (108). The memory (232) 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 (232) may include any non- transitory storage device, including, for example, volatile memory such as Random Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.

[0099] In an embodiment, the database (238) may include data that may be either stored or generated as a result of functionalities implemented by theprocessing engine (236). In an embodiment, the database (238) may be separate from the system (108). In an embodiment, the database (238) may be indicative of including, but not limited to, a relational database, a distributed database, a cloudbased database, or the like.

[0100] In an embodiment, the processing engine (236) may further comprise other modules (238) to perform the functionalities of the UPF (218). The processing engine (238) is configured to execute functionalities of network entities, such as the UPF (218). The processing engine (208) enables the system (108) to perform the necessary operations associated with allocating IP address to the one or more HGWs (212).

[0101] In an embodiment, the processing engine (238) is configured to receive an IP address discovery message from the at least one network equipment (212). The IP address discovery message is at least one of a Dynamic Host Configuration Protocol Version 4 (DHCPv4) discover message or a Dynamic Host Configuration Protocol Version 6 (DHCPv6) solicit message. The DHCPv4 discover message comprises a first set of configuration parameters relevant to IPv4 and IPv6. The first set of configuration parameters for the DHCPv4 discover message includes a client address, a router, a subnet mask, a Network Time Protocol (NTP) server, and a Domain Name System (DNS) server. The first set of configuration parameters for the DHCPv6 solicit message includes at least a client identifier, a Domain Name System (DNS) server, an Identity Association for Nontemporary Address (IA NA), or an Identity Association for Prefix Delegation (IA PD). The UPF (218) is then configured to transmit an IP address offer message in response to the discovery message.

[0102] In an embodiment, upon receiving the discovery message, the processing engine (238) transmits an IP address offer message to the network equipment (212). The offer message is either a DHCPv4 Offer message or a DHCPv6 Advertisement message, containing the offered IP address and a set of configuration information. If the message is the DHCPv4 Discover message, theresponse is the DHCPv4 Offer message. If the message is the DHCPv6 Solicit message, the UPF responds with the DHCPv6 Advertisement message. The offer includes a second set of configuration parameters. For the DHCPv4 Offer message, a second set of configuration parameters includes the allocated IP address, a lease time, a DHCP server Identifier, at least one value for a requested router, a subnet mask, a Network Time Protocol (NTP) server, and a Domain Name System (DNS) Server. For DHCPv6, a second set of configuration parameters includes the allocated IP address, a client identifier, a server identifier, a DNS server, an Identity Association for Non-temporary Address (IA_NA), or an Identity Association for Prefix Delegation (IA PD).

[0103] In an embodiment, the system continues the IP allocation process. The processing engine (238) is configured to receive an IP address request message. The IP address request message is either a DHCPv4 Request message or a DHCPv6 Request message, formally requesting the offered IP.

[0104] The processing engine (238) is then configured to transmit an IP address acknowledgment message to the network equipment (212). The IP address acknowledgment message is either an DHCPv4 Acknowledgment message or an DHCPv6 Reply message. This acknowledgment message allocates the IP address and includes relevant configuration information. For an IPv4 address, the UPF (218) transmits the second set of configuration information, and for an IPv6 address, the UPF (218) transmits a third set of configuration parameters. The third set of configuration parameters comprises at least one value for the DNS server, a lease time, a rebind time, and a renew time. In the event that the requested IP address cannot be allocated, the processing engine (238) is configured, to transmit a Negative Acknowledgment (NACK) message.

[0105] In an embodiment, the processing engine (238) is configured to renew the allocated IP address upon receiving a lease renewal message from the network equipment (212) prior to the expiration of a lease timer. In an embodiment, the UPF (218) maintains the lease timer for each allocated IP address. The UPF(218) processes these renewal requests based on the assigned IP address and its associated lease timer. The lease timer can be dynamically configured based on a type of service provided. For example, if the network equipment (212) is being used for a high-priority, continuous service like a video conferencing call or online gaming, the UPF could dynamically configure a long lease timer. This prevents the IP address from expiring during the session. The lease timer defines the validity of the address allocation. Before the timer expires, the network equipment (212) may send the renewal request / message. The lease timer is dynamically configured based on the type of service provided to the network equipment. For instance, premium users may receive longer lease durations than standard users. This is determined by the policy configuration by a Session Management Function (SMF) (220).

[0106] In an embodiment, the processing engine (238) is also configured to reassign a previously allocated IP address to the same network equipment upon receiving a new IP address discovery message that corresponds to an existing network session associated with the same equipment (212).

[0107] The system (108) also includes a mechanism, to identify a disconnected network equipment and release its IP address for reassignment by detecting the absence of renewal requests or receiving a disconnection notification.

[0108] In an embodiment, the UPF (218) is configured to interact with other network functions and messages to ensure seamless operation. The UPF (218) is configured to interact with the SMF (220) over an N4 interface to obtain policy control information for IP address allocation and management. The system (108) is also configured to handle IPv6 Router Solicitation (RS) and Router Advertisement (RA) messages. The RA messages are sent via a tunnel, such as the Ethernet over Generic Routing Encapsulation (EoGRE). The UPF (218) is configured to transmit an RA message containing a fourth set of configuration parameters. The fourth set of configuration parameters, which refers to the information contained in the RA message, provides essential details for a device to self-configure its IPv6 networking. This set may includes the IPv6 prefix for the local network (e.g.,2001 :db8:a0b:12f0:: / 64), the router lifetime (e.g., 1800 seconds) which indicates how long the UPF (218) should be considered a default gateway, and various flag bits that instruct the HGW (212) on whether to use DHCPv6 for further configuration. It may also contain the router's MAC address and the IPv6 addresses of DNS servers (e.g., 2001:4860:4860::8888), enabling the HGW (212) to get online without needing a full DHCPv6 stateful configuration process.

[0109] Furthermore, the UPF (218) is configured to validate whether the network equipment (212) is authorized to receive the requested IP address based on a set of preconfigured policies. The preconfigured policies may be maintained locally or received dynamically via the N4 interface from the SMF (220) or the Policy Control Function (PCF) (222).

[0110] FIG. 3 illustrates a flowchart of a method (300) for implementing the system (108) for the Internet Protocol (IP) address allocation for the network equipments (212) in the network (106), in accordance with embodiments of the present disclosure.

[0111] At 302, when the HGW (212) is powered on, it obtains an IP address by sending a DHCPv4 Discover message for IPv4 or DHCPv6 Solicit message for IPv6. This message may be encapsulated within the Ethernet over the EoGRE tunnel, ensuring the Ethernet frames can traverse through different network segments seamlessly. The encapsulated DHCP message is then transmitted to the gNodeB (226), the 5G base station responsible for wireless communication with the UE (104). Within the gNodeB (226), the DHCP message may be further encapsulated within the GTP tunnel, facilitating its transport to the core network. The GTP tunnel carries the DHCP message to the UPF (218), where the GTP tunnel encapsulation is terminated, and the original DHCP message is extracted. The UPF (218) acts as the DHCP server and processes the DHCPv4 Discover or DHCPv6 Solicit message, initiating the subsequent steps of verifying, authorizing, and allocating an IP address to the HGW (212). This process ensures that the HGW(212) can be seamlessly integrated into the 5G network with proper IP address allocation, enabling it to connect to the internet (228) and other network resources.

[0112] In an aspect, the UPF (218) acts as the DHCP server and follows a specific procedure for IPv4 address allocation. Initially, the UPF (218) receives the DHCPv4 Discover message from the HGW (212), which includes the HGW (212) address set in a client address field and requests for parameters such as a router, a subnet mask, a Network Time Protocol (NTP) server, and a Domain Name System (DNS) server. In response, the UPF (218) offers the IP address using a DHCPv4 Offer message, which includes the lease time, DHCP server identifier, and values for the requested parameters. The HGW (212) then broadcasts a DHCPv4 Request message to request the offered IP address. Upon receiving this request, the UPF (218) responds with a DHCPv4 ACK (Acknowledgment) message to acknowledge the IP assignment, containing the same parameter values as the DHCPv4 Offer. If necessary, the UPF (212) may send a DHCPv4 NACK (Negative Acknowledgment) message indicating that the IP address request was denied, which can occur due to reasons such as UPF recovery or policy issues.

[0113] In an aspect, the UPF (218) acting as the DHCP server also follows a specific procedure for IPv6 address allocation. The process begins when the HGW (212) initiates the DHCPv6 SOLICIT message containing a list of requested options, including client identifier, DNS (Domain Name System), IANA (Internet Assigned Numbers Authority), and IAPD (Internet Assigned Prefix Delegation). The UPF (218) responds with a DHCPv6 ADVERTISEMENT message, which includes the client identifier, server identifier, DNS, IA NA address, and IA PD address. Following this, the HGW (212) sends a DHCPv6 REQUEST message to request the IP address offered in the previous message, containing the parameters requested by the SOLICIT message. The UPF (218) then acknowledges the IP assignment by sending a DHCPv6 REPLY message, which includes the DNS servers, lease time, rebind time, and renew time. If the IP assignment is not possible, the UPF (218) sends a NACK message within the REPLY. Additionally, the HGW (212) multicasts an IPv6 RS (Router Solicitation) message to the multicast address(for example, ff02::2), which is transported to the UPF (218) over the EoGRE tunnel. The UPF (218) responds to the IPv6 RS with an IPv6 RA (Router Advertisement) message directed to the multicast address.

[0114] In an aspect, the UPF (218) provides the lease timer for the IP address assigned to the HGW (212). Before the lease timer expires, the HGW (212) sends the DHCPv4 or DHCPv6 Request to renew the lease of the allocated IP address. Upon receiving this request, the UPF (218) validates that the HGW (212) has been assigned the same IP address and responds with a DHCP ACK, acknowledging the IP renewal. The UPF (218) will send a DHCP NACK if the session is not found. The HGW (212) then extends the existing IP address lease by the lease timer mentioned in the DHCP ACK message.

[0115] In an aspect, upon receiving the DHCPv4 Discover or DHCPv6 Solicit message from the HGW (212) for an existing session, the UPF (218) may assign an existing IP address mapped to the HGW (212). This ensures continuity and stability of the network connection, allowing the HGW (212) to maintain its assigned IP address without disruption.

[0116] At step 304, the UPF (218) is configured to verify that the MAC address present in the client-identifier within the DHCP message matches a source MAC address of the Ethernet frame received from the HGW (212). This verification is crucial to ensure the integrity and authenticity of the connection request from the HGW (212). Upon successful verification, the UPF (218) generates a Session Report Request (SRR) message. This SRR message is transmitted to the SMF (220) over the established N4 session associated with the CPE (214). The SRR message informs the SMF (220) about detecting a new MAC address. Specifically, the SRR message may include the MAC address of the HGW (212) within the “MAC Address Detected” information element (IE) of the “Ethernet Traffic Information” section of the “Usage Report”. This reporting mechanism ensures that the network management entities know all connected HGWs (212), facilitating accurate tracking and management of devices within the 5G core network.

[0117] At step 306, the UPF (218) is configured to initiate a session management (SM) policy establishment request. The SMF (220) sends a policy establishment request to the PCF (222). This action is triggered following the detection of the HGW MAC address and its successful reporting. The purpose of the SM policy establishment request is to engage the PCF (222) in determining and enforcing appropriate policies for the newly detected HGW. By involving the PCF (222), the network ensures that the connection of the HGW (212) is subjected to the necessary authorization checks and policy rules, aligning with the overall security and management framework of the 5G core network. Additionally, to ensure accurate policy application, the PCF (222) also considers the International Mobile Subscriber Identity (IMSI) of the CPE (214). The UPF (218) may further be configured to facilitate a response from the PCF (222) to the SMF (220).

[0118] At step 308, after evaluating policies against the HGW’s MAC address and the associated CPE’s IMSI, the PCF (222) transmits a response to the SMF (220). This response may include whether the HGW (212) is granted permission to access the network. The decision is based on the outcome of the policy evaluation process, ensuring that only authorized devices can use network resources.

[0119] At step 310, the SMF (220) may send a Service Request (SR) response to the UPF (218). In an aspect, the SR response typically refers to the response sent by the SMF (220) to acknowledge or provide information regarding a service request made by the UPF (218). This could involve confirming that a session has been established, modified, or any other relevant updates.

[0120] At step 312, the UPF (218) may further be configured to handle the verification and authorization of the HGW (212) within the core network. Upon receiving a positive authorization decision from the PCF (222), the SMF (220) initiates a Session Modification (SM) Request to the UPF (218). This request conveys information about the newly authorized HGW, including its unique MAC address and specific network parameters. These parameters define the networkbehaviour and resource requirements of the HGW (212), enabling the UPF (218) to configure its resources and services for the incoming user appropriately. The message in the request may contain HGW MAC-ID in “Ethernet Packet Filter” of Packet Detection Information Element (PDI-IE), Packet Detection Rules (PDRs) and corresponding Forwarding Action Rule (FAR), QoS Enforcement Rule (QER) and Usage Report Rule (URR).

[0121] At step 314, upon receipt of the SM Request from the SMF (220), the UPF (218) commences a process of IP address allocation / modification and transmits a SM response towards the SMF (220). The SM response provides relevant information or confirmation regarding the SM Request. By referencing the previously received the DHCP request from the HGW (212), the UPF (218) assigns an appropriate IPv4 or IPv6 address to the SMF (220).

[0122] At step 316, the UPF (218) may be configured to transmit a DHCP Offer or DHCPv6 Advertise message to the HGW (212), conveying the allocated IP address. This message, which contains the allocated IP address and other configuration parameters, is sent directly from the UPF (218) to the HGW (212) to complete the IP address allocation and enable the HGW (212) to access the network (106). This process also creates a new session for the HGW (212) that is linked to the existing session of the CPE (214).

[0123] The UPF (218) allocates an IP address to the HGW (212) based on the DHCP request and includes it in the SM response to the SMF (220).

[0124] Upon receiving the SM response containing the necessary details of the authorized HGW, the UPF (218) may proceed to allocate an appropriate IP address. This allocation is guided by the preceding DHCP request initiated by the HGW (212). Once the IP address is determined, the UPF (218) may transmit a DHCP Offer or DHCPv6 Advertise message to the HGW (212), conveying the assigned IP address. To effectively manage network resources and facilitate communication, the UPF (218) establishes a dedicated session for the HGW (212). This newly created session is linked to the existing session of the CPE (214) towhich the HGW (212) is physically connected, ensuring seamless integration within the network infrastructure.

[0125] To summarize the allocation of Internet Protocol Version 4 (IPv4) / Intemet Protocol Version 6 (IPv6) address to one or more Home Gateways (HGWs) (212) using an embedded DHCP server, as described below.

[0126] IP Address Allocation: The UPF (218) allocates IPv4 / IPv6 addresses to the HGW (212) using an embedded DHCP server.

[0127] DHCP Request Initiation: When the HGW (212) is powered on, it sends the DHCPv4 Discover or DHCPv6 Solicit message. This message is carried over the EoGRE tunnel, through the gNodeB (226) inside the GTP tunnel and terminated at the UPF (218).

[0128] MAC Address Verification: The UPF (218) verifies that the MAC address in the client-identifier within the DHCP message matches the source MAC address of the received Ethernet frame. The UPF (218) then sends a SR Request message to the SMF (220) over the already established N4 session of the CPE (214) for the new detected MAC address. The SRR message includes the MAC address of the HGW (212) in the “MAC Address Detected” IE of the “Ethernet Traffic Information” section of the “Usage Report.”

[0129] Provisioning and Authorization Check: The SMF (220) interacts with the PCF (222) to check if the HGW’s MAC-ID is provisioned in the network and authorizes it by verifying the binding of the HGW’s MAC address with the CPE’s IMSI. Based on the provisioning status, a positive or negative acknowledgment is sent to the UPF (218).

[0130] Session Modification Request: If the HGW (212) is provisioned, the SMF (220) sends a Session Modification Request (SMR) to the UPF (218). This message includes the HGW’s MAC-ID in the “Ethernet Packet Filter” of the PDI IE, PDRs, and corresponding FAR, QER, and URR.

[0131] IP Address Allocation Confirmation: Upon detecting the SMR for the HGW (212), the UPF (218) allocates the IPv4 or IPv6 address as per the initiated DHCP procedure and provides the HGW’s MAC-ID and assigned IPv4 / IPv6 address to the SMF (220) in the SMR response.

[0132] DHCP Response: The UPF (218) responds to the DHCP Discover / DHCPv6 Solicit with a DHCP Offer / DHCPv6 Advertise message containing the allocated IPv4 / IPv6 address.

[0133] Session Creation and Maintenance: The UPF (218) creates a session for the HGW (212) and maintains it against the previously created CPE session to which the HGWs (212) are connected.

[0134] Data Consumption Initiation: After completing the above procedures, the HGW (212) initiates data consumption using the EoGRE tunnel established between the CPE (214) and the UPF (218).

[0135] FIG. 4 illustrates a flowchart of a method (300) for implementing the method (400) for the Internet Protocol (IP) address allocation for the network equipments (212) in the network (106), in accordance with embodiments of the present disclosure.

[0136] At step 402, the method (400) comprises receiving, by the User Plane Function (UPF) (218), an IP address discovery message from at least one network equipment (212). The network equipment (212) comprises the one or more Home Gateways (HGWs) (212-1, 212-2) connected to the Fixed Wireless Access (FWA) network via the Customer Premises Equipment (CPE). This is the initial step in the IP address allocation procedure. The UPF (218), acting as a DHCP server, receives a request from a network equipment (212) that needs an IP address. The IP address discovery message is either the Dynamic Host Configuration Protocol Version 4 (DHCPv4) discover message or the Dynamic Host Configuration Protocol Version 6 (DHCPv6) solicit message. The IP address discovery message includes the first set of configuration parameters such as theclient address, the router, the subnet mask, the NTP server, and the DNS server for IPv4, or the first set of configuration parameters such as the client identifier, the DNS server, the IA NA, or the IA PD for the IPv6.

[0137] At step 404, the method (400) comprises transmitting, by the UPF (218), an IP address offer message to the at least one network equipment in response to the IP address discovery message. Upon receiving the discovery message, the UPF (218) processes the request and selects an IP address to offer to the network equipment (212). The offer message is a DHCPv4 Offer message or a DHCPv6 Advertisement message based on the protocol version used. The offer message includes a proposed IP address and the second set of configuration parameters. For instance, in the case of a DHCPv4 Offer, it includes the client IP address (yiaddr), the subnet mask, router address (default gateway), Network Time Protocol (NTP) server, and Domain Name System (DNS) server. In the case of a DHCPv6 Advertisement, it includes the client identifier, server identifier, DNS server, Identity Association for Non-temporary Address (IA NA), or Identity Association for Prefix Delegation (IA PD).

[0138] At step 406, the method (400) comprises receiving, by the UPF (218), an IP address request message from the at least one network equipment (212), requesting allocation of the offered IP address. The IP address request message is in the form of the DHCPv4 Request or the DHCPv6 Request, and it contains the same client identifier and proposed IP address received earlier. The UPF (218) parses this message and checks for consistency between the requested IP and the earlier offer. This check helps avoid IP address collisions or unauthorized requests. The UPF (218) also validates whether the equipment is allowed to obtain the requested address based on its provisioning policies and active session context.

[0139] At step 408, the method (400) comprises transmitting, by the UPF (218), an IP address acknowledgment message to the at least one network equipment (212), thereby allocating the IP address to the at least one network equipment (212). The IP address is the IPv4 address or the IPv6 address. This is thefinal step in the IP address allocation process, where the UPF (218) confirms the IP assignment. Once the request is validated, the UPF completes the address assignment by sending the acknowledgment message to the network equipment. The acknowledgment may be the DHCPv4 Acknowledgment or the DHCPv6 Reply message depending on the protocol. The UPF (218) responds with the DHCPv4 ACK message indicating the acknowledgement of the IP assignment. The message will contain all the second set of configuration parameters in DHCPv4 Offer. The IP address acknowledgment message includes the confirmed IP address and the third set of configuration parameters such as lease time, DNS server, rebind time, and renew time for DHCPv6. If the allocation fails, a Negative Acknowledgment (NACK) may be sent instead, indicating unavailability or policy violation. The lease time dictates the duration the equipment can retain the IP address without requesting renewal.

[0140] At step 410, the method (400) comprises renewing, by the UPF (218), the allocated IP address upon receiving a lease renewal message from the at least one network equipment (212) prior to expiration of the lease timer associated with the allocated IP address. This step addresses the ongoing management of the IP address and ensures session continuity. The UPF (218) processes this renewal request based on the assigned IP address and its associated lease timer. The lease timer can be dynamically configured based on the type of service being provided to the at least one network equipment (212). The at least one network equipment (212) monitors the lease timer and initiates a renewal process before it expires. This is done by sending a DHCPv4 Request or DHCPv6 Renew message, depending on the IP version. Upon receiving the renewal message, the UPF (218) verifies the IP lease validity and updates the lease timer if the renewal is permitted. If the type of service or policy dictates, the UPF (218) may dynamically update the new lease time. This mechanism ensures uninterrupted connectivity for the at least one network equipment (212) and avoids unnecessary reconfiguration.

[0141] At step 412, the method (400) comprises reassigning, by the UPF (218), the previously allocated IP address to the at least one network equipment(212) upon receiving an IP address discovery message that corresponds to the existing network session associated with the same network equipment. The UPF (218) stores session context for active and recently connected at least one network equipment (212). When the UPF (218) receives a new DHCP Discover or DHCPv6 Solicit message, it performs a context lookup to determine if the at least one network equipment (212) has an ongoing or recently released session. If a match is found, and the associated IP address is still within the validity period or reserved pool, the UPF (218) bypasses fresh allocation and reassigns the same IP address to the at least one network equipment (212). This reassignment maintains service continuity and avoids unnecessary configuration changes at the user end.

[0142] In an embodiment, the method (400) further comprises, receiving, by the UPF (218), a Router Solicitation (RS) message from the network equipment (212) and transmitting a Router Advertisement (RA) message in response, which includes the fourth set of configuration parameters. This is part of the IPv6 allocation process.

[0143] In an embodiment, the method (400) further comprises, the UPF (218) validating whether the network equipment (212) is authorized to receive the requested IP address based on a set of preconfigured IP address allocation policies.

[0144] In an embodiment, the method (400) further comprises, the UPF (218) interacting with the Session Management Function (SMF) (220) over an N4 interface to obtain policy control information for IP address allocation and management.

[0145] In an embodiment, the method further comprises identifying a disconnected network equipment by the UPF (218) by detecting the absence of a renewal or release request within a predefined lease period. Upon identification, the UPF (218) releases the IP address to make it available for reassignment.

[0146] FIG. 5 illustrates an example computer system (500) in which or with which the embodiments of the present disclosure may be implemented.

[0147] As shown in FIG. 5, the computer system (500) may include an external storage device (510), a bus (520), a main memory (530), a read-only memory (540), a mass storage device (550), a communication port(s) (560), and a processor (570). A person skilled in the art will appreciate that the computer system (500) may include more than one processor and communication ports. The processor (570) may include various modules associated with embodiments of the present disclosure. The communication port(s) (560) may be any of an RS-232 port for use with a modem -based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (560) may be chosen depending on a network, such as a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (500) connects.

[0148] In an embodiment, the main memory (530) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing static information e.g., start-up or basic input / output system (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage solutions include, but are not limited to, Parallel Advanced Technology Attachment (PATA) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces).

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

[0150] In another embodiment, operator and administrative interfaces, e.g., a display, keyboard, and cursor control device may also be coupled to the bus (520) to support direct operator interaction with the computer system (500). Other operator and administrative interfaces can be provided through network connections connected through the communication port(s) (560). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system (500) limit the scope of the present disclosure.

[0151] In an exemplary embodiment, a network equipment configured to transmit an Internet Protocol (IP) address discovery message to a User Plane Function (UPF). The network equipment configured to receive, from the UPF, a previously allocated Internet Protocol (IP) address that is reassigned upon the UPF receiving the Internet Protocol address discovery message corresponding to an existing network session associated with the network equipment. The network equipment configured to establish a data communication session with the UPF (218) using the previously allocated IP address for exchange of user plane data packets associated with the network equipment.

[0152] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for Internet Protocol (IP) address allocation for network equipments in a network is described. The method includes receiving, by a User Plane Function (UPF), an IP address discovery message from at least one network equipment. The method includes transmitting, by the UPF, an IP address offer message to the at least one network equipment in response to the IP address discovery message. The method includes receiving, by the UPF, an IP address request message from the at least one network equipment, requesting allocation of the offered IP address. The method includes transmitting, by the UPF, an IP address acknowledgment message to the at least one network equipment, thereby allocating an IP address to the at least one network equipment, wherein the IP address is anInternet Protocol version 4 (IPv4) address or an Internet Protocol version 6 (IPv6) address. The method includes renewing, by the UPF, the allocated IP address upon receiving a lease renewal message from the at least one network equipment prior to expiration of a lease timer associated with the allocated IP address. The method includes reassigning, by the UPF, a previously allocated IP address to the at least one network equipment upon receiving an IP address discovery message that corresponds to an existing network session associated with the same equipment.

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

[0154] The present disclosure provides a technical advancement in the Internet Protocol (IP) address management for network equipment, such as Home Gateways (HGWs), in 5G networks by extending the capabilities of the User Plane Function (UPF) to include the functionality of an embedded DHCP server. Unlike conventional network architectures, where IP address allocation relies on a centralized DHCP server separate from the user plane, the present disclosure enables the UPF to directly allocate and manage IPv4 / IPv6 addresses to HGWs. This overcomes the limitations of increased signalling overhead and unnecessary session teardown and re-creation associated with traditional methods. The present disclosure enables the UPF to autonomously handle DHCPv4 and DHCPv6 procedures, including the renewal of allocated IP addresses and, uniquely, the reassignment of a previously allocated IP address to an HGW for an already existing session upon receiving a new discovery message.ADVANTAGES OF THE PRESENT DISCLOSURE

[0155] The present disclosure provides a system and a method that enable reuse of previously assigned Internet Protocol (IP) addresses for an existing Home Gateway (HGW) session, eliminating redundant allocation procedures.

[0156] The present disclosure provides the system and the method that facilitate seamless handling of Dynamic Host Configuration Protocol (DHCP) Discover and DHCP version 6 (DHCPv6) Solicit messages by assigning the premapped IP address from an existing User Plane Function (UPF) session, without invoking the Session Management Function (SMF).

[0157] The present disclosure provides the system and the method that ensure consistent Internet Protocol version 4 (IPv4) and Internet Protocol version 6 (IPv6) address allocation and renewal for each HGW session, thereby reducing signalling overhead and improving service reliability.

[0158] The present disclosure provides the system and the method that enables the UPF to serve as a consolidated Broadband Network Gateway (BNG), providing Internet Protocol (IP) addresses to multiple HGW s connected through a single Customer Premises Equipment (CPE). This architecture eliminates the limitations of conventional systems, which are typically designed to manage only a single session at the CPE level.

[0159] The present disclosure provides the system and the method that support managing one or more HGWs in a network by enabling efficient IP address allocation for multiple devices connected behind each HGW, thereby ensuring optimal resource utilization, simplified address management, and uninterrupted service delivery across all connected devices.

[0160] The present disclosure provides the system and the method that support managing one or more HGWs in a network by enabling broadband connectivity to multiple customers behind the CPE, thereby eliminating the need for multiple individual Fifth Generation (5G) devices for each customer.

[0161] The present disclosure provides the system and the method that support managing one or more HGWs in a network by eliminating the requirement for separate Broadband Network Gateway (BNG) deployment equivalent to User Plane Function (UPF) cluster throughput, thereby reducing capital expenditure (CapEx).

[0162] The present disclosure provides the system and the method that support managing one or more HGWs in a network by avoiding additional investment in Internet Protocol (IP) fabric elements such as routers or Small Formfactor Pluggables (SFPs) for handling traffic between the UPF, BNG, and the internet.

[0163] The present disclosure provides the system and the method that optimize core network performance by eliminating unnecessary teardown and setup of sessions for repetitive IP address allocation requests from the same HGW.

Claims

CLAIMS1. A method (400) for Internet Protocol (IP) address allocation for network equipments (212) in a network (106), the method (400) comprising: receiving (402), by a User Plane Function (UPF) (218), an IP address discovery message from at least one network equipment (212); transmitting (404), by the UPF (218), an IP address offer message to the at least one network equipment (212) in response to the IP address discovery message; receiving (406), by the UPF (218), an IP address request message from the at least one network equipment (212), requesting allocation of the offered IP address; transmitting (408), by the UPF (218), an IP address acknowledgment message to the at least one network equipment (212), thereby allocating an IP address to the at least one network equipment (212), wherein the IP address is an Internet Protocol version 4 (IPv4) address or an Internet Protocol version 6 (IPv6) address; renewing (410), by the UPF (218), the allocated IP address upon receiving a lease renewal message from the at least one network equipment (212) prior to expiration of a lease timer associated with the allocated IP address; and reassigning (412), by the UPF (218), a previously allocated IP address to the at least one network equipment (212) upon receiving the IP address discovery message that corresponds to an existing network session associated with the at least one network equipment (212).

2. The method (400) as claimed in claim 1, wherein: the IP address discovery message is at least one of a Dynamic Host Configuration Protocol Version 4 (DHCPv4) discover message or aDynamic Host Configuration Protocol Version 6 (DHCPv6) solicit message; the DHCPv4 discover message comprises a first set of configuration parameters including a client address, a router, a subnet mask, a Network Time Protocol (NTP) server, and a Domain Name System (DNS) server; and the DHCPv6 solicit message comprises a first set of configuration parameters including at least a client identifier, a Domain Name System (DNS) server, an Identity Association for Non-temporary Address (IA NA), or an Identity Association for Prefix Delegation (IA PD).

3. The method (400) as claimed in claim 1, wherein: the IP address offer message is atleast one of a DHCPv4 Offer message or a DHCPv6 Advertisement message; the DHCPv4 Offer message comprises a second set of configuration parameters including the allocated IP address, a lease time, a DHCP server Identifier, at least one value for a requested router, a subnet mask, a Network Time Protocol (NTP) server, and a Domain Name System (DNS) Server; and the DHCPv6 Advertisement message comprises a second set of configuration parameters including the allocated IP address, a client identifier, a server identifier, a DNS server, an Identity Association for Nontemporary Address (IA NA), or an Identity Association for Prefix Delegation (IA PD).

4. The method (400) as claimed in claim 1, wherein the IP address request message is one of a DHCPv4 Request message and a DHCPv6 Request message.

5. The method (400) as claimed in claim 1, wherein the IP address acknowledgment message is one of a DHCPv4 Acknowledgment message and a DHCPv6 Reply message.

6. The method (400) as claimed in claim 1, wherein the transmitting of the IP address acknowledgment message comprises: transmitting, by the UPF (218), the second set of configuration parameters provided in the the DHCPv4 Offer message along with the allocated IPv4 address; and transmitting, by the UPF (218), a third set of configuration information along with the allocated IPv6 address, wherein the third set of configuration information comprises at least one value corresponding to each of a Domain Name System (DNS) server, a lease time, a rebind time, and a renew time.

7. The method (400) as claimed in claim 1, wherein allocating the IP address comprises: determining, by the UPF (218), allocation of the IP requested by the at least network equipment (212); and transmitting, by the UPF (218), a Negative Acknowledgment (NACK) message if the requested IP cannot be allocated.

8. The method (400) as claimed in claim 1, wherein the UPF (218) processes an address renewal request or an address release request received from the at least one network equipment (212) based on at least one of the assigned IP address and a lease timer wherein the lease timer is dynamically configured based on a type of service provided to the network equipment (212).

9. The method (400) as claimed in claim 1, wherein the allocating of the IP address comprises:receiving, by the UPF (218), a Router Solicitation (RS) message from the at least one network equipment (212) via a tunnel; and transmitting, by the UPF (218), a Router Advertisement (RA) message to the at least one network equipment (212), the RA message includes a fourth set of configuration parameters.

10. The method (400) as claimed in claim 1, wherein the UPF (218) validates whether the network equipment (212) is authorized to receive the requested IP address based on a set of preconfigured IP address allocation policies.

11. The method (400) as claimed in claim 1, wherein the UPF (218) interacts with a Session Management Function (SMF) over an N4 interface to obtain policy control information for IP address allocation and management.

12. The method (400) as claimed in claim 1, wherein the allocating of the IP address comprises: identifying, by the UPF (218), a disconnected network equipment by detecting an absence of one of the IP address renewal request and the IP address release request for the allocated IP address within a predefined lease period or receiving a disconnection notification from the disconnected network equipment; and releasing, by the UPF (218), the IP address associated with the disconnected network equipment to make the IP address available for reassignment to another network equipment.

13. The method (400) as claimed in claim 1, wherein the plurality of network equipment (212) comprises Home Gateways (HGWs) connected to a Customer Premises Equipment (CPE) (214).

14. A system (108) for facilitating Internet Protocol (IP) address allocation for a plurality of network equipments (212) in a network (106), the system (108) comprising:a User Plane Function (UPF) (218) configured to: receive an IP address discovery message from at least one network equipment (212); transmit an IP address offer message to the at least one network equipment (212) in response to the IP address discovery message; receive an IP address request message from the at least one network equipment (212), requesting allocation of the offered IP address; transmit an IP address acknowledgment message to the at least one network equipment (212), thereby allocating an IP address to the at least one network equipment (212), wherein the IP address is an Internet Protocol version 4 (IPv4) address or an Internet Protocol version 6 (IPv6) address; renew the allocated IP address upon receiving a lease renewal message from the at least one network equipment (212) prior to expiration of a lease timer associated with the allocated IP address; and reassign a previously allocated IP address to the at least one network equipment (212) upon receiving the IP address discovery message that corresponds to an existing network session associated with the at least one network equipment (212).

15. The system (108) as claimed in claim 14, wherein: the IP address discovery message is at least one of a Dynamic Host Configuration Protocol Version 4 (DHCPv4) discover message or a Dynamic Host Configuration Protocol Version 6 (DHCPv6) solicit message;the DHCPv4 discover message comprises a first set of configuration parameters including a client address, a router, a subnet mask, a Network Time Protocol (NTP) server, and a Domain Name System (DNS) server; and the DHCPv6 solicit message comprises a first set of configuration parameters including at least a client identifier, a Domain Name System (DNS) server, an Identity Association for Non-temporary Address (IA NA), or an Identity Association for Prefix Delegation (IA PD).

16. The system (108) as claimed in claim 14, wherein: the IP address offer message is atleast one of a DHCPv4 Offer message or a DHCPv6 Advertisement message. the DHCPv4 Offer message comprises a second set of configuration parameters including the allocated IP address, a lease time, a DHCP server Identifier, at least one value for a requested router, a subnet mask, a Network Time Protocol (NTP) server, and a Domain Name System (DNS) Server; and the DHCPv6 Advertisement message comprises a second set of configuration parameters including the allocated IP address, a client identifier, a server identifier, a DNS server, an Identity Association for Nontemporary Address (IA NA), or an Identity Association for Prefix Delegation (IA PD).

17. The system (108) as claimed in claim 14, wherein the IP address request message is one of a DHCPv4 Request message and a DHCPv6 Request message.

18. The system (108) as claimed in claim 14, wherein the IP address acknowledgment message is one of a DHCPv4 Acknowledgment message and a DHCPv6 Reply message.

19. The system (108) as claimed in claim 14, wherein the UPF (218) is further configured to: transmit the second set of configuration information along with the allocated IPv4 address; and transmit a third set of configuration information along with the allocated IPv6 address, wherein the second set of configuration information comprises at least one value corresponding to each of the DNS server, a lease time, a rebind time, and a renew time.

20. The system (108) as claimed in claim 14, wherein the UPF (218) is further configured to: determine an allocation of the IP requested by the at least network equipment (212); and transmit a Negative Acknowledgment (NACK) message if the requested IP cannot be allocated.

21. The system (108) as claimed in claim 14, wherein the UPF (218) is configured to process an address renewal request or an address release request received from the at least one network equipment (212) based on at least one of the assigned IP address and a lease timer, wherein the lease timer is dynamically configured based on a type of service provided to the network equipment (212).

22. The system (108) as claimed in claim 14, wherein the UPF (218) is configured to: receive a Router Solicitation (RS) message from the at least one network equipment (212) via a tunnel; and transmit a Router Advertisement (RA) message to the at least one network equipment (212), the RA message includes a fourth set of configuration parameters.

23. The system (108) as claimed in claim 14, wherein the UPF (218) is further configured to validate whether the network equipment (212) is authorized to receive the requested IP address based on a set of preconfigured IP address allocation policies.

24. The system (108) as claimed in claim 14, wherein the UPF (218) interacts with a Session Management Function (SMF) (220) over an N4 interface to obtain policy control information for IP address allocation and management.

25. The system (108) as claimed in claim 14, wherein the UPF (218) is further configured to: identify a disconnected network equipment by detecting an absence of one of the IP address renewal request and the IP address release request for the allocated IP address within a predefined lease period or receiving a disconnection notification from the disconnected network equipment; and release the IP address associated with the disconnected network equipment to make the IP address available for reassignment to another network equipment.

26. The system (108) as claimed in claim 14, wherein the plurality of network equipment (212) comprises Home Gateways (HGWs) connected to a Premises Equipment (CPE) (214).

27. A network equipment (212), configured to: transmit an Internet Protocol (IP) address discovery message to a User Plane Function (UPF) (218); receive, from the UPF (218), a previously allocated Internet Protocol (IP) address that is reassigned upon the UPF (218) receiving the Internet Protocol address discovery message corresponding to an existing network session associated with the network equipment (212); andestablish a data communication session with the UPF (218) using the previously allocated IP address for exchange of user plane data packets associated with the network equipment (212).

28. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (400) for facilitating Internet Protocol (IP) address allocation for network equipments (212) in a network (106), the method (400) comprising: receiving (402), by a User Plane Function (UPF) (218), an IP address discovery message from at least one network equipment (212); transmitting (404), by the UPF (218), an IP address offer message to the at least one network equipment (212) in response to the IP address discovery message; receiving (406), by the UPF (218), an IP address request message from the at least one network equipment (212), requesting allocation of the offered IP address; transmitting (408), by the UPF (218), an IP address acknowledgment message to the at least one network equipment (212), thereby allocating an IP address to the at least one network equipment (212), wherein the IP address is an Internet Protocol version 4 (IPv4) address or an Internet Protocol version 6 (IPv6) address; renewing (410), by the UPF (218), the allocated IP address upon receiving a lease renewal message from the at least one network equipment (212) prior to expiration of a lease timer associated with the allocated IP address; and reassigning (412), by the UPF (218), a previously allocated IP address to the at least one network equipment (212) upon receiving the IPaddress discovery message that corresponds to an existing network session associated with the at least one network equipment (212).

Images