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

Abstract

The present disclosure relates to a system (108) and a method (400) for processing data traffic in a fixed wireless access network. The method (400) includes receiving, by a User Plane Function (UPF) (218), data traffic from Home Gateways (HGWs) (212) and a Customer Premises Equipment (CPE) (214) over one or more network interfaces. The method (400) includes determining, by the UPF (218), a type of the received data traffic by monitoring the reception of data traffic on at least one network interface. The type of the received data traffic includes an uplink data traffic or a downlink data traffic. The method (400) includes processing, by the UPF (218), the received data traffic in accordance with the determined type of the received data traffic. The processing includes executing a set of operative steps for the uplink data traffic and a set of operative steps for the downlink data traffic.

Description

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

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

[0002] The embodiments of the present disclosure generally relate to communication networks. In particular, the present disclosure relates to a system and a method for processing data traffic in a fixed wireless access network.DEFINITIONS

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

[0004] The term ‘Customer Premise Equipment (CPE)’ used hereinafter in the specification refers to a 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.

[0005] The term ‘network equipment or 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.

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

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

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

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

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

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

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

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

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

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

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

[0017] The expression ‘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.

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

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

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

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

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

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

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

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

[0026] The term “data traffic” refers to a stream of one or more data packets, while the term “data packet” refers to an individual unit of such traffic.

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

[0028] 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 onlyto enhance the understanding of the reader with respect to the present disclosure, and not as admissions of prior art.

[0029] In Fixed Wireless Access (FWA) networks, a User Plane Function (UPF) is responsible for handling user data traffic between customer premises and external networks. Such data traffic can be classified into uplink traffic (from a Customer Premises Equipment (CPE) or Home Gateway (HGW) towards a core network / intemet) and downlink traffic (from the core network / intemet towards the CPE or HGW). Efficient processing of these traffic types is critical for maintaining service quality, ensuring correct routing, and supporting multiple customer devices behind gateways.

[0030] In conventional systems, uplink and downlink data packets are often processed using a single, generalized processing path without considering a specific traffic origin or destination type. For example, data originating from the HGW and destined for the CPE behind it may be treated in a same manner as traffic sent directly between the CPE and the UPF. Such uniform handling may lead to a number of technical issues. For example, without accurately determining whether the traffic belongs to a gateway session or a direct CPE session, the UPF may associate packets with a wrong Packet Detection Rule (PDR) or session table entry. Also, downlink packets may be encapsulated in a wrong tunnel type, leading to routing errors and wasted processing overhead. Moreover, uplink and downlink flows for a same end-user device may not be correlated, preventing proper Quality- of-Service (QoS) enforcement or policy application. In addition, when decapsulation / encapsulation is performed unnecessarily or without optimization, packet handling times increase, directly impacting throughput and user experience.

[0031] Accordingly, there exists a need for a system and method that can overcome these limitations by providing differentiated and optimized processing of uplink and downlink data traffic in the FWA network, ensuring accurate session identification, appropriate encapsulation or decapsulation, and consistent policy application.OBJECTS OF THE PRESENT DISCLOSURE

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

[0033] An object of the present disclosure is to provide a system and method for processing both uplink and downlink data traffic in a Fixed Wireless Access (FWA) network by dynamically determining a type of traffic and applying a corresponding set of operative steps within a User Plane Function (UPF).

[0034] Another object of the present disclosure is to enable a UPF to accurately identify whether received data traffic corresponds to a Home Gateway (HGW) session or a direct Customer Premises Equipment (CPE) session by using Packet Detection Rules (PDR) and Packet Detection Information (PDI).

[0035] Yet another object of the present disclosure is to allow a UPF to decapsulate uplink data traffic from General Packet Radio Service (GPRS) Tunnelling Protocol (GTP) tunnels, detect Ethernet over Generic Routing Encapsulation (EoGRE) tunnels, and classify packets based on subscriber identity or CPE origin.

[0036] Another object of the present disclosure is to provide a mechanism for mapping relationships between CPE IP addresses, EoGRE tunnel IP addresses, and associated session identifiers to maintain accurate correlation between uplink and downlink flows.

[0037] Yet another object of the present disclosure is to ensure correct downlink encapsulation by dynamically selecting between EoGRE and GTP tunnels based on whether the traffic is destined for a HGW or a CPE, thereby reducing processing errors and unnecessary overhead.

[0038] Another object of the present disclosure is to enable a UPF to apply Quality of Service (QoS) and forwarding rules to uplink data traffic over an N6 interface using QoS Enforcement Rules (QER) and Forwarding Action Rules (FAR).

[0039] Another object of the present disclosure is to maintain session accuracy and improve resource utilization by referencing a session table that associates Media Access Control (MAC) addresses with active sessions for both uplink and downlink processing.

[0040] Another object of the present disclosure is to improve network efficiency and reduce latency by avoiding redundant encapsulation / decapsulation operations and by ensuring optimal packet forwarding paths in both uplink and downlink directions.SUMMARY

[0041] In an exemplary embodiment, a method for processing data traffic in a fixed wireless access network is described. The method includes receiving, by a User Plane Function (UPF), data traffic from one or more Home Gateways (HGWs) and a Customer Premises Equipment (CPE) over one or more network interfaces. The method includes determining, by the UPF, a type of the received data traffic by monitoring the reception of data traffic on at least one network interface. The type of the received data traffic includes an uplink data traffic or a downlink data traffic. The method includes processing, by the UPF, the received data traffic in accordance with the determined type of the received data traffic. The processing includes executing a set of operative steps for the uplink data traffic and a set of operative steps for the downlink data traffic.

[0042] In an embodiment, the one or more network interfaces include a N3 interface and aN6 interface.

[0043] In an embodiment, the set of operative steps for the uplink data traffic includes identifying, by the UPF, a first session associated with the CPE originating the uplink data traffic based on a Packet Detection Rule (PDR) configured at the UPF. The set of operative steps for the uplink data traffic includes decapsulating, by the UPF, the received uplink data traffic associated with the identified first session from a GTP (GPRS Tunnelling Protocol) tunnel to generate a decapsulated uplink data packet. The set of operative steps for the uplink datatraffic further includes determining, by the UPF, whether the decapsulated uplink data packets includes an EoGRE (Ethernet over Generic Routing Encapsulation) tunnel. The set of operative steps for the uplink data traffic further includes classifying, by the UPF, based on the determination, decapsulated uplink data packet as either an HGW packet or a CPE packet.

[0044] In an embodiment, if the packet is the HGW packet, further including: removing, by the UPF, the EoGRE tunnel encapsulation from the decapsulated uplink data packet; identifying, by the UPF, a second session corresponding to the HGW by matching a Packet Detection Information (PDI) based on a Media Access Control (MAC) address identifier with a source MAC address from the decapsulated uplink data packet within the EoGRE tunnel; maintaining, by the UPF, a mapping between a CPE internet protocol (IP) address to an EoGRE tunnel IP address corresponding to the second session; and maintaining, by the UPF, a mapping between the second session and the first session based on a CPE IP address corresponding to the second session.

[0045] In an embodiment, the method includes comparing, by the UPF, the PDR with a set of pre-configured rules stored in the CPE to identify the first session corresponding to the second session.

[0046] In an embodiment, the UPF maintains the source MAC address as the EoGRE tunnel IP against the second session in a session table.

[0047] In an embodiment, the method includes identifying the second session based on the source MAC address of the decapsulated uplink data packet in the EoGRE tunnel by referencing the session table stored by the CPE, which associates MAC addresses with active sessions.

[0048] In an embodiment, the method includes forwarding the processed uplink data traffic over the N6 interface by applying a set of traffic policies including quality-of-service (QoS) Enforcement Rule (QER) to the data traffic based on the flow mapping and forwarding action rules (FAR).

[0049] In an embodiment, the second set of operative steps for the downlink data traffic including: identifying, by the UPF, whether the downlink data traffic corresponds to a third session or a fourth session based on a Packet Detection Rule (PDR) applied to the received downlink data traffic; if the identified downlink data traffic corresponds to the third session, creating an EoGRE tunnel with a destination IP as a CPE internet protocol (IP) address and a source IP as the HGW IP address; if the identified downlink data traffic corresponds to the fourth session, creating a GTP (GPRS Tunnelling Protocol) tunnel with the destination IP as the CPE IP address and the source IP as the UPF IP address; encapsulating the downlink data traffic in the GTP tunnel or the EoGRE tunnel; and forwarding the encapsulated downlink data traffic to the destination based upon a session associated with the downlink data traffic.

[0050] In an embodiment, the method includes identifying the third session includes detecting a presence of the source MAC address in a Packet Detection Information (PDI) of the downlink data traffic.

[0051] In an embodiment, the fourth session is identified by determining that the PDR corresponds to the CPE IP address.

[0052] In an embodiment, the encapsulated downlink data traffic is forwarded to the at least one HGW via the CPE over a N3 interface when the third session is identified.

[0053] In an embodiment, the downlink data traffic corresponding to the fourth session is forwarded to the CPE via a network node using GTP tunnel encapsulation.

[0054] In an exemplary embodiment, a system for processing data traffic in a fixed wireless access network. The system includes a User Plane Function (UPF) configured to receive data traffic from one or more Home Gateways (HGWs) and a Customer Premises Equipment (CPE) over one or more network interfaces. The UPF is further configured to determine a type of the received data traffic bymonitoring the reception of data traffic on at least one network interface. The type of the received data traffic includes at least one of an uplink data traffic or a downlink data traffic. The UPF is further configured to process the received data traffic in accordance with the determined type of the received data traffic. The processing includes executing a set of operative steps for the uplink data traffic and a set of operative steps for the downlink data traffic.

[0055] In an embodiment, the one or more network interfaces include a N3 interface and aN6 interface.

[0056] In an embodiment, the UPF is configured to execute the set of operative steps for the uplink data traffic including: identify a first session associated with the CPE originating the uplink data traffic based on a Packet Detection Rule (PDR) configured at the UPF; decapsulate the received uplink data traffic associated with the identified first session from a GTP (GPRS Tunnelling Protocol) tunnel to generate a decapsulated uplink data packet; determine whether the decapsulated uplink data packet includes an EoGRE (Ethernet over Generic Routing Encapsulation) tunnel; and classify, based on the determination, decapsulated uplink data packet as either a subscriber entity traffic or a CPE packet.

[0057] In an embodiment, if the packet is the HGW packet, the UPF is configured to: remove the EoGRE tunnel encapsulation from the decapsulated uplink data packet; identify a second session corresponding to the HGW by matching a Packet Detection Information (PDI) based on a Media Access Control (MAC) address identifier with a source MAC address from the decapsulated uplink data packet within the EoGRE tunnel; maintain a mapping between a CPE internet protocol (IP) address to an EoGRE tunnel IP address corresponding to the second session; and maintain a mapping between the second session and the first session based on a CPE IP address corresponding to the second session.

[0058] In an embodiment, the UPF is configured to compare the PDR with a set of pre-configured rules stored in the CPE to identify the first session corresponding to the second session.

[0059] In an embodiment, the UPF is configured to maintain the source MAC address as the EoGRE tunnel IP against the second session in a session table.

[0060] In an embodiment, the UPF is configured to identify the second session based on the source MAC address of the decapsulated uplink data packet in the EoGRE tunnel by referencing the session table stored by the CPE, which associates MAC addresses with active sessions.

[0061] In an embodiment, the UPF is configured to process uplink data traffic over the N6 interface by applying a set of traffic policies including quality- of-service (QoS) Enforcement Rule (QER) to the data traffic based on the flow mapping and forwarding action rules (FAR).

[0062] In an embodiment, the UPF is configured to process the second set of operative steps: identify whether the downlink data traffic corresponds to a third session or a fourth session based on a Packet Detection Rule (PDR) applied to the received data traffic; if the identified downlink data traffic corresponds to the third session, create an EoGRE tunnel with a destination IP as the CPE IP address and a source IP as the HGW IP address; if the identified downlink data traffic corresponds to the fourth session, create a GTP (GPRS Tunnelling Protocol) tunnel with the destination IP as the CPE IP address and the source IP as the UPF IP address; encapsulate the downlink data traffic in the GTP tunnel or the EoGRE tunnel; and forward the encapsulated downlink data traffic to the destination based upon a session associated with the downlink data traffic.

[0063] In an embodiment, the UPF is configured to identify the third session by detecting a presence of the source MAC address in a Packet Detection Information (PDI) of the downlink data traffic.

[0064] In an embodiment, the UPF is configured to identify the fourth session by determining that the PDR corresponds to the CPE IP address.

[0065] In an embodiment, the UPF is configured to forward the encapsulated downlink data traffic to the HGW via the CPE over a N3 interface when the third session is identified.

[0066] In an embodiment, the UPF is configured to forward the downlink data traffic corresponding to the fourth session to the CPE via a network node using GTP tunnel encapsulation.

[0067] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for processing data traffic in a fixed wireless access network is described. The method includes receiving, by a User Plane Function (UPF), data traffic from one or more Home Gateways (HGWs) and a Customer Premises Equipment (CPE) over one or more network interfaces. The method includes determining, by the UPF, a type of the received data traffic by monitoring the reception of data traffic on at least one network interface. The type of the received data traffic includes at least one of an uplink data traffic or a downlink data traffic. The method includes processing, by the UPF, the received data traffic in accordance with the determined type of the received data traffic. The processing includes executing a set of operative steps for the uplink data traffic and a set of operative steps for the downlink data traffic.BRIEF DESCRIPTION OF DRAWINGS

[0068] 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 suchdrawings includes the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0069] FIG. 1 illustrates an exemplary network architecture for implementing a system for processing data traffic in a fixed wireless access network, in accordance with embodiments of the present disclosure.

[0070] FIG. 2A illustrates an exemplary system architecture for processing the data traffic in the fixed wireless access network, in accordance with embodiments of the present disclosure.

[0071] FIG. 2B illustrates an exemplary block diagram of the system for processing the data traffic in the fixed wireless access network, in accordance with embodiments of the present disclosure.

[0072] FIG. 3 illustrates a sequence diagram representing a process for processing the data traffic in the fixed wireless access network, in accordance with embodiments of the present disclosure.

[0073] FIG. 4 illustrates a flowchart of a method for processing the data traffic in the fixed wireless access network, in accordance with embodiments of the present disclosure.

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

[0075] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102-1, 102-2, 102-N - Users104-1, 104-2, 104-N - User Equipments (UEs)106 - Network108 - System200A - System Architecture212-1, 212-2 - One or more Home Gateways (HGWs)214 - Customer Premise Equipment (CPE)218 - User Plane Function (UPF)220 - Session Management Function (SMF)222 - Policy Control Function (PCF)226 - gNodeB228 - Internet200B - Block diagram202 - Processor(s)204 - Memory206 - Interface(s)208 - Processing engine210 - Other module (s)212 - Database300 - Sequence Diagram400 - Method Flowchart500 - Computer system510 - External storage device520 - Bus530 - Main memory540 - Read only memory550 - Mass storage device560 - Communication port(s)570 - ProcessorDETAILED DESCRIPTION OF DISCLOSURE

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

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

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

[0079] 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 afunction, its termination can correspond to a return of the function to the calling function or the main function.

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

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

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

[0083] The present disclosure relates to a system and a method for processing data traffic in a fixed wireless access network. Various embodiments throughout the disclosure will be explained in more detail with reference to FIGS. 1-5.

[0084] FIG. 1 illustrates an exemplary network architecture (100) for processing data traffic in the fixed wireless access network, in accordance with embodiments of the present disclosure.

[0085] Referring to FIG. 1, the network architecture (100) may include one or more computing devices or user equipment (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 equipment (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 equipment (104) are depicted in FIG. 1, however, any number of the user equipment (104) may be included without departing from the scope of the ongoing description. In an embodiment, each of the user equipment (104) may have a unique identifier attribute associated therewith. In an embodiment, the unique identifier attribute may be indicative of Mobile Station International Subscriber Directory Number (MSISDN), International Mobile Equipment Identity (IMEI) number, International Mobile Subscriber Identity (IMSI), Subscriber Permanent Identifier (SUPI) and the like.

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

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

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

[0089] 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. The FWA leverages a 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 the network (106) through a Customer Premises Equipment (CPE), which may be installed indoors (IDCPE) or outdoors (ODCPE).

[0090] Within the FWA deployments, one or more Home Gateways (HGWs) may be installed inside customer premises. A HGW serves as a 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 CPE to the network (106), aggregating traffic for processing by the core network functions, including the system (108).

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

[0092] FIG. 2A illustrates a system architecture (200A) for processing the data traffic in the fixed wireless access network, in accordance with embodiments of the present disclosure.

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

[0094] In an aspect, the HGW (212) represents an end-user device, such as a router or modem, within residential or commercial premises. The HGW (212) is an interface between the UE (104) and the network (106). The HGW (212) represents the end-user device within residential or commercial premises, such as arouter 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 an IP address to the HGW (212). 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 a 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).

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

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

[0097] The UPF (218) is responsible for anchoring a user plane by forwarding packets between the RAN and external data networks, enforcing traffic policies such as Quality of Service (QoS) and packet filtering, encapsulating and decapsulating GPRS Tunnelling Protocol-User Plane (GTP-U) packets over the N3 interface, and handling uplink and downlink routing in accordance with instructions from the SMF (220). In the present disclosure, the UPF (218) is enhanced to incorporate Broadband Network Gateway (BNG) functionality directly within the UPF (218), thereby eliminating the need for a separate BNG deployment. The enhanced UPF (218) further integrates a direct Dynamic Host Configuration Protocol (DHCP) server function, removing the reliance on an external DHCP server. The UPF (218) is configured to process both GTP payloads and Ethernet over Generic Routing Encapsulation (EoGRE) payloads in both uplink and downlink directions, and to dynamically classify traffic such as distinguishing between HGW sessions and direct CPE sessions through the use of Packet Detection Rules (PDR) and Packet Detection Information (PDI). Based on the detected traffic type and session mapping, the UPF (218) makes encapsulation and decapsulation decisions, selecting between the EoGRE and GTP as appropriate. On the N6 side, the UPF (218) applies QoS policies and Forwarding Action Rules(FAR) for uplink flows. The system (108) maintains uplink-downlink correlation by performing session mapping between CPE Internet Protocol (IP) addresses, EoGRE IP addresses, and Media Access Control (MAC) addresses. This configuration enables dynamic, real-time decision-making and packet processing for both uplink and downlink traffic without requiring re-establishment of sessions. The details of the enhanced UPF operation are explained in connection with FIG. 2B.

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

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

[0100] 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 senda request to the UPF (218), which then routes it to the internet (228), retrieving the necessary data and delivering it back to the UE (104).

[0101] FIG. 2B illustrates an exemplary block diagram (200B) of the system (108) for processing the data traffic in the fixed wireless access network, in accordance with embodiments of the present disclosure. FIG. 2B is explained in conjunction with FIG. 1 and FIG. 2A.

[0102] The system (108) is configured for supporting network equipments including the one or more HGWs (212-1, 212-2) connected via the CPE (214) and further includes the UPF (218), the SMF (220), and the PCF (222). The system (108) is adapted to receive, retrieve, and process encapsulated data packets associated with the HGWs (212), in accordance with a method and architecture that supports the integration of the BNG functionalities into the UPF (218).

[0103] It should be understood that the UPF (218) described herein and shown in the figures, such as FIG. 2A, is a physical hardware component. The UPF (218) may be implemented as a dedicated hardware appliance, a virtualized network function (VNF) running on a server, or a combination of hardware and software. In such implementations, the UPF (218) includes one or more processor(s) (202), a memory (204), an interface (206), a processing engine (208) and a database (212) to perform the functions described herein.

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

[0105] The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as RO 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 more components of the system (108). Examples of such components include, but are not limited to, the processing engine (208) and the database (212).

[0106] In an embodiment, the processing engine (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine (208). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine (208) may be processor-executable instructions stored on a non-transitory machine-readable storage medium, and the hardware for the processing engine (208) may 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 (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 (208) may be implemented by electronic circuitry. Among other capabilities, the processing engine (208) may be configured to fetch and execute computer-readable instructions stored in the memory (204) of the system (108).

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

[0108] In an embodiment, the processing engine (208) may further comprise other modules (210) to perform the functionalities of the UPF (218). The processing engine (208) is configured to execute functionalities of network entities, such as the UPF (218). The processing engine (208) enables the system (108) to perform the necessary operations associated with processing the data traffic in the fixed wireless access network.

[0109] In an embodiment, the processing engine (208) is configured to receive data traffic from the one or more HGWs (212) and the CPE (214) over one or more network interfaces. The one or more network interfaces include a N3 interface for traffic exchange with the fixed wireless access network and a N6 interface for traffic exchange with data network. The processing engine (208) is further configured to determine a type of the received data traffic by monitoring the reception of data traffic on at least one network interface. In an embodiment, the type of the received data traffic includes an uplink data traffic and a downlink data traffic. In an exemplary embodiment, the processing engine (208) may be configured to classify the data traffic as the uplink data traffic when the packets are received from the access network via the N3 interface, with a source address corresponding to the UE (104) or associated CPE (214) and a destination address corresponding to an external data network. Conversely, the processing engine (208) may be configured to classify the data traffic as the downlink data traffic when the packets are received from the data network via the N6 interface, with the source address corresponding to the external data network and the destination address corresponding to the UE (104) or CPE (214). In certain embodiments, the determination may involve inspecting protocol layer headers (e.g., IP, GTP-U) to identify bearer identifiers, quality of service (QoS) flow identifiers, or other control parameters that indicate an intended direction of the traffic. This classificationenables the processing engine (208) to selectively apply direction-specific processing, scheduling, and routing rules for uplink and downlink flows in real time.

[0110] The processing engine (208) is further configured to process the received data traffic in accordance with the determined type of the received data traffic. The processing includes executing a set of operative steps for the uplink data traffic and a set of operative steps for the downlink data traffic. In an embodiment, the set of operative steps for the uplink data traffic includes identifying a first session associated with the CPE (214) originating the uplink data traffic based on the PDR configured at the UPF (218). In an exemplary embodiment, the processing engine (208) may be configured to identify the first session associated with the CPE (214) originating the uplink traffic data by matching header parameters of the received packet against a pre-configured PDR stored in the UPF (218). The PDR may include matching fields such as a Tunnel Endpoint Identifier (TEID) in the GTP-U header, a source IP address, a destination IP address, and a Quality of Service (QoS) Flow Identifier, thereby enabling the UPF (218) to uniquely map the packet to a corresponding uplink session context.

[0111] Once the first session is identified, the processing engine (208) is configured to decapsulate the received uplink data traffic with the identified first session from the GTP tunnel to generate a decapsulated uplink data packet. In an exemplary embodiment, the processing engine (208) may be configured to decapsulate the received uplink data traffic by removing an outer GTP-U encapsulation header associated with the identified first session. The decapsulation process may involve stripping off the GTP-U, UDP, and IP headers to retrieve an original user payload, thereby generating the decapsulated uplink data packet.

[0112] The processing engine (208) is configured to determine whether the decapsulated uplink data packet includes the EoGRE tunnel. In an exemplary embodiment, the processing engine (208) may be configured to determine whetherthe decapsulated uplink data packet contains the EoGRE tunnel by inspecting a protocol type field in the Ethernet frame or by detecting a GRE header structure.

[0113] Based on the determination, the processing engine (208) classifies the decapsulated uplink data packet as either an HGW packet if a packet payload corresponds to an individual subscriber session, or as a CPE packet if the packet is encapsulated within the EoGRE tunnel representing aggregated subscriber traffic from the CPE (214).

[0114] In an embodiment, if the decapsulated uplink data packet is classified as the HGW packet, then the processing engine (208) is configured to remove the EoGRE tunnel encapsulation from the decapsulated uplink data packet. The processing engine (208) further identifies a second session corresponding to the HGW (212) by matching the PDI based on a Media Access Control (MAC) address identifier with a source MAC address from the decapsulated uplink data packet within the EoGRE tunnel. In an embodiment, the UPF (218) is configured to maintain the source MAC address as the EoGRE tunnel IP against the second session in a session table. The processing engine (208) is configured to identify the second session based on the source MAC address of the decapsulated uplink data packet in the EoGRE tunnel by referencing the session table stored by the CPE (214), which associates the MAC addresses with active sessions.

[0115] The processing engine (208) is further configured to maintain a mapping between a CPE internet protocol (IP) address to an EoGRE tunnel IP address corresponding to the second session. Further, the processing engine (208) is configured to maintain a mapping between the second session and the first session based on the CPE IP address corresponding to the second session. The processing engine (208) is configured to compare the PDR with a set of pre-configured rules stored in the CPE (214) to identify the first session corresponding to the second session.

[0116] Further, the processing engine (208) is configured to process the uplink data traffic over the N6 interface by applying a set of traffic policiesincluding quality-of-service (QoS) Enforcement Rule (QER) to the data traffic based on the flow mapping and forwarding action rules (FAR). In an embodiment, the processing engine (208) is configured to execute the set of operative steps for the downlink data traffic, where the processing engine (208) is configured to identify whether the downlink data traffic corresponds to a third session or a fourth session based on the PDR applied to the received data traffic. In an embodiment, the processing engine (208) is configured to identify the third session by detecting the presence of the source MAC address in the PDI of the downlink data traffic. In another embodiment, the processing engine (208) is configured to identify the fourth session by determining that the PDR corresponds to the CPE IP address.

[0117] In an embodiment, if the identified downlink data traffic corresponds to the third session, the processing engine (208) is configured to create the EoGRE tunnel with the destination IP as the CPE IP address and the source IP as the HGW IP address. In another embodiment, if the identified downlink data traffic corresponds to the fourth session, the processing engine (208) is configured to create the GTP tunnel with the destination IP as the CPE IP address and the source IP as the UPF IP address. The processing engine (208) is configured to encapsulate the downlink data traffic in the GTP tunnel or the EoGRE tunnel. Further, the processing engine (208) is configured to forward the encapsulated downlink data traffic to the destination based upon a session associated with the downlink data traffic. In an embodiment, the processing engine (208) is configured to forward the encapsulated downlink data traffic to the HGW (212) via the CPE (214) over a N3 interface when the third session is identified. In another embodiment, the processing engine (208) is configured to forward the downlink data traffic corresponding to the fourth session to the CPE (214) via a network node using GTP tunnel encapsulation.

[0118] FIG. 3 illustrates a sequence diagram (300) representing a process for processing the data traffic in the fixed wireless access network, in accordance with embodiments of the present disclosure.

[0119] At step (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 that Ethernet frames can traverse through different network segments seamlessly. The encapsulated DHCP message is then transmitted to the gNodeB (226), the 5G base station responsible for wireless communication with the UE (104). Within the gNodeB (226), the DHCP message may be further encapsulated within the GTP tunnel, facilitating its transport to the core network. The GTP tunnel carries the DHCP message to the UPF (218), where the GTP tunnel encapsulation is terminated, and the original DHCP message is extracted. The UPF (218) acts as the DHCP server and processes the DHCPv4 Discover or DHCPv6 Solicit message, initiating the subsequent steps of verifying, authorizing, and allocating an IP address to the HGW (212). This process ensures that the HGW (212) can be seamlessly integrated into the 5G network with proper IP address allocation, enabling it to connect to the internet (228) and other network resources.

[0120] 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 (218) may send a DHCPv4 NACK (Negative Acknowledgment) message indicating that the IP address request was denied, which can occur due to reasons such as UPF recovery or policy issues.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0138] Session Modification Request: If the HGW (212) is provisioned, theSMF (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.

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

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

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

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

[0143] Once the HGW (212) successfully obtains the IP address and its session is established with the UPF (218), the process proceeds to process user data traffic. This includes handling both uplink traffic (from the HGW (212) towards theinternet (228) or other external networks) and downlink traffic (from the internet (228) towards the HGW (212)).

[0144] In an uplink direction, when user data originates from the HGW (212), the Ethernet frames are encapsulated within the EoGRE tunnel and transmitted to the CPE (214). The CPE (214) forwards the encapsulated packets to the UPF (218) over the established N3 interface. The UPF (218) applies the Packet Detection Rules (PDRs) to identify the corresponding session, verifies the MAC address mapping between the HGW (212) and the associated CPE (214), and performs GTP decapsulation to retrieve the inner IP packet. For HGW-originated traffic, the UPF (218) removes the EoGRE header before forwarding the packet to the external data network via the N6 interface, as per the configured Forwarding Action Rules (FARs), Quality of Service Enforcement Rules (QERs), and Usage Reporting Rules (URRs).

[0145] In the downlink direction, when data packets are received from the external data network over the N6 interface, the UPF (218) applies the PDRs to identify whether the destination belongs to the HGW (212) or the CPE (214). For HGW-destined packets, the UPF (218) encapsulates the packets with an EoGRE header and then GTP encapsulation before sending them over the N3 interface towards the CPE (214). For CPE-only destinations, packets are sent directly with GTP encapsulation. This selective encapsulation ensures that HGW traffic maintains its Ethernet framing over the EoGRE tunnel, preserving layer-2 transparency, while still allowing efficient 5G transport for other traffic types.

[0146] FIG. 4 illustrates a flowchart of a method (400) for processing the data traffic in the fixed wireless access network, in accordance with embodiments of the present disclosure.

[0147] At step (402), the method (400) includes receiving, by the UPF (218), data traffic from the one or more HGWs (212) and the CPE (214) over the one or more network interfaces. The one or more network interfaces include a N3 interface and aN6 interface.

[0148] At step (404), the method (400) includes determining, by the UPF (218), the type of the received data traffic by monitoring the reception of data traffic on at least one network interface. The type of the received data traffic includes the uplink data traffic or the downlink data traffic.

[0149] At step (406), the method (400) includes processing, by the UPF (218), the received data traffic in accordance with the determined type of the received data traffic. The processing includes executing the set of operative steps for the uplink data traffic and a set of operative steps for the downlink data traffic. The set of operative steps for the uplink data traffic includes identifying, by the UPF (218), the first session associated with the CPE (214) originating the uplink data traffic based on the PDR configured at the UPF (218). The set of operative steps for the uplink data traffic further includes decapsulating, by the UPF (218), the received uplink data traffic associated with the identified first session from the GTP tunnel to generate the decapsulated uplink data packets. The set of operative steps for the uplink data traffic further includes determining, by the UPF (218), whether the decapsulated uplink data packets include the EoGRE tunnel. The set of operative steps for the uplink data traffic further includes classifying, by the UPF (218), based on the determination, decapsulated uplink data packet as either the HGW packet or the CPE packet. If the decapsulated uplink data packet is classified as the HGW packet, then the set of operative steps for the uplink data traffic includes removing, by the UPF (218), the EoGRE tunnel encapsulation from the decapsulated uplink data packet; identifying, by the UPF (218), a second session corresponding to the HGW (212) by matching the PDI based on the MAC address identifier with the source MAC address from the decapsulated uplink data packet within the EoGRE tunnel; maintaining, by the UPF (218), the mapping between the CPE internet protocol (IP) address to the EoGRE tunnel IP address corresponding to the second session; and maintaining, by the UPF (218), a mapping between the second session and the first session based on the CPE IP address corresponding to the second session.

[0150] This step further includes comparing, by the UPF (218), the PDR with the set of pre-configured rules stored in the CPE (214) to identify the first session corresponding to the second session. In an embodiment, the UPF (218) maintains the source MAC address as the EoGRE tunnel IP against the second session in the session table. This step further includes identifying the second session based on the source MAC address of the decapsulated uplink data packet in the EoGRE tunnel by referencing the session table stored by the CPE (214), which associates MAC addresses with active sessions.

[0151] In an embodiment, the method (400) includes forwarding the processed uplink data traffic over the N6 interface by applying the set of traffic policies including quality-of-service (QoS) Enforcement Rule (QER) to the data traffic based on the flow mapping and forwarding action rules (FAR).

[0152] The second set of operative steps for the downlink data traffic includes identifying, by the UPF (218), whether the downlink data traffic corresponds to the third session or the fourth session based on the PDR applied to the received downlink data traffic. The second set of operative steps for the downlink data traffic further includes if the identified downlink data traffic corresponds to the third session, the UPF (218) creates the EoGRE tunnel with the destination IP as the CPE internet protocol (IP) address and the source IP as the HGW IP address. The second set of operative steps for the downlink data traffic further includes if the identified downlink data traffic corresponds to the fourth session, the UPF (218) creates the GTP tunnel with the destination IP as the CPE IP address and the source IP as the UPF IP address. The second set of operative steps for the downlink data traffic further includes encapsulating the downlink data traffic in the GTP tunnel or the EoGRE tunnel. The second set of operative steps for the downlink data traffic further includes forwarding the encapsulated downlink data traffic to the destination based upon a session associated with the downlink data traffic.

[0153] In an embodiment, the method (400) includes identifying the third session includes detecting the presence of the source MAC address in the Packet Detection Information (PDI) of the downlink data traffic.

[0154] In an embodiment, the method (400) includes identifying the fourth session by determining that the PDR corresponds to the CPE IP address.

[0155] In an embodiment, the encapsulated downlink data traffic is forwarded to the at least one HGW (212) via the CPE (214) over the N3 interface when the third session is identified. In an embodiment, the downlink data traffic corresponding to the fourth session is forwarded to the CPE (214) via a network node using GTP tunnel encapsulation.

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

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

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

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

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

[0161] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for processing data traffic in a fixed wireless access network is described. The method includes receiving, by a User Plane Function (UPF), data traffic from one or more Home Gateways (HGWs) and a Customer Premises Equipment (CPE) over one or more network interfaces. Themethod includes determining, by the UPF, a type of the received data traffic by monitoring the reception of data traffic on at least one network interface. The type of the received data traffic includes at least one of an uplink data traffic or a downlink data traffic. The method includes processing, by the UPF, the received data traffic in accordance with the determined type of the received data traffic, wherein the processing comprises executing a set of operative steps for the uplink data traffic and a set of operative steps for the downlink data traffic.

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

[0163] The present disclosure provides a technical advancement in the management and optimization of uplink and downlink data handling for FWA sessions by introducing an intelligent session-type-aware traffic processing mechanism directly within a UPF. Unlike conventional approaches, where uplink and downlink flows are processed through fixed encapsulation and forwarding procedures irrespective of session type, the present disclosure integrates dynamic session identification, tunnel mapping, and QoS-based traffic handling within the UPF. This enables the UPF to autonomously distinguish between Home Gateway (HGW) sessions and direct Customer Premises Equipment (CPE) sessions, and accordingly adapt packet processing logic such as selective encapsulation / decapsulation, FAR / QER application, and uplink-downlink correlation in real time. By eliminating redundant encapsulation steps, avoiding unnecessary signalling exchanges with external functions, and performing simultaneous uplink and downlink optimization without requiring session reestablishment, the disclosure reduces processing latency, enhances throughput, andmaintains uninterrupted service continuity even under high-load and variable radio conditions. Furthermore, the disclosed mechanism improves spectral efficiency and resource utilization by aligning tunnel handling with actual service context and traffic patterns.ADVANTAGES OF THE PRESENT DISCLOSURE

[0164] The present disclosure provides a system and a method that enable adaptive management of uplink and downlink data transmission directly within a UPF, eliminating the need for separate control-plane signalling to configure data paths.

[0165] The present disclosure provides a system and a method that facilitate real-time dynamic path selection, bandwidth allocation, and Quality-of-Service (QoS)-based prioritization for both uplink and downlink directions, based on instantaneous traffic patterns, application demands, and radio link conditions.

[0166] The present disclosure provides a system and a method that ensure uninterrupted service continuity by enabling simultaneous uplink and downlink optimization decisions without requiring session re-establishment or user reregistration, thereby reducing latency and improving user experience.

[0167] The present disclosure provides a system and a method that optimize spectral efficiency and core network performance by avoiding unnecessary session signalling exchanges between network functions, reducing processing load and backhaul congestion.

[0168] The present disclosure provides a system and a method that enhance network adaptability in high-demand and variable radio conditions, ensuring consistent throughput, minimal packet loss, and improved fairness across multiple concurrent sessions.

Claims

CLAIMS1. A method (400) for processing data traffic in a fixed wireless access network, the method (400) comprising: receiving, by a User Plane Function (UPF) (218), data traffic from one or more Home Gateways (HGWs) (212) and a Customer Premises Equipment (CPE) (214) over one or more network interfaces; determining, by the UPF 218), a type of the received data traffic by monitoring the reception of data traffic on at least one network interface, wherein the type of the received data traffic includes an uplink data traffic or a downlink data traffic; and processing, by the UPF (218), the received data traffic in accordance with the determined type of the received data traffic, wherein the processing comprises executing a set of operative steps for the uplink data traffic and a set of operative steps for the downlink data traffic.

2. The method (400) as claimed in claim 1, wherein the one or more network interfaces include a N3 interface and aN6 interface.

3. The method (400) as claimed in claim 1, wherein the set of operative steps for the uplink data traffic comprising: identifying, by the UPF (218), a first session associated with the CPE (214) originating the uplink data traffic based on a Packet Detection Rule (PDR) configured at the UPF (218); decapsulating, by the UPF (218), the received uplink data traffic associated with the identified first session from a GTP (GPRS Tunnelling Protocol) tunnel to generate a decapsulated uplink data packets; determining, by the UPF (218), whether the decapsulated uplink data packets include an EoGRE (Ethernet over Generic Routing Encapsulation) tunnel; andclassifying, by the UPF (218), based on the determination, decapsulated uplink data packet as either an HGW packet or a CPE packet.

4. The method (400) as claimed in claim 3, if the packet is the HGW packet, further comprising removing, by the UPF (218), the EoGRE tunnel encapsulation from the decapsulated uplink data packet; identifying, by the UPF (218), a second session corresponding to the HGW (212) by matching a Packet Detection Information (PDI) based on a Media Access Control (MAC) address identifier with a source MAC address from the decapsulated uplink data packet within the EoGRE tunnel; maintaining, by the UPF (218), a mapping between a CPE internet protocol (IP) address to an EoGRE tunnel IP address corresponding to the second session; and maintaining, by the UPF (218), a mapping between the second session and the first session based on a CPE IP address corresponding to the second session.

5. The method (400) as claimed in claim 4, further comprising comparing, by the UPF (218), the PDR with a set of pre-configured rules stored in the CPE (214) to identify the first session corresponding to the second session.

6. The method (400) as claimed in claim 4, wherein the UPF (218) maintains the source MAC address as the EoGRE tunnel IP against the second session in a session table.

7. The method (400) as claimed in claim 6, further comprising identifying the second session based on the source MAC address of the decapsulated uplink data packet in the EoGRE tunnel by referencing the session table stored by the CPE (214), which associates MAC addresses with active sessions.

8. The method (400) as claimed in claim 2, further comprising forwarding the processed uplink data traffic over the N6 interface by applying a set of traffic policies including quality-of-service (QoS) Enforcement Rule (QER) to the data traffic based on the flow mapping and forwarding action rules (FAR).

9. The method (400) as claimed in claim 1, wherein the second set of operative steps for the downlink data traffic comprising: identifying, by the UPF (218), whether the downlink data traffic corresponds to a third session or a fourth session based on a Packet Detection Rule (PDR) applied to the received downlink data traffic; if the identified downlink data traffic corresponds to the third session, creating an EoGRE tunnel with a destination IP as a CPE internet protocol (IP) address and a source IP as the HGW IP address; if the identified downlink data traffic corresponds to the fourth session, creating a GTP (GPRS Tunnelling Protocol) tunnel with the destination IP as the CPE IP address and the source IP as the UPF IP address; encapsulating the downlink data traffic in the GTP tunnel or the EoGRE tunnel; and forwarding the encapsulated downlink data traffic to the destination based upon a session associated with the downlink data traffic.

10. The method (400) as claimed in claim 9, wherein identifying the third session includes detecting a presence of the source MAC address in a Packet Detection Information (PDI) of the downlink data traffic.

11. The method (400) as claimed in claim 9, wherein the fourth session is identified by determining that the PDR corresponds to the CPE IP address.

12. The method (400) as claimed in claim 9, wherein the encapsulated downlink data traffic is forwarded to the at least one HGW (212) via the CPE (214) over a N3 interface when the third session is identified.

13. The method (400) as claimed in claim 9, wherein the downlink data traffic corresponding to the fourth session is forwarded to the CPE (214) via a network node using GTP tunnel encapsulation.

14. A system (108) for processing data traffic in a fixed wireless access network, the system (108) comprising: a User Plane Function (UPF) (218) configured to: receive data traffic from one or more Home Gateways (HGWs) (212) and a Customer Premises Equipment (CPE) (214) over one or more network interfaces; determine a type of the received data traffic by monitoring the reception of data traffic on at least one network interface, wherein the type of the received data traffic includes at least one of an uplink data traffic or a downlink data traffic; and process the received data traffic in accordance with the determined type of the received data traffic, wherein the processing comprises executing a set of operative steps for the uplink data traffic and a set of operative steps for the downlink data traffic.

15. The system (108) as claimed in claim 14, wherein the one or more network interfaces include a N3 interface and aN6 interface.

16. The system (108) as claimed in claim 14, wherein the UPF (218) is configured to execute the set of operative steps for the uplink data traffic comprising: identify a first session associated with the CPE (214) originating the uplink data traffic based on a Packet Detection Rule (PDR) configured at the UPF (218);decapsulate the received uplink data traffic associated with the identified first session from a GTP (GPRS Tunnelling Protocol) tunnel to generate a decapsulated uplink data packet; determine whether the decapsulated uplink data packet includes an EoGRE (Ethernet over Generic Routing Encapsulation) tunnel; and classify, based on the determination, decapsulated uplink data packet as either a subscriber entity traffic or a CPE packet.

17. The system (108) as claimed in claim 16, if the packet is the HGW packet, the UPF (218) is configured to: remove the EoGRE tunnel encapsulation from the decapsulated uplink data packet; identify a second session corresponding to the HGW (212) by matching a Packet Detection Information (PDI) based on a Media Access Control (MAC) address identifier with a source MAC address from the decapsulated uplink data packet within the EoGRE tunnel; maintain a mapping between a CPE internet protocol (IP) address to an EoGRE tunnel IP address corresponding to the second session; and maintain a mapping between the second session and the first session based on a CPE IP address corresponding to the second session.

18. The system (108) as claimed in claim 17, the UPF (218) is configured to compare the PDR with a set of pre-configured rules stored in the CPE (214) to identify the first session corresponding to the second session.

19. The system (108) as claimed in claim 17, wherein the UPF (218) is configured to maintain the source MAC address as the EoGRE tunnel IP against the second session in a session table.

20. The system (108) as claimed in claim 19, the UPF (218) is configured to identify the second session based on the source MAC address of thedecapsulated uplink data packet in the EoGRE tunnel by referencing the session table stored by the CPE (214), which associates MAC addresses with active sessions.

21. The system (108) as claimed in claim 14, the UPF (218) is configured to process uplink data traffic over the N6 interface by applying a set of traffic policies including quality-of-service (QoS) Enforcement Rule (QER) to the data traffic based on the flow mapping and forwarding action rules (FAR).

22. The system (108) as claimed in claim 14, wherein the UPF (218) is configured to process the second set of operative steps: identify whether the downlink data traffic corresponds to a third session or a fourth session based on a Packet Detection Rule (PDR) applied to the received data traffic; if the identified downlink data traffic corresponds to the third session, create an EoGRE tunnel with a destination IP as the CPE IP address and a source IP as the HGW IP address; if the identified downlink data traffic corresponds to the fourth session, create a GTP (GPRS Tunnelling Protocol) tunnel with the destination IP as the CPE IP address and the source IP as the UPF IP address; encapsulate the downlink data traffic in the GTP tunnel or the EoGRE tunnel; and forward the encapsulated downlink data traffic to the destination based upon a session associated with the downlink data traffic.

23. The system (108) as claimed in claim 22, wherein the UPF (218) is configured to identify the third session by detecting a presence of the source MAC address in a Packet Detection Information (PDI) of the downlink data traffic.

24. The system (108) as claimed in claim 22, wherein the UPF (218) is configured to identify the fourth session by determining that the PDR corresponds to the CPE IP address.

25. The system (108) as claimed in claim 22, wherein the UPF (218) is configured to forward the encapsulated downlink data traffic to the HGW (212) via the CPE (214) over a N3 interface when the third session is identified.

26. The system (108) as claimed in claim 22, wherein the UPF (218) is configured to forward the downlink data traffic corresponding to the fourth session to the CPE (214) via a network node using GTP tunnel encapsulation.

27. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (400) for processing data traffic in a fixed wireless access network, the method (400) comprising: receiving, by a User Plane Function (UPF) (218), data traffic from one or more Home Gateways (HGWs) (212) and a Customer Premises Equipment (CPE) (214) over one or more network interfaces; determining, by the UPF (218), a type of the received data traffic by monitoring the reception of data traffic on at least one network interface, wherein the type of the received data traffic includes at least one of an uplink data traffic or a downlink data traffic; and processing, by the UPF (218), the received data traffic in accordance with the determined type of the received data traffic, wherein the processing comprises executing a set of operative steps for the uplink data traffic and a set of operative steps for the downlink data traffic.

Images