FORM 2
THE PATENTS ACT, 1970 (39 OF 1970) & THE PATENT RULES, 2003
COMPLETE SPECIFICATION
(See section 10 and rule 13)
“METHOD AND SYSTEM FOR LISTING DEVICES FOR OPTIMIZING ALLOCATION
OF IPV4 AND IPV6 ADDRESSES”
We, Jio Platforms Limited, an Indian National, of Office - 101, Saffron, Nr. Centre Point, Panchwati 5 Rasta, Ambawadi, Ahmedabad - 380006, Gujarat, India.
The following specification particularly describes the invention and the manner in which it is to be performed.

METHOD AND SYSTEM FOR LISTING DEVICES FOR OPTIMIZING ALLOCATION OF IPV4 AND IPV6 ADDRESSES
FIELD OF INVENTION
[0001] Embodiments of the present disclosure generally relate to wireless communication systems. More particularly, embodiments of the present disclosure relate to listing devices for allocation of internet protocol (IP) addresses.
BACKGROUND OF THE DISCLOSURE
[0002] The following description of the 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 is used only to enhance the understanding of the reader with respect to the present disclosure, and not as admissions of the prior art.
[0003] Wireless communication technology has rapidly evolved over the past few decades, with each generation bringing significant improvements and advancements. The first generation of wireless communication technology was based on analog technology and offered only voice services. However, with the advent of the second-generation (2G) technology, digital communication and data services became possible, and text messaging 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) technology revolutionized wireless communication with faster data speeds, better network coverage, and improved security. Currently, the fifth generation (5G) technology is being deployed, promising even faster data speeds, low latency, and the ability to connect multiple devices simultaneously. With each generation, wireless communication technology has become more advanced, sophisticated, and capable of delivering more services to its users.
[0004] The IMEI (International Mobile Equipment Identity) number is a unique 15-digit serial number for identifying a device. Every mobile phone in the world has a unique IMEI

number. This can be used to check details of a device, for example, the country from which
the mobile phone device has originated, warranty information, and more similar details.
One of the primary uses of IMEI numbers is blocking or tracking mobile phones through
a database where these IMEI numbers are stored. This database is called the IMEI database
(IMEI DB). When a phone powers on, the IMEI number is transmitted and verified by the
IMEI DB in the network’s Equipment Identity Register (EIR). The most common IMEI
format is AA-BBBBBB-CCCCCC-D, where:
AA: Represents the Reporting Body Identifier indicating Type Allocation Code (TAC) by
GSMA approval group
BBBBBB: Represents remaining TAC digits
CCCCCC: Represents the serial sequence of the model, or mobile phone
D: Algorithm used to validate the ID number.
[0005] As noted above, the first eight digits of an IMEI make up the Type Allocation Code (TAC). The TAC indicates the manufacturer and model of a particular device. So, all device models from a particular manufacturer will have the same TAC.
[0006] The previous internet architecture had fewer than 5 billion addresses available. But with rapidly growing number of Internet users, who increasingly used mobile computing devices, such as laptop computers, personal digital assistants (PDAs), and smart phones with IP data services, it became apparent that the pool of available IPv4 addresses was depleting at a rate that was not initially anticipated in the original design of the network. This depletion is one of the reasons for the development and deployment of its successor protocol, IPv6, which has trillions of addresses, enough to give every computer in the world a unique IP address. The long-term solution is to switch to Internet Protocol version 6 (IPv6). IPv6 is more advanced, and it is desirable that the devices are assigned IPv6 as it provides a vastly increased address space, but also allows improved route aggregation across the Internet, and offers large subnetwork allocations of a minimum of 264 host addresses to end users. However, IPv4 is not directly interoperable with IPv6, so that IPv4 only supported devices cannot directly communicate with IPv6 only supported devices.
[0007] But IPv6 addresses supporting devices may send request for IPv4 addresses also, along with the request for IPv6 addresses. This means that, that both IPv4 and IPv6

addresses are assigned to devices, which in turn means that IPv4 would be exhausted due to its limited number. The main difference between IPv4 and IPv6 is the address size of IP addresses. The IPv4 is a 32-bit address, whereas IPv6 is a 128-bit hexadecimal address. IPv6 provides a large address space, and it contains a simple header as compared to IPv4.
[0008] The new devices that are manufactured, are enabled for supporting both the IPv4 as well as IPv6 addresses. However, the previous generation devices support only IPv4 addresses and not IPv6 addresses. Now, since he IPv4 addresses are very limited, it would be prudent to think that they should be consumed by the devices that do not have any other option, that is, the devices that support only IPv4 addresses and not IPv6 addresses. In other words, the devices that do not support IPv6 and only support IPv4 may not get IPv4 assigned in case all IPv4 addresses get exhausted as they are assigned to all IPv6 supporting devices also.
[0009] Thus, there exists an imperative need in the art to provide a solution for listing devices for allocation of different versions of internet protocol (IP) addresses, which the present disclosure aims to address.
SUMMARY OF THE DISCLOSURE
[0010] This section is provided to introduce certain aspects of the present disclosure in a simplified form that are further described below in the detailed description. This summary is not intended to identify the key features or the scope of the claimed subject matter.
[0011] An aspect of the present disclosure may relate to a method for listing devices for allocation of internet protocol (IP) addresses. The method comprises receiving, by a transceiver unit of a session management function (SMF) module from a user device via an access and mobility management function (AMF) module, a first request for establishing a data session, the first request comprising an international mobile equipment identity type allocation code (IMEI TAC) of the user device. Further, the method comprises generating, by a decision unit of the SMF module, one of an IPv4 address decision and an IPv6 address decision, based on the IMEI TAC of the user device, and a pre-configured list of one or more IMEI TACs. Further, the method comprises sending, by

the transceiver unit of the SMF module to a user plane function (UPF) module, a second request for assigning one of the IPv4 address and the IPv6 address based on the generated decision, wherein the second request for assigning the IPv4 address is sent in an event the IPv4 address decision is generated, and the second request for assigning the IPv6 address is sent in an event the IPv6 address decision is generated.
[0012] In an exemplary aspect of the present disclosure, the method further comprises receiving, by the transceiver unit of the SMF module from the UPF module, an assignment of one of the IPv4 address and the IPv6 address; and communicating, by the transceiver unit of the SMF module to the AMF module, an attachment information based on the assignment of the one of the IPv4 address and the IPv6 address.
[0013] In an exemplary aspect of the present disclosure, the method further comprises communicating, by the AMF module to the user device, the attachment information.
[0014] In an exemplary aspect of the present disclosure, the method further comprises maintaining, by a storage unit, the pre-configured list of one or more IMEI TACs.
[0015] In an exemplary aspect of the present disclosure, the pre-configured list of one or more IMEI TACs includes IMEI TACs of one or more first type user devices, and wherein the one or more first type user devices support the IPv4 address only.
[0016] In an exemplary aspect of the present disclosure, the generating, by the decision unit of the SMF module, one of the IPv4 address decision and the IPv6 address decision, is based on: searching, by the decision unit, the IMEI TAC of the user device in the pre-configured list of one or more IMEI TACs; and generating, by the decision unit, one of the IPv4 address decision and the IPv6 address decision based on the searching, wherein the IPv4 address decision is generated in an event the IMEI TAC of the user device is present in the pre-configured list of one or more IMEI TACs, and the IPv6 address decision is generated in an event the IMEI TAC of the user device is absent in the pre-configured list of one or more IMEI TACs.

[0017] Another aspect of the present disclosure may relate to a system for listing devices for allocation of internet protocol (IP) addresses. The system comprises a session management function (SMF) module. The SMF module further comprises a transceiver unit configured to receive, from a user device via an access and mobility management function (AMF) module, a first request for establishing a data session, the first request comprising an international mobile equipment identity type allocation code (IMEI TAC) of the user device. Further, the SMF module comprises a decision unit connected to at least the transceiver unit, the a decision unit configured to generate one of an IPv4 address decision and an IPv6 address decision, based on the IMEI TAC of the user device, and a pre-configured list of one or more IMEI TACs. Further, the transceiver unit is configured to send, to a user plane function (UPF) module, a second request for assigning one of the IPv4 address and the IPv6 address based on the generated decision, wherein the second request for assigning the IPv4 address is sent in an event the IPv4 address decision is generated, and the second request for assigning the IPv6 address is sent in an event the IPv6 address decision is generated.
[0018] Yet another aspect of the present disclosure may relate to a non-transitory computer readable storage medium storing instructions for listing devices for allocation of internet protocol (IP) addresses. The instructions include executable code which, when executed by one or more units of a system comprising a SMF module, causes a transceiver unit of the SMF module to receive, from a user device via an access and mobility management function (AMF) module, a first request for establishing a data session, the first request comprising an international mobile equipment identity - type allocation codes (IMEI TAC) of the user device. Further, the instructions when executed, cause a decision unit of the SMF module to generate one of an IPv4 address decision and an IPv6 address decision, based on the IMEI TAC of the user device, and a pre-configured list of one or more IMEI TACs. Further, the instructions when executed, cause the transceiver unit of the SMF module to send, to a user plane function (UPF) module, a second request for assigning one of the IPv4 address and the IPv6 address based on the generated decision, wherein the second request for assigning the IPv4 address is sent in an event the IPv4 address decision is generated, and the second request for assigning the IPv6 address is sent in an event the IPv6 address decision is generated.

OBJECTS OF THE DISCLOSURE
[0019] Some of the objects of the present disclosure, which at least one embodiment disclosed herein satisfies are listed herein below.
[0020] It is an object of the present disclosure to provide a system and a method for listing devices for optimizing allocation of IPv4 and IPv6 addresses.
[0021] It is another object of the present disclosure to provide a solution that whitelists devices that support only IPv4.
[0022] It is yet another object of the present disclosure to provide a solution to save IPv4 addresses by providing IPv4 addresses only to the devices that do not support IPv6 addresses.
DESCRIPTION OF THE DRAWINGS
[0023] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of the disclosed methods and systems in which like reference numerals refer to the same parts throughout the different drawings. Components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present disclosure. Also, the embodiments shown in the figures are not to be construed as limiting the disclosure, but the possible variants of the method and system according to the disclosure are illustrated herein to highlight the advantages of the disclosure. It will be appreciated by those skilled in the art that disclosure of such drawings includes disclosure of electrical components or circuitry commonly used to implement such components.
[0024] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture.

[0025] FIG. 2 illustrates an exemplary block diagram of a computing device upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure.
[0026] FIG. 3 illustrates an exemplary block diagram of a system for listing devices for allocation of internet protocol (IP) addresses, in accordance with exemplary implementations of the present disclosure.
[0027] FIG. 4 illustrates a method flow diagram for listing devices for allocation of internet protocol (IP) addresses in accordance with exemplary implementations of the present disclosure.
[0028] The foregoing shall be more apparent from the following more detailed description of the disclosure.
DETAILED DESCRIPTION
[0029] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, that embodiments of the present disclosure may be practiced without these specific details. Several features described hereafter may 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.
[0030] 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.

[0031] 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, processes, and other components may be shown as components in block diagram form in order not to obscure the embodiments in unnecessary detail.
[0032] Also, it is noted that individual embodiments may be described as a process which is depicted as a flowchart, a flow diagram, a data flow diagram, a structure diagram, or a block diagram. Although a flowchart may describe the operations as a sequential process, many of the operations may 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.
[0033] 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—in a manner similar to the term “comprising” as an open transition word— without precluding any additional or other elements.
[0034] As used herein, a “processing unit” or “processor” or “operating processor” includes one or more processors, wherein processor refers to any logic circuitry for processing instructions. A processor may be a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor, a plurality of microprocessors, one or more microprocessors in association with a (Digital Signal Processing) DSP core, a controller, a microcontroller, Application Specific Integrated Circuits, Field Programmable Gate Array circuits, any other type of integrated circuits, etc. The processor may perform signal coding data processing, input/output processing, and/or

any other functionality that enables the working of the system according to the present disclosure. More specifically, the processor or processing unit is a hardware processor.
[0035] As used herein, “a user equipment”, “a user device”, “a smart-user-device”, “a smart-device”, “an electronic device”, “a mobile device”, “a handheld device”, “a wireless communication device”, “a mobile communication device”, “a communication device” may be any electrical, electronic and/or computing device or equipment, capable of implementing the features of the present disclosure. The user equipment/device may include, but is not limited to, a mobile phone, smart phone, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, wearable device or any other computing device which is capable of implementing the features of the present disclosure. Also, the user device may contain at least one input means configured to receive an input from at least one of a transceiver unit, a processing unit, a storage unit, a detection unit and any other such unit(s) which are required to implement the features of the present disclosure.
[0036] As used herein, “storage unit” or “memory unit” refers to a machine or computer-readable medium including any mechanism for storing information in a form readable by a computer or similar machine. For example, a computer-readable medium includes read¬only memory (“ROM”), random access memory (“RAM”), magnetic disk storage media, optical storage media, flash memory devices or other types of machine-accessible storage media. The storage unit stores at least the data that may be required by one or more units of the system to perform their respective functions.
[0037] As used herein “interface” or “user interface refers to a shared boundary across which two or more separate components of a system exchange information or data. The interface may also be referred to a set of rules or protocols that define communication or interaction of one or more modules or one or more units with each other, which also includes the methods, functions, or procedures that may be called.
[0038] All modules, units, components used herein, unless explicitly excluded herein, may be software modules or hardware processors, the processors being a general-purpose processor, a special purpose processor, a conventional processor, a digital signal processor

(DSP), a plurality of microprocessors, one or more microprocessors in association with a DSP core, a controller, a microcontroller, Application Specific Integrated Circuits (ASIC), Field Programmable Gate Array circuits (FPGA), any other type of integrated circuits, etc.
[0039] As used herein the transceiver unit includes at least one receiver and at least one transmitter configured respectively for receiving and transmitting data, signals, information or a combination thereof between units/components within the system and/or connected with the system.
[0040] As discussed in the background section, IPv4 only supported devices cannot directly communicate with IPv6 only supported devices. But IPv6 supported devices may send request for IPv4 addresses also, along with the request for IPv6 addresses. This means that, that both IPv4 and IPv6 addresses are assigned to devices, which in turn means that IPv4 would be exhausted due to its limited number. Therefore, we see that the current implementations have several shortcomings. The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing method and system of listing devices for allocation of internet protocol (IP) addresses.
[0041] FIG. 1 illustrates an exemplary block diagram representation of 5th generation core (5GC) network architecture, in accordance with exemplary implementation of the present disclosure. As shown in FIG. 1, the 5GC network architecture [100] includes a user equipment (UE) [102], a radio access network (RAN) [104], an access and mobility management function (AMF) [106], a Session Management Function (SMF) [108], a Service Communication Proxy (SCP) [110], an Authentication Server Function (AUSF) [112], a Network Slice Specific Authentication and Authorization Function (NSSAAF) [114], a Network Slice Selection Function (NSSF) [116], a Network Exposure Function (NEF) [118], a Network Repository Function (NRF) [120], a Policy Control Function (PCF) [122], a Unified Data Management (UDM) [124], an application function (AF) [126], a User Plane Function (UPF) [128], a data network (DN) [130], wherein all the components are assumed to be connected to each other in a manner as obvious to the person skilled in the art for implementing features of the present disclosure.

[0042] Radio Access Network (RAN) [104] is the part of a mobile telecommunications system that connects user equipment (UE) [102] to the core network (CN) and provides access to different types of networks (e.g., 5G network). It consists of radio base stations and the radio access technologies that enable wireless communication.
[0043] Access and Mobility Management Function (AMF) [106] is a 5G core network function responsible for managing access and mobility aspects, such as UE registration, connection, and reachability. It also handles mobility management procedures like handovers and paging.
[0044] Session Management Function (SMF) [108] is a 5G core network function responsible for managing session-related aspects, such as establishing, modifying, and releasing sessions. It coordinates with the User Plane Function (UPF) for data forwarding and handles IP address allocation and QoS enforcement.
[0045] Service Communication Proxy (SCP) [110] is a network function in the 5G core network that facilitates communication between other network functions by providing a secure and efficient messaging service. It acts as a mediator for service-based interfaces.
[0046] Authentication Server Function (AUSF) [112] is a network function in the 5G core responsible for authenticating UEs during registration and providing security services. It generates and verifies authentication vectors and tokens.
[0047] Network Slice Specific Authentication and Authorization Function (NSSAAF) [114] is a network function that provides authentication and authorization services specific to network slices. It ensures that UEs can access only the slices for which they are authorized.
[0048] Network Slice Selection Function (NSSF) [116] is a network function responsible for selecting the appropriate network slice for a UE based on factors such as subscription, requested services, and network policies.

[0049] Network Exposure Function (NEF) [118] is a network function that exposes capabilities and services of the 5G network to external applications, enabling integration with third-party services and applications.
[0050] Network Repository Function (NRF) [120] is a network function that acts as a central repository for information about available network functions and services. It facilitates the discovery and dynamic registration of network functions.
[0051] Policy Control Function (PCF) [122] is a network function responsible for policy control decisions, such as QoS, charging, and access control, based on subscriber information and network policies.
[0052] Unified Data Management (UDM) [124] is a network function that centralizes the management of subscriber data, including authentication, authorization, and subscription information.
[0053] Application Function (AF) [126] is a network function that represents external applications interfacing with the 5G core network to access network capabilities and services.
[0054] User Plane Function (UPF) [128] is a network function responsible for handling user data traffic, including packet routing, forwarding, and QoS enforcement.
[0055] Data Network (DN) [130] refers to a network that provides data services to user equipment (UE) in a telecommunications system. The data services may include but are not limited to Internet services, private data network related services.
[0056] FIG. 2 illustrates an exemplary block diagram of a computing device [200] upon which the features of the present disclosure may be implemented in accordance with exemplary implementation of the present disclosure. In an implementation, the computing device [200] may also implement a method for listing devices for allocation of internet protocol (IP) addresses utilising the system. In another implementation, the computing device [200] itself implements the method for listing devices for allocation of internet

protocol (IP) addresses using one or more units configured within the computing device [200], wherein said one or more units are capable of implementing the features as disclosed in the present disclosure.
[0057] The computing device [200] may include a bus [202] or other communication mechanism for communicating information, and a hardware processor [204] coupled with bus [202] for processing information. The hardware processor [204] may be, for example, a general-purpose microprocessor. The computing device [200] may also include a main memory [206], such as a random-access memory (RAM), or other dynamic storage device, coupled to the bus [202] for storing information and instructions to be executed by the processor [204]. The main memory [206] also may be used for storing temporary variables or other intermediate information during execution of the instructions to be executed by the processor [204]. Such instructions, when stored in non-transitory storage media accessible to the processor [204], render the computing device [200] into a special-purpose machine that is customized to perform the operations specified in the instructions. The computing device [200] further includes a read only memory (ROM) [208] or other static storage device coupled to the bus [202] for storing static information and instructions for the processor [204].
[0058] A storage device [210], such as a magnetic disk, optical disk, or solid-state drive is provided and coupled to the bus [202] for storing information and instructions. The computing device [200] may be coupled via the bus [202] to a display [212], such as a cathode ray tube (CRT), Liquid crystal Display (LCD), Light Emitting Diode (LED) display, Organic LED (OLED) display, etc. for displaying information to a computer user. An input device [214], including alphanumeric and other keys, touch screen input means, etc. may be coupled to the bus [202] for communicating information and command selections to the processor [204]. Another type of user input device may be a cursor controller [216], such as a mouse, a trackball, or cursor direction keys, for communicating direction information and command selections to the processor [204], and for controlling cursor movement on the display [212]. This input device typically has two degrees of freedom in two axes, a first axis (e.g., x) and a second axis (e.g., y), that allow the device to specify positions in a plane.

[0059] The computing device [200] may implement the techniques described herein using customized hard-wired logic, one or more ASICs or FPGAs, firmware and/or program logic which in combination with the computing device [200] causes or programs the computing device [200] to be a special-purpose machine. According to one implementation, the techniques herein are performed by the computing device [200] in response to the processor [204] executing one or more sequences of one or more instructions contained in the main memory [206]. Such instructions may be read into the main memory [206] from another storage medium, such as the storage device [210]. Execution of the sequences of instructions contained in the main memory [206] causes the processor [204] to perform the process steps described herein. In alternative implementations of the present disclosure, hard-wired circuitry may be used in place of or in combination with software instructions.
[0060] The computing device [200] also may include a communication interface [218] coupled to the bus [202]. The communication interface [218] provides a two-way data communication coupling to a network link [220] that is connected to a local network [222]. For example, the communication interface [218] may be an integrated services digital network (ISDN) card, cable modem, satellite modem, or a modem to provide a data communication connection to a corresponding type of telephone line. As another example, the communication interface [218] may be a local area network (LAN) card to provide a data communication connection to a compatible LAN. Wireless links may also be implemented. In any such implementation, the communication interface [218] sends and receives electrical, electromagnetic or optical signals that carry digital data streams representing various types of information.
[0061] The computing device [200] can send messages and receive data, including program code, through the network(s), the network link [220] and the communication interface [218]. In the Internet example, a server [230] might transmit a requested code for an application program through the Internet [228], the ISP [226226], the local network [222], the host [224], and the communication interface [218]. The received code may be executed by the processor [204] as it is received, and/or stored in the storage device [210], or other non-volatile storage for later execution.

[0062] Referring to FIG. 3, an exemplary block diagram of a system [300] for listing devices for allocation of internet protocol (IP) addresses, is shown, in accordance with the exemplary implementations of the present disclosure. The system [300] comprises at least one session management function (SMF) module [301]. The SMF module [301] further comprises at least one transceiver unit [302], at least one decision unit [306], and at least one storage unit [310]. Further, the system [300] comprises at least one access and mobility management function (AMF) module [304], and at least one user plane function (UPF) module [308]. Notably, the SMF module [301] as shown in Fig. 3 is same as the SMF [108] as shown in Fig. 1. Similarly, the AMF module [304] of Fig. 3 is same as the AMF [106] of Fig. 1, and the UPF module [308] of Fig. 3 is same as the UPF [128] of Fig. 1. Also, all the components/ units of the system [300] are assumed to be connected to each other unless otherwise indicated below. As shown in the figure, all units shown within the system should also be assumed to be connected to each other. Also, in Fig. 3 only a few units are shown, however, the system [300] may comprise multiple such units or the system [300] may comprise any such number of said units, as required to implement the features of the present disclosure. In another implementation, the system [300] may reside in a server or a network entity.
[0063] Further, in accordance with the present disclosure, it is to be acknowledged that the functionality described for the various components/units can be implemented interchangeably. While specific embodiments may disclose a particular functionality of these units for clarity, it is recognized that various configurations and combinations thereof are within the scope of the disclosure. The functionality of specific units as disclosed in the disclosure should not be construed as limiting the scope of the present disclosure. Consequently, alternative arrangements and substitutions of units, provided they achieve the intended functionality described herein, are considered to be encompassed within the scope of the present disclosure.
[0064] The system [300] is configured for listing devices for allocation of internet protocol (IP) addresses, with the help of the interconnection between the components/units of the system [300].

[0065] The transceiver unit [302] is configured to receive, from a user device via an access and mobility management function (AMF) [304] module, a first request for establishing a data session, the first request comprising an international mobile equipment identity type allocation code (IMEI TAC) of the user device. In an implementation this first request comprises a request for attaching with a network component for establishing the data session. The Type Allocation Code (TAC) may be the initial eight-digit portion of the 15-digit IMEI code of the user device. The Type Allocation Code may identify a particular model (i.e., a user device) of wireless telephone for use on a GSM, UMTS, LTE, 5G NR, iDEN, Iridium or other IMEI-employing wireless networks as known in the art.
[0066] Further, the decision unit [306] is connected to at least the transceiver unit [302]. The decision unit [306] is configured to generate one of: an IPv4 address decision, and an IPv6 address decision. This decision may be based on the IMEI TAC of the user device, and a pre-configured list of one or more IMEI TACs. In an implementation, the decision unit [306] is configured to generate: the IPv4 address decision in an event the user device is a first type user device, and the IPv6 address decision in an event the user device is a second type user device. The pre-configured list includes IMEI TACs of one or more first type user devices. Here, the first type user device refers to a user device that supports only the IPv4 address. Further, a second type refers to a user device that user device supports both the IPv4 address and the IPv6 address. For this purpose, the storage unit [310] is configured to maintain the pre-configured list of one or more IMEI TACs. Also, the pre-configured list of the IMEI TACs of the user devices may be updated time to time as the new devices may enter the market.
[0067] For example, the pre-configured list of the IMEI TACs may comprise the existing devices from various manufacturers. With the information provided by the device manufacturers, it is already known as to what IP version the device supports. Based on this information, the device may be categorized as a first type device or a second type device. For example, a manufacturer X of a user device Y discloses that the user device Y supports only IPv4, and a manufacturer A of a user device B discloses that the user device B supports both IPv4 and IPv6. Thus, the pre-configured list of the IMEI TACs may contain the IMEI TAC of the user device Y and not the IMEI TAC of the user device B. In an implementation, for generating one of the IPv4 address decision and the IPv6 address

decision, the decision unit [306] may search the IMEI TAC of the user device in the pre-configured list of one or more IMEI TACs. Once the IMEI TAC of the user device is found in the pre-configured list, the decision unit [306] generates the IPv4 address decision which means that an IPv4 address should be assigned to this user device. This is because the pre-configured list comprises IMEI TACs of only those user devices which support only IPv4 addresses only and not IPv6 addresses, i.e., IMEI TACs of the first type user devices only. Also, say for example, there are a total of 2000 devices that are being sold in the market, out of which 500 devices are first type user device and other 1500 user devices are second type user device. Since the manufacturers’ data is already available that which particular device supports only IPv4 address (first type device) and which device supports both IPv4 and IPv6 (second type device), the pre-configured list can be maintained for the 500 first type user devices.
[0068] Further, the transceiver unit [302] is configured to send, to a user plane function (UPF) module [308], a second request for assigning one of the IPv4 address and the IPv6 address based on the generated decision. Here, the second request for assigning the IPv4 address is sent in an event the IPv4 address decision is generated, and the second request for assigning the IPv6 address is sent in an event the IPv6 address decision is generated. This means that the SMF module [301] generates a decision to assign the IPv4 or the IPv6 address to the user device. Further, since the IP address is to be assigned by the UPF module [308], therefore the SMF module [301] sends a request, i.e., the second request as used herein, to the UPF module [308] for actual assignment of the IP address to the user device, based on the decision generated by the SMF module [301]. According to the decision of the SMF module [301], the UPF module [308] assigns one of the IPv4 address and the IPv6 address to the user device, and communicates an attachment information related to this assignment, to the SMF module [301].
[0069] Thus, for this purpose, in an implementation, the transceiver unit [302] is further configured to: receive, from the UPF module [308], an assignment of one of the IPv4 address and the IPv6 address. The assignment of IPv4 or IPv6 is done based on the decision communicated by the SMF module [301] to the UPF module [308]. For example, if it is determined that the user device supports IPv4 address only, then the assignment is done by the UPF module [308] by assigning an IPv4 address to the user device, and if it is

determined that the user device supports both IPv4 address as well as IPv6 address, then the assignment is done by the UPF module [308] by assigning an IPv6 address to the user device. Further, in this implementation, the transceiver unit [302] is further configured to communicate, to the AMF module [304], the attachment information based on the assignment of the one of the IPv4 address and the IPv6 address. In an implementation, the attachment information comprises the IP address for the user device that the UPF module [308] has assigned. Further, in an implementation, the AMF module [304] is configured to communicate, to the user device, the attachment information.
[0070] Referring to Figure 4, an exemplary method flow diagram [400] for listing devices for allocation of internet protocol (IP) addresses, in accordance with exemplary implementations of the present disclosure is shown. In an implementation the method [400] is performed by the system [300]. Further, in an implementation, the system [300] may be present in a server device to implement the features of the present disclosure. Also, as shown in Figure 4, the method [400] starts at step [402].
[0071] At step 402, the method comprises receiving, by a transceiver unit [302] of a session management function (SMF) module [301] from a user device via an access and mobility management function (AMF) [304] module, a first request for establishing a data session. The first request comprises an international mobile equipment identity type allocation code (IMEI TAC) of the user device. In an implementation, this first request comprises a request for attaching with a network component for establishing the data session. The Type Allocation Code (TAC) may be the initial eight-digit portion of the 15-digit IMEI code of the user device. The Type Allocation Code may identify a particular model (i.e., a user device) of wireless telephone for use on a GSM, UMTS, LTE, 5G NR, iDEN, Iridium or other IMEI-employing wireless networks as known in the art.
[0072] Further, at step 404, the method comprises generating, by a decision unit [306] of the SMF module [301], one of an IPv4 address decision and an IPv6 address decision. This decision may be based on the IMEI TAC of the user device, and a pre-configured list of one or more IMEI TACs. In an implementation, the decision unit [306] may generate: the IPv4 address decision in an event the user device is a first type user device, and the IPv6 address decision in an event the user device is a second type user device. The pre-

configured list includes one or more IMEI TACs of one or more first type user devices. Here, the first type user device refers to a user device that supports only the IPv4 address, and the second type user device refers to a user device that supports both the IPv4 address and the IPv6 address. For this purpose, in an implementation, the method comprises maintaining, by a storage unit [310], the pre-configured list of one or more IMEI TACs. Also, the pre-configured list of the IMEI TACs of the user devices may be updated time to time as the new devices may enter the market.
[0073] For example, the pre-configured list of the IMEI TACs may comprise the existing devices from various manufacturers. With the information provided by the device manufacturers, it is already known as to what IP version the device supports. Based on this information, the device may be categorized as a first type device or a second type device. For example, a manufacturer X of a user device Y discloses that the user device Y supports only IPv4, and a manufacturer A of a user device B discloses that the user device B supports both IPv4 and IPv6. Thus, the pre-configured list of the IMEI TACs may contain the IMEI TAC of the user device Y and not the IMEI TAC of the user device B. In an implementation, for generating one of the IPv4 address decision and the IPv6 address decision, the decision unit [306] may search the IMEI TAC of the user device in the pre-configured list of one or more IMEI TACs. Once the IMEI TAC of the user device is found in the pre-configured list, the decision unit [306] generates the IPv4 address decision which means that an IPv4 address should be assigned to this user device. This is because the pre-configured list comprises IMEI TACs of only those user devices which support only IPv4 addresses only and not IPv6 addresses, i.e., IMEI TACs of the first type user devices only. Also, say for example, there are a total of 2000 devices that are being sold in the market, out of which 500 devices are first type user device and other 1500 user devices are second type user devices. Since the manufacturers’ data is already available that which particular device supports only IPv4 address (first type device) and which device supports both IPv4 and IPv6 (second type device), the pre-configured list can be maintained for the 500 first type user devices.
[0074] Further, at step 406, the method comprises sending, by the transceiver unit [302] of the SMF module [301] to a user plane function (UPF) module [308], a second request for assigning one of the IPv4 address and the IPv6 address based on the generated decision.

Here, the second request for assigning the IPv4 address is sent in an event the IPv4 address decision is generated, and the second request for assigning the IPv6 address is sent in an event the IPv6 address decision is generated. This means that the SMF module [301] generates a decision to assign the IPv4 or the IPv6 address to the user device. Further, since the IP address is to be assigned by the UPF module [308], therefore the SMF module [301] sends a request, i.e., the second request as used herein, to the UPF module [308] for actual assignment of the IP address to the user device, based on the decision generated by the SMF module [301]. According to the decision of the SMF module [301], the UPF module [308] assigns one of the IPv4 address and the IPv6 address to the user device, and communicates an attachment information related to this assignment, to the SMF module [301].
[0075] Thus, for this purpose, in an implementation, the method comprises receiving, by the transceiver unit [302] of the SMF module [301] from the UPF module [308], an assignment of one of the IPv4 address and the IPv6 address. The assignment of IPv4 or IPv6 is done based on the decision communicated by the SMF module [301] to the UPF module [308]. For example, if it is determined that the user device supports IPv4 address only, then the assignment is done by the UPF module [308] by assigning an IPv4 address to the user device, and if it is determined that the user device supports both IPv4 address as well as IPv6 address, then the assignment is done by the UPF module [308] by assigning an IPv6 address to the user device. Further, in this implementation, the method comprises communicating, by the transceiver unit [302] of the SMF module [301] to the AMF module [304], the attachment information based on the assignment of the one of the IPv4 address and the IPv6 address. In an implementation, the attachment information comprises the IP address for the user device that the UPF module [308] has assigned. Further, in an implementation, the method comprises communicating, by the AMF module [304] to the user device, the attachment information.
[0076] The present disclosure further discloses a non-transitory computer readable storage medium storing instructions for listing devices for allocation of internet protocol (IP) addresses. The instructions include executable code. The executable code may be executed by one or more units of a system [300]. The system [300] comprises at least one session management function (SMF) module [301]. The SMF module [301] further comprises at

least one transceiver unit [302], at least one decision unit [306], and at least one storage unit [310]. Further, the system [300] comprises at least one access and mobility management function (AMF) module [304], and at least one user plane function (UPF) module [308]. The executable code, when executed by one or more units of a system [300], causes the transceiver unit [302] of the SMF module [301] to receive, from a user device via the AMF module [304], a first request for establishing a data session. The first request comprises an international mobile equipment identity -type allocation codes (IMEI TAC) of the user device. Further, the executable code when executed, causes a decision unit [306] of the SMF module [301] to generate one of an IPv4 address decision and an IPv6 address decision. This address decision is based on the IMEI TAC of the user device, and a pre-configured list of one or more IMEI TACs. Further, the executable code when executed, causes the transceiver unit [302] of the SMF module [301] to send, to the UPF module [308], a second request for assigning one of the IPv4 address and the IPv6 address based on the generated decision, wherein the second request for assigning the IPv4 address is sent in an event the IPv4 address decision is generated, and the second request for assigning the IPv6 address is sent in an event the IPv6 address decision is generated.
[0077] As is evident from the above, the present disclosure provides a technically advanced solution for listing devices for allocation of internet protocol (IP) addresses. The present solution enables one to optimize allocation of IPv4 and IPv6 addresses. Further, the present solution enables one to whitelist devices that support only IPv4. Also, the present solution enables one to save IPv4 addresses by providing IPv4 addresses only to the devices that do not support IPv6 addresses.
[0078] While considerable emphasis has been placed herein on the disclosed implementations, it will be appreciated that many implementations can be made and that many changes can be made to the implementations without departing from the principles of the present disclosure. These and other changes in the implementations of the present disclosure will be apparent to those skilled in the art, whereby it is to be understood that the foregoing descriptive matter to be implemented is illustrative and non-limiting.

We Claim:
1. A method for listing devices for allocation of internet protocol (IP) addresses, the
method comprising:
- receiving, by a transceiver unit [302] of a session management function (SMF) module [301] from a user device via an access and mobility management function (AMF) module [304], a first request for establishing a data session, the first request comprising an international mobile equipment identity type allocation code (IMEI TAC) of the user device;
- generating, by a decision unit [306] of the SMF module [301], one of an IPv4 address decision and an IPv6 address decision based on the IMEI TAC of the user device, and a pre-configured list of one or more IMEI TACs; and
- sending, by the transceiver unit [302] of the SMF module [301] to a user plane function (UPF) module [308], a second request for assigning one of an IPv4 address and an IPv6 address based on the generated decision, wherein the second request for assigning the IPv4 address is sent in an event the IPv4 address decision is generated, and the second request for assigning the IPv6 address is sent in an event the IPv6 address decision is generated.
2. The method as claimed in claim 1, the method further comprising:
- receiving, by the transceiver unit [302] of the SMF module [301] from the UPF module [308], an assignment of one of the IPv4 address and the IPv6 address; and
- communicating, by the transceiver unit [302] of the SMF module [301] to the AMF module [304], an attachment information based on the assignment of the one of the IPv4 address and the IPv6 address.
3. The method as claimed in claim 2, the method further comprising:
- communicating, by the AMF module [304] to the user device, the attachment
information.
4. The method as claimed in claim 1, wherein the method comprises:

- maintaining, by a storage unit [310], the pre-configured list of one or more
IMEI TACs.
5. The method as claimed in claim 1, wherein the pre-configured list of one or more IMEI TACs includes IMEI TACs of one or more first type user devices, and wherein the one or more first type user devices support the IPv4 address only.
6. The method as claimed in claim 1, wherein the generating, by the decision unit [306] of the SMF module [301], one of the IPv4 address decision and the IPv6 address decision, is based on:

- searching, by the decision unit [306], the IMEI TAC of the user device in the pre-configured list of one or more IMEI TACs; and
- generating, by the decision unit [306], one of the IPv4 address decision and the IPv6 address decision based on the searching,
wherein the IPv4 address decision is generated in an event the IMEI TAC of the user device is present in the pre-configured list of one or more IMEI TACs, and the IPv6 address decision is generated in an event the IMEI TAC of the user device is absent in the pre-configured list of one or more IMEI TACs.
7. A system for listing devices for allocation of internet protocol (IP) addresses, the
system comprising a session management function (SMF) module [301], the SMF
module [301] further comprising:
- a transceiver unit [302] configured to receive, from a user device via an access and mobility management function (AMF) module [304], a first request for establishing a data session, the first request comprising an international mobile equipment identity type allocation code (IMEI TAC) of the user device; and
- a decision unit [306] connected to at least the transceiver unit [302], the decision unit [306] configured to generate one of an IPv4 address decision and an IPv6 address decision, based on the IMEI TAC of the user device, and a pre-configured list of one or more IMEI TACs,
wherein the transceiver unit [302] is further configured to send, to a user plane function (UPF) module [308], a second request for assigning one of an IPv4 address and an IPv6 address based on the generated decision, wherein the

second request for assigning the IPv4 address is sent in an event the IPv4 address decision is generated, and the second request for assigning the IPv6 address is sent in an event the IPv6 address decision is generated.
8. The system as claimed in claim 7, wherein the transceiver unit [302] is further
configured to:
- receive, from the UPF module [308], an assignment of one of the IPv4 address and the IPv6 address; and
- communicate, to the AMF module [304], an attachment information based on the assignment of the one of the IPv4 address and the IPv6 address.

9. The system as claimed in claim 8, wherein the AMF module [304] is configured to communicate, to the user device, the attachment information.
10. The system as claimed in claim 7, further comprising:
- a storage unit [310] configured to maintain the pre-configured list of one or
more IMEI TACs.
11. The system as claimed in claim 7, wherein the pre-configured list of one or more IMEI TACs includes IMEI TACs of one or more first type user devices, and wherein the one or more first type user devices support the IPv4 address only.
12. The system as claimed in claim 7, wherein for generating one of the IPv4 address decision and the IPv6 address decision, the decision unit [306] is configured to:

- search the IMEI TAC of the user device in the pre-configured list of one or more IMEI TACs; and
- generate one of the IPv4 address decision and the IPv6 address decision based on the searching,
wherein the IPv4 address decision is generated in an event the IMEI TAC of the user device is present in the pre-configured list of one or more IMEI TACs, and the IPv6 address decision is generated in an event the IMEI TAC of the user device is absent in the pre-configured list of one or more IMEI TACs.