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

Abstract

The present disclosure relates to a method (500) and system (108) for supporting a plurality of network equipment in a network (106). The method (500) comprises receiving (502) a plurality of encapsulated data packets associated with each of the plurality of network equipment. The method (500) further comprises retrieving (504) a plurality of data packets from an encapsulated data traffic by 10 performing a decapsulation process, and processing (506) the plurality of retrieved data packets to perform at least one operation to support the plurality of network equipment. The operations include authentication, authorization, and accounting based on Dynamic Host Configuration Protocol (DHCP) and MAC-IMSI binding, allocation and renewal of IP addresses, and enforcement of policy and Quality of 15 Service (QoS) rules, thereby enabling an integrated User Plane Function (UPF (218)) (218) to operate with BNG functionality within a 5G core network. 2B

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 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 managing one or more home gateways (HGW s) 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 expression ‘Home Gateway (HGW)’ used hereinafter in the specification refers to a customer-located device that interfaces user equipment with the Customer Premises Equipment (CPE) and the core network via network elements such as the Outdoor CPE (ODCPE), Radio Access Network (RAN), and User Plane Function (UPF). The HGW enables local network connectivity within the premises and facilitates data communication to and from the core network in Fixed Wireless Access (FWA) deployments.

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

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

[0007] The expression ‘International Mobile Subscriber Identity (IMSI)’ used hereinafter in the specification refers to a unique identifier associated with a mobile device or a Customer Premises Equipment (CPE), including configurations where a Home Gateway (HGW) is connected via such CPE to the core network.

[0008] The expression ‘Customer Premises Equipment (CPE)’ used hereinafter in the specification refers to a terminal device located at a subscriber’s premises for enabling connectivity to the network in Fixed Wireless Access (FWA) deployments, and may be implemented as an Outdoor CPE (ODCPE), Indoor CPE (IDCPE), or a combination thereof.

[0009] 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, a Dynamic Host Configuration Protocol (DHCP) server, and policy enforcement. It may also involve Quality of Service (QoS) management and security features.

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

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

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

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

[0014] The expression ‘Dynamic Host Configuration Protocol (DHCP) server’ used hereinafter in the specification refers to a network component that automatically assigns IP addresses and other network settings to devices connected to a network. It simplifies network administration by eliminating the need for manual configuration.

[0015] The expression ‘General Packet Radio Service (GPRS) Tunnelling Protocol (GTP)’ used hereinafter in the specification refers to a group of IP-based communication protocols used to carry data traffic within 3G, 4G, and 5G mobile networks. The GTP encapsulates and transports user data between network elements, enabling seamless communication and mobility.

[0016] The expression ‘HGW (Home Gateway) sessions’ refers to the network communication sessions established and managed by the Home Gateway within a local network environment. These sessions facilitate the interaction between user devices (such as computers, smartphones, smart TVs, and loT devices) and the external internet or service provider networks.

[0017] The expression ‘CPE sessions’ used hereinafter refers to the network communication sessions established and managed by the CPE, which serves as an interface between the customer’s external network equipment and the service provider's core network.

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

[0019] The following description of related art is intended to provide background information pertaining to the field of the disclosure. This section may include certain aspects of the art that may be related to various features of the present disclosure. However, it should be appreciated that this section be used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0020] In modem telecommunications systems, high-speed broadband services are delivered to end-users through a variety of access technologies and network topologies. A fixed wireless access broadband deployment architecture includes an Customer Premises Equipment (CPE) device situated at the subscriber’s premises, either indoor or outdoor, typically responsible for facilitating connectivity between the Home Gateway (HGW) and the 5G core network. In traditional implementations, each customer or household is provisioned with a dedicated CPE device, which in turn connects to a centralized Broadband Network Gateway (BNG). The BNG handles essential control plane and user plane functions including Authentication, Authorization, and Accounting (AAA), IP address allocation through Dynamic Host Configuration Protocol (DHCP), and Quality of Service (QoS) enforcement.

[0021] The deployment and management of BNG nodes are inherently resource-intensive. These nodes must be dimensioned and scaled in proportion to the anticipated subscriber base and traffic throughput, necessitating substantial investment in hardware, software, and associated network fabric such as routers and interfaces. Moreover, each CPE requires procurement, installation, firmware maintenance, and troubleshooting. This architecture results in elevated Capital Expenditure (CapEx) and Operational Expenditure (OpEx), particularly as the number of subscribers increases or as demands for higher throughput and lower latency grow.

[0022] Further, the interaction between the CPE and the BNG over the core network introduces additional complexity in terms of session management and IPaddress distribution. Each subscriber’s HGW functions as a DHCP client, requesting and receiving an IP address from a DHCP server located in the network, commonly integrated with the BNG. Consequently, the traffic flow involves multiple tunneling layers, such as Generic Routing Encapsulation (GRE) or Ethernet over GRE (EoGRE), and further encapsulation using GPRS Tunneling Protocol (GTP) to facilitate transport across the radio and core network segments.

[0023] Several techniques have been implemented to reduce the network load, simplify subscriber management, or virtualize certain BNG functions. For example, existing approaches have investigated deploying BNG control plane functions over software-defined network (SDN) architectures or integrating virtualized AAA functions within UPF (User Plane Function) entities. Other attempts rely on traditional RADIUS-based authentication mechanisms deployed alongside the UPF, often leaving a fragmented deployment of control and user plane functionalities across multiple logical entities.

[0024] However, these solutions still entail a separation of functions across different network elements, leading to coordination overhead, redundant data paths, and operational inefficiencies. Particularly, when supporting multiple HGWs behind a single CPE device, existing architectures fall short in enabling streamlined authentication, IP address management, traffic classification, and accounting functionalities without incurring additional infrastructure costs.

[0025] Additionally, there remain challenges with regard to uniquely identifying and managing multiple HGWs connected to a single CPE, especially in scenarios where subscriber traffic must be classified, metered, and charged independently. Conventional BNG-UPF interaction does not support direct association of traffic flows from individual HGWs based on unique identifiers such as Media Access Control (MAC) addresses coupled with subscriber identity information (e.g., IMSI or SUPI), and therefore cannot implement per-HGW policy enforcement or dynamic QoS controls in a granular manner. Further, DHCP-basedIP allocation in the traditional sense requires a separate DHCP server infrastructure and does not scale effectively when integrated within the UPF context.

[0026] Therefore, there is a need for a system and method that overcomes the limitations of the existing approaches by enabling the UPF to perform integrated DHCP and BNG functionalities for multiple HGWs behind a single CPE. Such a solution would reduce infrastructure requirements, streamline subscriber identification and traffic processing, enable per-HGW AAA and policy enforcement, and optimize overall broadband service delivery over 5G access networks.OBJECTS OF THE PRESENT DISCLOSURE

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

[0028] An object of the present disclosure is to provide a system and a method for supporting multiple Home Gateways (HGWs) connections through a single Premises Equipment (CPE) device to a core network.

[0029] Another object of the present disclosure is to provide a system and a method for authenticating HGWs based on their Medium Access Control (MAC) addresses by interacting with a Policy Control Function (PCF) via a Session Management function (SMF).

[0030] Another object of the present disclosure is to provide a system and a method that enables a User Plane Function (UPF) to manage Authentication, Authorization, Accounting (AAA) functionalities typically performed by a Broadband Network Gateway (BNG).

[0031] Another object of the present disclosure is to provide aa system and a method that reduces capital and operational expenditures by consolidating BNG functionalities within the UPF, eliminating the need for separate BNG nodes.

[0032] Another object of the present disclosure is to provide a system and a method for allocating Internet Protocol Version 4 (IPv4) / Internet Protocol Version 6 (IPv6) addresses to HGWs using an embedded Dynamic Host Configuration Protocol (DHCP) server within the UPF.

[0033] Another object of the present disclosure is to provide a system and a method for enforcing policies and Quality of Service (QoS) on HGW traffic as per the policy received from the PCF via the SMF.

[0034] Another object of the present disclosure is to provide a system and a method for individual HGW charging by sending data usage reports to the SMF.

[0035] Another object of the present disclosure is to provide a system and a method to optimize Internet Protocol (IP) address management and reduce inefficiencies associated with IP allocation in traditional systems.

[0036] Another object of the present disclosure is to provide a system and a method that enhances scalability and resource allocation efficiency in broadband networks.

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

[0038] In an exemplary embodiment, a method for supporting a plurality of network equipment in a network is described. The method comprising receiving, by a receiving unit, a plurality of encapsulated data packets associated with each of the plurality of network equipment. The method comprising retrieving, by a processing unit, a plurality of data packets from an encapsulated data traffic by performing a decapsulation process. The method comprising processing, by the processing unit, the plurality of retrieved data packets to perform at least one operation to support the plurality of network equipment.

[0039] In an embodiment, the decapsulation process comprises decapsulating, by the processing unit, the encapsulated data traffic by terminating a General Packet Radio Service (GPRS) Tunnelling Protocol (GTP) tunnel to obtain a plurality of encapsulated Ethernet frames, and decapsulating, by the processing unit, the plurality of encapsulated Ethernet frames by terminating an Ethernet over Generic Routing Encapsulation (EoGRE) tunnel to extract the plurality of data packets corresponding to each of the plurality of network equipment.

[0040] In an embodiment, the at least one operation comprises authenticating, by the processing unit, each of the plurality of network equipments based on a Media Access Control (MAC) address included in a client identifier of a Dynamic Host Configuration Protocol (DHCP) message, authorizing, by the processing unit, each of the plurality of network equipment by validating a binding between the MAC address and an International Mobile Subscriber Identity (IMSI) associated with a Customer Premises Equipment (CPE), and accounting, by the processing unit, the data traffic for each of the plurality of network equipment based on an allocated Internet Protocol (IP) address.

[0041] In an embodiment, the at least one operation further comprises receiving, by the processing unit, at least one policy rule and at least one Quality of Service (QoS) rule from a Policy Control Function (PCF) via a Session Management Function (SMF), and enforcing, by the processing unit, the at least one policy rule and the at least one QoS rule on the plurality of data packets corresponding to each of the plurality of network equipment.

[0042] In an embodiment, the method further comprises allocating, by the processing unit, the IP address to each of the plurality of network equipment based on the DHCP message.

[0043] In an embodiment, the method further comprises allocating, by the processing unit, the IP address to a respective network equipment in response to a DHCPv4 Discover message or a DHCPv6 Solicit message, and renewing, by theprocessing unit, a lease for the allocated IP address upon receiving a DHCPv4 Request message or a DHCPv6 Renew message prior to expiration of a lease timer.

[0044] In an embodiment, the plurality of network equipment comprises at least one of a User Equipment (UE) and a Home Gateway (HGW), wherein each of the one or more network equipment is communicatively coupled to the network via the CPE.

[0045] In an exemplary embodiment, a system for supporting a plurality of network equipment in a network is disclosed. The system comprising a receiving unit configured to receive a plurality of encapsulated data packets associated with each of the plurality of network equipment. The system comprising a processing unit configured to retrieve a plurality of data packets from an encapsulated data traffic by performing a decapsulation process, and process the plurality of retrieved data packets to perform at least one operation to support the plurality of network equipment.BRIEF DESCRIPTION OF DRAWINGS

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

[0047] FIG. 1 illustrates an exemplary network architecture for implementing a system for managing one or more Home Gateways (HGWs) in a network, in accordance with embodiments of the present disclosure.

[0048] FIG. 2A illustrates an exemplary system architecture for managing the one or more HGWs in a network, in accordance with embodiments of the present disclosure.

[0049] FIG. 2B illustrates an exemplary block diagram of the system for managing one or more HGWs in a network, in accordance with embodiments of the present disclosure.

[0050] FIG. 3 illustrates a flowchart of a method for managing the one or more HGWs in the network, in accordance with embodiments of the present disclosure.

[0051] FIG. 4 illustrates another exemplary flow diagram of the method for managing the one or more HGWs in the network, in accordance with embodiments of the present disclosure.

[0052] FIG. 5 illustrates a method for enhancing the UPF for supporting a plurality of network equipment in the network in accordance with embodiments of the present disclosure.

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

[0054] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102-1, 102-2 - Users104-1, 104-2 - User equipments112-1, 112-2 - Base stations106 - Network108 - System200A - System architecture212-1, 212-2 - One or more Home Gateway (HGW)214 - Customer Premises Equipment (CPE)218 - User Plane Function (UPF)220 - Session Management Function (SMF)222 - Policy Control Function (PCF)226 - gNodeB228 - Internet200B - Block diagram202 - Processors204 - Memory206 - Interface(s)208 - Processing engine209 - Other module(s)210 - Database211- Receiving Unit300 - Flow diagram400 - Method flow diagram500 - Method Flow diagram600 - Computer system610 - External storage device620 - Bus630 - Main memory’640 - Read only memory650 - Mass storage device660 - Communication port(s)670 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

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

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

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

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

[0059] 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 constmed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, such terms are intended to be inclusive in a manner similar to the term “comprising” as an open transition word without precluding any additional or other elements.

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

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

[0062] The present disclosure relates to a system and a method for improving communication in a network by managing one or more Home Gateways (HGWs). Various embodiments throughout the disclosure will be explained in more detail with reference to FIGS. 1-6.

[0063] FIG. 1 illustrates an exemplary network architecture (100) for implementing a system (108) for managing one or more HGWs in a network (106), in accordance with embodiments of the present disclosure.

[0064] Referring to FIG. 1, the network architecture (100) may include one or more computing devices or referred to as user equipments (104-1, 104-2. . . 104- N) associated with one or more users (102-1, 102-2. . . 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102-N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more user equipments (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, InternationalMobile Subscriber Identity (IMSI), Subscriber Permanent Identifier (SUPI) and the like.

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

[0066] 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), awearable computer device (e.g., aheadmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the 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.

[0067] 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 wireless network, a mobile network, a Virtual Private Network (VPN), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0068] The network (106) is configured to support Fixed Wireless Access (FWA) deployments. In the context of the present disclosure, FWA refers to the use of advanced wireless network technology, such as 4G LTE, 5G NR, or future 6G systems, to deliver high-speed broadband connectivity to customer premises without relying on traditional wired infrastructure like DSL, cable, or fiber to the home. FWA leverages the Radio Access Network (RAN) for last-mile connectivity and provides an alternative for extending broadband service to remote, rural, or underserved areas where wired deployments are impractical or cost-prohibitive. In such deployments, dedicated wireless links connect customer premises to thenetwork (106) through Customer Premises Equipment (CPE), which may be installed indoors (IDCPE) or outdoors (ODCPE).

[0069] Within FWA deployments, one or more Home Gateways (HGW s) may be installed inside the customer premises. An HGW serves as the central routing and access point for all connected user equipment (104) within the premises. It manages wired and wireless connectivity (e.g., Ethernet, Wi-Fi) for UEs, enforces local network policies, and acts as the termination point for the broadband service delivered via the CPE. The HGW may also perform network address translation (NAT), firewalling, DHCP, Quality of Service (QoS) enforcement, and traffic routing between the LAN (Local Area Network) and the WAN (Wide Area Network) provided via the FWA connection. Multiple HGWs can be connected via a single ODCPE to the network (106), aggregating traffic for processing by the core network functions, including the system (108).

[0070] The communicative coupling between the UE (104) or HGWs and the network (106) comprises receiving, from the UE or HGW, a connection request by the network (106), sending an acknowledgment of the connection request, and transmitting a plurality of signals in response. The network (106) may include a wireless card or another transceiver connection to facilitate this communication and may be implemented as or include a WAN, LAN, wireless network, mobile network, VPN, the Internet, PSTN, satellite network, fiber-optic network, or combinations thereof.

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

[0072] FIG. 2A illustrates a system architecture (200A) for managing the one or more HGWs (212), in accordance with embodiments of the present disclosure.

[0073] In an embodiment, the system architecture (200A) further comprises the one or more HGWs (212), an 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).

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

[0075] In an aspect, the CPE (214) may be installed externally to connect with the HGW (212). The ODCPE (214) may be a central point for connecting the HGW (212) to the core network. The ODCPE (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 HGWs (212-1, 212-2) residing at individual customer premises passes through the ODCPE (314). The ODCPE (314) creates the EoGRE tunnel with the core network and encapsulates the HGW traffic sent to the core network.

[0076] 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 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 and the UPF (218). This 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 multiple mobile devices and ensures it is correctly routed through the network. The gNodeB (226) ensures the data packets are appropriately formatted and transmitted, maintaining a stable connection between the CPE (214) and the core network.

[0077] In an aspect, upon receiving the packets, the UPF (218) decapsulates the GTP tunnel and retrieves the EoGRE packets. The UPF (218) has specific rules or actions defined for forwarding EoGRE packets associated with each session, including those from the CPE (214). These rules determine how packets should be handled based on the type of session, the intended destination, and the quality of service (QoS) requirements. Based on the established forwarding rules for the CPE session, the UPF (218) processes incoming EoGRE packets. This involves checkingthe packet headers, determining the appropriate next hop (destination), and forwarding the packets accordingly. For example, if the EoGRE packets are meant for an external service or application, the UPF (218) may route them to reach that destination.

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

[0079] In an aspect the BNG may be equipped with additional capabilities to decapsulate the HGW packets from the EoGRE tunnel and further process them. The BNG provides essential functionalities to the HGWs (212), including AAA of subscriber sessions, policy management, and QoS enforcement.

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

[0081] To implement the BNG functionality, it is required that the BNG deployment match the throughput and sizing of the UPF clusters. Such approach would also incur additional capital expenditure (capex) on IP fabric (in terms of additional router / 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 networkinfrastructure and enhances efficiency by reducing the need for additional hardware and resource.

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

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

[0084] 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, retrieving the necessary data and delivering it back to the UE (104).

[0085] FIG. 2B illustrates an exemplary block diagram (200B) of the system (108) for improving communication in the network (106), in accordance with embodiments of the present disclosure.

[0086] The system (108) is configured for supporting a plurality of network equipment including one or more Home Gateways (HGWs) (212) connected via an r Customer Premises Equipment (CPE) (214), and further comprises a User Plane Function (UPF) (218), a Session Management Function (SMF) (220), and a 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 Broadband Network Gateway (BNG) and Dynamic Host Configuration Protocol (DHCP) functionalities into the UPF (218).

[0087] In an aspect, the system (108) may include one or more processor(s) (202). The one or more processor(s) (202) may be implemented as one or more microprocessors, microcomputers, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer- readable instructions or routines in a non-transitory computer-readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non-transitory storage device including, for example, volatile memory such as Random Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like.

[0088] Referring to FIG. 2B, the system (108) may include an interface(s) (206). The interface (206) may also be referred to as a web platform. The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) (206) may facilitate communication to / from the system (108). The interface(s) (206) may also provide a communication pathway for one or morecomponents of the system (108). Examples of such components include but are not limited to, a processing engine(s) (208) and a database (210).

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

[0090] In an embodiment, the processing engine (208) may further comprise other modules (209). The processing engine (208) may include multiple sub-components responsible for different functionalities related to managing the one or more HGWs (212).

[0091] In an embodiment, the CPE (214) may be configured to connect to the one or more HGWs (212). The CPE (214) serves as the intermediary between the HGWs (212) and the core network, facilitating their interaction. The ODCPE (214) connects to multiple HGWs (212), aggregating their data and managing their connections to the network. The CPE (214) handles the combined data traffic by performing signal amplification, modulation, and multiplexing. This aggregationand management capability ensures that the HGWs (212) can communicate effectively with the core network, optimizing the overall network performance.

[0092] In an embodiment, the traffic originating from the HGWs (302) residing at individual customer premises passes through the CPE (214). The CPE (214) creates the EoGRE tunnel and encapsulates the HGW traffic sent to the core network. In an example, the EoGRE tunnel performs generic routing encapsulation (GRE) on an Ethernet protocol-based packet so that a packet obtained through encapsulation can be transmitted in a network that uses another network layer protocol. EoGRE tunnel uses a tunnelling protocol that encapsulates Ethernet frames. This enables the transport of Ethernet frames over IP networks, allowing for the extension of Ethernet networks across geographically dispersed locations. From the CPE (214), the traffic reaches the gNodeB (226), creating the GPRS Tunnelling protocol (GTP) tunnel for the packets.

[0093] In an aspect, the system (108) comprises a receiving unit (211) configured to receive a plurality of encapsulated data packets associated with each of the plurality of network equipment. The receiving unit (211) may be integrated within the UPF (218) and adapted to receive General Packet Radio Service (GPRS) Tunnelling Protocol (GTP)-encapsulated packets from a gNodeB (226), where each packet carries encapsulated Ethernet frames originating from the HGWs (212) via the CPE (214) in the form of Ethernet over Generic Routing Encapsulation (EoGRE) packets.

[0094] In an embodiment, the processing engine (208) is configured to retrieve a plurality of data packets from an encapsulated data traffic by performing a decapsulation process. The decapsulation process comprises: decapsulating, by the processing engine (208), the encapsulated data traffic by terminating the GTP tunnel to obtain a plurality of encapsulated Ethernet frames. The processing engine (208) is further configured to decapsulate the plurality of encapsulated Ethernet frames by terminating the EoGRE tunnel to extract the plurality of data packets corresponding to each of the plurality of network equipment.

[0095] The processing engine (208) is further configured to process the plurality of retrieved data packets to perform at least one operation to support the plurality of network equipment. The at least one operation the AAA functions performed for network security and management.

[0096] The authenticating operation of each of the plurality of network equipment is based on a Media Access Control (MAC) address included in a client identifier of a Dynamic Host Configuration Protocol (DHCP) message. The UPF (218) verifies the identity of the HGW (212) based on its MAC address, ensuring that only authorized devices can access network resources. The MAC address is obtained from the client-identifier within the DHCP message sent by the HGW (212) and is matched against the source MAC address of the Ethernet frame received by the UPF (218).

[0097] The authorizing operation of each of the plurality of network equipment is performed by validating a binding between the MAC address and an International Mobile Subscriber Identity (IMSI) associated with a Customer Premises Equipment (CPE). The CPE may comprise any device that facilitates connectivity for end-user equipment, including but not limited to Home Gateways (HGWs) or User Equipment (UE). In some embodiments, the CPE may be implemented as an indoor device, such as a residential modem or router, configured to connect directly to end-user terminals. In other embodiments, the CPE may be implemented as an Outdoor CPE (ODCPE), installed externally on the premises and configured to interface with the core network over wireless or wired channels. The UPF (218) further authorizes the HGWs (212) by validating a binding between the MAC address and an International Mobile Subscriber Identity (IMSI) associated with the CPE (214).

[0098] The accounting operation corresponding to the data traffic for each of the plurality of network equipment is based on an allocated Internet Protocol (IP) address. The UPF (218) performs accounting by tracking the data usage of each HGW (212) based on the allocated IP address.

[0099] The processing engine (208) is further configured to receive at least one policy rule and at least one Quality of Service (QoS) rule from the PCF (222) via a Session Management Function (SMF) (220). The processing engine (208) further enforces the at least one policy rule and the at least one QoS rule on the plurality of data packets corresponding to each of the plurality of network equipment. The UPF (218) ensures that these policies are correctly applied to all uplink and downlink data, including managing bandwidth, prioritizing traffic classes, and ensuring that security and service delivery requirements are met for each session.

[0100] The processing engine (208) is also configured to allocate the IP address to each of the plurality of network equipment based on the DHCP message. In furtherance thereof, the processing engine (208) allocates the IP address to a respective network equipment in response to a DHCPv4 Discover message or a DHCPv6 Solicit message, and renews a lease for the allocated IP address upon receiving a DHCPv4 Request message or a DHCPv6 Renew message prior to expiration of a lease timer through UPF (218).

[0101] The plurality of network equipment comprises one or more of a UserEquipment (UE) and a Home Gateway (HGW) (212), wherein each of the one or more network equipment is communicatively coupled to the network (106) via the CPE (214). The UPF (218), as the central anchor point, integrates DHCP and BNG functionality, thereby eliminating the need for separate deployment of BNG nodes and reducing capital and operational expenditure.

[0102] In an aspect, the system (108) includes one or more processor(s) (202), which may be implemented as microprocessors, microcontrollers, edge or fog microcontrollers, digital signal processors, central processing units, or other logic circuitries capable of executing instructions. These processor(s) (202) are configured to fetch and execute non-transitory computer-readable instructions stored in a memory (204). The memory (204) may comprise volatile memory such as Random Access Memory (RAM) or non-volatile memory such as flash memoryor Erasable Programmable Read-Only Memory (EPROM), and may store routines configured to create, receive, or transmit the data packets.

[0103] The system (108) further comprises an interface(s) (206), also referred to as a web platform, that includes interfaces for data input and output devices and storage devices. The interface(s) (206) facilitate communication to / from the system (108), and provide a communication pathway between components such as the processing engine(s) (208) and a database (210). The database (210) may store critical information such as HGW details, network configurations, session data, usage records, and system logs.

[0104] In an embodiment, the processing engine(s) (208) may be implemented as a combination of hardware and programming and may include additional modules (209) responsible for managing HGW-related functionalities. The processing engine(s) (208) is configured to interact with the SMF (220) and the PCF (222) to execute AAA, policy enforcement, and QoS control for the HGW traffic.

[0105] In an embodiment, the SMF (220) is coupled to the UPF (218), playing a pivotal role in managing sessions for the HGW (212). The SMF (220) may ensure that the HGW (212) can connect to and communicate over the network effectively. The primary function of the SMF (220) is to establish, maintain, and terminate sessions forthe HGWs (212). When the HGW (212) initiates a connection request, the SMF (220) is responsible for setting up the new connection, ensuring that the necessary resources are allocated and that the connection parameters meet the required network policies and QoS standards. This involves negotiating the terms of the session with the core network and ensuring that the UPF (218) is configured to handle the data traffic associated with the session. Once a session is established, the SMF (220) is critical in maintaining the ongoing session. The SMF (220) monitors the session’s health, manages resource allocation, and ensures that the session complies with network policies. The SMF (220) interacts with the PCF (222) to receive and implement policy decisions, which include bandwidthmanagement, traffic prioritization, and security measures. This continuous management ensures that each session is optimized for performance and reliability, providing a consistent and high-quality user experience. In addition to establishing and maintaining sessions, the SMF (220) is responsible for properly closing sessions when they are no longer needed. This includes deallocating resources, updating network records, and ensuring the termination process does not negatively impact other ongoing sessions. By efficiently managing the session lifecycle, the SMF (220) helps to optimize network resource utilization and maintain overall network stability.

[0106] In an embodiment, the database (210) may be configured as a centralized repository for storing critical information such as HGW details, network configurations, usage data, and system logs. By consolidating data in the database (210), the system (108) can optimize performance, facilitate data retrieval, and support various system functions. For instance, the UPF (218) can access the database (210) to obtain information on the HGW (212) for processing data traffic and generating usage reports, similarly, the SMF (220) can utilize the database (210) to store session information and track user activities.

[0107] In an illustrative working example, when multiple HGW s (212) from different households connect to the CPE (214), each HGW (212) sends a DHCPv6 Solicit message requesting an IP address. The CPE (214) encapsulates the DHCP message within EoGRE and forwards it via gNodeB (226) using GTP encapsulation. The receiving unit (211) within the UPF (218) receives these encapsulated packets and forwards them to the processing engine (208), which retrieves the original DHCP message by first decapsulating the GTP tunnel, then the EoGRE tunnel. The processing engine (208) authenticates the MAC address, verifies the IMSI binding, allocates a unique IPv6 address from the embedded DHCP server, applies applicable QoS rules received from the PCF (222) via the SMF (220), and begins tracking data usage. This ensures that broadband services are dynamically provisioned for each customer device behind the ODCPE (214) without requiring traditional BNG infrastructure.

[0108] FIG. 3 illustrates a flowchart of a method (300) for managing the one or more HGWs (212) in the network (106), in accordance with embodiments of the present disclosure.

[0109] 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 and other network resources.

[0110] 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 (NegativeAcknowledgment) message indicating that the IP address request was denied, which can occur due to reasons such as UPF recovery or policy issues.

[0111] 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, ffD2::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.

[0112] In an aspect, the UPF (218) provides a 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.

[0113] In an aspect, upon receiving a DHCPv4 Discover or DHCPv6 Solicit message from the HGW (212) for an existing session, the UPF (218) may assign anexisting 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.

[0114] At step 304, the UPF (218) is configured to perform AAA functions, which are critical for network security and management. The UPF (218) first verifies that the MAC address present in the client-identifier within the DHCP message matches the 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 ODCPE (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.

[0115] 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 associated ODCPE (214). The UPF (218)may further be configured to facilitate a response from the PCF (222) to the SMF (220).

[0116] At step 308, after evaluating policies against the HGW’s MAC address and the associated ODCPE’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.

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

[0118] 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 network behaviour 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).

[0119] 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 thepreviously received the DHCP request from the HGW (212), the UPF (218) assigns an appropriate IPv4 or IPv6 address to the SMF (220).

[0120] 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. To facilitate efficient network management, the UPF (218) establishes a dedicated session for the HGW (212), linking it to the existing session of the ODCPE (214) to which the HGW (212) is connected.

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

[0122] 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 ODCPE (214) to which the HGW (212) is physically connected, ensuring seamless integration within the network infrastructure.

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

[0124] HGW Authentication: The UPF (218) authenticates the HGW (212) based on its MAC address by interacting with the PCF (222) via the SMF (220).

[0125] HGW Authorization: The UPF (218) authorizes the HGW (212) based on the binding of MAC address of the HGW (212) and the ODCPE IMSI, also facilitated by the PCF (222) via the SMF (220).

[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 ODCPE (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 ODCPE’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 ODCPE 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 ODCPE (214) and the UPF (218).

[0135] FIG. 4 illustrates an exemplary flowchart of a method (400) improving communication in the network (106), in accordance with embodiments of the present disclosure.

[0136] At step (402), the method (400) may be configured to assign an IP address to each of the one or more Home Gateways (HGWs) (212) using the DHCP server.

[0137] When the HGW (212) is powered on, it obtains the IP address by sending the DHCP Discover message for Internet Protocol Version 4 (IPv4) or by sending the DHCP Solicit message for Internet Protocol Version 6 (IPv6). This message may be encapsulated within the EoGRE tunnel, ensuring the Ethernet frames can traverse different network segments seamlessly. The encapsulated DHCP message is then transmitted to a Next Generation RAN (NG-RAN) Node B (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, andallocating 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 and other network resources.

[0138] The following procedures are implemented at the UPF (218) for IPv4 / IPv6 allocation to the HGWs (212), as well as the renewal of allocated IP addresses: a. IPv4 Address Allocation i. DHCP Discover Message: The UPF (218) acting as DHCP Server receives DHCPv4 Discover message containing HGW Address set in the Client address, along with requests for Router, Subnet Mask, NTP Server, and DNS Server in the parameter list. ii. DHCP Offer Message: The UPF (218) offers an IP address using aDHCPv4 Offer message, which includes Uease Time, DHCP server Identifier, Router, Subnet Mask, Network Time Protocol (NTP) Server, and Domain Name System (DNS) Server. iii. DHCP Request Broadcast: The HGW (212) broadcasts a DHCPv4 Request message to request the offered IP address. iv. DHCP Acknowledgement (ACK) Response: The UPF (218) responds with a DHCPv4 ACK message to acknowledge the IP assignment, including the requested parameters. v. DHCP NACK Response: The UPF (218) may send a DHCPv4 Negative Acknowledgment (NACK) message if the IP Address request is denied for reasons like UPF recovery or policy. b. IPv6 Address Allocation i. DHCPv6 SOUCIT Message: The HGW (212) initiates a DHCPv6 SOUICIT message containing requested options such as client identifier,Domain Name System (DNS), (Internet Assigned Numbers Authority) IANA, and Identifier Assignment for Prefix Delegation (IAPD). ii. DHCPv6 ADVERTISEMENT Message: The UPF (218) responds with a DHCPv6 ADVERTISEMENT message containing client identifier, server identifier, DNS, IA_NA address, and IA_PD address. iii. DHCPv6 REQUEST Message: The HGW (212) sends a DHCPv6 REQUEST message to request the offered IP address, including the requested parameters from the SOLICIT message. iv. DHCPv6 REPLY Message: The UPF (218) acknowledges the IP assignment with a DHCPv6 REPLY message, containing the DNS servers, Lease, Rebind, and Renew Time. v. DHCPv6 NACK Message: If the IP assignment is not possible, the UPF (218) sends a NACK inside the REPLY message. vi. Router Solicitation: The HGW (212) multicasts the IPv6 RS (Router Solicitation) message to the multicast address ffD2::2, transported to the UPF over the EoGRE tunnel. vii . Router Advertisement: The UPF (218) responds to the IPv6 RS with an IPv6 RA (Router Advertisement) sent to the destination IP ffD2: : 1. c. Renewal of Allocated IP Address i. Lease Timer: The UPF (218) provides a lease timer for the IP address assigned to the HGW (212). ii. DHCP Request: Before the lease timer expires, the HGW (212) sends a DHCPv4 / DHCPv6 Request to renew the IP address lease. iii. DHCP ACK: The UPF (218) validates assigned IP address of the HGW (212) and responds with a DHCP ACK message to acknowledge the renewal.iv. DHCP NACK: If the session is not found, the UPF (218) sends a DHCP NACK message. v. Lease Extension: The HGW (212) extends the existing IP address lease by the lease timer mentioned in the DHCP ACK message. d. Handling of DHCP Discover / DHCPv6 Solicit from the HGW (212) for Already Existing Session i. On receiving a DHCP Discover / DHCPv6 Solicit message for an existing session, the UPF (218) assigns the existing IP mapped with the HGW (212). e. IP Allocation RenewalThe UPF (218) provides a lease timer for the assigned IP address. i. DHCP Request: The HGW (212) sends a DHCPv4 / DHCPv6 Request to renew the lease before the timer expires. ii. DHCP ACK: The UPF (218) validates the same IP address assignment and responds with a DHCP ACK. iii. DHCP NACK: If the session is not found, the UPF (218) sends a DHCP NACK. iv. Lease Extension: The HGW (212) extends the lease by the time mentioned in the DHCP ACK. f. DHCP Discover / DHCPv6 Solicit from the HGW (212) for Existing Session i. Upon receiving DHCP Discover / DHCPv6 Solicit for an existing session, the UPF (218) assigns the existing IP mapped with the HGW (212). g. HGW Disconnect i. Session Release: The UPF (218) initiates the HGW (212) session release procedures upon receiving events like DHCP Release from the HGW (212) or DHCP Lease expiry.ii. Session Report Request: The UPF (218) sends a Session Report Request to the SMF (220) with HGW MAC address. iii. Session Report Response: The SMF (220) responds with a Session Report Response. iv. Session Cleanup: The SMF (220) initiates cleanup of the session in a Charging Function (CHF) and the PCF (222). v. Session Modification Request: The SMF (220) sends a Session Modification Request to the UPF (218) to delete all associated PDRs, FARs, QERs, and URRs. vi. Session Context Removal: The UPF (218) removes the HGW (212) session context and responds with a Session Modification Response to the SMF (220) with the final consumed volume quota. h. HGW Reboot i. New DHCP Discover: The HGW (212) initiates a new DHCP Discover message upon reboot. The UPF (218) will either clean up the existing session or continue it by assigning the same IP address. ii. DHCP Request Handling: If the HGW (212) sends a DHCP Request message, the UPF (218) checks for the existing session. If present, it responds with the already assigned IP. If absent, the UPF (218) replies with DHCP NACK / DHCPv6 Reply (No Session Binding) and creates a new session on the next DHCP Discover message. i. ODCPE Reboot i. ODCPE Connection: The ODCPE (214) reconnects to the 5G core network, clearing old sessions of the ODCPE (214) and associated the HGWs (212) without awareness of the HGW (212).ii. Uplink Packets: When the HGW (212) sends packets in the UL direction with the previous session’s source IP, the UPF (218) sends DHCPv4 FORCERENEW for IPv4 and DHCPv6 RECONFIGURE for IPv6 if no session is found. iii. IP Renewal: The HGW (212) initiates IP renewal upon receiving DHCPv4 FORCERENEW or DHCPv6 Reconfigure. The UPF (218) responds with DHCP NACK for IPv4 or DHCP Reply with “No session binding” for IPv6, leading to fresh DHCP procedures.

[0139] At step (404), the method (400) may be configured to perform authentication, authorization, and accounting (AAA) functions for the one or more HGWs (212). To perform AAA functions for the one or more HGWs (212), the UPF (218), may configured to receive the DHCP request and verifying the MAC address against the source Ethernet frame. The source Ethernet frame may refer to a specific field within an Ethernet frame that contains the MAC address of the HGW (212) that originally sent the frame. The verified MAC address is reported to the SMF (220), which engages the PCF (222) to establish session management policies. The PCF (222) evaluates these policies and authorizes the HGW (212) based on its MAC address and the IMSI of the associated ODCPE (214). The SMF (220) then sends an SMR to the UPF (218), including the necessary network parameters for the authorized HGW. The UPF (218) configures its resources, ensuring that only authorized HGWs can access the network, maintaining secure and authenticated access.

[0140] At step (406), the method (400) may be configured to process data traffic for the one or more HGWs (212).

[0141] In an aspect, the UPF (218) may be enhanced by including the functionality of the DHCP server, supporting both the DHCPv4 and the DHCPv6 procedures. Further enhancements are made in a Packet Forwarding Control Protocol (PFCP) procedures over the N4 interface for interaction with the SMF (220), the CHF (Charging Function), and the PCF (222) via the SMF (220). Thefollowing enhancements are implemented for the identification and processing of the uplink (UL) and downlink (DL) traffic associated with the HGW (212). a) Uplink Traffic Processing i. On receiving data traffic over the N3 interface, the UPF (218) identifies the session of the ODCPE (214) based on PDR. ii. The UPF (218) decapsulates the packet from the GTP tunnel. If the packet has the EoGRE tunnel, it is identified as originating from the HGW (212). If not, it is the ODCPE (214)-originated packet and is forwarded on the N6 interface after applying a QoS Enforcement Rule (QER) as per Forwarding Action Rule (FAR) of the ODCPE (214). iii. For packets from the EoGRE tunnel, the UPF (218) removes the EoGRE tunnel. Based on the PDI having the MAC-ID and the source MAC of the Ethernet frame in EoGRE, the HGW (212) session is identified, and flow mapping with the session is created. The packet is then forwarded over the N6 interface as per the FAR. iv. The UPF (218) maintains the ODCPE (214) IP as the EoGRE tunnel IP against the HGW (212) session and maps the HGW (212) session with the ODCPE (214) session. b) Downlink Traffic Processing i. On receiving data traffic over the N6 interface, the UPF (218) identifies the PDR based on the destination IP address (either the HGW (212) IP Address or the ODCPE (214) IP Address). ii. If the PDR belongs to the HGW (212), identified by the presence of the HGW (212) MAC address in the PDI, the HGW (212) session is identified. An EoGRE tunnel is created with the destination IP as the ODCPE (214) IP and the source IP as the UPF (218) IP. The ODCPE (214) session is identified from the HGW (212) MAC-ID, and the GTP tunnel is createdbefore forwarding the packet over the N3 interface towards the HGW (212) via the ODCPE (214). iii. If the PDR belongs to the ODCPE (214) IP, the packet is processed as per the QER and URR associated with the PDR and forwarded to the ODCPE (214) via the gNodeB (226) using GTP tunnel encapsulation.

[0142] At step (408), the method (400) may be configured to enforce network policies for the one or more HGWs (212) based on policies received from the PCF (222).

[0143] In an aspect, the UPF (218) enforces network policies to ensure proper QoS and security for the HGWs (212). After the PCF (222) evaluates and authorizes the HGW (212), the UPF (218) implements the policies received from the PCF (222). These policies include bandwidth allocation, traffic prioritization, and security measures. The UPF (218) enforces these policies throughout the session lifecycle, ensuring optimal resource usage and a high-quality user experience. By integrating the BNG functionality within the UPF (218), the solution eliminates additional capex and opex, providing a more optimized and efficient network management system.

[0144] Following procedures may be implemented at the UPF (218) to ensure service continuity once the HGWs (212) or the ODCPE (214) reboots abruptly. a) For HGW Reboot i. HGW Reboot Initiation: Upon rebooting, the HGW (212) initiates a new DHCP Discover message, signalling to the network its need for a new IP address and network configuration parameters. ii. Session Handling: The UPF (218) receives the DHCP Discover message and determines the appropriate course of action. If an existing session for the HGW (212) is found, the UPF (218) may either continue the existing session by assigning the same IP address or initiate a cleanup process.iii. DHCP Request Handling: If the HGW (212) subsequently sends a DHCP Request message, the UPF (218) verifies the request. If an existing session is found, the UPF (218) responds with the previously assigned IP address. Otherwise, it replies with a DHCP NACK or DHCPv6 Reply (No Session Binding) message, prompting the HGW (212) to initiate a new session establishment process. b) For ODCPE Reboot i. ODCPE Reconnection: When the ODCPE (214) reboots, it re-establishes its connection to the 5G core network. This process results in the termination of all HGW sessions associated with the ODCPE (214). ii. HGW Traffic: Upon rebooting, the ODCPE (214) reconnects to the 5G core network. Old sessions of the ODCPE (214) and the HGWs (212) are cleared in the 5G core network without the HGW (212) being aware of it. When the HGW (212) attempts to send data using its previously assigned IP address, the UPF (218) detects the missing session and initiates a session recovery process. iii. IP Renewal: To re-establish connectivity, the UPF (218) sends a DHCPv4 FORCERENEW message (for IPv4) or a DHCPv6 RECONFIGURE message (for IPv6) to the HGW (212). iv. HGW Response: The HGW (212) responds to the FORCERENEW or RECONFIGURE message by initiating a fresh DHCP discovery and allocation process.

[0145] For HGW Charging and Plan Modification a) HGW Charging i. The UPF (218) monitors data consumption for each HGW (212) and generates usage records.ii. The UPF (218) includes data usage information in Session Report Request (SRR) messages sent to the SMF (220). iii. The UPF (218) utilizes the Usage Report Rule ID (URR ID) configured by the SMF (220) to associate data usage with the HGWs (212). iv. The SMF (220) receives usage reports from the UPF (218) and forwards them to charging systems for billing purposes. b) HGW Plan Modification / Suspension i. Any HGW service plan or policy changes are communicated to the UPF (218) via the SMR (Session Modification Request / Response). ii. The UPF (218) updates its configuration based on the received SMR to reflect the modified plan or policy for the HGW (212).

[0146] FIG. 5 illustrates a method for supporting a plurality of network equipment in a network.

[0147] In step 502, the method comprises receiving, by a receiving unit (211), a plurality of encapsulated data packets associated with each of the plurality of network equipment. In an embodiment, the receiving unit (211) receives GTP- encapsulated packets from a gNodeB, wherein the GTP packets encapsulate Ethernet over Generic Routing Encapsulation (EoGRE) frames, which in turn encapsulate data traffic from the plurality of network equipment. The plurality of network equipment may include one or more Home Gateways (HGWs) and User Equipment (UEs), each connected to the network via a Customer Premises Equipment (CPE).

[0148] In step 504, the method comprises retrieving, by a processing unit, a plurality of data packets from an encapsulated data traffic by performing a decapsulation process. In an embodiment, the processing unit is configured to perform the decapsulation process by terminating a General Packet Radio Service (GPRS) Tunnelling Protocol (GTP) tunnel to obtain a plurality of encapsulatedEthernet frames, and further terminating an Ethernet over Generic Routing Encapsulation (EoGRE) tunnel to extract the plurality of data packets corresponding to each of the network equipment.

[0149] In step 506, the method comprises processing, by the processing unit, the plurality of retrieved data packets to perform at least one operation to support the plurality of network equipment. The at least one operation includes authentication, authorization, accounting, IP address allocation, and policy and Quality of Service (QoS) enforcement.

[0150] The method may further comprise authenticating, by the processing unit, each of the plurality of network equipment based on a Media Access Control (MAC) address included in a client identifier of a Dynamic Host Configuration Protocol (DHCP) message. The MAC address is validated against the source MAC address extracted from the encapsulated packet received at the processing unit.

[0151] The method may further comprise authorizing, by the processing unit, each of the plurality of network equipment by validating a binding between the MAC address and an International Mobile Subscriber Identity (IMSI) associated with a CPE.

[0152] The method may further comprise accounting, by the processing unit, the data traffic for each of the plurality of network equipment based on an allocated Internet Protocol (IP) address. In an example, the processing unit tracks per-session usage data for each HGW and reports it for billing or analytics purposes.

[0153] The method may further comprise receiving, by the processing unit, at least one policy rule and at least one Quality of Service (QoS) rule from a Policy Control Function (PCF) via a Session Management Function (SMF). The processing unit enforces these policy and QoS rules on the data packets associated with each of the plurality of network equipment.

[0154] The method may further comprise allocating, by the processing unit, the IP address to each of the plurality of network equipment based on the DHCPmessage. In an example, the IP address is allocated in response to a DHCPv4 Discover message or a DHCPv6 Solicit message, and the lease for the allocated IP address is renewed upon receiving a DHCPv4 Request message or a DHCPv6 Renew message before expiration of a lease timer.

[0155] In some embodiments, the network equipment comprises one or more of: a User Equipment (UE), or a Home Gateway (HGW), wherein each is communicatively coupled to the network via a Customer Premises Equipment (CPE). The network may include a 5G core network comprising a gNodeB, User Plane Function (UPF), Session Management Function (SMF), and Policy Control Function (PCF), which collaboratively facilitate traffic routing, session management, and policy enforcement for each of the network equipment.

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

[0157] As shown in FIG. 6, the computer system (600) may include an external storage device (610), a bus (620), a main memory (630), a read-only memory (640), a mass storage device (650), a communication port(s) (660), and a processor (670). A person skilled in the art will appreciate that the computer system (600) may include more than one processor and communication ports. The processor (670) may include various modules associated with embodiments of the present disclosure. The communication port(s) (660) may be any of an RS-232 port for use with a modem-based dialup connection, a 10 / 100 Ethernet port, a Gigabit or 10 Gigabit port using copper or fiber, a serial port, a parallel port, or other existing or future ports. The communication ports(s) (660) 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 (600) connects.

[0158] In an embodiment, the main memory (630) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (640) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chip for storing staticinformation e.g., start-up or basic input / output system (BIOS) instructions for the processor (670). The mass storage device (650) may be any current or future mass storage solution, which can be used to store information and / or instructions. Exemplary mass storage 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).

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

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

[0161] 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 foregoingdescriptive matter to be implemented merely as illustrative of the disclosure and not as limitation.ADVANTAGES OF THE PRESENT DISCLOSUREThe present disclosure provides a system and method for delivering broadband connectivity to multiple customer premises using a single Outdoor Customer Premises Equipment (ODCPE) in a Fixed Wireless Access (FWA) network, thereby optimizing network resource utilization and reducing last-mile infrastructure costs.The present disclosure eliminates the need for deploying a separate Broadband Network Gateway (BNG) node by integrating BNG functionality directly within the User Plane Function (UPF), resulting in reduced capital expenditure (capex) and operational expenditure (opex) while maintaining full AAA (Authentication, Authorization, and Accounting) capabilities.The present disclosure supports both DHCPv4 and DHCPv6 procedures directly at the UPF through an embedded DHCP server, enabling efficient IP address allocation and lease management for each connected Home Gateway (HGW) without the need for external DHCP infrastructure.The present disclosure enhances the UPF to perform two-stage decapsulation, terminating GTP tunnels and subsequently terminating Ethernet over GRE (EoGRE) tunnels, to retrieve data packets corresponding to multiple HGWs, ensuring accurate traffic separation and per-customer identification using a combination of MAC address and IMSI.The present disclosure enables per-subscriber policy enforcement and Quality of Service (QoS) management at the UPF based on rules received from the Policy Control Function (PCF) via the Session Management Function (SMF), thereby ensuring consistent service quality across all connected customers.The present disclosure increases the robustness and reliability of 5G FWA deployments by reducing dependency on multiple network elements for subscriber management, simplifying the call flow, and enhancing interoperability with existing 3GPP core components. The present disclosure improves scalability of fixed broadband delivery over 5G access by supporting multiple HGWs behind a single ODCPE while maintaining independent session management, accounting, and security for each customer.

Claims

CLAIMS1. A method for supporting a plurality of network equipment in a network, the method comprising: receiving, by a receiving unit (211), a plurality of encapsulated data packets associated with each of the plurality of network equipment; retrieving, by a processing unit (208), a plurality of data packets from an encapsulated data traffic by performing a decapsulation process; and processing, by the processing unit (208), the plurality of retrieved data packets to perform at least one operation to support the plurality of network equipment.

2. The method as claimed in claim 1, wherein the decapsulation process comprises: decapsulating, by the processing unit (208), the encapsulated data traffic by terminating a General Packet Radio Service (GPRS) Tunnelling Protocol (GTP) tunnel to obtain a plurality of encapsulated Ethernet frames; and decapsulating, by the processing unit (208), the plurality of encapsulated Ethernet frames by terminating an Ethernet over Generic Routing Encapsulation (EoGRE) tunnel to extract the plurality of data packets corresponding to each of the plurality of network equipment.

3. The method as claimed in claim 1, wherein the at least one operation comprises: authenticating, by the processing unit (208), each of the plurality of network equipments based on a Media Access Control (MAC) address included in a client identifier of a Dynamic Host Configuration Protocol (DHCP) message;authorizing, by the processing unit (208), each of the plurality of network equipment by validating a binding between the MAC address and an International Mobile Subscriber Identity (IMSI) associated with a Customer Premises Equipment (CPE); and accounting, by the processing unit (208), the data traffic for each of the plurality of network equipment based on an allocated Internet Protocol (IP) address.

4. The method as claimed in claim 3, wherein the at least one operation further comprises: receiving, by the processing unit (208), at least one policy rule and at least one Quality of Service (QoS) rule from a Policy Control Function (PCF (222)) via a Session Management Function (SMF (220)); and enforcing, by the processing unit (208), the at least one policy rule and the at least one QoS rule on the plurality of data packets corresponding to each of the plurality of network equipment.

5. The method as claimed in claim 1, comprising allocating, by the processing unit (208), the IP address to each of the plurality of network equipment based on the DHCP message.

6. The method as claimed in claim 5, comprising: allocating, by the processing unit (208), the IP address to a respective network equipment in response to a DHCPv4 Discover message or a DHCPv6 Solicit message; and renewing, by the processing unit (208), a lease for the allocated IP address upon receiving a DHCPv4 Request message or a DHCPv6 Renew message prior to expiration of a lease timer.

7. The method as claimed in claim 1, wherein the plurality of network equipment comprises at least one of:a User Equipment (UE); and a Home Gateway (HGW 212); wherein each of the one or more network equipment is communicatively coupled to the network via the CPE.

8. A system for supporting a plurality of network equipment in a network, the system comprising: a receiving unit (211) configured to receive a plurality of encapsulated data packets associated with each of the plurality of network equipment; a processing unit (208) configured to: retrieve a plurality of data packets from an encapsulated data traffic by performing a decapsulation process; and process the plurality of retrieved data packets to perform at least one operation to support the plurality of network equipment.

9. The system as claimed in claim 8, wherein the processing unit (208) is configured to: decapsulate the encapsulated data traffic by terminating a General Packet Radio Service (GPRS) Tunnelling Protocol (GTP) tunnel to obtain a plurality of encapsulated Ethernet frames; and decapsulate the plurality of encapsulated Ethernet frames by terminating an Ethernet over Generic Routing Encapsulation (EoGRE) tunnel to extract the plurality of data packets corresponding to each of the plurality of network equipment.

10. The system as claimed in claim 8, wherein the processing unit (208) is configured to:authenticate each of the plurality of network equipment based on a Media Access Control (MAC) address included in a client identifier of a Dynamic Host Configuration Protocol (DHCP) message; authorize each of the plurality of network equipment by validating a binding between the MAC address and an International Mobile Subscriber Identity (IMSI) associated with an Customer Premises Equipment (CPE); and account the data traffic for each of the plurality of network equipment based on an allocated Internet Protocol (IP) address.

11. The system as claimed in claim 10, wherein the processing unit (208) is further configured to: receive at least one policy rule and at least one Quality of Service (QoS) rule from a Policy Control Function (PCF (222)) via a Session Management Function (SMF (220)); and enforce the at least one policy rule and the at least one QoS rule on the plurality of data packets corresponding to each of the plurality of network equipment.

12. The system as claimed in claim 8, wherein the processing unit (208) is configured to allocate the IP address to each of the plurality of network equipment based on the DHCP message.

13. The system as claimed in claim 8, wherein the processing unit (208) is further configured to: allocate the IP address to a respective network equipment in response to a DHCPv4 Discover message or a DHCPv6 Solicit message; andrenew a lease for the allocated IP address upon receiving a DHCPv4 Request message or a DHCPv6 Renew message prior to expiration of a lease timer.

14. The system as claimed in claim 8, wherein the plurality of network equipment comprises one or more of: a User Equipment (UE); a Home Gateway (HGW 212), and wherein each of the one or more network equipment is communicatively coupled to the network via the CPE.

15. 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 for supporting a plurality of network equipment in a network, the method comprising: receiving, by a receiving unit (211), a plurality of encapsulated data packets associated with each of the plurality of network equipment; retrieving, by a processing unit (208), a plurality of data packets from an encapsulated data traffic by performing a decapsulation process; and processing, by the processing unit (208), the plurality of retrieved data packets to perform at least one operation to support the plurality of network equipment.

Images