System and method for internet protocol (IP) allocation based on a type allocation code (TAC)

Abstract

The present disclosure provides a system (108) and a method (500, 600) for internet protocol (IP) allocation based on a user equipment's type allocation code (TAC) in a network (106). The system (108) includes a session management function (SMF) (210) and a user plane function (UPF) (214). The SMF (210) receives a session establishment request from the UE (104), including an identifier such as International Mobile Equipment Identity (IMEI) or Permanent Equipment Identifier (PEI), and transmits the identifier to the UPF (214). The UPF (214) extracts the TAC from the identifier, compares it with one or more predefined TACs associated with dedicated IP address pools, and allocates an IP address to the UE (104) accordingly. When the TAC does not match, the UPF (214) assigns the IP address from a general pool based on a data network name (DNN) or network slice.

Description

SYSTEM AND METHOD FOR INTERNET PROTOCOL (IP) ALLOCATION BASED ON A TYPE ALLOCATION CODE (TAC)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 (JPL) or its affiliates (hereinafter referred as owner). The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all rights whatsoever. All rights to such intellectual property are fully reserved by the owner.TECHNICAL FIELD

[0002] The present disclosure relates generally to the field of telecommunications. In particular, the present disclosure relates to a system and a method for internet protocol (IP) allocation based on type allocation code (TAC) in a network.DEFINITIONS

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

[0004] The term “Network Function (NF)” used hereinafter in the specification refers to a modular component in a network that performs specific tasks such as data processing, service management, and user interactions.

[0005] The term “Unified Data Management (UDM)” used hereinafter in the specification refers to a network function responsible for managing and storing subscription data and network-related information in a centralized manner.

[0006] The term “Access and Mobility Management Function (AMF)” used hereinafter in the specification refers to a network function responsible for handling UE registration, authentication, mobility management, and connection management.

[0007] The term “Session Management Function (SMF)” used hereinafter in the specification refers to a network function responsible for managing Protocol Data Unit (PDU) sessions, including session establishment, modification, and release.

[0008] The term “User Plane Function (UPF)” used hereinafter in the specification refers to a network function responsible for handling user plane data, including packet routing, forwarding, QoS handling, and traffic reporting.

[0009] The term “Authentication Server Function (AUSF)” used hereinafter in the specification refers to a network function responsible for authentication of user equipment to ensure security of network access.

[0010] The term “Unified Data Repository (UDR)” used hereinafter in the specification refers to a network repository function that stores subscription data, policy data, and application-related information.

[0011] The term “Network Repository Function (NRF)” used hereinafter in the specification refers to a network function in the 5G Core (5GC) responsible for service discovery and management of available network functions.

[0012] The term “Packet Forwarding Control Protocol (PFCP)” used hereinafter in the specification refers to a control protocol used between the control plane and user plane to manage packet forwarding, session handling, and resource allocation.

[0013] The term “Type Allocation Code (TAC)” used hereinafter in the specification refers to the first eight digits of the IMEI, which uniquely identify the type and model of a User Equipment (UE).

[0014] The term “International Mobile Equipment Identity (IMEI)” used hereinafter in the specification refers to a unique identifier assigned to mobile devices, used by networks to identify and manage the UE.

[0015] The term “Permanent Equipment Identifier (PEI)” used hereinafter in the specification refers to a permanent identifier to uniquely identify the UE accessing the network.

[0016] The term “Nudr interface” used hereinafter in the specification refers to a service-based interface used by network functions to access data stored in the UDR.

[0017] The term “Nudm interface” used hereinafter in the specification refers to a service-based interface provided by the UDM to expose subscription and policy- related services to other network functions.

[0018] The term “Nausf interface” used hereinafter in the specification refers to a service- based interface provided by the AUSF to expose authentication services to other network functions.

[0019] The term “Namf interface” used hereinafter in the specification refers to a service-based interface provided by the AMF to expose registration, mobility, and connection management services.

[0020] The term “Nsmf interface” used hereinafter in the specification refers to a service-based interface provided by the SMF to expose PDU session management services.

[0021] The term “Nnrf interface” used hereinafter in the specification refers to a service-based interface provided by the NRF to enable service discovery and NF registration.

[0022] The term “Data Network Name (DNN)” used hereinafter in the specification refers to a unique identifier that specifies a particular data network or service in a telecommunications system.

[0023] The term “Packet Detection Rule (PDR)” used hereinafter in the specification refers to a set of rules maintained by the UPF to identify and classify user traffic flows. Each PDR specifies conditions such as packet filters, forwarding actions, and associated QoS treatment, enabling the UPF to process packets in accordance with session requirements.

[0024] The term “Prefix” used hereinafter in the specification refers to a portion of an Internet Protocol (IP) address that represents a block of addresses or an address range. Prefixes are used in IP networking for routing and allocation purposes, and in the context, may be allocated to the UE to support efficient addressing and aggregation.

[0025] The term “Traffic endpoint” used hereinafter in the specification refers to a logical termination point for user-plane traffic within the UPF. Traffic endpoints are associated with IP addresses or prefixes and facilitate the handling of uplink and downlink flows by mapping them to the correct PDRs.

[0026] The term “Internet Protocol version 4 (IPv4)” used hereinafter in the specification refers to a 32-bit addressing scheme for uniquely identifying devices in a network. IPv4 addresses are typically represented in dotted-decimal notation and are widely used for packet-based communication.

[0027] The term “Internet Protocol version 6 (IPv6)” used hereinafter in the specification refers to a 128-bit addressing scheme designed as the successor to IPv4,enabling a significantly larger address space and improved routing efficiency. IPv6 addresses are typically represented in hexadecimal notation separated by colons, and support advanced features such as stateless address autoconfiguration and enhanced security.

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

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

[0030] In telecommunication, an internet protocol (IP) may be a fundamental structure and operation of modern networks. The modern network includes an internet, private networks and other communication systems. The IP may be responsible for addressing, routing, and delivering data packets between devices across different networks. The IP provides IP addresses for devices on the network. An IP packet may be used to send data across the devices within the network. The IP packet may contain both the IP address of a sender and receiver device. The IP addresses ensures that IP packets reach correct destination device in the network.

[0031] In a conventional approach, user devices were assigned with IP address of various versions, such as Internet protocol version 4 (IPv4), Internet protocol version 6 (IPv6) and Internet protocol version 4 and 6 (IPv4v6). The assignment of the IP address was as per the default data name network (DNN) settings. The assignment of the IP address based on DNN settings led to wastage of some addresses for a large set of user devices, as some of the user devices did not require both IPv4 and IPv6addresses. Also, assigning both IPv4 and IPv6 addresses to all the user devices may consume additional address space in the IP packets. Supporting both IPv4 and IPv6 address assignments simultaneously was complex, as both assigning and routing schemes were different.

[0032] Further, the network system may face a shortage of IPv4 addresses due to unnecessary assignment of IPv4 addresses to user devices that require IPv6 address. The network system may have complexity in managing both IPv4 and IPv6 address for each of the devices in the network. The usage of both IPv4 and IPv6 address for all the user devices may also raise security vulnerability issues in the network system.

[0033] Therefore, there is a need for a system and a method that overcomes the limitations of the prior art.OBJECTIVES OF THE DISCLOSURE

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

[0035] An objective of the present disclosure is to provide a system and a method for allocating an internet protocol (IP) address to a user equipment (UE) in a network based on type allocation code (TAC).

[0036] Another objective of the present disclosure is to provide a system and a method for assigning IP address based on international mobile equipment identity (IMEI) for efficient management of the UE.

[0037] Another objective of the present disclosure is to provide a system and a method for allocating IP address or prefix in a user plane function (UPF).

[0038] Yet another objective of the present disclosure is to provide a system and a method for allocating IP address based on IP version type according to the UE.

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

[0040] In an exemplary embodiment, a method for allocating an internet protocol (IP) address to a user equipment (UE) in a network is disclosed. The method includes receiving, by a session management function (SMF), at least one request from the UE to establish a session. The at least one request comprises at least one information element (IE). The method includes transmitting, by the SMF, the at least one received IE to a user plane function (UPF). The method includes extracting, by the UPF, at least one identifier from the at least one transmitted IE. The method includes detecting, by the UPF, at least one type allocation code (TAC) from the at least one extracted identifier. The method includes comparing, by the UPF, the at least one detected TAC with one or more predefined TACs associated with corresponding IP addresses stored in a first IP pool. The method includes allocating, by the UPF, the IP address to the UE from the first IP pool when the at least one detected TAC matches one of the one or more predefined TACs in the first IP pool.

[0041] In some embodiments, the at least one information element (IE) comprises a user identifier, a quality of service (QoS) parameter, a session type, a user location, an access point name (APN), a network service type, and a configuration type.

[0042] In some embodiments, the at least one identifier is one of an International Mobile Equipment Identity (IMEI) and a Permanent Equipment Identifier (PEI).

[0043] In some embodiments, the method further includes assigning, by the UPF, the IP address to the UE from a second pool, designated to a data network node(DNN) or a network slice, when the at least one detected TAC fails to match any of the one or more predefined TACs in the first IP pool.

[0044] In some embodiments, the assigned IP address is selected from an internet protocol version 4 (IPv4) address, an internet protocol version 6 (IPv6) address or a combination thereof.

[0045] In some embodiments, the method further includes storing, by the UPF, a record of at least one detected TAC, at least one corresponding identifier of the UE and at least one allocated IP address in the first IP pool.

[0046] In another exemplary embodiment, a system for allocating an internet protocol (IP) address to a user equipment (UE) in a network is disclosed. The system includes a session management function (SMF) configured to receive at least one request from the UE to establish a session. The at least one request comprises at least one information element (IE). The SMF is further configured to transmit the at least one received IE to a user plane function (UPF). The UPF is configured to extract at least one identifier from the at least one transmitted IE. The UPF is further configured to detect at least one type allocation code (TAC) from the at least one extracted identifier. The UPF is further configured to compare the at least one detected TAC with one or more predefined TACs associated with corresponding IP addresses stored in a first IP pool. The UPF is further configured to allocate the IP address to the UE from the first IP pool when the at least one detected TAC matches one of the one or more predefined TACs in the first IP pool.

[0047] In another exemplary embodiment, a method for allocating an Internet Protocol (IP) address or prefix in a user plane function (UPF) is disclosed. The method includes receiving, by the UPF, a first request from a control plane (CP) function to allocate a user equipment (UE) IP address or prefix. The first request comprises a UE IP address information element (IE) comprising one or more IP version flags, whereinthe one or more IP version flags comprises an IPv4 flag and / or an IPv6 flag. The first request further comprises a network instance IE indicating an IP address pool from which the UE IP address or prefix is to be allocated. The method includes determining, by the UPF, an IP version selected from one or both of an IPv4 address and / or an IPv6 address, to be allocated, based on the IPv4 flag and / or the IPv6 flag included in the UE IP address IE. The method includes selecting, by the UPF, the UE IP address or prefix corresponding to the determined IP version from the IP address pool, indicated by the network instance IE in the first request. The method includes allocating, by the UPF, the selected UE IP address or prefix to one or more packet detection rules (PDRs) and / or traffic endpoints to be created or modified, in response to the first request.

[0048] In some embodiments, the first request is selected from at least one of a packet forwarding control protocol (PFCP) session establishment request or a PFCP session modification request.

[0049] In some embodiments, the response is selected from at least one of a PFCP session establishment response or a PFCP session modification response.

[0050] In some embodiments, upon determining that both the IPv4 flag and the IPv6 flag are included in the UE IP address IE, the UP function allocates at least one of the IPv4 address, the IPv6 address, or a combination thereof based on an operator policy. The operator policy is determined based on at least one of a locally configured international mobile equipment identity type allocation code (IMEI TAC) and a protocol data unit (PDU) session type mapping.

[0051] In some embodiments, receiving, by the UPF, the first request from the CP function to allocate the UE IP address or prefix comprises receiving a single request to allocate a same UE IP address or prefix to a plurality of PDRs to be created or modified, wherein each of the plurality of PDRs comprises a UE IP address IEcomprising one or more IP version flags, indicating the request to allocate the same UE IP address or prefix to the plurality of PDRs.

[0052] In some embodiments, the receiving, by the UPF, the first request from the CP function to allocate the UE IP address or prefix comprises receiving a request to allocate a same UE IP address or prefix to a plurality of PDRs to be created or modified. The request comprises a create traffic endpoint IE or an update traffic endpoint IE, wherein the create traffic endpoint IE or the update traffic endpoint IE comprises a UE IP Address IE with one or more IP version flags indicating a selection of a new UE IP address or prefix. The further request comprises the plurality of PDRs to be created or modified, each comprising a traffic endpoint identity (ID), wherein an inclusion of the traffic endpoint ID in each of the plurality of PDRs and a use of one or more IP version flags in the UE IP Address IE of the traffic endpoint IE, enable the UPF to allocate the same UE IP address or prefix to the plurality of PDRs.

[0053] In some embodiments, the first request further comprises a UE IP address pool identity indicating the IP address pool for allocation of the UE IP address or prefix by the UPF.

[0054] In some embodiments, the method further comprises receiving, by the UPF, a second request selected from at least one of: a request to delete a PF CP session; a request to delete the traffic endpoint associated with the allocated UE IP address or prefix; and a request to remove a packet detection rule (PDR) associated with the allocated UE IP address or prefix. The method further comprises deallocating, by the UPF, the UE IP address or prefix allocated to at least one of the PFCP session, the traffic endpoint, and the PDR in response to the second request.

[0055] In some embodiments, the method further comprises receiving, by the UPF, a third request from the CP function to allocate an additional UE IP address or prefix. The request comprises at least one of: an update PDR IE or an update trafficendpoint IE. The additional UE IP address or prefix is different from the UE IP address or prefix allocated in response to the first request.

[0056] In some embodiments, the method further comprises selecting, by the UPF, the UE IP address or prefix based on one or more of a single network slice selection assistance information (S-NSSAI) associated with a PFCP session, the network instance IE, and a UE IP address pool identity; and allocating, by the UPF, the UE IP address or prefix based on the selection.

[0057] In some embodiments, the method further comprises transmitting, by the UPF, a response to the CP function. The response comprises at least one UE IP address IE having a list of IP addresses or prefixes allocated to each of the one or more PDRs and / or the traffic endpoints, in response to creation or modification of the one or more PDRs or the traffic endpoints.

[0058] In another exemplary embodiment, a system for allocating an Internet Protocol (IP) address or prefix in a user plane function (UPF) is disclosed. The system includes the UPF configured to receive a first request from a control plane (CP) function to allocate a UE IP address or prefix. The first request comprises a user equipment (UE) IP address information element (IE) comprising one or more IP version flags, the one or more IP version flags comprise an IPv4 flag and / or an IPv6 flag. The first request further comprises a network instance IE, indicating an IP address pool from which the UE IP address or prefix is to be allocated. The UPF is further configured to determine an IP version selected from one or both of an IPv4 address and / or an IPv6 address, to be allocated, based on the IPv4 flag and / or the IPv6 flag included in the UE IP address IE. The UPF is further configured to select the UE IP address or prefix corresponding to the determined IP version from the IP address pool, indicated by the network instance IE in the first request. The UPF is further configured to allocate the selected UE IP address or prefix to one or more packet detection rules(PDRs) and / or traffic endpoints to be created or modified, in response to the first request.

[0059] In another exemplary embodiment, a user equipment (UE) communicatively coupled with a network is disclosed. The coupling comprises steps of: receiving a connection request; sending an acknowledgment of the connection request to the network; and transmitting a plurality of signals in response to the connection request. The UE is connected with a system configured to allocate an internet protocol (IP) address to the UE.

[0060] In another exemplary embodiment, a user equipment (UE) communicatively coupled with a network is disclosed. The coupling comprises steps of: receiving a connection request; sending an acknowledgment of the connection request to the network; and transmitting a plurality of signals in response to the connection request. The UE is connected with a system configured to allocate an internet protocol (IP) address or prefix in a user plane function (UPF).

[0061] In another exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for allocating an internet protocol (IP) address to a user equipment (UE) in a network. The method includes receiving, by a session management function (SMF), at least one request from the UE to establish a session. The at least one request comprises at least one information element (IE). The method includes transmitting, by the SMF, the at least one received IE to a user plane function (UPF). The method includes extracting, by the UPF, at least one identifier from the at least one transmitted IE. The method includes detecting, by the UPF, at least one type allocation code (TAC) from the at least one extracted identifier. The method includes comparing, by the UPF, the at least one detected TAC with one or more predefined TACs associated with corresponding IP addresses stored in a first IP pool. The methodincludes allocating, by the UPF, the IP address to the UE from the first IP pool when the at least one detected TAC matches one of the one or more predefined TACs in the first IP pool.

[0062] In yet another exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for allocating an Internet Protocol (IP) address or prefix in a user plane function (UPF). The method includes receiving, by the UPF, a first request from a control plane (CP) function to allocate a user equipment (UE) IP address or prefix. The first request comprises a UE IP address information element (IE) comprising one or more IP version flags, wherein the one or more IP version flags comprises an IPv4 flag and / or an IPv6 flag. The first request further comprises a network instance IE indicating an IP address pool from which the UE IP address or prefix is to be allocated. The method includes determining, by the UPF, an IP version selected from one or both of an IPv4 address and / or an IPv6 address, to be allocated, based on the IPv4 flag and / or the IPv6 flag included in the UE IP address IE. The method includes selecting, by the UPF, the UE IP address or prefix corresponding to the determined IP version from the IP address pool, indicated by the network instance IE in the first request. The method includes allocating, by the UPF, the selected UE IP address or prefix to one or more packet detection rules (PDRs) and / or traffic endpoints to be created or modified, in response to the first request.

[0063] 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.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

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

[0065] FIG. 1 illustrates an exemplary network architecture of a system for allocating an internet protocol (IP) address to a user equipment (UE) in a network, in accordance with an embodiment of the present disclosure.

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

[0067] FIG. 3 illustrates an exemplary architecture of the system, in accordance with an embodiment of the present disclosure.

[0068] FIG. 4 illustrates an exemplary flow diagram of a method for allocating the IP address to the UE in the network, in accordance with an embodiment of the present disclosure.

[0069] FIG. 5 illustrates another exemplary flow diagram of a method for allocating the IP address to the UE in the network, in accordance with an embodiment of the present disclosure.

[0070] FIG. 6 illustrates an exemplary flow diagram of a method for allocating the IP address or prefix in a user plane function (UPF), in accordance with an embodiment of the present disclosure.

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

[0072] 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 - System110- Central database200- Block diagram202- Unified Data Management (UDM)204- Authentication Server Function (AUSF)206- Unified Data Repository (UDR)208- Access and Mobility Management Function (AMF)210- Session Management Function (SMF)212- Network Repository Function (NRF)214- User Plane Function (UPF)216- interface(s)218 - Database 300- Exemplary Architecture302- Radio network304- Internet / data network400, 500, 600 - Flow Diagram700 - A computer system 710 - External Storage Device720 - Bus730 - Main Memory740 - Read Only Memory750 - Mass Storage Device 760 - Communication Port770 - ProcessorDETAILED DESCRIPTION

[0073] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding ofY1 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.

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

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

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

[0077] 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, such terms are intended to be inclusive like the term “comprising” as an open transition word without precluding any additional or other elements.

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

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

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

[0081] Wireless communication technology has rapidly evolved over the past few decades. The first generation of wireless communication technology was analog, offering only voice services. Further, text messaging and data services became possible when the second-generation (2G) technology was introduced. The third generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. The fourth generation (4G) technologyrevolutionized wireless communication with faster data speeds, improved network coverage, and security. Currently, fifth-generation (5G) technology is being deployed, offering significantly faster data speeds, lower latency, and the ability to connect many devices simultaneously. These advancements represent a significant leap forward from previous generations, enabling enhanced mobile broadband, improved Internet of Things (loT) connectivity, and more efficient use of network resources. The sixth generation (6G) technology promises to build upon these advancements, pushing the boundaries of wireless communication even further. While the 5G technology is still being rolled out globally, research and development into the 6G are rapidly progressing, with the aim of revolutionizing the way to connect and interact with technology.

[0082] In a network system, the allocation of IP addresses by a user plane function (UPF) based on default data name network (DNN) settings may be complex to manage and lead to IP address exhaustion (for example, IPv4). However, the conventional technique requires maintenance of a large number of IP ranges that may be cumbersome and error-prone. Thus, there is a need for a system and a method that can overcome the disadvantages of the conventional system.

[0083] According to the present disclosure, the allocation of IP addresses by the user plane function (UPF) is based on a type allocation code (TAC). The TAC may be extracted from an international mobile equipment number (IMEI) or permanent equipment identification (PEI) number. The type allocation code (TAC) may be the first eight digit of the IMEI number. The UPF may check if the TAC matches with the already provisioned TAC stored in the database. The UPF may allocate the IP from a dedicated IP data when the TAC matches with the provisioned TAC. Otherwise, the UPF may allocate the IP from a general IP data.

[0084] In an embodiment, the present disclosure provides a system and a method for allocating an internet protocol (IP) address to a user equipment (UE) in anetwork. The method includes receiving, by a session management function (SMF), at least one request from the UE to establish a session. The at least one request comprises at least one information element (IE). The method includes transmitting, by the SMF, the at least one received IE to a user plane function (UPF). The method includes extracting, by the UPF, at least one identifier from the at least one transmitted IE. The method includes detecting, by the UPF, at least one type allocation code (TAC) from the at least one extracted identifier. The method includes comparing, by the UPF, the at least one detected TAC with one or more predefined TACs associated with corresponding IP addresses stored in a first IP pool. The method includes allocating, by the UPF, the IP address to the UE from the first IP pool when the at least one detected TAC matches one of the one or more predefined TACs in the first IP pool.

[0085] In another embodiment, a method for allocating an Internet Protocol (IP) address or prefix in a user plane function (UPF) is disclosed. The method includes receiving, by the UPF, a first request from a control plane (CP) function to allocate a user equipment (UE) IP address or prefix. The first request comprises a UE IP address information element (IE) comprising one or more IP version flags, wherein the one or more IP version flags comprises an IPv4 flag and / or an IPv6 flag. The first request further comprises a network instance IE indicating an IP address pool from which the UE IP address or prefix is to be allocated. The method includes determining, by the UPF, an IP version selected from one or both of an IPv4 address and / or an IPv6 address, to be allocated, based on the IPv4 flag and / or the IPv6 flag included in the UE IP address IE. The method includes selecting, by the UPF, the UE IP address or prefix corresponding to the determined IP version from the IP address pool, indicated by the network instance IE in the first request. The method includes allocating, by the UPF, the selected UE IP address or prefix to one or more packet detection rules (PDRs) and / or traffic endpoints to be created or modified, in response to the first request

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

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

[0088] FIG. 1 illustrates an exemplary network architecture (100) of a system (108) for allocating an internet protocol (IP) address to a user equipment (UE) in a network based on type allocation code (TAC), in accordance with an embodiment of the present disclosure.

[0089] As illustrated in FIG. 1, the network architecture (100) may include one or more user equipment (UE) (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 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 collectively referred to as the UE (104). Although only three UE (104) are depicted in FIG. 1, however, any number of the UE (104) may be included without departing from the scope of the ongoing description.

[0090] 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 are not limited to, smartphones, smart watches, smart sensors (e.g., mechanical, thermal, electrical, magnetic, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart television (TV), computers, smart security system, smart home system, other devices for monitoring or interacting with or for the users (102) and / or entities, or any combination thereof. A person of ordinary skill in the artwill appreciate that the UE (104) may include, but not limited to, intelligent, multisensing, network-connected devices, that may integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

[0091] Additionally, in some embodiments, the UE (104) may include, but is not limited to, a handheld wireless communication device (e.g., a mobile phone, a smartphone, a phablet device, and so on), a wearable computer device (e.g., a headmounted display computer device, a head-mounted camera device, a wristwatch computer device, and so on), a Global Positioning System (GPS) device, a laptop computer, a tablet computer, or another type of portable computer, a media playing device, a portable gaming system, and / or any other type of computer device with wireless communication capabilities, and the like. In an embodiment, the UE (104) may include, but are not limited to, any electrical, electronic, electromechanical, or 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 touchpad, 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.

[0092] Referring to FIG. 1 , the UE (104) may communicate with a system (108) through a network (wireless communication network) (106) for sending or receiving various types of data. In an embodiment, the network (106) may include at least one of a fifth generation (5G) network, sixth generation (6G) network, or the like. The network (106) may enable the UE (104) to communicate with other devices in the networkarchitecture (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), the Internet, the Public Switched Telephone Network (PSTN), or the like.

[0093] In an embodiment, the network (106) may include, 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. The network (106) may also include, by way of example but not limitation, one or more of a wireless network, a wired network, 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.

[0094] In an embodiment, the UE (104) is communicatively coupled with the network ( 106). The network (106) may receive a connection request from the UE ( 104). The network (106) may send an acknowledgment of the connection request to the UE (104). The UE (104) may transmit a plurality of signals in response to the connection request. In an embodiment, the UE (104) is connected with the system (108) configured to allocate an IP address to the UE (104). In an alternative embodiment, the UE (104) is connected with the system (108) configured to allocate an IP address or prefix in a user plane function (UPF).

[0095] In an embodiment, the system (108) may communicate with a central database (110). In an aspect, the central database (110) may store data related to theUE (104). For example, the data may include a dedicated IP data. The dedicated IP data may include dedicated IP address for each of the UE (104) based on an IP version type. The dedicated IP data may include a plurality of IP addresses of different IP version type. The IP version type may include, but not be limited to, an internet protocol version 4 (IPv4), an internet protocol version 6 (IPv6) and an internet protocol version 4 and version 6 (IPv4v6). In another exemplary aspect, the data may be a general IP data. The general IP data may include general IP addresses for each of the UE (104). For example, the general IP data may include a plurality of internet protocol version 6 (IPv6).

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

[0097] FIG. 2 illustrates an exemplary block diagram (200) of the system (108), in accordance with an embodiment of the present disclosure.

[0098] Referring to FIG. 2, in an embodiment, the system (108) may include a unified data management (UDM) (202), an authentication server function (AUSF) (204), a user data repository (UDR) (206), an access and mobility management function (AMF) (208), a session management function (SMF) (210), a network repository function (NRF) (212), a user plane function (UPF) (214), a database (218) and one or more interfaces (216).

[0099] In an embodiment, the interface(s) (216) may include a variety of interfaces, for example, interfaces for data input and output devices (VO), storagedevices, and the like. The interface(s) (216) may facilitate communication through the system (108). The interface(s) (216) 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 UDM (202), the AUSF (204), the UDR (206), the AMF (208), the SMF (210), the NRF (212), the UPF (214) and a database (218).[000100] In an embodiment, the database (218) includes data that may be either stored or generated as a result of functionalities implemented by any of the components, including the UDM (202), the AUSF (204), the UDR (206), the AMF (208), the SMF (210), the NRF (212) and the UPF (214).[000101] In an embodiment, the UDM (202) is configured to store and provide subscription-related information, including identifiers such as PEI / IMEI, which are used by the SMF (210) to support TAC-based IP address allocation for the UE (104). The AUSF (204) is configured to authenticate the UE (104) during registration and ensures secure access to the network before the TAC-based IP allocation procedure is triggered. The UDR (206) is configured to store user subscription data, policy information, and device identifiers that can be accessed by the UDM (202) and other NFs to support IP allocation decisions in the UPF (214). The AMF (208) manages registration, authentication signaling, and mobility events, and forwards UE identifiers such as IMEI / PEI to the SMF (210) during session establishment. The SMF (210) receives session establishment requests from the UE (104), extracts the IMEI / PEI, and transmits this information to the UPF (214) over PF CP to enable TAC-based IP allocation. The NRF (212) enables service discovery and ensures that the SMF (210) and UPF (214) may dynamically discover each other’s capabilities, including support for TAC-based IP allocation policies. The term “support” refers to the ability of the SMF (210) and UPF (214) to recognize, advertise, and enforce specific operational features. In particular, the support for TAC-based IP allocation policies signifies that the SMF (210) and UPF (214) are configured to allocate IP addresses based onpredefined rules that map TAC values to corresponding IP address pools. Such TAC- based IP allocation policies enable differentiated IP assignment strategies across device categories, thereby allowing optimized network resource utilization, enhanced service differentiation, and improved address management across the 5G core network. The UPF (214) is configured to extract the TAC from the IMEI / PEI, compare it with predefined TAC entries, and allocate an IP address from a dedicated TAC-based pool or a general pool depending on the match.[000102] In order to allocate the IP address to the UE (104) in the network (106), the SMF (210) is configured to receive at least one request from the UE (104) to establish a session (e.g., a PDU session). The PDU session establishment is a procedure defined in the 5G core network architecture for enabling user-plane connectivity between the UE (104) and a data network. In an embodiment, the at least one request includes at least one information element (IE). The at least one IE includes a user identifier, a quality of service (QoS) parameter, a session type, a user location, an access point name (APN), a network service type, and a configuration type.[000103] In an embodiment, the user identifier refers to an identifier, such as an International Mobile Subscriber Identity (IMSI), Globally Unique Temporary Identifier (GUTI), or Subscription Permanent Identifier (SUPI), which uniquely identifies the UE (104) within the network (106) and is used for correlating session information with the subscriber. Further, the QoS parameter refers to information defining service quality requirements for the session, including priority level, guaranteed bit rate (GBR), non-GBR, latency, and packet loss tolerances, which are utilized by the SMF (210) and UPF (214) for establishing traffic handling rules. Further, the session type refers to the requested type of session, which may include an Internet Protocol version 4 (IPv4) session, an Internet Protocol version 6 (IPv6) session, or a dual-stack (IPv4v6) session, thereby defining the address family to be allocated to the UE (104). Further, the user location refers to location information ofthe UE (104), such as Tracking Area Identifier (TAI) or Cell Global Identifier (CGI), which provides contextual information regarding the access network used for the session establishment. Further, the APN refers to a logical identifier that specifies the data network to which the PDU session is to be established and determines the corresponding DNN or external network connectivity. Further, the network service type refers to a classification of the requested network service, such as enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communication (URLLC), or massive Machine Type Communication (mMTC), which influences the IP allocation policy. Additionally, the configuration type refers to additional configuration parameters associated with the session, such as protocol options, security parameters, and device-specific requirements, which assist the SMF (210) in determining appropriate session establishment rules and IP allocation.[000104] The SMF (210) is further configured to transmit the at least one received IE to the UPF (214) by including the IE in a Packet Forwarding Control Protocol (PFCP) Session Establishment Request. The transmission of the IE to the UPF (214) enables the UPF (214) to extract at least one identifier from the at least one transmitted IE. The at least one identifier is one of an International Mobile Equipment Identity (IMEI) and a Permanent Equipment Identifier (PEI).[000105] The UPF (214) further detects at least one type allocation code (TAC) from the at least one extracted identifier. In particular, when the SMF (210) transmits the IMEI or PEI as part of the PFCP session establishment request, the UPF (214) parses the identifier and extracts the TAC, which corresponds to the first eight digits of the IMEI. The TAC uniquely identifies the device model and type of the UE (104). By detecting the TAC, the UPF (214) is enabled to correlate the UE (104) with one or more pre-provisioned TAC entries that are associated with corresponding IP address pools. Such detection allows the UPF (214) to differentiate between device categories, for example, UEs requiring IPv4 connectivity versus UEs that may be provisioned withIPv6 or dual-stack IPv4v6 connectivity. The TAC detection thus serves as the decisive step that enables the UPF (214) to perform device-specific IP allocation beyond conventional DNN or slice-based methods.[000106] The UPF (214) is further configured to compare the at least one detected TAC with one or more predefined TACs associated with corresponding IP addresses stored in a first IP pool. In particular, the UPF (214) maintains a first IP pool in which each entry is mapped to one or more TAC values and a corresponding IP version type, such as IPv4, IPv6, or dual-stack IPv4v6. Upon detecting the TAC from the identifier received in the PF CP signaling, the UPF (214) performs a check against the provisioned TAC entries. When a match is identified, the UPF (214) selects the IP address from the corresponding IP pool associated with that TAC. This comparison enables the UPF (214) to allocate addresses in a device-aware manner, ensuring that UEs (104) requiring IPv4 connectivity receive an IPv4 address, while other UEs may be allocated IPv6- only or dual-stack addresses, thereby conserving IPv4 resources and improving address pool utilization efficiency.[000107] The UPF (214) is further configured to allocate the IP address to the UE (104) from the first IP pool when the at least one detected TAC matches one of the one or more predefined TACs in the first IP pool. In such a case, the UPF (214) selects an available IP address from the dedicated pool associated with the matched TAC entry, where the pool may include IPv4 addresses, IPv6 addresses, or a combination thereof. In an embodiment, the matching refers to a comparison process performed by the UPF (214), where the detected TAC extracted from the identifier of the UE (104) (such as the first eight digits of the IMEI or PEI) is compared against a list or database of predefined TAC values stored in association with the first IP pool. A match is determined when the detected TAC corresponds exactly to, or falls within a range of, one or more predefined TAC values configured in the system (108). Such matching ensures that UEs belonging to a particular equipment category or device type, asindicated by their TAC, are allocated IP addresses from a specific pool reserved for that category, thereby enabling policy-driven and device-specific IP management.[000108] The allocation is carried out in accordance with operator-defined policies to ensure that device-specific requirements are met, such as assigning an IPv4v6 address for a smartphone device TAC or an IPv6-only address for an loT device TAC. By performing allocation directly from the first IP pool, the UPF (214) ensures efficient utilization of address resources, prevents unnecessary consumption of scarce IPv4 addresses, and enables differentiated IP assignment based on device category.[000109] In some embodiments, the UPF (214) is configured to assign the IP address to the UE (104) from a second pool, designated to a data network node (DNN) or a network slice, when the at least one detected TAC fails to match any of the one or more predefined TACs in the first IP pool. The second pool is designated to a specific DNN or a network slice, and represents the conventional mechanism for IP allocation in the 5G core network. In this case, the UPF (214) selects the IP address based on parameters such as the DNN, slice information, and operator configuration, independent of the UE’s TAC. The allocated address may correspond to an IPv4 address, an IPv6 address, or a combination thereof, depending on the session type requested by the UE (104). This mechanism ensures service continuity for UEs with TACs that are not provisioned in the first IP pool, while still maintaining flexibility in address allocation across slices and data networks.[000110] In some embodiments, the UPF (214) is further configured to store a record of at least one detected TAC, at least one corresponding identifier of the UE and at least one allocated IP address in the first IP pool. The record may include, for example, the TAC extracted from the IMEI, the PEI of the UE (104), the allocated IPv4, IPv6, or dual-stack address, and a timestamp of the allocation event. Maintaining such records enables the network to support auditing, troubleshooting, and regulatory compliance by providing a historical mapping of device identifiers to allocatedaddresses. Furthermore, these records can be leveraged by operator policy engines and analytics systems to optimize IP pool management, monitor IPv4 consumption, and predict future allocation requirements for specific TAC groups. Thus, the recordkeeping functionality enhances transparency, improves resource utilization, and supports dynamic adaptation of IP allocation policies.[000111] In an overall aspect, the SMF (210) may initiate a PFCP session establishment request during the PDU session towards the UPF (214). The SMF (210) may send a user ID information element (IE) of the UE (104) to the UPF (214). The user ID IE may contain an IMEI or a PEI number. The UPF (214) may extract a TAC from the received user ID IE. The UPF (214) may check for the received TAC matches with an already provisioned TAC. The provisioned TAC may be stored in the database (218). The UPF (214) may allocate the IP for the user equipment (104) based on the TAC. In an example, the TAC of the user equipment (104) may be provisioned in the UPF (214). The UPF (214) may allocate the IP for the UE (104) from the dedicated IP data. In another example, the TAC of the UE (104) may not be provisioned in the UPF (214). The UPF (214) may allocate the IP for the UE (104) from the general IP data. In an aspect, the dedicated IP data may be a set of IP addresses stored in the database (218). The set of IP addresses may be according to configured IP type. The configured IP type may include an IPv4, an IPv6 and an IPv4v6. In an aspect, the general IP data may be a group of IP addresses stored in the central database (110). The IP allocation may be from the general IP data assigned to a specific DNN / slice served by the UPF (214).[000112] In an alternative embodiment, the system (108) may be configured to allocate an IP address or prefix in the UPF (214). In such an embodiment, the system (108) includes the UPF (214). The UPF (214) is configured to receive a first request from a control plane (CP) function to allocate a UE IP address or prefix. The CP function may correspond to the SMF (210), which is responsible for establishing,modifying, and releasing PDU sessions. The SMF (210) acts as the control-plane entity that manages session context, determines IP allocation requirements, and communicates such requirements to the UPF (214) through a PFCP session establishment request or session modification request. In certain embodiments, the CP function may further operate in conjunction with other control-plane entities, such as a Policy Control Function (PCF) or Access and Mobility Management Function (AMF), to provide subscription information, policy rules, and UE context that influence the IP allocation performed by the UPF (214).[000113] In an embodiment, the first request includes a UE IP address information element (IE) comprising one or more IP version flags, the one or more IP version flags comprise an IPv4 flag and / or an IPv6 flag. The setting of these flags indicates the version of the IP address to be allocated to the UE (104). The first request further includes a network instance IE, which identifies an IP address pool from which the UE IP address or prefix is to be allocated by the UPF (214). In certain embodiments, the first request may further include a UE IP address pool identity, which explicitly specifies the pool to be used for allocation, thereby providing greater flexibility to the operator in managing multiple address pools. The first request is transmitted as part of a PFCP session establishment request or a PFCP session modification request. The PFCP session establishment request refers to a control-plane message sent from the SMF (210) to the UPF (214) for creating a new PFCP session. The PFCP session establishment request includes rules and information elements such as UE IP address, PDRs, and traffic endpoint configurations required for handling a new Protocol Data Unit (PDU) session. The PFCP session modification request refers to a control-plane message sent from the SMF (210) to the UPF (214) to update an existing PFCP session, where the modification may involve creating or deleting PDRs, updating traffic endpoints, or reallocating IP addresses or prefixes. In the present disclosure, the inclusion of the first request in either the establishment or modification message ensures that the UPF (214) allocates or updates the UE IP address or prefix in a mannerconsistent with the PDU session requirements. This enables address assignments to be performed in a policy-driven and pool-specific manner, supporting both IPv4 and IPv6 allocation according to operator configuration and session requirements.[000114] In an embodiment, the first request received by the UPF (214) from the CP function to allocate the UE IP address or prefix includes receiving a single request to allocate the same UE IP address or prefix to a plurality of PDRs to be created or modified. In an embodiment, the PDR refers to a control-plane defined rule within the UPF (214) that specifies how user-plane packets are to be identified and handled. Each of the plurality of PDRs includes a UE IP address IE comprising one or more IP version flags, indicating the request to allocate the same UE IP address or prefix to the plurality of PDRs. This configuration allows the UPF (214) to assign a common IP address or prefix across multiple PDRs, ensuring that different traffic flows belonging to the same PDU session are attached to a single UE IP identity. For example, a first PDR may identify uplink video streaming traffic from the UE, while a second PDR may identify uplink voice traffic; both PDRs may share the same UE IP address, thereby ensuring that all flows belonging to the same PDU session are consistently mapped to the same UE identity. By enabling allocation through a consolidated request, the system (108) reduces signaling overhead, avoids redundant address assignments, and improves consistency in address management within the UPF (214).[000115] In an embodiment, the first request received by the UPF from the CP function to allocate the UE IP address or prefix further includes receiving a request to allocate the same UE IP address or prefix to a plurality of PDRs to be created or modified within the UPF (214). The request comprises either a create traffic endpoint information element (IE) or an update traffic endpoint IE. The create traffic endpoint IE refers to an information element included in a PF CP message that instructs the UPF (214) to establish a new logical traffic endpoint for the UE (104), thereby anchoring an IP address or prefix for use by one or more PDRs within the PF CP session. The termupdate traffic endpoint IE refers to an information element that instructs the UPF (214) to modify an existing traffic endpoint, such as by changing the associated UE IP address, prefix, or supported IP version. The create traffic endpoint IE or the update traffic endpoint IE includes a UE IP Address IE with one or more IP version flags, such as an IPv4 flag and / or an IPv6 flag, indicating a selection of a new IP address or prefix.[000116] In an embodiment, the request further comprises the plurality of PDRs to be created or modified, each PDR including a traffic endpoint identity (ID). The inclusion of the traffic endpoint ID in each PDR, together with the use of the IP version flags in the UE IP Address IE of the traffic endpoint IE, enables the UPF (214) to consistently allocate the same IP address or prefix across the plurality of PDRs. This ensures that multiple traffic flows associated with the same UE (104) session are bound to a common IP identity, thereby reducing allocation inconsistencies, simplifying session management, and improving forwarding efficiency in the user plane.[000117] In an embodiment, the request further includes the plurality of PDRs to be created or modified, each comprising a traffic endpoint identity (ID). The inclusion of the traffic endpoint ID in each PDR, together with the use of one or more IP version flags in the UE IP Address information element (IE) of the traffic endpoint IE, enables the UPF (214) to consistently allocate the same UE (104) IP address or prefix across the plurality of PDRs. This ensures that multiple traffic flows associated with a single PDU session are bound to a common IP identity, thereby reducing address fragmentation, simplifying session continuity, and improving routing efficiency within the user plane.[000118] The UPF (214) is further configured to determine an IP version selected from one or both of an IPv4 address and / or an IPv6 address, to be allocated, based on the IPv4 flag and / or the IPv6 flag included in the UE IP address IE. The presence of the IPv4 flag indicates that the allocation is to be performed using IPv4, whereas the presence of the IPv6 flag indicates that the allocation is to be performed using IPv6.When both flags are included, the UPF (214) recognizes that the allocation may support both IPv4 and IPv6, and proceeds to identify the applicable version or combination thereof. This determination ensures that the address assignment process is guided by signaling from the control plane function, thereby aligning the allocation procedure with the session requirements conveyed in the request.[000119] In an embodiment, upon determining that both the IPv4 flag and the IPv6 flag are included in the UE IP address IE, the UP function allocates at least one of the IPv4 address, the IPv6 address, or a combination thereof based on an operator policy. The operator policy defines how dual-flag scenarios are to be resolved and may be based on locally configured criteria such as an International Mobile Equipment Identity Type Allocation Code (IMEI TAC) associated with the UE (104) or a Protocol Data Unit (PDU) session type mapping provisioned by the operator. For example, the operator policy may mandate IPv6-only allocation for loT devices identified by their TAC, while smartphones identified by another TAC may receive dual-stack IPv4v6 allocation. By applying the operator policy in such cases, the UPF (214) ensures device-specific and service-specific allocation decisions, thereby providing flexibility, conserving scarce IPv4 addresses, and aligning address assignment with network deployment strategies.[000120] The UPF (214) is further configured to select the UE IP address or prefix corresponding to the determined IP version from the IP address pool, indicated by the network instance IE in the first request. The network instance IE indicates the logical association to a data network or slice-specific pool, thereby guiding the UPF (214) to the correct address pool for allocation. In some embodiments, the UPF (214) is configured to refine the selection based on one or more additional parameters, including a Single Network Slice Selection Assistance Information (S-NSSAI) associated with the Packet Forwarding Control Protocol (PF CP) session, the network instance IE, and a UE IP address pool identity. The S-NSSAI refers to an identifier thatspecifies a particular network slice instance within a 5G network. Each S-NSSAI consists of a Slice / Service Type (SST), which indicates the type of service (e.g., enhanced Mobile Broadband, Ultra-Reliable Low Latency Communication, or massive Machine Type Communication), and an optional Slice Differentiator (SD), which uniquely identifies multiple slices of the same SST. In an embodiment, the UPE (214) may use the S-NSSAI associated with the PFCP session to refine IP address or prefix allocation so that traffic belonging to different slices may be assigned from distinct IP pools. By applying these parameters, the UPF (214) is able to select the appropriate IP address or prefix from the relevant pool and allocate it to the UE (104). Such selective allocation ensures that address assignment adheres to slice-level isolation, operator policies, and service-specific requirements, thereby optimizing address pool utilization and maintaining session integrity across the network.[000121] The UPF (214) is further configured to allocate the selected UE IP address or prefix to one or more packet detection rules (PDRs) and / or traffic endpoints to be created or modified, in response to the first request. The allocation ensures that all PDRs and traffic endpoints associated with the same PDU session consistently reference the same assigned IP address or prefix, thereby maintaining session integrity across multiple flows. In an embodiment, the PDR refers to a rule provisioned by the control plane and installed at the UPF (214) to classify packets belonging to a particular user flow, based on parameters such as UE IP address, header fields, or QoS attributes. Each PDR instructs the UPF (214) on how to process identified packets, for example by forwarding, buffering, or applying QoS treatment. The traffic endpoint refers to a logical termination point within the UPF (214) that anchors a UE’s IP address or prefix and provides a binding reference for multiple PDRs associated with the same session.[000122] Once the allocation is completed, the UPF (214) transmits a response to the CP function to confirm the assignment. In an embodiment, the response is selected from at least one of a PFCP session establishment response or a PFCP sessionmodification response. The response includes at least one UE IP address IE having a list of IP addresses or prefixes that have been allocated to each of the one or more PDRs and / or traffic endpoints, in response to the creation or modification of such PDRs or traffic endpoints. By including the allocated IP address or prefix in the response, the UPF (214) ensures that the CP function, such as the SMF (210), is informed of the precise addressing configuration applied within the user plane. This enables the SMF (210) to maintain an accurate session context and allows other network functions to reference the assigned IP addresses when enforcing policy, charging, or routing operations. The explicit listing of allocated addresses or prefixes in the response provides transparency, consistency, and synchronization between the control plane and the user plane, thereby preventing allocation mismatches and improving session reliability.[000123] In an embodiment, the UPF (214) is further configured to receive a second request selected from at least one of: a request to delete a PFCP session, a request to delete the traffic endpoint associated with the allocated UE IP address or prefix, and a request to remove a packet detection rule (PDR) associated with the allocated UE IP address or prefix. Such a second request is generated by the CP function, for example, the SMF (210), when a PDU session is released, a traffic endpoint is no longer required, or a specific PDR is to be modified or removed. The receipt of this second request indicates that the previously allocated IP address or prefix is no longer needed for the corresponding session or flow, and triggers the UPF (214) to initiate an IP deallocation procedure in order to release the address back into the appropriate pool for future reuse.[000124] In an embodiment, the UPF (214) is further configured to receive a second request to deallocate the UE IP address or prefix that was previously assigned to at least one of the PFCP sessions, the traffic endpoint, or the PDR, in response to the second request. Upon receiving the second request, the UPF (214) identifies thecorresponding session or flow context, releases the allocated IP address or prefix from the active assignment, and returns the released address to the designated pool for reuse. This deallocation prevents address leakage, ensures optimal utilization of limited IPv4 and IPv6 address resources, and maintains accuracy in IP pool management. By systematically deallocating addresses upon session or rule termination, the UPF (214) preserves pool availability, supports scalability, and enables efficient address reassignment for subsequent UEs or sessions.[000125] In an embodiment, the UPF (214) is configured to receive a third request from the CP function to allocate an additional UE IP address or prefix. The third request is transmitted in scenarios where multiple IP addresses or prefixes are required for the same PDU session, such as for multi-homing, dual connectivity, or differentiated traffic handling. The third request includes at least one of: an update PDR IE or an update traffic endpoint IE.[000126] In an embodiment, the update PDR IE is utilized to modify an existing PDR in the UPF (214), such that the detection criteria for packet flows associated with the UE (104) may be updated to incorporate an additional IP address or prefix. For example, when the UE (104) has been allocated an IPv4 address in response to the first request, and an additional IPv6 address is to be assigned, the update PDR IE modifies the existing rule to detect and forward traffic corresponding to both the IPv4 and the newly allocated IPv6 address, thereby ensuring dual-stack operation within the same PDU session.[000127] Further, the update traffic endpoint IE enables the modification of an existing traffic endpoint in the UPF (214), such that the endpoint may be associated with an additional IP address or prefix. For example, when the UE (104) has been allocated a first IP address for a traffic endpoint toward the DNN, the update traffic endpoint IE allows the same endpoint to be updated with a new IPv6 address or an additional IPv4 address, thereby extending the connectivity of the UE (104) withoutcreating a separate endpoint. This ensures continuity of service and efficient use of resources while supporting multiple IP bindings within the same session context.[000128] In an embodiment, the additional UE IP address or prefix is different from the UE IP address or prefix allocated in response to the first request. The difference may be in terms of IP version, where the first request results in the allocation of an IPv4 address and the third request results in the allocation of an IPv6 address, or vice versa. Alternatively, the difference may be in terms of distinct prefixes or addresses within the same IP version, for example, allocation of a first IPv6 prefix in the first request and allocation of a second, different IPv6 prefix in the third request. The allocation of a different IP address or prefix enables the UE (104) to operate with multiple network identities within a single PDU session, thereby supporting scenarios such as dual-stack operation, multi-homing, and differentiated traffic management.[000129] FIG. 3 illustrates an exemplary architecture (300) of the system (108), in accordance with an embodiment of the present disclosure.[000130] In an embodiment, the system (108) may be coupled with a radio network (302), the user equipment (104) (e.g., UE 104) and an intemet / data network (304). The radio network (302) may establish a communicative connection between the user equipment (104) and the internet / data network (304). The user equipment (104) connects to the internet / data network (304) via the system (108). The system (108) may comprise the UDM (202), the AUSF (204), the UDR (206), the AMF (208), the SMF (210), the NRF (212) and the UPF (214).[000131] In an embodiment, the AMF (208) may manage access and mobility aspects for user devices in the 5G network. The AMF (208) handles access control, mobility management, and connection establishment for the user equipment (104). In an exemplary embodiment, the user equipment (104) requests the AMF (208) for a service. The SMF (210) may be configured for managing the user session based on therequested service. In an aspect, the AMF (208) communicates with the network entities via a Namf interface.[000132] In an embodiment, the SMF (210) manages and controls user sessions in the 5G network. The SMF (210) facilitates the establishment, modification, and termination of user sessions, ensuring efficient and secure communication. In an aspect, the SMF (210) communicates with the network entities via a network slice management function (Nsmf) interface.[000133] In an embodiment, the UPF (214) may transport an IP data traffic between the user equipment (104) and the internet / data network (304). The IP data traffic may include transmission of data packets that route and deliver information between the user equipment (104) on the internet / data network (304). The SMF (210) may provide the UPF (214) with a set of instructions for session establishment and management. The UPF (214) may process and manage the user data traffic.[000134] In an embodiment, the AUSF (204) may handle authentication procedures in the 5G network. The AUSF (204) may verify the user (102) and the user equipment (104) before enabling the access to the internet / data network (304). The AUSF (204) interacts with the AMF (208) to provide authentication services and support security management on the internet / data network (304). In an aspect, the AUSF (204) communicates with the network entities via a Nausf interface.[000135] In an embodiment, the NRF (212) supports the service discovery function, maintains network function (NF) profile and available NF instances. The network repository function (NRF) 212 supports the network in discovering and selecting appropriate network functions and instances to optimize service delivery. In an aspect, the NRF communicates with the network function entities via a Nnrf interface.[000136] In an embodiment, the UDM (202) may manage a user data and a user profile in the 5G network. The UDM (202) may stores the user data, a user access credentials, and a user service-specific data. The AMF (208) may interact with the UDM (202) to manage access control and mobility for the user equipment (104). In an aspect, the UDM (202) may communicate with the network function entities via a Nudm interface.[000137] In an embodiment, the UDR (206) may serve as a repository for managing and storing the user data. The user data may be essential for network operation and service delivery. The UDR (206) provides accurate user data to the other network function entities for authentication and session management. In an aspect, the UDR (206) may communicate with the network function entities via a Nudr interface.[000138] FIG. 4 illustrates an exemplary flow diagram of a method (400) for allocating the IP address to the UE (104) in the network (106), in accordance with an embodiment of the present disclosure.[000139] At step 402, the SMF (210) may initiate a PFCP session establishment request (SER) towards the UPF (214). The PFCP SER may be initiated during the PDU session establishment phase. In an aspect, the SMF (210) may share a user ID information element (IE) with the UPF (214). The user ID information element (IE) may include the IMEI or PEI number.[000140] At step 404, the UPF (214) may extract the TAC from the received user ID information element (IE). The TAC may be the first eight digits of the IMEI number. The first eight digits of the IMEI identify the make and model of the UE (104) and provide an equipment-level classification for network operations. In operation, when the IMEI number is transmitted as part of the information elements received from the SMF (210), the UPF (214) parses the IMEI value, isolates the initial eight digits, and records them as the TAC. The extracted TAC is then used for subsequent comparisonwith one or more predefined TACs stored in association with corresponding IP address pools, thereby enabling equipment-specific IP address allocation.[000141] At step 406, the UPF (214) may check for the extracted TAC with a set of provisioned TAC. The set of provisioned TAC may be stored in the database (218). The UPF (214) may allocate IP from either the dedicated IP data or the general IP data. The UPF (214) may allocate IP from dedicated IP data if UPF (214) matches the extracted TAC with the provisioned TAC. In case, the UPF (214) does not match the extracted TAC with the provisioned TAC, the UE (104) may be allocated an IP address from the general IP data. In an aspect, the UPF (214) may send a session establishment response to the SMF (210).[000142] At step 408, the UPF (214) may allocate a configured IP type from the dedicated IP data to the UE (104), if the received TAC matches with the provisioned TAC. The configured IP type may include an internet protocol version 4 (IPv4), an internet protocol version 6 (IPv6) and an internet protocol version 4 and version 6 (IPv4v6). The dedicated IP data may be stored in the database (218). The dedicated IP data may comprise a set of IP addresses for already provisioned TAC.[000143] At step 410, the UPF (214) may allocate the IP from the general IP data, if the received TAC does not match with the provisioned TAC. The general IP data may comprise a group of IP addresses. The group of IP addresses may be stored in the central database (110).[000144] In an aspect, the dedicated IP data may be a set of IP addresses stored in the database (218). The set of IP addresses may be according to configured IP type. The configured IP type may include an internet protocol version 4 (IPv4), an internet protocol version 6 (IPv6) and an internet protocol version 4 and version 6 (IPv4v6).[000145] In an aspect, the general IP data may be a group of IP addresses stored in the central database (110). The IP allocation may be from the general IP data assigned to a specific DNN / slice served by the UPF (214).[000146] FIG. 5 illustrates another exemplary flow diagram of a method (500) for allocating the IP address to the UE (104) in the network (106), in accordance with an embodiment of the present disclosure.[000147] At step 502, the SMF (210) is configured to receive at least one request from the UE (104) to establish a session (e.g., PDU session). The at least one request comprises at least one information element (IE). The at least one IE includes a user identifier, a quality of service (QoS) parameter, a session type, a user location, an access point name (APN), a network service type, and a configuration type.[000148] At step 504, the SMF (210) is further configured to transmit the at least one received IE to the UPF (214). The transmission of the IE from the SMF (210) to the UPF (214) ensures that the UPF (214) has access to all session-related identifiers and parameters required for IP address allocation and traffic handling.[000149] At step 506, the UPF (214) is configured to extract at least one identifier from the at least one transmitted IE. The at least one identifier is one of an International Mobile Equipment Identity (IMEI) and a Permanent Equipment Identifier (PEI). In an embodiment, the IMEI refers to a globally unique identifier assigned to the UE (104). The IMEI is typically a 15-digit numeric value that enables the network (106) to identify and authenticate the UE independently of the subscriber’s credentials. The initial eight digits of the IMEI represent the Type Allocation Code (TAC), which specifies the device make and model. In the context of the present disclosure, the UPF (214) utilizes the TAC derived from the IMEI for determining IP address allocation policies, thereby ensuring equipment-aware management of IP resources. Further, the PEI refers to a unique identifier allocated to the UE (104). Unlike subscriber-specificidentifiers, such as the IMSI, the PEI remains tied to the physical device, providing a stable reference for device recognition across sessions and network slices. In the present disclosure, the UPF (214) may extract the PEI from a received information element (IE) and map it to a TAC through preconfigured associations, thereby supporting TAC-based IP address allocation even when the IMEI is not directly available.[000150] At step 508, the UPF (214) further detects at least one TAC from the at least one extracted identifier. The TAC serves as an equipment-specific classification derived from identifiers such as the IMEI or the PEI. In one embodiment, when the extracted identifier is an IMEI, the UPF (214) isolates the first eight digits of the IMEI to determine the TAC, which uniquely identifies the make and model of the UE (104). In another embodiment, when the extracted identifier is a PEI, the UPF (214) maps the corresponding PEI value to a TAC based on a preconfigured association stored within the system (108). The detection of the TAC enables the UPF (214) to subsequently perform comparison with predefined TACs linked to specific IP address pools, thereby facilitating device-aware and policy-driven IP address allocation.[000151] At step 510, the UPF (214) is further configured to compare the at least one detected TAC with one or more predefined TACs associated with corresponding IP addresses stored in a first IP pool. The predefined TACs may be provisioned by the operator in advance and linked to specific ranges or categories of IP addresses reserved for the UE (104) of a particular type or model. In operation, the UPF (214) retrieves the detected TAC derived from the identifier of the UE and performs a matching operation against the stored list of predefined TACs. Upon identifying a match, the UPF (214) is able to determine the appropriate IP address pool that corresponds to the specific equipment classification. This comparison ensures that the allocation of IP addresses is not arbitrary but is instead based on equipment type, thereby enablingdifferentiated treatment, efficient address utilization, and policy-driven control within the network (106).[000152] At step 512, the UPF (214) is further configured to allocate the IP address to the UE (104) from the first IP pool when the at least one detected TAC matches one of the one or more predefined TACs in the first IP pool. The first IP pool is a reserved set of addresses configured by the operator for assignment to the UE of specific types, models, or categories, as determined by their TAC. Upon detecting a match, the UPF (214) selects an available IP address from the corresponding pool and binds the allocated address to the session context of the UE (104). The allocation ensures that UEs identified by certain TACs consistently receive addresses from predefined ranges, thereby supporting operator policies related to traffic management, QoS enforcement, device-specific optimizations, and regulatory compliance. The allocated IP address may further be associated with the PDRs to enable correct routing and handling of user-plane traffic.[000153] In some embodiments, the UPF (214) is configured to assign the IP address to the UE (104) from a second pool, designated to a data network node (DNN) or a network slice, when the at least one detected TAC fails to match any of the one or more predefined TACs in the first IP pool. The assigned IP address is selected from an internet protocol version 4 (IPv4) address, an internet protocol version 6 (IPv6) address or a combination thereof.[000154] In some embodiments, the UPF (214) is further configured to store a record of at least one detected TAC, at least one corresponding identifier of the UE and at least one allocated IP address in the first IP pool. Such storage enables the creation of a persistent mapping between the UE’s identity and the allocated IP resource, thereby facilitating consistency across ongoing and subsequent sessions. The stored records may be maintained in a dedicated data structure or repository within the UPF (214) to support auditing, policy enforcement, troubleshooting, and lawful interceptionrequirements. Furthermore, the recordkeeping allows the operator to monitor address utilization within the first IP pool, detect anomalies such as repeated allocation failures or TAC mismatches, and optimize IP pool management by analyzing device-type- specific address consumption patterns.[000155] In an embodiment, the present disclosure provides a system and a method for the IP allocation based on the UE (104) TAC in the network (106). The method includes initiation of at least one PFCP request to the UPF (214) in the PDU session establishment by the SMF (210). The method includes sharing at least one user ID information element (IE) with the UPF (214) by the SMF (210). The method includes the extraction of one or more TAC from the received user ID information element (IE). The method includes evaluating the one or more extracted TAC with a provisioned TAC by the UPF (214). The method includes allocation of the IP address based on the evaluation of the TAC by the UPF (214).[000156] FIG. 6 illustrates an exemplary flow diagram of a method (600) for allocating the IP address or prefix in the UPF (214), in accordance with an embodiment of the present disclosure.[000157] At step 602, the UPF (214) is configured to receive a first request from a control plane (CP) function to allocate a UE IP address or prefix. In an embodiment, the first request received by the UPF (214) from the CP function to allocate the UE IP address or prefix includes receiving a single request to allocate the same UE IP address or prefix to a plurality of PDRs to be created or modified. Each of the plurality of PDRs includes a UE IP address IE comprising one or more IP version flags, indicating the request to allocate the same UE IP address or prefix to the plurality of PDRs.[000158] In an embodiment, the first request received by the UPF from the CP function to allocate the UE IP address or prefix includes receiving a request to allocate the same UE IP address or prefix to a plurality of PDRs to be created or modified. Therequest includes a create traffic endpoint IE or an update traffic endpoint IE. The create traffic endpoint IE or the update traffic endpoint IE comprises a UE IP Address IE with one or more IP version flags indicating a selection of a new UE IP address or prefix. In an embodiment, the request further includes the plurality of PDRs to be created or modified, each comprising a traffic endpoint identity (ID). An inclusion of the traffic endpoint ID in each of the plurality of PDRs and a use of one or more IP version flags in the UE IP Address IE of the traffic endpoint IE, enable the UPF to allocate the same UE IP address or prefix to the plurality of PDRs.[000159] In an embodiment, the first request includes a UE IP address information element (IE) comprising one or more IP version flags, the one or more IP version flags comprise an IPv4 flag and / or an IPv6 flag. The first request further includes a network instance IE, indicating an IP address pool from which the UE IP address or prefix is to be allocated. In an embodiment, the first request is selected from at least one of a packet forwarding control protocol (PFCP) session establishment request or a PFCP session modification request. The first request further includes a UE IP address pool identity indicating the IP address pool for allocation of the UE IP address or prefix by the UPF.[000160] At step 604, the UPF (214) is further configured to determine an IP version selected from one or both of an IPv4 address and / or an IPv6 address, to be allocated, based on the IPv4 flag and / or the IPv6 flag included in the UE IP address IE.[000161] In an embodiment, upon determining that both the IPv4 flag and the IPv6 flag are included in the UE IP address IE, the UP function allocates at least one of the IPv4 address, the IPv6 address, or a combination thereof based on an operator policy. The operator policy is determined based on at least one of a locally configured international mobile equipment identity type allocation code (IMEI TAC) and a protocol data unit (PDU) session type mapping.[000162] At step 606, the UPF (214) is further configured to select the UE IP address or prefix corresponding to the determined IP version from the IP address pool, indicated by the network instance IE in the first request. In some embodiments, the UPF (214) is configured to select the UE IP address or prefix based on one or more of a single network slice selection assistance information (S-NSSAI) associated with a PF CP session, the network instance IE, and a UE IP address pool identity and further allocate the UE IP address or prefix based on the selection.[000163] At step 608, the UPF (214) is further configured to allocate the selected UE IP address or prefix to one or more packet detection rules (PDRs) and / or traffic endpoints to be created or modified, in response to the first request. In an embodiment, the response is selected from at least one of a PF CP session establishment response or a PF CP session modification response.[000164] In an embodiment, the UPF (214) is further configured to transmit a response to the CP function. The response comprises at least one UE IP address IE having a list of IP addresses or prefixes allocated to each of the one or more PDRs and / or the traffic endpoints, in response to creation or modification of the one or more PDRs or the traffic endpoints.[000165] In an embodiment, the UPF (214) is further configured to receive a second request selected from at least one of: a request to delete a PFCP session, a request to delete the traffic endpoint associated with the allocated UE IP address or prefix, and a request to remove a packet detection rule (PDR) associated with the allocated UE IP address or prefix.[000166] In an embodiment, the UPF (214) is further configured to receive a second request to deallocate the UE IP address or prefix allocated to at least one of the PFCP session, the traffic endpoint, and the PDR in response to the second request.[000167] In an embodiment, the UPF (214) is configured to receive a third request from the CP function to allocate an additional UE IP address or prefix. The request comprises at least one of: an update PDR IE or an update traffic endpoint IE, wherein the additional UE IP address or prefix is different from the UE IP address or prefix allocated in response to the first request.[000168] In an overall aspect, certain UEs need to be assigned IPv4 only / IPv6 only / IPv4v6 for specific PDU sessions. Assigning IP addresses as per default DNN settings may lead to the wastage of some IP addresses for a large set of UEs that do not require both IPv4 and IPv6 addresses. There is always a shortage of IPv4 addresses, and therefore, wasting them by assigning all UEs with IPv4 addresses is not an optimal solution. In the 5G network, IPv6 addresses may mostly be assigned to UEs, however, the requirement of IPv4 assignment to select UEs cannot be denied.[000169] Thus, IPv4 / IPv6 / IPv4v6 assignment by UPF based on UE’s IMEI Type Allocation Code (TAC) may solve the above problem and may ensure IP allocation requirements are met appropriately. The present disclosure proposes to define an operator policy to support IMEI TAC- based IP allocation by the UPF. Further, the present disclosure proposes UE IP address or prefix allocation in the UPF.[000170] In an exemplary embodiment, when performing UE IP addr ess / prefix allocation in the UP function, the CP function may request the UP function to allocate the UE IP address / prefix by setting the CHOOSE flags (CHOOSE IPV4 and / or CHOOSE IPV6) in the UE IP Address IE of the PDR IE. The term “CHOOSE flag” refers to an indicator bit or field within the UE IP Address IE that specifies the version of IP address to be allocated by the UPF. The CHOOSE IPv4 flag instructs the UPF to allocate an IPv4 address, the CHOOSE IPv6 flag instructs the UPF to allocate an IPv6 address, and the presence of both flags allows the UPF to allocate either one or both versions of the IP address in accordance with operator policy. In an embodiment, the IPv6 prefix length (PL) may be indicated in the UE IP address if an IPv6 prefix otherthan default / 64 and other than for IPv6 prefix delegation is to be assigned, and the UPF indicates support of the IP6PL feature.[000171] Further, the CP function may request the UPF to allocate the UE IP address / prefix by including the network instance IE to indicate the IP address pool from which the UE IP address / prefix is to be assigned. Further, the CP function may request the UP function to allocate the UE IP address / prefix by optionally including the UE IP address pool identity from which the UPF may allocate the UE IP address.[000172] In an exemplary embodiment, the CP function may request the UP function (e.g., UPF) to allocate the same UE IP address / prefix to several PDRs to be created (i.e., using Create PDR) within one single PF CP session establishment request or PFCP session modification request, or to several PDRs to be modified (i.e., using Update PDR) within one single PFCP session modification request by:• setting the CHOOSE flags (CHOOSE IPV4 and / or CHOOSE IPV6) in the UE IP address IE of each PDR to be created with a new UE IP address / prefix or each PDR to be modified; or, if the UP function indicated support of the PDI optimization, by:• including the UE IP Address IE in the Create Traffic Endpoint IE or Update Traffic Endpoint IE, and by setting the CHOOSE flags (CHOOSE IPV4 and / or CHOOSE IPV6) in that UE IP Address IE; and• including the Traffic Endpoint ID in all the PDRs to be created with the same UE IP address, or all PDRs to be modified with additional UE IP addresses.[000173] It may be noted that (Note 1), if both flags, CHOOSE IPV4 and CHOOSE IPV6, are set by the CP function, based on operator policy, the UPF may allocate IPv4, IPv6, or both as per locally configured IMEI TAC and PDU session type mapping.[000174] In an exemplary embodiment, if the PDR(s) is created or modified successfully or the traffic Endpoint(s) is created or modified successfully, the UPF may always return the full list of UE IP address / prefix in the UE IP address IE(s) it has assigned to the PDR(s) or to the traffic endpoint(s) in the PF CP session establishment response or PF CP session modification response.[000175] In an exemplary embodiment, upon receiving a request to delete a PF CP session, to remove a traffic endpoint associated with the UE IP address / prefix, or to remove the last PDR associated with the UE IP address / prefix, the UP function may release the UE IP address / prefix that was assigned to the PFCP session, to the traffic endpoint, or to the PDR.[000176] It may be noted that (Note 2), when the CP function requests the additional UE IP address in the update PDR or update traffic endpoint IE, it need not include any existing UE IP addresses.[000177] In an exemplary embodiment, if the UPF supports the “Per Slice UP Resource management” feature and if the feature is enabled in the UPF, the UPF may take the S-NSSAI associated with the PFCP session into account when allocating the UE IP address, together with other information present (e.g., Network Instance, UE IP address pool identity.[000178] FIG. 7 illustrates an exemplary computer system (700) in which or with which embodiments of the present disclosure may be implemented.[000179] As shown in FIG. 7, the computer system (700) may include an external storage device (710), a bus (720), a main memory (730), a read-only memory (740), a mass storage device (750), a communication port (760), and a processor (770). A person skilled in the art will appreciate that the computer system (500) may include more than one processor (770) and communication ports (760). The processor (770) may include various modules associated with embodiments of the present disclosure.[000180] In an embodiment, the communication port (760) 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 fibre, a serial port, a parallel port, or other existing or future ports. The communication port (760) may be chosen depending on the network (106), such a Local Area Network (LAN), Wide Area Network (WAN), or any network to which the computer system (700) connects.[000181] In an embodiment, the memory (730) may be Random Access Memory (RAM), or any other dynamic storage device commonly known in the art. Read-only memory (740) 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 (770).[000182] In an embodiment, the mass storage device (750) may be any current or future mass storage solution, which may 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 Lirewire interfaces), one or more optical discs, Redundant Array of Independent Disks (RAID) storage, e.g., an array of disks (e.g., SATA arrays).[000183] In an embodiment, the bus (720) communicatively couples the processor(s) (770) with the other memory, storage, and communication blocks. The bus (720) 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 (770) to the computer system (500).[000184] Optionally, operator and administrative interfaces, e.g., a display, keyboard, joystick, and cursor control device, may also be coupled to the bus (720) to support direct operator interaction with the computer system (500). Other operator and administrative interfaces may be provided through network connections connected through the communication port (760). The components described above are meant only to exemplify various possibilities. In no way should the aforementioned exemplary computer system 7500) limit the scope of the present disclosure.[000185] In an exemplary embodiment, the disclosure provides a system for allocating an internet protocol (IP) address to a UE in a network is disclosed. The system includes a session management function (SMF) configured to receive at least one request from the UE to establish a session. The at least one request comprises at least one information element (IE). The SMF is further configured to transmit the at least one received IE to a user plane function (UPF). The UPF is configured to extract at least one identifier from the at least one transmitted IE. The UPF is further configured to detect at least one type allocation code (TAC) from the at least one extracted identifier. The UPF is further configured to compare the at least one detected TAC with one or more predefined TACs associated with corresponding IP addresses stored in a first IP pool. The UPF is further configured to allocate the IP address to the UE from the first IP pool when the at least one detected TAC matches one of the one or more predefined TACs in the first IP pool.[000186] In another exemplary embodiment, a system for allocating an Internet Protocol (IP) address or prefix in a user plane function (UPF) is disclosed. The system includes the UPF configured to receive a first request from a control plane (CP) function to allocate a UE IP address or prefix. The first request comprises a user equipment (UE) IP address information element (IE) comprising one or more IP version flags, the one or more IP version flags comprise an IPv4 flag and / or an IPv6 flag. The first request further comprises a network instance IE, indicating an IP addresspool from which the UE IP address or prefix is to be allocated. The UPF is further configured to determine an IP version selected from one or both of an IPv4 address and / or an IPv6 address, to be allocated, based on the IPv4 flag and / or the IPv6 flag included in the UE IP address IE. The UPF is further configured to select the UE IP address or prefix corresponding to the determined IP version from the IP address pool, indicated by the network instance IE in the first request. The UPF is further configured to allocate the selected UE IP address or prefix to one or more packet detection rules (PDRs) and / or traffic endpoints to be created or modified, in response to the first request.[000187] In another exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The medium includes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for allocating an internet protocol (IP) address to a user equipment (UE) in a network. The method includes receiving, by a session management function (SMF), at least one request from the UE to establish a session. The at least one request comprises at least one information element (IE). The method includes transmitting, by the SMF, the at least one received IE to a user plane function (UPF). The method includes extracting, by the UPF, at least one identifier from the at least one transmitted IE. The method includes detecting, by the UPF, at least one type allocation code (TAC) from the at least one extracted identifier. The method includes comparing, by the UPF, the at least one detected TAC with one or more predefined TACs associated with corresponding IP addresses stored in a first IP pool. The method includes allocating, by the UPF, the IP address to the UE from the first IP pool when the at least one detected TAC matches one of the one or more predefined TACs in the first IP pool.[000188] In yet another exemplary embodiment, a computer program product comprising a non-transitory computer-readable medium is disclosed. The mediumincludes instructions that, when executed by one or more processors, cause the one or more processors to execute a method for allocating an Internet Protocol (IP) address or prefix in a user plane function (UPF). The method includes receiving, by the UPF, a first request from a control plane (CP) function to allocate a user equipment (UE) IP address or prefix. The first request comprises a UE IP address information element (IE) comprising one or more IP version flags, wherein the one or more IP version flags comprises an IPv4 flag and / or an IPv6 flag. The first request further comprises a network instance IE indicating an IP address pool from which the UE IP address or prefix is to be allocated. The method includes determining, by the UPF, an IP version selected from one or both of an IPv4 address and / or an IPv6 address, to be allocated, based on the IPv4 flag and / or the IPv6 flag included in the UE IP address IE. The method includes selecting, by the UPF, the UE IP address or prefix corresponding to the determined IP version from the IP address pool, indicated by the network instance IE in the first request. The method includes allocating, by the UPF, the selected UE IP address or prefix to one or more packet detection rules (PDRs) and / or traffic endpoints to be created or modified, in response to the first request.[000189] The present disclosure provides a technical advancement in an IP address allocation within a 5G core network by enabling the UPF to allocate IP addresses based on the International Mobile Equipment Identity Type Allocation Code (IMEI TAC). Unlike conventional approaches, where the UPF allocates IP addresses solely based on Data Network Name (DNN) and network slice configurations, the present disclosure introduces device-specific allocation using TAC. The present disclosure further enables the UPF to allocate IP addresses or prefixes from a dedicated TAC-based pool or from a general pool depending on the UE type, and to selectively assign IPv4, IPv6, or dual-stack (IPv4v6) addresses in accordance with operator policy. This approach conserves scarce IPv4 resources, ensures efficient utilization of IP address pools, and provides operators with flexible policy-driven allocation mechanisms. The present disclosure significantly improves network efficiency andenhances device management, thereby optimizing scalability and operational flexibility in real-world deployments.TECHNICAL ADVANCEMENTS[000190] The present disclosure described herein above has several technical advantages including, but not limited to, the realization of the system and the method that:[000191] The present disclosure provides a system and a method that enables allocation of an internet protocol (IP) address to a user equipment (UE) in a network based on type allocation code (TAC).[000192] The present disclosure provides a system and a method that assigns IP address based on international mobile equipment identity (IMEI) for efficient management and identification of the UE.[000193] The present disclosure provides a system and a method that allocates IP address or prefix in a user plane function (UPF).[000194] The present disclosure provides a system and a method for allocating IP addresses based on IP version type (e.g., IPv4, IPv6, or IPv4v6) according to the UE.[000195] The present disclosure provides a system and a method that conserves scarce IPv4 addresses by selectively allocating them only to UEs that require IPv4, thereby preventing wastage.[000196] The present disclosure provides a system and a method that efficiently manages IP address pools by allocating from a dedicated TAC-based pool or a general DNN / Slice pool, depending on UE type.

Claims

CLAIMS1. A method (500) for allocating an internet protocol (IP) address to a user equipment (UE) (104) in a network (106), the method comprising: receiving (502), by a session management function (SMF) (210), at least one request from the UE (104) to establish a session, wherein the at least one request comprises at least one information element (IE); transmitting (504), by the SMF (210), the at least one received IE to a user plane function (UPF) (214); extracting (506), by the UPF (214), at least one identifier from the at least one transmitted IE; detecting (508), by the UPF (214), at least one type allocation code (TAC) from the at least one extracted identifier; comparing (510), by the UPF (214), the at least one detected TAC with one or more predefined TACs associated with corresponding IP addresses stored in a first IP pool; and allocating (512), by the UPF (214), the IP address to the UE (104) from the first IP pool when the at least one detected TAC matches one of the one or more predefined TACs in the first IP pool.

2. The method (500) as claimed in claim 1, wherein the at least one information element (IE) comprises a user identifier, a quality of service (QoS) parameter, a session type, a user location, an access point name (APN), a network service type, and a configuration type.

3. The method (500) as claimed in claim 1, wherein the at least one identifier is one of an International Mobile Equipment Identity (IMEI) and a Permanent Equipment Identifier (PEI).

4. The method (500) as claimed in claim 1, further comprising: assigning, by the UPF (214), the IP address to the UE (104) from a second pool, designated to a data network (106) node (DNN) or a network (106) slice, when the at least one detected TAC fails to match any of the one or more predefined TACs in the first IP pool.

5. The method (500) as claimed in claim 1, wherein the assigned IP address is selected from an internet protocol version 4 (IPv4) address, an internet protocol version 6 (IPv6) address or a combination thereof.

6. The method (500) as claimed in claim 1, further comprising storing, by the UPF (214), a record of at least one detected TAC, at least one corresponding identifier of the UE (104) and at least one allocated IP address in the first IP pool.

7. A system (108) for allocating an internet protocol (IP) address to a user equipment (UE) (104) in a network (106), wherein the system (108) comprising: a session management function (SMF) (210) configured to: receive at least one request from the UE (104) to establish a session, wherein the at least one request comprises at least one information element (IE); and transmit the at least one received IE to a user plane function (UPF) (214), wherein the UPF (214) is configured to: extract at least one identifier from the at least one transmitted IE; detect at least one type allocation code (TAC) from the at least one extracted identifier;compare the at least one detected TAC with one or more predefined TACs associated with corresponding IP addresses stored in a first IP pool; and allocate the IP address to the UE (104) from the first IP pool when the at least one detected TAC matches one of the one or more predefined TACs in the first IP pool.

8. The system (108) as claimed in claim 7, wherein the at least one information element (IE) comprises a user identifier, a quality of service (QoS) parameter, a session type, a user location, an access point name (APN), a network service type, and a configuration type.

9. The system (108) as claimed in claim 7, wherein the at least one identifier is one of an International Mobile Equipment Identity (IMEI) and a Permanent Equipment Identifier (PEI).

10. The system (108) as claimed in claim 7, wherein the UPF (214) is configured to assign the IP address to the UE (104) from a second pool, designated to a data network (106) node (DNN) or a network (106) slice, when the at least one detected TAC fails to match any of the one or more predefined TACs in the first IP pool.

11. The system (108) as claimed in claim 7, wherein the assigned IP address is selected from an internet protocol version 4 (IPv4) address, an internet protocol version 6 (IPv6) address or a combination thereof.

12. The system (108) as claimed in claim 7, wherein the UPF (214) is further configured to store a record of at least one detected TAC, at least onecorresponding identifier of the UE (104) and at least one allocated IP address in the first IP pool.

13. A method (600) for allocating an Internet Protocol (IP) address or prefix in a user plane function (UPF) (214), the method (600) comprising: receiving (602), by the UPF (214), a first request from a control plane (CP) function to allocate a user equipment (UE) (104) IP address or prefix, wherein the first request comprises: a UE (104) IP address information element (IE) comprising one or more IP version flags, wherein the one or more IP version flags comprises an IPv4 flag and / or an IPv6 flag; and a network instance IE indicating an IP address pool from which the UE (104) IP address or prefix is to be allocated; determining (604), by the UPF (214), an IP version selected from one or both of an IPv4 address and / or an IPv6 address, to be allocated, based on the IPv4 flag and / or the IPv6 flag included in the UE (104) IP address IE; selecting (606), by the UPF (214), the UE (104) IP address or prefix corresponding to the determined IP version from the IP address pool, indicated by the network (106) instance IE in the first request; and allocating (608), by the UPF (214), the selected UE (104) IP address or prefix to one or more packet detection rules (PDRs) and / or traffic endpoints to be created or modified, in response to the first request.

14. The method (600) as claimed in claim 13, wherein the first request is selected from at least one of a packet forwarding control protocol (PFCP) session establishment request or a PFCP session modification request.

15. The method (600) as claimed in claim 13, wherein the response is selected from at least one of a PFCP session establishment response or a PFCP session modification response.

16. The method (600) as claimed in claim 13, wherein upon determining that both the IPv4 flag and the IPv6 flag are included in the UE (104) IP address IE, the UP function allocates at least one of the IPv4 address, the IPv6 address, or a combination thereof based on an operator policy, wherein the operator policy is determined based on at least one of a locally configured international mobile equipment identity type allocation code (IMEI TAC) and a protocol data unit (PDU) session type mapping.

17. The method (600) as claimed in claim 13, wherein receiving, by the UPF (214), the first request from the CP function to allocate the UE (104) IP address or prefix comprises receiving a single request to allocate a same UE (104) IP address or prefix to a plurality of PDRs to be created or modified, wherein each of the plurality of PDRs comprises a UE (104) IP address IE comprising one or more IP version flags, indicating the request to allocate the same UE (104) IP address or prefix to the plurality of PDRs.

18. The method (600) as claimed in claim 13, wherein receiving, by the UPF (214), the first request from the CP function to allocate the UE (104) IP address or prefix comprises receiving a request to allocate a same UE (104) IP address or prefix to a plurality of PDRs to be created or modified, wherein the request comprises: a create traffic endpoint IE or an update traffic endpoint IE, wherein the create traffic endpoint IE or the update traffic endpoint IE comprises aUE (104) IP Address IE with one or more IP version flags indicating a selection of a new UE (104) IP address or prefix; and the plurality of PDRs to be created or modified, each comprising a traffic endpoint identity (ID), wherein an inclusion of the traffic endpoint ID in each of the plurality of PDRs and a use of one or more IP version flags in the UE (104) IP Address IE of the traffic endpoint IE, enable the UPF (214) to allocate the same UE (104) IP address or prefix to the plurality of PDRs.

19. The method (600) as claimed in claim 13, wherein the first request further comprises a UE (104) IP address pool identity indicating the IP address pool for allocation of the UE (104) IP address or prefix by the UPF (214).

20. The method (600) as claimed in claim 13, further comprising: receiving, by the UPF (214), a second request selected from at least one of: a request to delete a PFCP session; a request to delete the traffic endpoint associated with the allocated UE (104) IP address or prefix; and a request to remove a packet detection rule (PDR) associated with the allocated UE (104) IP address or prefix; and deallocating, by the UPF (214), the UE (104) IP address or prefix allocated to at least one of the PFCP session, the traffic endpoint, and the PDR in response to the second request.

21. The method (600) as claimed in claim 13, further comprising receiving, by the UPF (214), a third request from the CP function to allocate an additional UE (104) IP address or prefix, wherein the request comprises at least one of: an update PDR IE or an update traffic endpoint IE, wherein theadditional UE (104) IP address or prefix is different from the UE (104) IP address or prefix allocated in response to the first request.

22. The method (600) as claimed in claim 13, further comprising: selecting, by the UPF (214), the UE (104) IP address or prefix based on one or more of a single network (106) slice selection assistance information (S-NSSAI) associated with a PFCP session, the network (106) instance IE, and a UE (104) IP address pool identity; and allocating, by the UPF (214), the UE (104) IP address or prefix based on the selection.

23. The method (600) as claimed in claim 13, further comprising transmitting, by the UPF (214), a response to the CP function, wherein the response comprises at least one UE (104) IP address IE having a list of IP addresses or prefixes allocated to each of the one or more PDRs and / or the traffic endpoints, in response to creation or modification of the one or more PDRs or the traffic endpoints.

24. A system (108) for allocating an Internet Protocol (IP) address or prefix in a user plane function (UPF) (214), the system (108) comprising: the UPF (214) configured to: receive a first request from a control plane (CP) function to allocate a UE (104) IP address or prefix, wherein the first request comprises: a user equipment (UE) (104) IP address information element (IE) comprising one or more IP version flags, wherein the one or more IP version flags comprises an IPv4 flag and / or an IPv6 flag; anda network instance IE indicating an IP address pool from which the UE (104) IP address or prefix is to be allocated; determine an IP version selected from one or both of an IPv4 address and / or an IPv6 address, to be allocated, based on the IPv4 flag and / or the IPv6 flag included in the UE (104) IP address IE; select the UE (104) IP address or prefix corresponding to the determined IP version from the IP address pool, indicated by the network (106) instance IE in the first request; and allocate the selected UE (104) IP address or prefix to one or more packet detection rules (PDRs) and / or traffic endpoints to be created or modified, in response to the first request.

25. The system (108) as claimed in claim 24, wherein the first request is selected from at least one of a packet forwarding control protocol (PFCP) session establishment request or a PFCP session modification request.

26. The system (108) as claimed in claim 24, wherein the response is selected from at least one of a PFCP session establishment response or a PFCP session modification response.

27. The system (108) as claimed in claim 24, wherein upon determining that both the IPv4 flag and the IPv6 flag are included in the UE (104) IP address IE, the UP function allocates at least one of the IPv4 address, the IPv6 address, or a combination thereof based on an operator policy, wherein the operator policy is determined based on at least one of a locally configured international mobile equipment identity type allocation code (IMEI TAC) and a protocol data unit (PDU) session type mapping.

28. The system (108) as claimed in claim 24, wherein the first request received by the UPF (214) from the CP function to allocate the UE (104) IP address or prefix comprises receiving a single request to allocate a same UE (104) IP address or prefix to a plurality of PDRs to be created or modified, wherein each of the plurality of PDRs comprises a UE (104) IP address IE comprising one or more IP version flags, indicating the request to allocate the same UE (104) IP address or prefix to the plurality of PDRs.

29. The system (108) as claimed in claim 24, wherein the first request received by the UPF (214) from the CP function to allocate the UE (104) IP address or prefix comprises receiving a request to allocate a same UE (104) IP address or prefix to a plurality of PDRs to be created or modified, wherein the request comprises: a create traffic endpoint IE or an update traffic endpoint IE, wherein the create traffic endpoint IE or the update traffic endpoint IE comprises a UE (104) IP Address IE with one or more IP version flags indicating a selection of a new UE (104) IP address or prefix; and the plurality of PDRs to be created or modified, each comprising a traffic endpoint identity (ID), wherein an inclusion of the traffic endpoint ID in each of the plurality of PDRs and a use of one or more IP version flags in the UE (104) IP Address IE of the traffic endpoint IE, enable the UPF (214) to allocate the same UE (104) IP address or prefix to the plurality of PDRs.

30. The system (108) as claimed in claim 24, wherein the first request further comprises a UE (104) IP address pool identity indicating the IP address pool for allocation of the UE (104) IP address or prefix by the UPF (214).

31. The system (108) as claimed in claim 24, wherein the UPF (214) is configured to: receive a second request selected from at least one of: a request to delete a PF CP session; a request to delete the traffic endpoint associated with the allocated UE (104) IP address or prefix; and a request to remove a packet detection rule (PDR) associated with the allocated UE (104) IP address or prefix; and deallocate the UE (104) IP address or prefix allocated to at least one of the PF CP session, the traffic endpoint, and the PDR in response to the second request.

32. The system (108) as claimed in claim 24, wherein the UPF (214) is configured to receive a third request from the CP function to allocate an additional UE (104) IP address or prefix, wherein the request comprises at least one of: an update PDR IE or an update traffic endpoint IE, wherein the additional UE (104) IP address or prefix is different from the UE (104) IP address or prefix allocated in response to the first request.

33. The system (108) as claimed in claim 24, wherein the UPF (214) is configured to: select the UE (104) IP address or prefix based on one or more of a single network (106) slice selection assistance information (S-NSSAI) associated with a PFCP session, the network (106) instance IE, and a UE (104) IP address pool identity; and allocate the UE (104) IP address or prefix based on the selection.

34. The system (108) as claimed in claim 24, wherein the UPF (214) is configured to transmit a response to the CP function, wherein the response comprises at least one UE (104) IP address IE having a list of IP addresses or prefixes allocated to each of the one or more PDRs and / or the traffic endpoints, in response to creation or modification of the one or more PDRs or the traffic endpoints.

35. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of: receiving a connection request; sending an acknowledgment of the connection request to the network (106); and transmitting a plurality of signals in response to the connection request, wherein the UE (104) is connected with a system (108) configured to allocate an internet protocol (IP) address to the UE (104), as claimed in claim 7.

36. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for allocating an internet protocol (IP) address to a user equipment (UE) in a network (106), the method (500) comprising: receiving (502), by a session management function (SMF) (210), at least one request from the UE (104) to establish a session, wherein the at least one request comprises at least one information element (IE); transmitting (504), by the SMF (210), the at least one received IE to a user plane function (UPF) (214);extracting (506), by the UPF (214), at least one identifier from the at least one transmitted IE; detecting (508), by the UPF (214), at least one type allocation code (TAC) from the at least one extracted identifier; comparing (510), by the UPF (214), the at least one detected TAC with one or more predefined TACs associated with corresponding IP addresses stored in a first IP pool; and allocating (512), by the UPF (214), the IP address to the UE (104) from the first IP pool when the at least one detected TAC matches one of the one or more predefined TACs in the first IP pool.

37. A user equipment (UE) (104) communicatively coupled with a network (106), the coupling comprises steps of: receiving a connection request; sending an acknowledgment of the connection request to the network (106); and transmitting a plurality of signals in response to the connection request, wherein the UE (104) is connected with a system (108) configured to allocate an internet protocol (IP) address or prefix in a user plane function (UPF) (214), as claimed in claim 24.

38. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for allocating an Internet Protocol (IP) address or prefix in a user plane function (UPF) (214), the method (600) comprising: receiving (602), by the UPF (214), a first request from a control plane (CP) function to allocate a user equipment (UE) (104) IP address or prefix, wherein the first request comprises:a UE (104) IP address information element (IE) comprising one or more IP version flags, wherein the one or more IP version flags comprises an IPv4 flag and / or an IPv6 flag; and a network instance IE indicating an IP address pool from which the UE (104) IP address or prefix is to be allocated; determining (604), by the UPF (214), an IP version selected from one or both of an IPv4 address and / or an IPv6 address, to be allocated, based on the IPv4 flag and / or the IPv6 flag included in the UE (104) IP address IE; selecting (606), by the UPF (214), the UE (104) IP address or prefix corresponding to the determined IP version from the IP address pool, indicated by the network (106) instance IE in the first request; and allocating (608), by the UPF (214), the selected UE (104) IP address or prefix to one or more packet detection rules (PDRs) and / or traffic endpoints to be created or modified, in response to the first request.

Images