System and method for transmitting downlink data notification to customer premise equipment (CPE)

Abstract

A method (400) for transmitting downlink data to at least one second network element via a first network element is disclosed. The method (400) includes a User Plane Function (UPF) (232) receives downlink data intended for a second network element via a first network element. The UPF (232) assesses whether the first network element is in idle mode. If the idle mode is detected, the UPF (232) sends an identifier linked to the downlink data to a Session Management Function (SMF) (230). Upon receiving this identifier, the SMF (230) dispatches a Downlink Data Notification (DDN) concerning the downlink data to the Access and Mobility Management Function (AMF) (228). Initiate a network process to transition the first network element from the idle mode to an active mode. Once the first element is active, the UPF (232) forwards the downlink data to the second network element through the first network element.

Description

SYSTEM AND METHOD FOR TRANSMITTING DOWNLINK DATA NOTIFICATIONTO CUSTOMER PREMISE EQUIPMENT (CPE)RESERVATION OF RIGHTS

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

[0002] The present disclosure generally relates to the field of communication systems. More particularly, the present disclosure relates to a system and method for transmitting downlink data notification to a customer premise equipment (CPE) on receiving downlink data for a home gateway (HGW).DEFINITION

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

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

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

[0006] The term TP PDU session’ as used hereinafter in the specification, refers to an internet protocol (IP) protocol data unit (PDU) session. The IP PDU session is an establishment and management of data transmission using IP packets within a network environment.

[0007] The term ‘Downlink data’ as used hereinafter in the specification, refers to data that is transmitted from a network to a user device (e.g., user equipment). The downlink data represents the flow of information from the network to the user devices, supporting various services and applications essential for modem communication and internet access.

[0008] The term ‘SMF’ as used hereinafter in the specification, refers to Session Management Function. The SMF is responsible for managing the session setup, modification, and releasing procedures for user equipment (UE) accessing the network.

[0009] The term ‘UPF’ as used hereinafter in the specification, refers to User Plane Function. The UPF is responsible for handling and forwarding user data packets.

[0010] The term ‘AMF’ as used hereinafter in the specification, refers to Access and Mobility Management Function. The AMF is responsible for managing network access and mobility for user equipment (UE).

[0011] The term ‘AUSF’ as used hereinafter in the specification, refers to Authentication Server Function. The AUSF manages the authentication and key agreement process, which is crucial for verifying the identity of subscribers and establishing secure communication sessions.

[0012] The term ‘MDU as used hereinafter in the specification, refers to Multiple Dwelling Unit. The MDU is installed in residentials, or buildings and distributes optical fiber to the end users.

[0013] The term ‘PoE’ as used hereinafter in the specification, refers to Power over Ethernet, is a technology for implementing wired Ethernet local area networks (LANs) that enables the electrical current necessary for operating each device to be carried by Ethernet data cables instead of standard electrical power cords and wiring.

[0014] The term ‘PDR IDs’ as used hereinafter in the specification, refers to Packet Detection Rule Identifiers. The PDR IDs enable a user plane gateway (PGW-U in 4G and UPF in 5G) to identify each packet belongs to which application or service. The PGW-U and the UPF are the network elements that play a role in managing data traffic between the mobile devices (User Equipment or UE) and external packet data networks, such as the internet or private corporate networks.

[0015] The term ‘LAN interface’ as used hereinafter in the specification, refers to an interface that allows a computer or mobile device to connect to a local area network (LAN) using Ethernet as the transmission mechanism.

[0016] The term ‘PCF’ as used hereinafter in the specification, refers to policy control function. The PCF is responsible for managing and enforcing policy decisions related to network resources, quality of service (QoS), and access control.

[0017] The term ‘N4 session’ as used hereinafter in the specification, is a bridge between the control plane and the user plane in a network. N4 session management procedures are used to control the functionality of the UPF. The SMF can create, update, and remove the N4 session context in the UPF.

[0018] The term ‘N7 session’ as used hereinafter in the specification, refers to establishment and management of a communication session between the PCF and SMF. N7 session enables the PCF to exchange policy information, apply policy decisions based on real-time network conditions and subscriber profiles, and manage QoS parameters for data sessions.

[0019] The term ‘N40 session’ as used hereinafter in the specification, refers to the communication and interaction that occurs between the SMF and the CHF via the N40 interface. This session enables the SMF to coordinate with the CHF to set up and manage the quota management and charging, ensuring that data flows efficiently between UEs and external networks or services while maintaining Quality of Service (QoS) requirements.

[0020] The term ‘CHF’ as used hereinafter in the specification, refers to charging function. The CHF is responsible for handling charging and billing functions for subscriber services. The CHF supports service providers in implementing flexible billing models, enforcing charging policies, and maintaining transparency in subscriber billing and usage. The CHF is essential for operators to effectively monetize their services while providing customers with clear and reliable billing information.

[0021] The term ‘GTP tunnel’ as used hereinafter in the specification, refers to General packet radio service (GPRS) Tunneling Protocol tunnel. The GTP tunnel is alogical connection established between two endpoints in a mobile network to transmit user data or signaling messages.

[0022] The term ‘network-initiated service request’ as used hereinafter in the specification, refers to a procedure in a mobile network that occurs when the network, rather than the mobile device, triggers the procedure to establish or activate a connection for communication. This typically happens when the network needs to deliver data or initiate a service for a user, and the device is in an idle state. The term ‘idle mode’ as used hereinafter in the specification, refers to a state where the end device is connected to the network but is not actively transmitting or receiving data. Hence, the radio connection of the device is torn down.

[0023] The term ‘active mode’ as used hereinafter in the specification, refers to an operational state of end device when it is actively transmitting and / or receiving data, processing data, managing connections, and performing their designated tasks.

[0024] The term ‘5GCN’ as used hereinafter in the specification, refers to a fifth generation (5G) core network. The 5GCN provides connectivity and services to end-users (such as mobile devices and loT devices). It is designed to support higher data rates, lower latency, and massive connectivity compared to previous generations (e.g., 4G / LTE).

[0025] The term ‘EoGRE’ as used hereinafter in the specification, refers to Ethernet over Generic Routing Encapsulation. The EoGRE enables customer premises equipment (CPE) devices to bridge the Ethernet traffic from an end host and encapsulate the traffic in Ethernet packets over an IP GRE tunnel. The IP GRE tunnel terminates on a service provider broadband network gateway, which then terminates the end host traffic and manages the subscriber session for the end host.

[0026] The term ‘N1 message’ as used hereinafter in the specification, refers to a specific type of signaling message that is exchanged between the 5G UE and the AMF over the N 1 interface.

[0027] The term ‘N2 message’ as used hereinafter in the specification, refers to a specific type of signaling message that is exchanged between the 5G Access Network (5GAN) and the AMF over N2 interface.

[0028] The term ‘SRR’ as used hereinafter in the specification refers to Session Report Request. It refers to the N4 interface message where the UPF reports events for a PDU session to Session Management Function (SMF) for an established PDU session for the UE.

[0029] The term, ‘CPE IP PDU’ involves several interrelated components such as the CPE and the IP PDU. At the networking layer for the IP, the PDU is a packet. Together, these terms describe how data is encapsulated, transmitted, and managed as it moves from customer-based equipment across an IP network infrastructure.

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

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

[0032] The recent days setup involves a fifth generation (5G) core network supporting a customer premise equipment (CPE) and a home gateway (HGW) session.In a configuration, multiple HGWs are linked to the CPE through a multiple dwelling unit (MDU) using Power over Ethernet (PoE) cables. The setup implies that the MDU and the CPE receive power through the PoE connections from the HGWs.

[0033] Furthermore, the connectivity between the CPE and the multiple HGWs is not restricted to just the MDU. Other established technologies can be employed for this purpose, provided that the necessary Quality of Service (QoS) is maintained. The flexibility in connectivity options ensures that a robust and reliable network can be established while adhering to QoS requirements crucial for supporting 5G capabilities.

[0034] The process of establishing sessions in a 5G network for transmitting internet packet (IP) data units involves several steps. Initially, a parent CPE IP protocol data unit (PDU) session is configured to facilitate an IP data transmission for the CPE. The parent CPE IP PDU session supports multiple child Ethernet sessions for the HGWs.

[0035] Each child session is distinguished by different identifiers for packet detection rules (PDRs), all over a shared N4 session, which serves as the interface between the User Plane Function (UPF) and the Session Management Function (SMF). The sessions use an Ethernet over Generic Routing Encapsulation (EoGRE) tunnel between the CPE and the UPF to ensure a seamless data flow.

[0036] Additionally, the SMF establishes individual N7 and N40 sessions with a Policy Control Function (PCF) and a Charging Function (CHF). The sessions apply to both the parent CPE and each child HGW session to manage policy control and charging operations, ensuring comprehensive and efficient network functionality.

[0037] In mobile networks, the CPE enters an idle mode when there is no traffic for a certain period, which leads to the de-establishment of the General Packet Radio Service (GPRS) Tunneling Protocol (GTP) tunnel that connects the 5G radio network with the UPF. The GTP tunnel is necessary for forwarding data to the HGW. Whendownlink data destined for the HGW arrives during this idle period, a need arises to reestablish the GTP tunnel to ensure the data is correctly delivered.

[0038] Upon reception of downlink data, the UPF notifies the system using a specific Packet Detection Rule Identifier (PDR ID). The PDR Id is assigned to the HGW. The UPF then follows techniques, as per standards, to initiate a service request. The request marks the beginning of the re-establishment of the GTP tunnel, transitioning the CPE from idle to active mode.

[0039] In more complex scenarios, where the multiple HGWs are connected through a single CPE IP PDU session, each operating within the Ethernet session, network management becomes significantly more challenging. Each gateway requires correct identification and handling of corresponding respective data flows to prevent packet mix-ups and ensure accurate routing. This requires sophisticated coordination and management within the network infrastructure, employing advanced signaling procedures and state management techniques to manage the simultaneous data sessions effectively.

[0040] Such operations highlight the intricacies of transitioning the CPE from the idle mode to the active mode efficiently, a crucial task for maintaining seamless user experiences in high-demand network environments. Effective state transitions and resource allocations are pivotal to the network's capacity to dynamically adapt to traffic demands and ensure high-quality service delivery.

[0041] The techniques involve signaling across various network elements to ensure the previously idle CPE is activated and prepared to handle the incoming data traffic. The GTP tunnel is re-initiated, employing standard protocols that negotiate resources and allocate the necessary network pathways for data delivery to the HGW.

[0042] There is, therefore, a need in the art to provide a method and a system that can mitigate the disadvantages of the prior art.OBJECTIVE

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

[0044] An objective of the present disclosure is to transmit downlink data notification to a customer premise equipment (CPE) on receiving downlink data for a home gateway (HGW).

[0045] Another objective of the present disclosure is to notify a user plane function (UPF) about the packet detection rule (PDR) identifier (ID) of the CPE to a session management function (SMF) for downlink data by bringing the CPE from an idle mode to an active mode.

[0046] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.SUMMARY

[0047] In an exemplary embodiment, a method for transmitting downlink data to at least one second network element via a first network element is described. The method includes receiving, by a user plane function (UPF), the downlink data for the at least one second network element connected with the first network element. The method includes detecting, by the UPF, whether the first network element is in an idle mode. On detecting that the first network element is in the idle mode, the method includes sending, by the UPF, an identifier associated with the downlink data to a session management function (SMF). On receiving the identifier, the method includes sending, by the SMF, at least one downlink data notification (DDN) corresponding to the downlink data to an access and mobility management function (AMF) to initiate a network process to bring the first network element from the idle mode to an activemode. The method includes transmitting, by the UPF, the received downlink data to the at least one second network element via the first network element upon bringing the first network element to the active mode.

[0048] In an embodiment, the first network element is a customer premise equipment (CPE), and the at least one second network element is a user equipment (UE), a home gateway (HGW) or a multiple dwelling unit (MDU).

[0049] In an embodiment, the first network element is a customer premise equipment (CPE), and the at least one second network element is a user equipment (UE), a home gateway (HGW) or a multiple dwelling unit (MDU).

[0050] In an embodiment, the identifier is either a first network element packet detection rule (PDR) identifier or at least one second network element PDR identifier.

[0051] In an embodiment, the network process is performed over a session of the first network element, and where the first network element session is an internet protocol (IP) protocol data unit (PDU) session and each second network element session is an Ethernet session established as a child session of the first network element session.

[0052] In an embodiment, on receiving the first network element PDR identifier from the UPF, the network process includes performing, by the AMF, a network-initiated service activation to bring the first network element from the idle mode to the active mode and transmitting, by the UPF, the received downlink data to the at least one second network element via the first network element.

[0053] In an embodiment, on receiving the at least one second network element PDR identifier from the UPF, the network process includes mapping, by the SMF, the at least one second network element identifier to a first network element session corresponding to the first network element. The method includes sending, by the SMF,the at least one DDN to the AMF. The method performing, by the AMF, the network- initiated service activation to bring the first network element from the idle mode to the active mode and transmitting, by the UPF, the received downlink data to the at least one second network element via the first network element.

[0054] In an exemplary embodiment, a system for transmitting downlink data to at least one second network element via a first network element is disclosed. The system includes a user plane function (UPF) configured to receive the downlink data for the at least one second network element connected with the first network element. The system includes detecting whether the first network element is in an idle mode. The system includes sending an identifier associated with the downlink data to a session management function (SMF), on detecting the first network element is in the idle mode. On receiving the identifier from the UPF, the SMF is configured to send the at least one downlink data notification (DDN) to an access and mobility management function (AMF) to initiate a network process to bring the first network element from the idle mode to the active mode.

[0055] In an embodiment, the first network element is a customer premise equipment (CPE), and the at least one second network element is a user equipment (UE), home gateway (HGW), or a multiple dwelling unit (MDU).

[0056] In an embodiment, the identifier is either a first network element packet detection rule (PDR) identifier or at least one second network element PDR identifier.

[0057] In an embodiment, the first network element is associated with a first network element session and the at least one second network element is associated with at least one second network element session, and includes the first network element session is an internet protocol IPPDU session and each second network element session is an Ethernet session established as a child session of the first network element session.

[0058] In an embodiment, on receiving the first network element PDR identifier from the UPF, the network process includes perform, by the AMF, a network- initiated service activation to bring the first network element from the idle mode to the active mode and transmit, by the UPF, the received downlink data to the at least one second network element via the first network element.

[0059] In an embodiment, on receiving the at least one second network element PDR identifier from the UPF, the network process is configured to map, by the SMF, the at least one second network element identifier to a first network element session corresponding to the first network element. The network process is configured to send, by the SMF, the at least one DDN to the AMF. The network process is configured to perform, by the AMF, the network-initiated service activation to bring the first network element from the idle mode to the active mode and transmit, by the UPF, the received downlink data to the at least one second network element via the first network element.

[0060] In another exemplary embodiment, a computer program product includes a non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to perform a method for transmitting at least one downlink data notification to a plurality of network elements is disclosed. The method includes receiving, by a user plane function (UPF), the downlink data for the at least one second network element connected with the first network element. In addition, the method includes detecting, by the UPF, whether the first network element is in an idle mode. On detecting the first network element is in the idle mode, the method further includes sending, by the UPF, an identifier associated with the downlink data to a session management function (SMF). On receiving the identifier, the method also includes sending, by the SMF, at least one downlink data notification (DDN) to an access and mobility management function (AMF) to initiate a network process to bring the first network element from the idle mode to an active mode. The method includes transmitting, by the UPF, the received downlink data tothe at least one second network element via the first network element upon bringing the first network element to the active mode.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

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

[0062] FIG. 1 illustrates an exemplary network architecture for implementing a system for transmitting downlink data to at least one second network element via a first network element, in accordance with an embodiment of the present disclosure.

[0063] FIG. 2A illustrates an exemplary block diagram of the system, in accordance with an embodiment of the present disclosure.

[0064] FIG. 2B illustrates an exemplary system architecture of the system, in accordance with an embodiment of the present disclosure.

[0065] FIG. 3A illustrates an exemplary flow diagram of a method for transmitting at least one downlink data notification to a plurality of network elements, in accordance with an embodiment of the present disclosure.

[0066] FIG. 3B illustrates another exemplary flow diagram of the method, in accordance with an embodiment of the present disclosure.

[0067] FIG. 4 illustrates another exemplary flow diagram of the method, in accordance with an embodiment of the present disclosure.

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

[0069] 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 Plurality of Users104-1, 104-2... 104-N Plurality of User Equipments106 Network108 System200A Block Diagram202 Processor(s)204 Memory206 Interface(s)208 Processing Engine(s)210 Database200B System Architecture212 Home Gateway (HGW)214 Multiple Dwelling Unit (MDU)216 Customer Premise Equipment (CPE)218 Base Station220 Authentication Server Function (AUSF)222 Unified Data Management (UDM)224 Policy Control Function (PCF)226 Charging Function (CHF)228 Access Management and Mobility Function (AMF)230 Session Management Function (SMF)232 User Plane Function (UPF)234 Internet300A Flow Diagram300B Flow Diagram400 Flow Diagram500 Computer System510 External Storage Device520 Bus530 Main Memory540 Read-Only Memory550 Mass Storage Device560 Communication Ports570 ProcessorDETAILED DESCRIPTION

[0070] Embodiments herein relate to a method and system for transmitting downlink (DL) data to at least one second network element via a first network element. The present disclosure may address one or more problems encountered in a setup where multiple Home Gateway (HGW 212) Ethernet sessions operate behind a single Customer Premises Equipment (CPE) IP PDU session. In a situation where the CPE enters idle mode and DL data for the HGW 212 is received, there may be a challenge in bringing the CPE 216 back to an active state to deliver the DL data to the HGW 212. The situation leads to delays in data delivery, negatively impacting networkperformance and user experience. The disclosure describes solutions that overcome the drawbacks by enabling the automatic transition of the CPE 216 from the idle to an active mode when DL data intended for the HGW 212 is received. The present disclosure provides efficient data delivery, maintaining continuous data flow and reducing the need for manual intervention, thereby streamlining operations.

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

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

[0073] FIG. 1 illustrates an exemplary network architecture 100 for transmitting DL data to at least one second network element via a first network element, in accordance with an embodiment of the present disclosure. As illustrated in FIG. 1, the network architecture 100 may include one or more computing devices or User Equipment (UEs) 104-1, 104-2... 104-N associated with one or more users 102-1, 102- 2... 102-N in an environment. A person of ordinary skill in the art will understand that one or more users 102- 1 , 102-2... 102-N may 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 UEs 104-1, 104-2... 104-N may be individually referred to as the UE 104 and collectively referred to as the UEs 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 UEs 104 are depicted in FIG. 1, any number of the UEs 104 may be included without departing from the scope of the ongoing description.

[0074] In an embodiment, the UE 104 may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE 104 may include, but is not limited to, smartphones, smartwatches, smart sensors (e.g., a mechanical sensor, a thermal sensor, an electrical sensor, a magnetic sensor, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart televisions (TVs), computers, smart security systems, smart home systems, other devices for monitoring or interacting with or for the user 102 and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE 104 may include, but 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.

[0075] In an embodiment, the UE 104 may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smart phone, a phablet device, and so on), a wearable computer device (e.g., a head-mounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE 104 may include, but is not limited to, any electrical, electronic, electro-mechanical, or an equipment, or a combination of one or more of the above devices such as virtual reality (VR) devices, augmented reality (AR) devices, a laptop, a general-purpose computer, a desktop, a personal digital assistant, a tablet computer, a mainframe computer, or any other computing device. Further, the UE 104 may include one or more in-built or externally coupled accessories including, but not limited to, a visual aid device such as a camera, an audio aid, a microphone, a keyboard, and input devices for receiving input from the user 102 or an entity such as a touch pad, a touch enabled screen, an electronic pen, and the like. A person of ordinary skill in the art will appreciate that the UE 104 may not be restricted to the mentioned devices and various other devices may be used.

[0076] As will be appreciated, the customer premise equipment (CPE) (HGW) may correspond to a UE. Further, with each customer premise equipment (CPE), a set of HGW devices may be connected. A person of ordinary skill in the art will appreciate that the terms “CPE” and “UE” may be used interchangeably throughout the disclosure. As will be appreciated, the CPE is a network device that may be installed outdoors and indoors at customer locations to facilitate connectivity and network services. In an embodiment, examples of the CPE include a Fifth Generation (5G) or a Fourth Generation (4G) customer premise equipment which can provide a high throughput broadband connectivity to end users. The CPE can also have a functionality to connect to the 5GNon-Terrestrial Network (NTN). In this context the CPE is no more dedicated to a customer premises but the set of HGWs in individual customers premise (i.e., homes) connects to a single CPE using a Multiple Dwelling Unit (MDU). In that sense the CPE is shared across multiple homes and the CPE becomes a network element for a Fixed Wireless Access (FWA) deployment serving multiple subscribers. In an embodiment, the UE 104 may be deployed as the HGW connected to the CPE for use in the FWA environment. In an example, the UE 104 may be statically located at a fixed customer premises and connected to the core network via a wireless access network.

[0077] In FIG. 1 , the UE 104 may communicate with the system 108 through the network 106. In particular, the UE 104 may be communicatively coupled with the network 106. The coupling includes steps of receiving, by network 106, a connection request from UE 104. Upon receiving the connection request, the coupling includes steps of sending, by the network 106, an acknowledgment of the connection request to the UE 104. Further, the coupling includes steps of transmitting a plurality of signals in response to the connection request.

[0078] In an embodiment, the network 106 may include at least one of the 4G network, the 5G network, the 6G network, or the like. The network 106 may enable theUE 104 to communicate with other devices in the network architecture 100 and / or with the system 108. The network 106 may include a wireless card or some other transceiver connection to facilitate this communication. In another embodiment, the network 106 may be implemented as, or include any of a variety of different communication technologies such as a wide area network (WAN), a local area network (LAN), a wireless network, a mobile network, a Virtual Private Network (VPN), an internet, an intranet, a public network, a private network, a packet- switched network, a circuit- switched network, an ad hoc network, an infrastructure network, a Public-Switched Telephone Network (PSTN), a cable network, a cellular network, a satellite network, a fiber optic network, or some combination thereof. In another embodiment, the network 106 includes, by way of example but not limitation, at least a portion of one or more networks having one or more nodes that transmit, receive, forward, generate, buffer, store, route, switch, process, or a combination thereof, etc. one or more messages, packets, signals, voltage or current levels, some combination thereof, or so forth.

[0079] In another exemplary embodiment, the network architecture 100 may include a centralized server (not shown) may include or comprise, by way of example but not limitation, one or more of a stand-alone server, a server blade, a server rack, a bank of servers, a server farm, a hardware supporting a part of a cloud service or a system, a home server, a hardware running a virtualized server, one or more processors executing code to function as a server, one or more machines performing server-side functionality as described herein, at least a portion of any of the above, some combination thereof.

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

[0081] FIG. 2A illustrates an exemplary block diagram 200A of the system 108 configured for transmitting DL data to at least one second network element via the first network element, in accordance with an embodiment of the disclosure. FIG. 2A is explained in conjunction with FIG. 1. In an embodiment, the network may be, for example, the 4G network, the 5G network, the 6G network, and the like.

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

[0083] In an embodiment, the system 108 may include an interface(s) 206. The interface(s) 206 may include a variety of interfaces, for example, interfaces for data input and output devices (VO), storage devices, and the like. The interface(s) 206 may facilitate communication through the system 108. The interface(s) 206 may also provide a communication pathway for one or more components of the system 108. Examples of such components include, but are not limited to, a processing engine 208 and a database 210.

[0084] 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 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 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 and the processing resource. In other examples, the processing engine 208 may be implemented by electronic circuitry.

[0085] In an embodiment, the database 210 may store data that may be generated as a result of functionalities implemented by any of the components of the processor 202 or the processing engine 208. In an embodiment, the database 210 may be indicative of including, but not limited to, a relational database, a distributed database, a cloud-based database, or the like. In an exemplary embodiment, the processing engine 208 may include one or more units having functions that may include, but are not limited to, testing, storage, and peripheral functions, such as a wireless communication unit for remote operation, and the like.

[0086] In an embodiment, the processing engine 208 is configured to transmit at least one DL data notification to the plurality of network elements. The processing engine 208 includes a user plane function (UPF) 232. In the network, the UPF 232 may receive DL data for at least one second network element. In an example, the atleast one second network element is connected with a first network element. In some embodiments, the first network element may be the CPE 216, and the at least one second network element may be the HGW 212.

[0087] The UPF 232 may detect whether the first network element is in an idle mode, or an active mode based on a general packet radio service (GPRS) Tunnelling Protocol (GTP) tunnel availability with the radio network for the first network element. In an aspect, by monitoring the transmission of data between the network and the first network element, the UPF 232 may detect the idle mode or the active mode of the first network element. The UPF 232 may send an identifier to a session management function (SMF 230), on detecting the first network element is in the idle mode. In some embodiments, the identifier may be either a first network element identifier or at least one second network element identifier. The identifier includes a packet detection rule (PDR) identifier (ID).

[0088] On receiving the identifier from the UPF 232, the SMF 230 may initiate a network process to bring the first network element from the idle mode to the active mode and send the at least one downlink data notification (DDN) to an access and mobility management function (AMF 228).

[0089] In some embodiments, a plurality of second network element sessions corresponding to a plurality of second network elements is created using a plurality of PDR / second network element identifiers over a first network element session. The first network element session may be an internet protocol (IP) PDU session.

[0090] In some embodiments, on receiving the first network element identifier from the UPF 232 to SMF 230 and then further the DDN message sent to AMF 228, the AMF 228 may perform a network-initiated service activation on receiving the at least one DE data notification. The UPF 232 may transmit the received DL data to the at least one second network element via the first network element.

[0091] In some embodiments, on receiving the at least one second network element identifier from the UPF 232, the SMF 230 may map the at least one second network element identifier with the plurality of second network element identifiers corresponding to the first network element session. The SMF 230 may send the at least one DDN to the AMF 228. The DDN is a signal used in mobile networks to alert network elements, such as the AMF 228, that DL data needs to be delivered to a device. The DDN prompts the network to activate the relevant elements from the idle to the active mode to facilitate data transmission. The AMF 228 may perform the network- initiated service activation on receiving the at least one DL data notification. The UPF 232 may transmit the received DL data to the at least one second network element via the first network element. The process for transmitting DL data to at least one second network element via the first network element is described in subsequent figures in more detail.

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

[0093] FIG. 2B illustrates an exemplary system architecture 200B of the system 108, in accordance with an embodiment of the present disclosure.

[0094] The system architecture 200B may include a plurality of HGW 212s (212-1, 212-2, 212-3, ,212-N), a multiple dwelling unit (MDU) 214, the CPE 216, a base station 218, and a plurality of network functions. The plurality of network functions may include an authentication server function (AUSF) 220, a unified data management (UDM) 222, a policy control function (PCF) 224, a charging function (CHF) 226, the AMF 228 228, the SMF 230, and the UPF 232. The AMF 228 and theUPF 232 network functions may be connected to the base station 218 to which the first network element (CPE) connects over the radio interface. Further, the UE connects to the network 234 through the UPF 232.

[0095] The plurality of the HGW 212s (212-1, 212-2, 212-3,.. 212-N) is connected to the CPE 216 via the MDU 214. The connection between the plurality of HGW 212s (212-1, 212-2, 212-3,... , 212-N) and the CPE 216 via the MDU 214 may be established using, for example, Power over Ethernet (PoE) cables. In an aspect, the PoE cables may be Ethernet cables that carry both data and electrical power, allowing devices (e.g., wireless access points) to receive power and data over the cable connection. The PoE connection may ensure that both the MDU 214 and the CPE 216 may draw power from the HGW 212 connected to their LAN interfaces.

[0096] In an embodiment, the system architecture 200 may also include components such as the AUSF 220, the UDM 222, and the AMF 228. The AUSF 220 is connected to both the UDM 222 and the AMF 228, handling authentication processes to ensure secure network access. The UDM 222 may manage subscriber data and profiles, facilitating user authentication and session management. The AMF 228 may interact with the UDM 222 to retrieve user subscription information and with the AUSF 220 for user authentication. The AMF 228 may be connected to the 5G CN 218 and the SMF 230. The AMF 228 may oversee access and mobility functions, ensuring connectivity for mobile devices 104.

[0097] In an embodiment, the CPE IP PDU session is created for the CPE 216 in the network 106. The CPE 216 is communicatively coupled with the plurality of HGW 212 (212-1, 212-2, 212-3,.., 212-N) creating a plurality of CPE IP PDU sessions. Each CPE IP PDU session may have a unique PDR ID. The PDR IDs of the plurality of the HGW 212s (212-1, 212-2, 212-3,.. 212-N) are used to identify the HGW 212 intended for DL data transmission. Over the CPE IP PDU session, the plurality of the HGW 212 sessions (e.g., ethernet sessions of home gateway) corresponding to theHGW 212 (212-1, 212-2, 212-3,... ,212-N) is established using the PDR IDs of the HGW 212 (212-1, 212-2, 212-3,..,212-N) using an ethernet over generic routing encapsulation (EoGRE) tunnel between the CPE 216 and the UPF 232. The SMF 230 creates distinct N7 and N40 sessions with PCF 224 and the CHF 226 for the CPE IP PDU session and each of the HGW 212 sessions. In one example, a N7 session is used to exchange signaling messages related to call control, network management, and supplementary services. In some examples, N40 session is used for interactions between the SMF 230 and the CHF 226 to enable online and offline charging.

[0098] In one aspect, the ethernet sessions of the HGW 212s are the ethernet connections between the CPE 216 and the network. The HGW 212 establishes ethernet connections with the UPF 232 in the network. Once the ethernet session is established, the ethernet session facilitates the transmission of data (e.g., uplink data, DL data) between the HGW 212 and the network. The uplink data is data sent from the HGW 212 to the network. The DL data is data received by the HGW 212 from the network. The ethernet sessions of the HGW 212s within the CPE IP PDU session enable efficient connectivity and data delivery in the network.

[0099] In an aspect, the EoGRE tunnel encapsulates data packets, allowing the encapsulated data packets to be transmitted over the network. The EoGRE tunnel encapsulates the data packets, including their headers and payloads. The encapsulation process adds a header to the data packet, preserving the original data packet intact. Once the data packets are encapsulated, these packets can be transmitted over the network (e.g., internet or private IP networks). The EoGRE tunnel is used for providing connectivity between geographically dispersed the Ethernet networks or the devices.

[0100] In one aspect, the PCF 224 enforces policies to determine which user equipment has access to the network resources within the CPE IP PDU session. For example, when receiving a request from the user equipment for receiving IP address, the PCF 224 determines the user's access authorization based on policies.

[0101] In the present disclosure, the processing engine 208 may be configured for the DL data transmission by managing the transition of network 106 elements from the idle mode to the active mode. The first network element, such as the CPE 216, operates within the IP PDU session. The processing engine 208 includes components like the UPF 232, which receives DL data destined for the second network element, such as UE 104 or HGW 212. The UPF 232 determines if the first network element is idle, and if so, sends the PDR identifier to the SMF 230. The SMF 230 issues the DDN to the AMF 228, activating the first network element from the idle mode to the active mode. The activation allows the UPF 232 to transmit the DL data.

[0102] The PDR Identifiers in the system 108 can be either from the first network element or one or more second network elements, used for managing session information and facilitating the idle mode to the active mode transitions. The system 108 operates with session hierarchies, with each second network element having Ethernet sessions as child sessions to the first network element's IP PDU session. The network process relies on the PDR identifiers to activate the appropriate network elements for the data transmission. Upon receiving the first network element PDR identifier, the AMF 228 performs a network- initiated service activation, enabling seamless data delivery from the UPF 232 to the second network element through the first network element once activated. The system 108 may support data handling, conserving resources by keeping network elements idle when not in use and activating them when data transfer is necessary.

[0103] In an example, a suburban neighborhood equipped with a telecommunications network, the system architecture 200B, as shown in FIG. 2B, may be used for managing data transmission. The user may be in the neighborhood starts streaming video on a smartphone, which is connected through to the CPE 216 via HGW 212. The UPF 232 receives the video data intended for the user smartphone. Upon detection that the CPE 216 is in the idle mode, the UPF 232 sends the PDR identifier1 to the SMF 230. The SMF 230, using PDR identifier, sends the DDN to the AMF 228. The AMF 228 then triggers a network process to activate the CPE 216 from the idle to the active mode. Once activated, the UPF 232 can transmit the DL data through the CPE 216 to the smartphone of the user via HGW 212, ensuring seamless streaming. The system architecture 200B employs PoE connections, allowing the CPE 216 and the MDU 214 device to draw both power and data from the network 106. Ethernet sessions, coupled with the EoGRE tunnels, facilitate efficient data encapsulation and transmission across the network. The policies enforced by the PCF regulate access to network resources, ensuring authorized usage. Throughout the process, the system 108 maintains efficient resource management by keeping elements in the idle mode when inactive and activating them as needed. This balance of energy conservation and data delivery enhances UE 104 and optimizes network performance, illustrating a sophisticated method of handling dynamic data requirements in real-time scenarios.

[0104] FIG. 3 A illustrates an exemplary flow diagram 300A of a method for transmitting at least one DL data notification to the plurality of network elements, in accordance with an embodiment of the present disclosure.

[0105] As illustrated in FIG. 3A, at step 302, the CPE IP PDU session is established between the CPE 216 and the plurality of network functions such as the AMF 228, the UPF 232, the SMF 230, the PCF 224, and other 5G core network (5GCN) elements 236.

[0106] In an aspect, the establishment of the CPE IP PDU session may include the following steps:

[0107] Authenticating the CPE 216 with the 5G network core and establishing secure connections between the CPE 216 with the 5G network core.

[0108] Establishing IP PDU sessions between the CPE and the 5G core network.

[0109] At step 304, the EoGRE tunnel is established between the CPE 216 and the UPF 232. The EoGRE enables the CPE devices to bridge Ethernet traffic coming from the second network element (i.e. the HGW 212) and encapsulate the traffic in ethernet packets over an IP GRE tunnel. In an aspect, the EoGRE tunnel is established between the CPE 216 and the UPF 232 to encapsulate the data coming from the UPF 232.

[0110] At step 306 an IP address assignment request is sent by the HGW 212, to the UPF 232. In an aspect, the IP address assignment request refers to a request for allocating IP addresses to devices on the network so that devices can communicate with each other and with other networks over the internet. In an embodiment, the HGW 212 sends the IP address assignment request to the UPF 232 for the IP address assignment.

[0111] At step 308, a session report request and the HGW 212 identifier (ID) are sent by the UPF 232 to the SMF 230.

[0112] At step 310, a session management (SM) policy association establishment request, the HGW 212 ID and the CPE ID may be sent to the PCF 224 by the SMF 230. The SM policy association establishment request may refer to a request for either establishing a new policy association or modifying an existing one based on the session requirements.

[0113] At step 312, the HGW 212 is authorized by the PCF 224 for services. In an aspect, on receiving the SM policy association establishment request, the HGW 212 ID and the CPE ID, the PCF 224 may establish a SM policy association with the SMF 230. Then, the PCF 224 may authorize the HGW 212 to provide the services.

[0114] At step 314, the PCF 224 sends a SM policy association establishment response to the SMF 230. After SM policy association establishment, the PCF 224 may send the SM policy association establishment response to the SMF 230.

[0115] At step 316, a session report response is sent by the SMF 230, to the UPF 232. After receiving the SM policy association establishment response from the PCF 224, the SMF 230 may send the session report response for the received session report request to the UPF 232. The session report response may include session identifiers, session status, session events, etc. The session status may provide information, but is not limited to, corresponding to the current status of the session, such as active, idle, or undergoing specific operations (e.g., session establishment, modification, termination). The session events may be session establishment, modification, re-authentication, handovers, or session release, etc.

[0116] At step 318, a session modification procedure is performed between the UPF 232 and the SMF 230. In an aspect, the session modification procedure between the UPF 232 and the SMF 230 involves updating or modifying existing session parameters to accommodate changes in Quality of Service (QoS), user requirements, or network conditions specifically for the second network element i.e. HGW 212 session.

[0117] The session modification procedure may include the steps:

[0118] The SMF 230 initiates a session modification request to the UPF 232. The SMF 230 transfers relevant session context information (e.g., bearer context, QoS profiles, QoS Enforcement Rules (QERs), Packet Detection Rules (PDRs), and Usage Reporting Rules (URRs) to the UPF 232 to facilitate the modification process specific to the second network element.

[0119] The UPF 232 evaluates the session modification request and sends a session modification response to the SMF 230, confirming the acceptance and implementation of the requested changes, completing the session modification procedure.

[0120] At step 320, an IP address assignment response is sent by the UPF 232 to the HGW 212. After performing the session modification procedure, the UPF 232 may send the IP address assignment response to the HGW 212.

[0121] At step 322, the HGW 212 ethernet session is established between the CPE 216 and the 5G core network (CN). After assigning the IP address, the HGW 212 ethernet session is established between the HGW 212 and the 5GCN 236.

[0122] At step 324, the CPE 216 may go to the idle mode. If there is no traffic for a defined duration, the radio network brings the CPE 216 in idle mode and the underlying GTP tunnel for the CPE 216 between the radio network and the UPF 232 is removed. The defined duration may be configured according to the network traffic conditions.

[0123] At step 326, the UPF 232 may receive DL (DL) data for the HGW 212. When the CPE 216 goes to the idle mode, the UPF 232 may receive DL (DL) data for the HGW 212.

[0124] At step 328, the UPF 232 may send CPE PDR ID to the SMF 230 through a Session Report Request (SRR). The SRR refers to a signaling procedure used to establish or modify resources for a communication session between the UE 104 and the network 106. On receiving the DL data for the HGW 212 and if the CPE 216 goes to the idle mode, the UPF 232 sends PDR ID of the CPE 216 to the SMF 230.

[0125] At step 330, the SMF 230 may send a session initiation message (e.g., N1N2 message) to the AMF 228. On receiving the PDR ID of the CPE 216 from the UPF 232, the SMF 230 may send the session initiation message to the AMF 228. The session initiation message may include N1N2 message.

[0126] At step 332, a network- initiated service request procedure is performed for the CPE 216. The network-initiated service request in a mobile network occurswhen the network, rather than the mobile device, triggers a procedure to establish or activate a connection for communication. The network-initiated service request is generated when the network is configured to deliver data or initiate a service for a user, and the CPE 216 is in the idle state. On receiving the session initiation message (e.g., N1N2 message), the AMF 228 performs a network-initiated service request procedure for the CPE 216. Subsequently, the CPE 216 comes into active mode and the GTP tunnel between a Radio Access Network (RAN) network and the UPF 232 is reestablished. The RAN is used as a part of the cellular network infrastructure that connects user devices, such as smartphones and tablets, to the core network, allowing data transmission and communication

[0127] At step 334, the UPF 232 may send DL data to the HGW 212. After performing the network-initiated service request procedure, the session is established between the AMF 228, the HGW 212 and the CPE 216. Then, the UPF 232 forwards the received DL data to the HGW 212.

[0128] FIG. 3B illustrates another exemplary flow diagram 300B of the method, in accordance with an embodiment of the present disclosure.

[0129] As illustrated in FIG. 3B, at step 342, a CPE IP PDU session is established between the ODPCE 216 and the plurality of network functions such as the AMF 228, the UPF 232, the SMF 230, the PCF 224, and the other 5GCN 236.

[0130] At step 344, the EoGRE tunnel is established between the CPE 216 and the UPF 232. In an embodiment, the EoGRE tunnel is established between the CPE 216 and the UPF 232 to encapsulate the data between the CPE 216 and the UPF 232.

[0131] At step 346, an IP address assignment request is sent by the HGW 212 to the UPF 232. In an aspect, IP address assignment request refers to a request for allocating IP addresses to devices on the network so that devices can communicate witheach other and with other networks. In an embodiment, the HGW 212 sends the IP address assignment request to the UPF 232 for the IP address assignment.

[0132] At step 348, a session report request and the HGW 212 ID is sent by the UPF 232 to the SMF 230.

[0133] At step 350, a session management (SM) policy association establishment request, the HGW 212 ID and the CPE ID may be sent by the SMF 230 to the PCF 224. The SM policy association establishment request may refer to a request for either establishing a new policy association or modifying an existing one based on the session requirements.

[0134] At step 352, the HGW 212 is authorized by the PCF 224 for services. In an aspect, on receiving the SM policy association establishment request, the HGW 212 ID and the CPE ID, the PCF 224 may establish SM policy association with the SMF 230. Then, the PCF 224 may authorize the HGW 212 for the services.

[0135] At step 354, a SM policy association establishment response is sent by the PCF 224 to the SMF 230. After SM policy association establishment, the PCF 224 may send the SM policy association establishment response to the SMF 230.

[0136] At step 356, a session report response is sent by the SMF 230 to the UPF 232. After receiving the SM policy association establishment response from the PCF 224, the SMF 230 may send the session report response for the received session report request to the UPF 232. The session report response may include session identifiers, session status, session events, etc. The session status may provide information, but not limited to, corresponding to current status of session such as active, idle, or undergoing specific operations (e.g., session establishment, modification, or termination). The session events may be session establishment, modification, re-authentication, handovers, or session release, etc.

[0137] At step 358, a session modification procedure is performed between the UPF 232 and the SMF 230. In an aspect, the session modification procedure between the UPF 232 and the SMF 230 involves updating or modifying existing session parameters to accommodate changes in Quality of Service (QoS), user requirements, or network conditions, PDRs, QERs, URRs specific for the second network element’s (HGW 212) session.

[0138] At step 360, an IP address assignment response is sent by the UPF 232, to the HGW 212. After performing the session modification procedure, the UPF 232 may send the IP address assignment response to the HGW 212.

[0139] At step 362, the HGW 212 ethernet session is established between the HGW 212 and the 5GCN in the network. After assigning IP address, the HGW 212 ethernet session is established between the HGW 212 and the other 5GCN 236 in the network.

[0140] At step 364, the CPE 216 may go to the idle mode. If there is no traffic for a specified duration, the radio network brings the CPE 216 in idle mode and the underlying GTP tunnel for the CPE 216 between the radio network and the UPF 232 is removed. The specified duration is configured according to the network traffic conditions.

[0141] At step 366, the UPF 232 may receive DL (DL) data for the HGW 212. When the CPE 216 goes to the idle mode, the UPF 232 may receive DL (DL) data for the HGW 212.

[0142] At step 368, the UPF 232 may send the HGW 212 PDR ID to the SMF 230 through the SRR On receiving the DL data for the HGW 212 and if the CPE 216 is in the idle mode, the UPF 232 sends PDR ID of the HGW 212 to the SMF 230.

[0143] At step 370, the SMF 230 may perform mapping of the HGW 212 PDR ID to the CPE 216 session towards the AMF 228. The SMF 230 maps the PDR IDs configured in the HGW 212 to specific parameters and requirements of the CPE 216 session towards the AMF 228.

[0144] At step 372, the SMF 230 may send a session initiation message (e.g., N1N2 message) to the AMF 228. On receiving the PDR ID of the HGW 212 from the UPF 232, the SMF 230 may send a session initiation message to the AMF 228 for the CPE 216 session. The session initiation message includes N1N2 message.

[0145] At step 374, a network- initiated service request procedure is performed between the CPE 216 and the 5G core network. On receiving the session initiation message (e.g., N1N2 message), the AMF 228 performs a network-initiated service request procedure for the CPE 216. This procedure brings the CPE 216 into active mode and the GTP tunnel for the CPE 216 session between the radio network and UPF 232 is re-established.

[0146] At step 376, the UPF 232 may send DL data to the HGW 212. After performing the network-initiated service request procedure, the session is established between the AMF 228 and 5G core, the HGW 212 and the CPE 216. Then, the UPF 232 sends the received DL data to the HGW 212.

[0147] In FIG. 3B, the UPF 232 directly notifies the SMF 230 with the PDR ID to the CPE 216. This allows the SMF 230 to straightforwardly trigger the network procedures necessary to bring the CPE 216 from an idle to an active state, directly targeting the CPE 216 based on the provided PDR ID. In FIG. 3B, the UPF 232 sends the PDR ID related to the HGW 212 instead. In response, the SMF 230 must map this HGW PDR ID to the CPE 216 session, interpreting that the data intended for the HGW 212 relates to the CPE 216 session. Once this mapping is completed, the SMF 230 initiates the procedures to activate the CPE 216 from the idle mode. The distinctionlies in the source of the PDRID, one being directly associated with the CPE 216, while the other requires interpretation and mapping from a related component like the HGW 212bbefore proceeding with the CPE 216 activation. FIG. 4 illustrates an exemplary flow diagram of a method 400 for transmitting at least one DL data notification to the plurality of network elements (i.e., the network 106), in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIG. 1, FIG. 2A, FIG. 2B, FIG. 3A and FIG. 3B. Each step of the method 400 may be performed by various units present within the processing engine 208 of the system 108.

[0148] At step 402, the method 400 may include receiving, by the UPF 232, the DL data for the at least one second network element connected with the first network element. In some embodiments, the first network element is the CPE 216. The at least one second network element is the UE 104, the HGW 212 or the MDU 214. In an aspect, for receiving of the DL data by the UPF 232, the CPE 216 session between the customer premises equipment (CPE), which includes the HGW 212, and the network is established. The UE 104 within the customer premises (e.g., the UE 104 connected to one of the HGW 212) sends a request for service (e.g., streaming media, web browsing) to the internet via one of applications running on the user equipment. The request is transmitted via the HGW 212 to the server of the service provider. The request travels through the network infrastructure (e.g., between the CPE 216 enabled nodes), until the request reaches the UPF 232 and then the end application server responsible for handling the DL data delivery. On receiving the request from the user equipment via the HGW 212, the server processes the request and prepares the data corresponding to the request (i.e., DL data). The server sends the prepared DL data to the UPF 232 responsible for handling the DL data delivery. The UPF 232 receives the DL data destined for the HGW 212, which then forwards this data to the user equipment through the CPE 216 and the HGW 212. In some cases, the application server needs to send some notification or any traffic to the end devices. But if there was no traffic inbetween for a considerable amount of time, to save the overall resource usage, the CPE216 is brought to idle mode by the 5G core network

[0149] At step 404, the method 400 may include detecting, by the UPF 232, whether the first network element is in an idle mode. In an aspect, if there is no traffic for a certain duration, the network sets the CPE 216 in an idle mode. So, the UPF 232 detects whether the CPE 216 is in the idle mode or the active mode. If the CPE 216 is in the idle mode, then the CPE 216 needs to transition from the idle mode to the active mode to send the DL data to the HGW 212.

[0150] At step 406, the method 400 may include on detecting the first network element is in the idle mode, sending, by the UPF 232, an identifier associated with the DL data to a SMF 230. The identifier includes the PDR identifier. The identifier is either a first network element identifier (e.g., CPE PDR ID) or at least one second network element identifier (e.g., HGW PDR ID). In an embodiment, on detecting the CPE 216 is in idle mode, the UPF 232 may send the identifier corresponding to the CPE 216 or the HGW 212 to the SMF 230. The SMF 230 is responsible for management of the established CPE 216 session.

[0151] At step 408, the method 400 may include receiving the identifier, sending, by the SMF 230, at least one DDN corresponding to the DL data to the AMF 228 to initiate a network process to bring the first network element from the idle mode to an active mode. In an aspect, on receiving the identifier corresponding to the CPE 216 or the HGW 212, the SMF 230 may initiate the network process to perform transition of the CPE from the idle mode to the active mode.

[0152] At step 410, the method 400 may include transmitting, by the UPF 232, the received DL data to the at least one second network element via the first network element upon bringing the first network element to the active mode. In an aspect, theSMF 230 sends the DL data notification to the AMF 228 as the AMF 228 has information corresponding to the CPE 216 session.

[0153] In an embodiment, a plurality of second network element sessions corresponding to a plurality of second network elements is created using a plurality of PDR / second network element identifiers over a first network element session. The first network element session is the IP PDU session. In an aspect, the CPE IP PDU session is created for the CPE 216 in the network 106. The plurality of the HGW 212 may be connected to the CPE 216 via the MDU 214. The CPE 216 and the plurality of HGW 212 have PDR IDs for the CPE IP PDU session. The PDR IDs of the HGW 212 may be used to identify the HGW 212 intended for DL data transmission. Over the CPE IP PDU session, the plurality of the HGW 212 sessions (e.g., ethernet sessions of HGW 212) corresponding to the HGW 212 is established using PDR IDs of the HGW 212s. The ethernet sessions of the HGW 212 may be the ethernet connections between the CPE 216 and the 5G core network nodes in the network. The HGW 212 establishes ethernet connections with the UPF. Once the ethernet session is established, the ethernet session facilitates the transmission of data between the HGW 212 and the network. This may include both the uplink (data sent from the HGW 212 to the network) and DL (data received by the HGW 212 from the network) traffic. The ethernet sessions of the HGW 212 within the CPE IP PDU session enables efficient connectivity and data delivery in the network.

[0154] In an embodiment, the method 400 may include on receiving the first network element PDR identifier from the UPF 232. The network process includes performing, by the AMF 228, a network-initiated service activation to bring the first network element from the idle mode to the active mode. The UPF 232 transmits the received DL data to the at least one second network element via the first network element. In an embodiment, the AMF 228 receives the identifier corresponding to the CPE 216 from the UPF 232. To bring the CPE 216 from the idle mode to the activemode, the AMF 228 performs the network-initiated service activation on receiving the DL data notification. The CPE 216 transitions from the idle mode to the active mode. Once the CPE 216 is back in the active mode, the UPF 232 transmits the received DL data to one of the HGW 212 via the CPE 216.

[0155] In an embodiment, the method 400 may include, on receiving the at least one second network element PDR identifier from the UPF 232. The network process includes mapping, by the SMF 230, the at least one second network element identifier with the plurality of created second network element identifiers corresponding to the first network element session. The SMF 230 sends the at least one DL data notification to the AMF 228. The AMF 228 performs the network-initiated service activation on receiving the at least one DL data notification. The UPF 232 transmits the received DL data to the at least one second network element via the first network element. In an aspect, on receiving PDR ID corresponding to one of the HGW 212 from the UPF 232, the SMF 230 maps the received PDR ID with plurality of created PDR IDs of the HGW 212 corresponding to the CPE IP PDU session. The SMF 230 sends the DL data notification to the AMF 228. To bring the CPE 216 from the idle mode to the active mode, the AMF 228 performs the network-initiated service activation on receiving the DL data notification. The CPE 216 transitions from the idle mode to the active mode. Once the CPE 216 is back in the active mode, the UPF 232 transmits the received DL data to one of the HGW 212 via the CPE 216.

[0156] The method 400 involves transmitting DL data via a structured interaction between network entities. The primary entities include the UPF 232, the SMF 230, and the AMF 228, all of which coordinate with the first network element, such as the CPE 216, to deliver data to the second network element, like UE 104.

[0157] Initially, the UPF 232 receives the DL data intended for the second network element. It then checks if the first network element, the CPE 216, is in the idle mode, meaning it is inactive or in a low-power state

[0158] If the CPE 216 is idle, the UPF 232 sends the identifier, which may be PDR identifier, to the SMF 230. The PDR identifier may be used for the SMF 230 230 to recognize the data and its intended path.

[0159] Upon receiving the PDR identifier, the SMF 230 may issue the DDN to the AMF 228. The DDN notification is essential as it prompts the network to activate the idle CPE 216, transitioning it to the active mode capable of transmitting the received data.

[0160] Once the CPE 216 is active, the UPF 232 completes the process by transmitting the DL data through the now-active CPE 216 to the intended second network element, such as the UE 104.

[0161] The method 400 design can vary slightly depending on the type of identifier used. For an example, if the identifier is linked to the first network element, direct service activation is performed. If linked to a second network element, the SMF 230 maps the identifier to the correct session before activating the service, ensuring seamless data transmission.

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

[0163] FIG. 5 illustrates an exemplary computer system 500 in which or with which embodiments of the present disclosure may be implemented. 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, 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 port(s) 560 may be chosen depending on a network, such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system 500 connects.

[0164] 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) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor 570. The mass storage device 550 may be any current or future mass storage solution, which can be used to store information and / or instructions. The mass storage device 550 includes, but is 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), one or more optical discs, a Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks.

[0165] The bus 520 communicatively couples the processor 570 with the other memory, storage, and communication blocks. The bus 520 may be, e.g. a Peripheral Component Interconnect (PCI) / PCI Extended (PCLX) 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.

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

[0167] In an exemplary embodiment, the system 108 for transmitting DL data to at least one second network element via the first network element. The system 108 includes the UPF configured to receive the DL data for the at least one second network element connected with the first network element. The system 108 includes detecting whether the first network element is in the idle mode. The system 108 includes sending an identifier associated with the DL data to the SMF 230, on detecting the first network element is in the idle mode. The system 108 on receiving the identifier from the UPF 232, the SMF 230 is configured to send the at least one DDN to an access and the AMF 228 to initiate a network process to bring the first network element from the idle mode to the active mode. In an embodiment, the system 108 includes the first network element is the CPE 216, and the at least one second network element is the UE 104, the HGW 212, or the MDU 214.

[0168] In another exemplary embodiment, the present disclosure discloses a computer program product includes a non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to perform the method 400 for transmitting at least one DL data notification to a plurality of network elements, the method includes receiving, by UPF 232, the DL data for the at least one second network element connected with the first network element. The method 400 includes detecting, by the UPF 232, whether the first network element is in an idle mode. The method includes on detecting the first network element is in the idle mode, sending, by the UPF 232, an identifier associated with the DL data to the SMF 230. The method 400 includes on receiving the identifier, sending, by the SMF 230, at least one DDN to the AMF 228 to initiate a network process to bring the first network element from the idle mode to the active mode. The method 400 includes transmitting, by the UPF 232, the received DL data to the at leastone second network element via the first network element upon bringing the first network element to the active mode.

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

[0170] The method and system of the present disclosure may be implemented in a number of ways. For example, the methods and systems of the present disclosure may be implemented by software, hardware, firmware, or any combination of software, hardware, and firmware. The above-described order for the steps of the method is for illustration only, and the steps of the method of the present disclosure are not limited to the order specifically described above unless specifically stated otherwise. Further, in some embodiments, the present disclosure may also be embodied as programs recorded in a recording medium, the programs including machine-readable instructions for implementing the methods according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

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

[0172] The present disclosure provides a technical advancement related to sending DL data notification to the CPE 216 on receiving DL data for the HGW 212 behind the CPE 216. This advancement addresses the limitations of existing solutions by notifying the DL data received for the HGW 212 while the CPE 216 is the idle mode. The disclosure may involve sending, by the SMF 230 and the UPF 232, the DL data notification for the CPE 216 session to the AMF 228 while the DL data received at the UPF 232 is for the HGW 212. The system 108 and method 400 notifies the UPF 232 about the PDR ID of the CPE 216 to the SMF 230 for DL data by bringing the CPE 216 from the idle mode to the active mode. Further, The system 108 and method 400 notifies the UPF 232 about the PDR ID of the HGW 212 to the SMF 230 for the DL data by mapping the SMF 230 the PDR ID to the CPE 216 session and bringing the CPE 216 from the idle mode to the active mode. The CPE 216 brings back to the active mode from the idle mode to deliver the DL data intended for the HGW 212. By implementing, the present disclosure eliminates the need for re-establishing the GTP tunnel again so as to deliver the received DL data destined to the HGW 212.ADVANTAGES OF THE PRESENT DISCLOSURE

[0173] The present disclosure provides a method and a system for transmitting downlink data to at least one second network element via a first network element.

[0174] In the present disclosure efficient data notification is obtained. The system and method for sending downlink (DL) data notifications efficiently manages network resources by eliminating the need for re-establishing General packet radio service (GPRS) Tunneling Protocol tunnel (GTP) tunnels.

[0175] The present disclosure optimizes the resource utilization by keeping a customer premise equipment (CPE) in an idle mode when not directly handling data and quickly transitioning to active mode as needed. The system maximizes the efficient use of network resources and reduces operational costs.

[0176] The present disclosure enhances data delivery speed. The ability to activate the CPE facilitates faster data delivery to a home gateway (HGW), contributing to reduced overall latency in network operations.

[0177] The present disclosure improves network reliability using the packet detection rule (PDR) ensures accurate session mapping and reduces errors in data transmission, enhancing the reliability of network operations.

[0178] The present disclosure increases scalability by the system architecture allowing for scalable management of numerous CPEs and the HGW s, supporting larger networks with more efficient data handling capabilities.

[0179] The present disclosure informs the user plane function (UPF) about the PDR identifier (ID) of the CPE to a session management function (SMF) for the DL data by activating the CPE from the idle mode. The present disclosure informs the UPF about the PDR ID of the HGW to the SMF for the DL data by associating the SMF PDR ID with the CPE session and activating the CPE from the idle mode. The present disclosure enhances the user Experience. Users benefit from a seamless experience as the system maintains consistent connectivity and service quality without disruptions from inactive states.

[0180] The system highlights technical improvements in managing downlink data processes within telecommunications networks.

Claims

We Claim:

1. A method (400) for transmitting downlink data to at least one second network element via a first network element, the method comprising: receiving, by a user plane function (UPF) (232), the downlink data for the at least one second network element connected with the first network element; detecting, by the UPF (232), whether the first network element is in an idle mode; on detecting the first network element is in the idle mode, sending, by the UPF (232), an identifier associated with the downlink data to a session management function (SMF) (230); on receiving the identifier, sending, by the SMF (230), at least one downlink data notification (DDN) corresponding to the downlink data to an access and mobility management function (AMF) (228) to initiate a network process to bring the first network element from the idle mode to an active mode; and transmitting, by the UPF (232), the received downlink data to the at least one second network element via the first network element upon bringing the first network element to the active mode.

2. The method as claimed in claim 1, wherein the first network element is a customer premise equipment (CPE) (216), and the at least one second network element is an user equipment (UE), a home gateway (HGW) (212) or a multiple dwelling unit (MDU) (214).

3. The method as claimed in claim 1 , wherein the identifier is either a first networkelement packet detection rule (PDR) identifier or at least one second network element PDR identifier.

4. The method as claimed in claim 1, wherein the network process is performed over a session of the first network element, and wherein the first network element session is an internet protocol (IP) protocol data unit (PDU) session, and each second network element session is an Ethernet session established as a child session of the first network element session.

5. The method as claimed in claim 3, wherein on receiving the first network element PDR identifier from the UPF (232), the network process comprising: performing, by the AMF (228), a network-initiated service activation to bring the first network element from the idle mode to the active mode; and transmitting, by the UPF (232), the received downlink data to the at least one second network element via the first network element.

6. The method as claimed in claim 3, wherein on receiving the at least one second network element PDR identifier from the UPF (232), the network process comprising: mapping, by the SMF (230), the at least one second network element identifier to a first network element session corresponding to the first network element; sending, by the SMF (230), the at least one DDN to the AMF (228); performing, by the AMF (228), the network-initiated service activation to bring the first network element from the idle mode to the active mode; and transmitting, by the UPF (232), the received downlink data to the at least one second network element via the first network element.

7. A system (108) for transmitting downlink data to at least one second network element via a first network element, the system comprising: a user plane function (UPF) (232) configured to: receive the downlink data for the at least one second network element connected with the first network element; detect whether the first network element is in an idle mode; and send an identifier associated with the downlink data to a session management function (SMF) (230), on detecting the first network element is in the idle mode; and on receiving the identifier from the UPF (232), the SMF (230) is configured to: send the at least one downlink data notification (DDN) to an access and mobility management function (AMF) (228) to initiate a network process to bring the first network element from the idle mode to the active mode.

8. The system as claimed in claim 7, wherein the first network element is a customer premise equipment (CPE) (216), and the at least one second network element is a user equipment (UE) (104), home gateway (HGW) (212), or a multiple dwelling unit (MDU) (214).

9. The system as claimed in claim 7, wherein the identifier is either a first network element packet detection rule (PDR) identifier or at least one second network element PDR identifier.

10. The system as claimed in claim 7, wherein the first network element is associated with a first network element session and the at least one secondnetwork element is associated with at least one second network element session, and wherein the first network element session is an internet protocol (IP) protocol data unit (PDU) session, and each second network element session is an Ethernet session established as a child session of the first network element session.

11. The system as claimed in claim 9, wherein on receiving the first network element PDR identifier from the UPF (232), the network process is configured to: perform, by the AMF (228), a network-initiated service activation to bring the first network element from the idle mode to the active mode; and transmit, by the UPF (232), the received downlink data to the at least one second network element via the first network element.

12. The system as claimed in claim 9, wherein on receiving the at least one second network element PDR identifier from the UPF (232), the network process configured to: map, by the SMF (230), the at least one second network element identifier to a first network element session corresponding to the first network element; send, by the SMF (230), the at least one DDN to the AMF (228); perform, by the AMF (228), the network-initiated service activation to bring the first network element from the idle mode to the active mode; and transmit, by the UPF (232), the received downlink data to the at least one second network element via the first network element.

13. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or moreprocessors, cause the one or more processors to perform a method for transmitting at least one downlink data notification to a plurality of network elements, the method comprising: receiving, by a user plane function (UPF) (232), the downlink data for the at least one second network element connected with the first network element; detecting, by the UPF (232), whether the first network element is in an idle mode; on detecting the first network element is in the idle mode, sending, by the UPF (232), an identifier associated with the downlink data to a session management function (SMF) (230); on receiving the identifier, sending, by the SMF (230), at least one downlink data notification (DDN) to an access and mobility management function (AMF) (228) to initiate a network process to bring the first network element from the idle mode to an active mode; and transmitting, by the UPF (232), the received downlink data to the at least one second network element via the first network element upon bringing the first network element to the active mode.

Images