Method and system for creating sessions in a telecommunication network

Abstract

The present disclosure provides a method (500) and system (108) for creating sessions in a telecommunication network (106). The method includes receiving session request from the CPE and establishing the CPE session in the telecommunication network (106). Upon successful establishment, an individual HGW session request is received corresponding to HGW child sessions for each of a set of HGW devices connected over the CPE session. A unique Packet Detection Rule (PDR) Identifier (ID) is assigned to each HGW child session based on the respective HGW session request. Subsequently, the HGW child sessions are created using the assigned PDR IDs. The method enables efficient session creation, resource optimization, and independent session handling for multiple HGWs operating behind a common CPE in the telecommunication network (106).

Description

METHOD AND SYSTEM FOR CREATING SESSIONS IN A TELECOMMUNICATION NETWORKRESERVATION OF RIGHTS

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

[0002] The present disclosure relates generally to the field of telecommunications. More particularly, the present disclosure relates to a method and a system for creating sessions in a telecommunication network.DEFINITION

[0003] The term ‘Customer Premise Equipment (CPE)’ used hereinafter in the specification refers to a specialized network device that may be deployed outdoors or indoors, depending on the network design and signal requirements at customer locations, to facilitate connectivity and network services.

[0004] The term “Home Gateway (HGW) device” used hereinafter in the specification refers to refers to a type of Residential Gateway (RG), which is a device configured to provide communication services such as voice, data, broadcast video, and video on demand to other devices within a customer premises. 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.

[0005] The term “Multiple Dwelling Unit (MDU)” used hereinafter in the specification refers to a device or system deployed in a residential building or complex to facilitate network connectivity. The residential building or complex contains multiple separate housing units, such as apartments, condominiums, or dormitories. The deployment of MDU may involve centralized or per-unit CPE, with shared access infrastructure like fiber splitters or Ethernet switches.

[0006] The term ‘N4 interface as used hereinafter in the specification refers to an interface between a Session Management Function (SMF) and a User Plane Function (UPF) in the 5G core network. The N4 interface is used for creating and managing data sessions.

[0007] The term ‘N7 interface as used hereinafter in the specification refers to an interface between the SMF and a Policy Control Function (PCF) in the 5G core network. The N7 interface is utilized for a policy control and an enforcement related to session management.

[0008] The term ‘N40 interface as used hereinafter in the specification refers to an interface between the SMF and a Charging Function (CHF) in the 5G core network. The N40 interface is used for managing charging data related to network usage.

[0009] The term ‘EoGRE’ as used hereinafter in the specification refers to an Ethernet over Generic Routing Encapsulation. The EoGRE is an advanced tunneling protocol that allows an encapsulation of Ethernet frames within GRE tunnels, enabling a transmission of Ethernet headers across Internet Protocol (IP) networks.

[0010] The term ‘PDU’ as used hereinafter in the specification refers to a Protocol Data Unit. The PDU is a unit of data specified in a protocol of a given layer and represents an information delivered as a unit among peer entities of the 5G core network.

[0011] The term ‘SMF’ as used hereinafter in the specification refers to the Session Management Function in the 5G core network. The SMF is responsible for session management, including session establishment, modification, and release.

[0012] The term ‘UPF’ as used hereinafter in the specification refers to the User Plane Function in the 5G core network. The UPF handles data traffic and routing between end devices (i.e., the electronic devices) and the 5G core network.

[0013] The term ‘PCF’ as used hereinafter in the specification refers to the Policy Control Function in the 5G core network. The PCF manages policy rules for controlling network behaviour and ensuring compliance with service requirements.

[0014] The term ‘CHF’ as used hereinafter in the specification refers to the Charging Function in the 5G core network. The CHF handles a collection and a processing of charging data for billing and accounting purposes.

[0015] The term ‘UDM’ as used hereinafter in the specification refers to the Unified Data Management Function in the 5G core network. The UDM is responsible for managing subscription data, user authentication, authorization, and mobility management functions.

[0016] The term ‘AUSF’ as used hereinafter in the specification refers to the Authentication Server Function in the 5G core network. The AUSF is responsible for performing authentication procedures for User Equipment (UE) accessing the network. The AUSF interacts with the UDM to retrieve subscriber credentials and validate the user’s identity, thereby ensuring secure and authorized access to network services.

[0017] The term ‘Ethernet session’ used hereinafter in the specification refers to a network session that provides Layer 2 (Data Link Layer) connectivity, enabling transmission of Ethernet frames between devices. Lor instance, an Ethernet session is established between the Home Gateway (HGW) device and the core network to facilitate data communication over an encapsulated tunnel such as the Ethernet over GRE (EoGRE).

[0018] The term ‘Child session’ used hereinafter in the specification refers to an individual session created for a Home Gateway (HGW) device behind a parent session. Each child session operates independently, with its own policy and charging rules, and is uniquely identified within the parent Customer Premise Equipment (CPE) session.

[0019] The term ‘Parent session’ used hereinafter in the specification refers to a primary session, specifically the CPE IP Protocol Data Unit (PDU) session established between the CPE and the 5G core network. The parent session serves as a shared transport layer over which multiple HGW child Ethernet sessions are created and managed.

[0020] The term “Power over Ethernet (PoE)” used hereinafter in the specification refers to a technology that allows network cables to carry electrical power to devices.

[0021] The term “Packet Detection Rule (PDR)” used hereinafter in the specification refers to a rule used in a UPF to identify and classify packets for specific handling in a 5G core network.

[0022] The term “Dynamic Host Configuration Protocol (DHCP)” used hereinafter in the specification refers to a network management protocol used to dynamically assign IP addresses and other communication parameters to devices connected to a network.

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

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

[0025] In telecommunications networks, efficient management of data sessions is essential for maintaining high performance and optimal resource utilization.

[0026] In existing standards, Internet Protocol (IP) Protocol Data Unit (PDU) sessions and Ethernet PDU sessions have been treated as separate entities. The IP PDU session typically handles general internet traffic, while Ethernet PDU sessions are used for specific Ethernet frame-based communications. However, in scenarios where multiple Home Gateway (HGW) devices connect to a Customer Premise Equipment CPE) device, treating each HGW session independently may lead to an inefficient utilization of network resources, particularly in the UPF data plane.

[0027] In existing systems, each HGW connected to the CPE may establish its own independent Ethernet PDU session, leading to a high overhead in managing these sessions separately. This approach may result in the inefficient use of the UPF data- plane resources, increased complexity in a session management, and potential performance restrictions.

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

[0029] In an exemplary embodiment, a method for creating one or more sessions in a telecommunication network is disclosed. The method includes receiving, by a receiving unit, a session request corresponding to a CPE session, from a CPE. The method includes establishing, by a processing unit, the session corresponding to the CPE in the telecommunication network, in response to receiving the session request. The method includes receiving, by the receiving unit, a Home Gateway (HGW) session request corresponding to an HGW child session for each of a set of HGW devices over the CPE session, upon establishing the session. The method includes assigning, by a processing unit, a unique Packet Detection Rule (PDR) Identifier (ID) to each of the HGW child sessions associated with the set of HGW devices based on the HGW session request. The method includes creating, by the processing unit, the HGW child session corresponding to each of the set of HGW devices based on the unique PDR ID.

[0030] In some embodiments, each of the set of HGW devices is connected to the CPE through a Multiple Dwelling Unit (MDU).

[0031] In some embodiments, the session request is an Internet Protocol (IP) Protocol Data Unit (PDU) session request, and wherein the session is a CPE IP PDU session, and the HGW child session is an Ethernet session.

[0032] In some embodiments, the method further receiving, by the receiving unit, a registering request corresponding to the CPE. the method further includes registering the CPE with the processing unit, in response to receiving the registering request, and upon registering, enabling, by the processing unit, the CPE to initiate the session request corresponding to the CPE session.

[0033] In some embodiments, the method further includes establishing, by the processing unit, a CPE policy session and a CPE charging session with a Policy Control Function (PCF) and a Charging Function (CHF), respectively.

[0034] In some embodiments, the method further includes creating, by the processing unit, a HGW policy session and a HGW charging session with the PCF and the CHF, over an N7 interface and an N40 interface respectively.

[0035] In some embodiments, the method further includes receiving, by the receiving unit, a HGW session update request corresponding to an HGW child session associated with an HGW device of the set of HGW devices and updating, by the processing unit, the HGW child session associated with the HGW device in response to receiving the HGW session update request.

[0036] In some embodiments, updating the HGW child session comprises modifying, by the processing unit, the unique PDR ID associated with the HGW child session.

[0037] In another exemplary embodiment, a system for creating one or more sessions in a telecommunication network is disclosed. The system includes a receiving unit configured to receive a session request corresponding to a CPE session, from a CPE. The system includes a processing unit configured to establish the session corresponding to the CPE in the telecommunication network, in response to receiving the session request. The receiving unit configured to receive a Home Gateway (HGW) session request corresponding to an HGW child session for each of a set of HGW devices over the CPE session, upon establishing the session. The processing unit configured to assign a unique Packet Detection Rule (PDR) Identifier (ID) to each of the HGW child sessions associated with the set of HGW devices based on the HGW session request. The processing unit configured to create the HGW child session corresponding to each of the set of HGW devices based on the unique PDR ID.

[0038] In an exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or moreprocessors to perform a method for creating one or more sessions in a telecommunication network is disclosed. The method includes receiving, by a receiving unit, a session request corresponding to a CPE session, from a CPE. The method includes establishing, by a processing unit, the session corresponding to the CPE in the telecommunication network, in response to receiving the CPE session request. The method includes receiving, by the receiving unit, a Home Gateway (HGW) session request corresponding to an HGW child session for each of a set of HGW devices over the CPE session upon establishing the session. The method includes assigning, by a processing unit, a unique Packet Detection Rule (PDR) Identifier (ID) to each of the HGW child sessions associated with the set of HGW devices based on the HGW session request. The method includes creating, by the processing unit, the HGW child session corresponding to each of the set of HGW devices based on the unique PDR ID.

[0039] The foregoing general description of the illustrative embodiments and the following detailed description thereof are merely exemplary aspects of the teachings of this disclosure, and are not restrictive.OBJECTIVES OF THE PRESENT DISCLOSURE

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

[0041] An object of the present disclosure is to provide a system and a method that creates multiple child home gateway (HGW) sessions for a set of HGW devices over a single parent Customer Premise Equipment (CPE) Internet Protocol (IP) Protocol Data Unit (PDU) session.

[0042] Another object of the present disclosure is to optimize a utilization of the User plane function (UPF) data-plane resources by consolidating the multiple child HGW sessions over the single parent CPE IP PDU session.

[0043] Another object of the present disclosure is to manage the multiple childHGW sessions in the 5G network by allowing the SMF to maintain independent N7 and N40 sessions with a PCF and a CHF for the parent CPE session and the child HGW sessions.

[0044] Other objectives and advantages of the present disclosure will be more apparent from the following description, which is not intended to limit the scope of the present disclosure.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

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

[0046] FIG. 1 illustrates an exemplary network architecture in which or with a system configured for creating one or more sessions in a telecommunication network may be implemented, in accordance with embodiments of the present disclosure.

[0047] FIG. 2 illustrates an exemplary block diagram of the system configured for creating the one or more sessions in the telecommunication network, in accordance with embodiments of the present disclosure.

[0048] FIG. 3 illustrates an exemplary system architecture for creating the one or more sessions in the telecommunication network, in accordance with an embodiment of the present disclosure.

[0049] FIG. 4 illustrates an exemplary sequence diagram representing a process for creating the one or more sessions in the telecommunication network, in accordance with an embodiment of the present disclosure.

[0050] FIG. 5 illustrates an exemplary flow diagram of a method for creating the one or more sessions in the telecommunication network, in accordance with an embodiment of the present disclosure.

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

[0052] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102 - User(s)104 - User Equipments (UEs)106 - Network108 - System200 -Block Diagram202 - Receiving Unit204 - Memory206 - Interface(s)208 - Processing Unit210 - Database302 - Power over Ethernet (PoE) cable 304 - Multiple Dwelling Unit (MDU)306 - Customer Premise Equipment (CPE)308 - Base station310 - User Plane Function (UPF)312 - Internet 314 - Session Management Function (SMF)316 - Policy Control Function (PCF)318 - Charging Function (CHF)320 -Access and Mobility Management Function (AMF)322 - Unified Data Management (UDM) 324 - Authentication Server Function (AUSF)400 - Sequence Diagram500 - Method Flow Diagram600 - Computer System610 - External Storage Device620 - Bus630 - Main Memory640 - Read Only Memory650 - Mass Storage Device660 - Communication Port(S)670 - ProcessorDETAILED DESCRIPTION

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

[0054] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It shouldbe understood that various changes may be made in the function and arrangement of elements without departing from the spirit and scope of the disclosure as set forth.

[0055] Specific details are given in the following description to provide a thorough understanding of the embodiments. However, it will be understood by one of ordinary skill in the art that the embodiments may be practiced without these specific details. For example, circuits, systems, networks, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail. In other instances, well-known circuits, processes, algorithms, structures, and techniques may be shown without unnecessary detail in order to avoid obscuring the embodiments.

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

[0057] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Furthermore, to the extent that the terms “includes,” “has,” “contains,” and other similar words are used in either the detailed description or the claims, suchterms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.

[0058] Reference throughout this specification to “one embodiment” or “an embodiment” or “an instance” or “one instance” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the present disclosure. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0059] The terminology used herein is to describe particular embodiments only and is not intended to be limiting the disclosure. As used herein, the singular forms “a”, “an”, and “the” are intended to include the plural forms as well, unless the context indicates otherwise. It will be further understood that the terms “comprises” and / or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof. As used herein, the term “and / or” includes any combinations of one or more of the associated listed items. It should be noted that the terms “mobile device”, “user equipment”, “user device”, “communication device”, “device” and similar terms are used interchangeably for the purpose of describing the invention. These terms are not intended to limit the scope of the invention or imply any specific functionality or limitations on the described embodiments. The use of these terms is solely for convenience and clarity of description. The invention is not limited to any particular type of device or equipment, and it should be understood that other equivalent terms or variations thereof may be used interchangeably without departing from the scope of the invention as defined herein.

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

[0061] In existing standards, Internet Protocol (IP) Protocol Data Unit (PDU) sessions and Ethernet PDU sessions have been treated as separate entities. In scenarios where the set of Home Gateway (HGW) devices are connected to a Customer Premise Equipment (CPE), the conventional approach often manages each child HGW session independently of the parent CPE session. This approach may lead to inefficient utilization of the User Plane Function (UPF) data-plane resources. Therefore, the present disclosure addresses these challenges by providing a system and a method that creates multiple child HGW sessions over a single parent CPE IP PDU session. By utilizing an efficient tunneling protocol, such as an Ethernet over Generic Routing Encapsulation (EoGRE), the present disclosure enhances the network efficiency and simplifies the session management, thereby optimizing an overall network performance and a resource allocation.

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

[0063] FIG. 1 illustrates an exemplary network architecture 100 in which or with which a system 108 configured for creating one or more sessions in a telecommunication network 106 may be implemented, in accordance with embodiments of the present disclosure.

[0064] In an embodiment, the network architecture (100) may include one or more user equipments (UEs) 104-1, 104-2... 104-N associated with one or more users 102-1, 102-2... 102-N in an environment. A person of ordinary skill in the art 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. Further, the user 102 may correspond to a network administrator or a network service provider. 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. Although three UEs 104 are depicted in FIG. 1, however, any number of the UEs 104 may be included without departing from the scope of the ongoing description.

[0065] In an exemplary implementation, the UE 104 may be deployed as a Home Gateway Device (HGW) in a residential or enterprise network environment. In an example, when operating as an HGW, the UE 104 is connected to a Customer Premises Equipment (CPE) via a Multi-Dwelling Unit (MDU), typically using a Power over Ethernet (PoE) cable. In another exemplary implementation, the UE 104 may be deployed as the HGW connected to the CPE for use in a Fixed Wireless Access (FWA) environment. In an example, the UE 104 may be statically located at a fixed customer premises and connected to the core network via a wireless access network.

[0066] In another implementation, the UE 104 may function as 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, smart phones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the usersY1102 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, multisensing, network- connected devices, which 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.

[0067] 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, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other computing device, wherein 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 the entity such as touch pad, touch enabled screen, 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.

[0068] In FIG. 1, the UE 104 (i.e., the HGW) may communicate with the system 108 via a telecommunication network 106 (interchangeably referred to as a network 106). In order to establish communication, initially, the telecommunication network 106 is configured to receive a connection request from the UE 104. In response to receiving the connection request, the telecommunication network 106 is configured to send an acknowledgment of the connection request to the UE 104. Further, a plurality of signals is transmitted in response to the connection request. Based on the connection request, the sessions are created in the telecommunication network 106. In an embodiment, the network 106 includes at least one of the 4G network, the 5G network, the 6G network, or the like. The telecommunication network 106 may enablethe UE 104 to communicate with other devices in the network architecture 100 and / or with the system 108.

[0069] 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 telecommunication 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, waves, voltage or current levels, some combination thereof, or so forth.

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

[0071] FIG. 2 illustrates a block diagram 200 of the system 108 configured for creating the one or more sessions in the telecommunication network 106 in accordance with an embodiment of the present disclosure.

[0072] In an embodiment, the system 108 may include a receiving unit 202. The receiving unit 202 may be configured to receive data signals, messages, or instructions from one or more external sources over the telecommunication network 106. In an embodiment, the receiving unit 202 may include one or more transceivers, antennas, ports, or communication modules compatible with various protocols such as Ethernet, 4G / 5G, or other network technologies. The receiving unit 202 may further include signal conditioning components such as filters, amplifiers, or decoders to process incoming signals and convert them into a format suitable for further analysis by a processing unit 208, which is included in the system 108.

[0073] In an embodiment, the system 108 may include a memory 204. 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 a Random- Access Memory (RAM), or a non-volatile memory such as an Erasable Programmable Read Only Memory (EPROM), a flash memory, and the like.

[0074] 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, the processing unit 208 and a database 210.

[0075] The processing unit 208 may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing unit 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 unit 208 may be processor-executable instructions stored on a non-transitory machine-readable storage medium and the hardware for the processing unit 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 unit 208. In such examples, the system 108 may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine- readable storage medium may be separate but accessible to the system 108 and the processing resource. In other examples, the processing unit 208 may be implemented by an electronic circuitry.

[0076] In one implementation, the receiving unit 202 may be operatively coupled to the interface(s) 206 and the processing unit 208 to enable seamless data acquisition, decoding, and dispatching of received information for further handling or storage.

[0077] In an embodiment, the processing unit 208 may be associated with a User Plane Function (UPF), and a Session Management Function (SMF),

[0078] In an embodiment, the system 108 is configured for creating one or more sessions in the telecommunication network 106. The one or more sessions may be, for example, multiple child HGW sessions, which may be created over a single parent Customer Premise Equipment (CPE) Internet Protocol (IP) Protocol Data Unit (PDU) session.

[0079] In order to create the multiple HGW child sessions in the telecommunication network 106, the receiving unit 202 may be configured to receive a registration request corresponding to the CPE. The registration request may includeidentification credentials, the CPE capabilities, subscription-related information and the like. In response to receiving the registration request, the processing unit 208 may register the CPE with itself. In an example, the UDM / AUSF may perform authentication and authorization procedures with the CPE, such as validating CPE credentials and subscriber profile information. Upon successful validation, the UDM / AUSF may store an association record of the CPE, allocate initial network resources and complete the registration process, and finally, the CPE is registered with the UDM / AUSF. Upon registering, the processing unit 208 may enable the CPE to initiate the ession request corresponding to the CPE session.

[0080] In an embodiment, upon registration, the receiving unit 202 may receive a session request corresponding to a CPE session from the CPE. The CPE session is a CPE IP PDU session. In an aspect, the session request is a IP PDU session request. In an aspect, the session is the CPE IP PDU session. The IP PDU session request refers to a control-plane signaling message initiated by the CPE to establish a data session with the 5G core network for IP-based traffic exchange. The CPE IP PDU session request may be received from the CPE over a standardized interface, such as the N1 / N2 interface via an Access Network (AN) and is forwarded to the AMF for resource allocation.

[0081] In response to receiving the session request, the processing unit 208 may be configured to establish the session corresponding to the CPE in the telecommunication network 106. In a more elaborative way, to establish the CPE IP PDU session, the processing unit 208 may set up a CPE policy session with a Policy Control Function (PCF) and a CPE charging session with a Charging Function (CHF) to manage policies and charging, respectively. In an example, the PCF may define Quality of Service (QoS) parameters and traffic handling rules for the CPE, such as prioritizing video streaming traffic or limiting bandwidth during peak hours. Simultaneously, the CHF may enable real-time or offline charging for the dataconsumed over the CPE session, ensuring accurate billing per data usage, time, or service type. These control-plane interactions allow the CPE session to operate within the constraints and entitlements defined by the network operator.

[0082] Upon establishing the CPE session, the receiving unit 202 may be configured to receive a HGW session request corresponding to an HGW child session from each of a set of HGW devices over the CPE session. The HGW child session is an Ethernet session. The HGW session request refers to a signaling message initiated by an individual HGW device to establish its own Ethernet session toward the 5G core network, using the parent IP PDU session already established by the CPE. The HGW session request may include the HGW’s identifier, MAC address, session initiation parameters, and any required service characteristics. In an aspect, each of the set of the HGW devices is connected to the CPE through a Multiple Dwelling Unit (MDU) such that each of the set of HGW devices transmits the HGW session request to the CPE. In an aspect, an Ethernet over Generic Routing Encapsulation (EoGRE) tunnel is used to transmit the HGW session request. The EoGRE represents an advanced form of Generic Routing Encapsulation (GRE), wherein the underlying Ethernet header is also transparently transmitted within the GRE tunnel.

[0083] In an aspect, the HGW session request from each of the set of HGW devices is transported using the same underlying IP PDU session that was initially established for the CPE. Instead of each HGW device requiring a separate IP PDU session, the traffic and control messages from each of the set of HGW devices are logically multiplexed and tunneled through the parent CPE IP PDU session, optimizing resource usage and simplifying session management.

[0084] In an embodiment, the processing unit 208 may assign a unique Packet Detection Rules (PDR) Identifier (ID) to each HGW child session associated with the set of HGW devices based on the HGW session request. The PDR ID is a unique identifier used within the UPF to detect and differentiate traffic flows associated witheach HGW child session. The PDR defines rules for packet matching, forwarding, QoS enforcement, and charging actions. The PDR ID allows the network to reference and apply the correct set of instructions for handling specific data flow. The PDR ID is assigned based on the HGW session request to ensure that each HGW child session is individually managed and monitored according to its specific session parameters, even though all traffic is tunneled over the same parent CPE IP PDU session.

[0085] Further, the processing unit 208 is configured to create the HGW child session corresponding to each of the set of HGW devices based on the unique PDR ID. The creation of the HGW child session refers to the end-to-end establishment of a logical data session for each of the set of the HGW devices using the assigned PDR ID.

[0086] In order to create the HGW child session, the processing unit 208 is configured to create a HGW policy session and a HGW charging session with the Policy Control Function (PCF) and the Charging Function (CHF), respectively. Creating the HGW policy session and the HGW charging session means initiating by the processing unit 208 (i.e., the SMF) a dedicated signaling procedures toward the PCF and the CHF to define and activate service-specific policies (e.g., bandwidth, QoS class, access restrictions) and charging rules (e.g., volume-based, duration-based billing) applicable to each created HGW child session. In an aspect, the processing unit 208 (i.e., the SMF) creates distinct N7 and N40 sessions with PCF and CHF for each HGW child sessions.

[0087] In an example, upon receiving an HGW session request, the SMF (i.e., the processing unit 208) may assign a PDR ID to identify and route the HGW's traffic. Using this PDR ID, the SMF sends a session establishment request to the PCF to define a QoS rule for video streaming and to the CHF to apply a per- usage-based charging model. These control-plane interactions result in a complete HGW child session that is distinguishable, manageable, and billable independently of other HGW sessions, even though all share the same parent CPE IP PDU session.

[0088] In an embodiment, the receiving unit 208 may be configured to receive a HGW session update request corresponding to the HGW child session associated with an HGW device of the set of HGW devices. The HGW session update request is a control-plane signaling message initiated either by the HGW device itself or by the CPE on behalf of the HGW. This request is sent HGW device when there is a need to modify, reconfigure, or refresh session-specific parameters for that particular HGW child session. The HGW session update request allows ongoing HGW child sessions to remain flexible, efficient, and aligned with real-time operational or service changes.

[0089] In response to receiving the HGW session update request, the processing unit 208 may update the corresponding HGW child session. In order to update the HGW child session, the processing unit 208 may modify the unique PDR ID associated with the HGW child session. It should be noted that upon receiving the HGW session update request, the processing unit 208 may update both the HGW policy session and the HGW charging session, as a separate PDR, Forwarding Action Rule (FAR), QoS Enforcement Rule (QER) and Usage Reporting Rule (URR) are provided for the HGW session from the SMF to the UPF.

[0090] In an embodiment, the database 210 may include data that may be either stored or generated as a result of functionalities implemented by any of the components of the processor(s) 202 or the processing engine 208.

[0091] Although FIG. 2 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. 2. 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.

[0092] FIG. 3 illustrates an exemplary architecture 300 for creating the one or more sessions in the telecommunication network 106, in accordance with an embodiment of the disclosure. FIG. 3 is explained in conjunction with FIGS. 1 and 2.

[0093] As depicted in FIG. 3, a set of HGW devices, i.e., an HGW-1 device, an HGW-2 device, an HGW-3 device, up to an HGW-N device, may be connected to a CPE 306 through an MDU 304. It should be noted that ‘N’ may be any number of an HGW device (for example, an HGW-10 device) based on a requirement of the network service provider. Each of the set of HGW devices is connected with the MDU 304 via a Power over Ethernet (PoE) cable 302. For example, as depicted in the architecture 300, the HGW-2 device and the HGW-3 device are connected via the PoE cable 302, also, the HGW-1 and the HGW-N device are connected via the PoE cable 302. Further, the MDU 304 is connected with the CPE 306 via the PoE cable 302. The PoE cable 302 passes an electric power over a twisted-pair Ethernet cable to powered devices (PD), i.e., the MDU 304 and the CPE 306. In other words, the MDU 304 and the CPE 306 draws power from the set of HGW devices that are connected in an associated Local Area Network (LAN) interface, via the PoE cable 302.

[0094] Further, the CPE 306 may be configured to establish a CPE IP PDU session with the telecommunication network 106, for example, the 5G core network. For this, the CPE 306 sends a CPE IP PDU session request corresponding to the CPE IP PDU session to a UPF 310 and an AMF 320.

[0095] In an embodiment, a base station 308 is configured to receive the CPE IP PDU session request from the CPE 306 and transmit the CPE IP PDU to the UPF 310 and the AMF 320.

[0096] The UPF 310 is configured for interacting with the SMF 314 over N4 interface. The SMF 314 is configured for interacting with a PCF 316, a CHF 318, an AMF 320 and an UDM 322, and vice versa. The AMF 320 is configured for interactingwith the SMF 314, UDM 322 and an AUSF 324, and vice versa. The AUSF 324 is configured for interacting with the UDM 322 and vice versa.

[0097] Once the CPE IP PDU session is created, multiple HGW child sessions, i.e., multiple HGW sessions are created corresponding to the set of HGW devices, i.e., the HGW-1 device, the HGW-2 device, the HGW- 3 device, up to, the HGW -10 device. Each of an HGW child session corresponding to the set of HGW devices are created over the CPE IP PDU session. In an embodiment, the N4 session refers to a session between the SMF 314 and the UPF 310 over an N4 session interface in the 5G network (i.e., the internet 312). This N4 session interface is used for creating and managing data sessions. Further, the multiple HGW child sessions are created to enable each HGW of the set of HGW devices to interact with the internet 312 over the CPE IP PDU session. In an embodiment, the multiple HGW child sessions are created by assigning a unique PDR ID to each of the HGW child session over the N4 interface.

[0098] Further, the SMF 314 creates distinct N7 and N40 sessions with the PCF 316 and the CHF 318, respectively, for the CPE 306 and each of the HGW child session. In an embodiment, the N7 session refers to a session between the SMF 314 and the PCF 316 in the 5G network over N7 session interface. This N7 session interface is utilized for policy control and enforcement related to session management. Further, the N40 session as used herein refers to a session between the SMF 314 and the CHF 318 over N40 session interface in the 5G network. This N40 session interface is used for managing charging data related to network usage.

[0099] FIG. 4 illustrates an exemplary sequence diagram representing a process 400 for creating the one or more sessions in the telecommunication network 106, in accordance with embodiments of the present disclosure.

[0100] The present FIG. 4 depicts the interactions among various network functions, including a HGW 402, the CPE 306, the AMF 320, the SMF 314, the UPF310, the PCF 316, the UDM / AUSF 322 / 324, and the CHF 318. These interactions may help to create multiple child HGW sessions under the single parent CPE IP PDU session in the telecommunication network 106.

[0101] The process 400 begins with the CPE 306 registering with the network at step 404.

[0102] At step 406, a N4 session for the CPE 306 is established between the SMF 314 and the UPF 310.

[0103] Once the N4 session is established, at step 408, a CPE IP PDU session request is initiated, leading to the establishment of the CPE IP PDU session.

[0104] Further, at step 410, the SMF 314 proceeds to associate and subscribe to the CPE Session Management (SM) policy with the PCF 316. During the association phase, the SMF 314 identifies the CPE IP PDU session context and shares relevant session parameters with the PCF 316, such as the Session ID, user subscription profile, requested QoS parameters, Data Network Name (DNN), and Slice / Service Type (SST / SD). The PCF 316, in turn, evaluates applicable policy rules based on operator- defined configurations and subscriber-specific information retrieved from the UDM 322. This may result in the creation of the CPE policy session at step 412.

[0105] Simultaneously, the SMF 314 initiates the creation of the CPE charging session with the CHF 318 at step 414. During the charging session, the SMF 314 transmits a Charging Data Request (CDR) to the CHF 318 over the N40 interface. This request contains charging-related parameters associated with the CPE IP PDU session, such as the Session ID, service usage type, Data Network Name (DNN), slice identifiers (SST / SD), and applicable charging characteristics. Upon receiving the request, the CHF 318 processes the provided information and creates a charging control session for the corresponding CPE 306. This session enables real-time monitoring, rating, and accounting of the data usage generated by the CPE 306. The CHF 318 mayalso provide the SMF 314 with charging policy rules, including reporting triggers, quota thresholds, or usage limits that must be enforced during the session.

[0106] At step 416, an Ethernet over Generic Routing Encapsulation (EoGRE) tunnel is established between the CPE 306 and the UPF 310. Further, at step 418, the HGW 402 initiates a Dynamic Host Configuration Protocol (DHCP) Discover or DHCPv6 Solicit message, which is transferred over the EoGRE tunnel. The DHCP Discover message refers to a broadcast message sent by the HGW 402 in an IPv4 environment to discover available DHCP servers and request IP configuration parameters such as IP address, subnet mask, and gateway. Alternatively, in an IPv6 environment, the HGW 402 may initiate a DHCPv6 Solicit message, which is used to locate DHCPv6 servers capable of assigning IPv6 addresses and providing associated network configuration data. These messages enable the HGW 402 to dynamically obtain necessary network information for establishing connectivity with the core network through the EoGRE tunnel. In an embodiment, the EoGRE tunnel is necessary to transport an Ethernet frames of the HGW 402 to the core network. The EoGRE represents an advanced form of Generic Routing Encapsulation (GRE), wherein the underlying Ethernet header is also transparently transmitted within the GRE tunnel. In addition to EoGRE, other tunneling protocols capable of transporting the underlying Ethernet header may also be utilized, such as Ethernet Over Internet Protocol (EoIP), Ethernet over Multiprotocol Label Switching (EoMPLS), and the like. EoIP refers to a network tunneling protocol that encapsulates Layer 2 Ethernet frames within Layer 3 IP packets. EoIP is typically used in scenarios where traditional Ethernet bridging is required over wide-area IP links, allowing remote sites to appear as if they are part of the same broadcast domain. EoMPLS refers to Multiprotocol Label Switching, which may be employed in IP transport networks. The EoMPLS is a tunneling method where the Ethernet frames are encapsulated using MPLS labels for transmission over an MPLS-enabled transport network. EoMPLS is particularly useful in service providerenvironments where high-performance Ethernet connectivity is needed across geographically distributed sites.

[0107] Subsequently, at step 422, the SMF 314 receives a session report request from UPF 310 mentioning the HGW Identity (MAC address). The purpose of the session report request is to notify the SMF 314 about a new or modified data session associated with the HGW 402.

[0108] Upon receiving the session report request, the SMF 314 initiates the creation of the HGW policy session with the PCF 316 at step 420. Following this, at step 424, the SMF 314 sends a session report response to the UPF 310. The session report response serves as an acknowledgment and instruction message following the successful processing of the session report request the session report response may include updated or newly assigned Packet Detection Rule (PDR) or other session parameters required for the UPF 310 to properly handle and forward subsequent data packets associated with the HGW 402.

[0109] At step 426, the SMF 314 then exchanges session modification request / response message with UPF 310 to create the HGW child session for each of the HGW 402 by assigning separate Packet Detection Rules (PDR), Usage Reporting Rules (URR), QoS Enforcement Rule (QER) and Forwarding Action Rules (FAR) IDs. The PDR ID refers to the identifier of a Packet Detection Rule, which specifies how to recognize and match specific uplink / downlink packets (e.g., by source / destination IP address, port, MAC, etc.). The URR ID refers to the identifier of a Usage Reporting Rule, which defines how traffic usage (volume, time, etc.) should be measured and reported for charging or analytics purposes. The QER ID refers to the identifier of a QoS Enforcement Rule, which dictates Quality of Service (QoS) parameters like bitrate limits, priority levels, and traffic handling behavior. The FAR ID refers to the identifier of a Forwarding Action Rule, which describes what forwarding action the UPF 310should apply to the matched packet, such as forwarding, dropping, or buffering, and to which interface or tunnel the packet should be routed.

[0110] After the session modification done between the SMF 314 and the UPF 310, the HGW policy session is updated at step 428 between the SMF 314 and the PCF 316 to update the HGW IP address to the PCF 316. This update is sent by the SMF 314 to the PCF 316.

[0111] Simultaneously, at step 430, the SMF 314 creates the HGW charging session with the CHF 318. In other words, upon receiving the HGW child session update request, the SMF 314 updates both the HGW policy session and the HGW charging session, as separate PDR, FAR, and URR are provided for the HGW session from the SMF 314 to the UPF 310.

[0112] Finally, at step 434, the DHCP process continues with the HGW 402 receiving a DHCP Offer or DHCPv6 advertise message (at step 432). This is followed by the HGW 402 sending a DHCP Request or DHCPv6 request message.

[0113] The process 400 terminates at step 436 with the HGW 402 receiving a DHCP acknowledgement or DHCPv6 reply from the UPF 310.

[0114] FIG. 5 illustrates an exemplary flow chart of a method 500 for creating the one or more sessions in the telecommunication network 106, in accordance with an embodiment of the present disclosure. FIG. 5 is explained with reference to FIG. 2.

[0115] The method 500, at step 502 includes receiving, by a receiving unit 202, a session request corresponding to a CPE session, from a CPE. In some embodiments, prior to receiving the CPE IP PDU session request, the method 500 includes receiving, by the receiving unit 202, a registering request corresponding to the CPE. In response to receiving the registering request, the method 500 includes registering the CPE withthe processing unit 208. Upon registering, enabling, by the processing unit 208, the CPE to initiate the session request corresponding to the CPE session

[0116] In response to receiving the session request, the method 500, at step 504, includes establishing, by the processing unit 208, the session corresponding to the CPE in the telecommunication network 106. In some embodiments, the session request is a Internet Protocol (IP) Protocol Data Unit (PDU) session request, and the session is a CPE IP PDU session. In some embodiments, the method 500 includes establishing, by the processing unit 208, a CPE policy session and a CPE charging session with a PCF and a CHF, respectively.

[0117] The method 500, at step 506, upon establishing the CPEsession, receiving, by the receiving unit 208, a Home Gateway (HGW) session request corresponding to an HGW child session for each of a set of HGW devices over the CPE session. In some embodiments, the HGW child session is an Ethernet session.

[0118] The method 500, at step 508, includes assigning, by the processing unit 208, a unique PDR ID to each of a set of the HGW child session associated with the set of HGW devices based on the HGW session request. In some embodiments, the set of HGW devices is connected to the CPE through the MDU.

[0119] The method 500, at step 510 includes creating, by the processing unit 208, the HGW child session corresponding to each of the set of HGW devices based on the unique PDR ID. In some embodiments, to create the HGW child session, the method 500 includes creating, by the processing unit 208, a HGW policy session and a HGW charging session with the PCF and the CHF, respectively.

[0120] In some embodiments, the method 500 includes receiving, by the receiving unit 202, a HGW session update request corresponding to the HGW child session associated with an HGW device of the set of HGW devices, and updating, by the processing unit 208, the HGW child session associated with the HGW device inresponse to receiving the HGW session update request. The HGW session update request may include one or more updated session parameters such as revised Quality of Service (QoS) attributes, modified traffic detection rules, updated Packet Detection Rule (PDR) Identifiers, Usage Reporting Rule (URR) parameters, or Forwarding Action Rule (FAR) definitions. Additionally, the update request may also carry session state information, identifiers for the target HGW, and signaling information required to synchronize the policy and charging sessions with the PCF and CHF respectively.

[0121] In some embodiments, to update the HGW child session, the method 500 includes modifying, by the processing unit 208, the unique PDR ID associated with the HGW child session. The SMF modifies the unique PDR ID. The SMF evaluates the updated session requirements, such as changes in traffic flow characteristics, QoS parameters, or application type and revise the PDR ID that reflects the updated detection and forwarding rules.

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

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

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

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

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

[0127] In an exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable mediumcomprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method for creating one or more sessions in a telecommunication network. A Consumer Premise Equipment (CPE) IP PDU session is created with a 5G core network, and over this PDU session, multiple child ethemet sessions of HGWs are created. The CPE IP PDU session and all the associated HGW ethernet session are created over single N4 session between a UPF and a SMF. Further, the SMF creates independent N7 and N40 sessions with a PCF and a CHF respectively for parent CPE session and child HGW sessions.

[0128] The present disclosure provides a technical advancement in the field of session management and resource optimization within 5G telecommunication networks. By enabling the creation of multiple Home Gateway (HGW) Ethernet child sessions over a single Customer Premise Equipment (CPE) IP Protocol Data Unit (PDU) parent session, the system introduces a scalable and efficient session multiplexing mechanism. The use of unique Packet Detection Rule (PDR) Identifiers (ID) for each HGW session over the same N4 interface allows distinct data flows to be managed independently while reusing existing control plane resources. Furthermore, the dynamic establishment of separate N7 and N40 sessions for each HGW child session ensures individualized policy and charging control without the overhead of separate parent sessions. This architectural leads to significant reductions in signaling load, optimal utilization of UPF data-plane resources, and simplified integration with Multiple Dwelling Unit (MDU) deployments. Overall, the system and the method enhance network scalability, operational efficiency, and service differentiation capabilities in multi-tenant broadband environments.

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

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

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

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

[0133] The present disclosure provides a system that efficiently manages multiple child home gateway (HGW) Ethernet sessions over a single parent ConsumerPremise Equipment (CPE) Internet Protocol (IP) Packet Data Unit (PDU) session established by the CPE, thereby optimizing the utilization of a User Plane Function (UPF) data-plane resources.

[0134] The present disclosure enables a Session Management Function (SMF) to maintain independent N7 and N40 sessions with a Policy Control Function (PCF) and a Charging Function (CHF) for both the parent CPE IP PDU session and each child HGW session, ensuring precise policy and charging management, and enhancing network control and billing accuracy.

[0135] The present disclosure provides a simplified session lifecycle management architecture by reducing signaling overhead between control plane functions, thereby improving scalability and responsiveness in high-density deployment scenarios.

[0136] The present disclosure enables differentiated Quality of Service (QoS) and policy enforcement per HGW session, allowing service providers to tailor network behavior to individual households or services while maintaining a unified data communication path.

[0137] The present disclosure enables the creation of a parent CPE IP PDU session, allowing for a single, unified uplink and downlink transport path to be established in the 5G core network. This reduces the need for per-HGW IP session establishment, thereby minimizing signaling overhead and improving scalability.

[0138] The present disclosure further enables the creation of individual HGW child Ethernet-over-GRE (EoGRE) sessions behind the created parent CPE IP PDU session, each mapped with a unique PDR ID. This facilitates per-HGW session identification, differentiated policy enforcement, and charging, while efficiently utilizing a common N4 user-plane path and IP PDU session.

Claims

CLAIMS1. A method (500) for creating one or more sessions in a telecommunication network (106), the method (500) comprising: receiving (502), by a receiving unit (202), a session request corresponding to a CPE session, from a CPE; establishing (504), by a processing unit (208), the session corresponding to the CPE in the telecommunication network, in response to receiving the session request; upon establishing the session, receiving (506), by the receiving unit (202), a Home Gateway (HGW) session request corresponding to an HGW child session for each of a set of HGW devices over the CPE session; assigning (508), by a processing unit (208), a unique Packet Detection Rule (PDR) Identifier (ID) to each of the HGW child sessions associated with the set of HGW devices based on the HGW session request; and creating (510), by the processing unit (208), the HGW child session corresponding to each of the set of HGW devices based on the unique PDR ID.

2. The method (500) as claimed in claim 1, wherein each of the set of HGW devices is connected to the CPE through a Multiple Dwelling Unit (MDU).

3. The method (500) as claimed in claim 1, wherein the session request is an Internet Protocol (IP) Protocol Data Unit (PDU) session request, and wherein the session is a CPE IP PDU session, and the HGW child session is an Ethernet session.

4. The method (500) as claimed in claim 1, further comprising: receiving, by the receiving unit (202), a registering request corresponding to the CPE; registering the CPE with the processing unit (208), in response to receiving the registering request; andupon registering, enabling, by the processing unit (208), the CPE to initiate the session request corresponding to the CPE session.

5. The method (500) as claimed in claim 3, wherein establishing the IP PDU session comprises: establishing, by the processing unit (208), a CPE policy session and a CPE charging session with a Policy Control Function (PCF) and a Charging Function (CHF), respectively.

6. The method (500) as claimed in claim 1, wherein creating the HGW child session comprises: creating, by the processing unit (208), a HGW policy session and a HGW charging session with the PCF and the CHF, over an N7 interface and an N40 interface respectively.

7. The method (500) as claimed in claim 1, further comprising: receiving, by the receiving unit (208), a HGW session update request corresponding to an HGW child session associated with an HGW device of the set of HGW devices; and updating, by the processing unit (208), the HGW child session associated with the HGW device in response to receiving the HGW session update request.

8. The method (500) as claimed in claim 7, wherein updating the HGW child session comprises modifying, by the processing unit (208), the unique PDR ID associated with the HGW child session.

9. A system (108) for creating one or more sessions in a telecommunication network (106), the system (108) comprising: a receiving unit (202) configured to receive a session request corresponding to a CPE session from a CPE;a processing unit (208) configured to establish the session corresponding to the CPE in the telecommunication network (106), in response to receiving the session request; the receiving unit (202) is configured to receive a Home Gateway (HGW) session request corresponding to an HGW child session for each of a set of HGW devices over the CPE session, upon establishing the session; the processing unit (208) is configured to assign a unique Packet Detection Rule (PDR) Identifier (ID) to each of the HGW child sessions associated with the set of HGW devices based on the HGW session request; and the processing unit (208) is configured to create the HGW child session corresponding to each of the set of HGW devices based on the unique PDR ID.

10. The system (108) as claimed in claim 9, wherein each of the set of HGW devices is connected to the CPE through a Multiple Dwelling Unit (MDU).

11. The system (108) as claimed in claim 9, wherein the session request is an Internet Protocol (IP) Protocol Data Unit (PDU) session request, and wherein the session is a CPE IP PDU session, and the HGW child session is an Ethernet session.

12. The system (108) as claimed in claim 9, wherein: the receiving unit (202) is configured to receive a registering request corresponding to the CPE; in response to receiving the registering request, register the CPE with the processing unit (208); and the processing unit (208) is configured to enable the CPE to initiate the session request corresponding to the CPE session, upon registering.

13. The system (108) as claimed in claim 11, wherein to establish the IP PDU session, the processing unit (208) is configured to establish a CPE policy session anda CPE charging session with a Policy Control Function (PCF) and a Charging Function (CHF), respectively.

14. The system (108) as claimed in claim 9, wherein to create the HGW child session, the processing unit (208) is configured to create a HGW policy session and a HGW charging session with the PCF and the CHF, over an N7 interface and an N40 interface respectively.

15. The system (108) as claimed in claim 9, wherein: the receiving unit (202) is configured to receive a HGW session update request corresponding to an HGW child session associated with an HGW device of the set of HGW devices; and the processing unit (208) is configured to update the HGW child session associated with the HGW device in response to receiving the HGW session update request.

16. The system (108) as claimed in claim 15, wherein to update the HGW child session, the processing unit (208) is configured to modify the unique PDR ID associated with the HGW child session.

17. A computer program product comprising a non- transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform a method (500) for creating sessions in a telecommunication network (106), the method (500) comprising: receiving (502), by a receiving unit (202), a session request corresponding to a CPE session, from a CPE; establishing (504), by a processing unit (208), the session corresponding to the CPE in the telecommunication network, in response to receiving the session request; upon establishing the session, receiving (506), by the receiving unit (202), a Home Gateway (HGW) session request corresponding to an HGW child session for each of a set of HGW devices over the CPE session;assigning (508), by a processing unit (208), a unique Packet Detection Rule (PDR) Identifier (ID) to each of the HGW child sessions associated with the set of HGW devices based on the HGW session request; and creating (510), by the processing unit (208), the HGW child session corresponding to each of the set of HGW devices based on the unique PDR ID.

Images