System and method for policy determination using international mobile equipment identity-type allocation code (IMEI-TAC)

Abstract

SYSTEM AND METHOD FOR POLICY DETERMINATION The present disclosure relates to a system (108) and a method (400) for determining a plurality of policies for a plurality of user equipments (UEs) (104). The method (400) includes a policy control function (PCF) (110). The PCF (110) includes 5 receiving a policy creation request from at least one UE (104) of the plurality of UEs (104) and extracting information from the received policy creation request, where the information includes international mobile equipment identity (IMEI) corresponding to the at least one UE (104). The PCF (110) includes detecting whether the extracted IMEI is present in a list stored in a database, where the list includes a plurality of IMEI-Type 10 Allocation Codes (TACs) and installing at least one of a plurality of policies for the at least one UE (104) based on detecting that the extracted IMEI is present in the list stored in the database.

Description

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

[0002] The present disclosure generally relates to the field of communication systems. More particularly, the present disclosure relates to a method and a system for policy determination using International Mobile Equipment Identity-Type Allocation Code (IMEI-TAC).DEFINITION

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

[0004] A “User Equipment (UE) Route Selection Policy (URSP)” refers to a policy that governs how user equipment (UE) selects routes within a network for communication. Specifically, it determines which packet data unit (PDU) session on a network slice a particular service or application should utilize upon activation. Thenetwork slice is a virtualized, isolated segment of a physical network designed to provide specific network services.

[0005] A “packet data unit (PDU) session” refers to a connection between a UE and a network that facilitates data transfer. It encompasses setting up and managing the communication path for transferring user data, application data, or service-specific data.

[0006] A “policy control function (PCF)” refers to a network function that provides policy control and decision-making capabilities. It is responsible for defining and enforcing policies related to quality of service (QoS), network slicing, and other network management aspects.

[0007] An “International Mobile Equipment Identity (IMEI)” refers to a unique identifier assigned to UE (e.g., mobile device). The IMEI number typically consists of 15 digits and comprises a type allocation code (TAC), a serial number (SND), and a check digit (CD).

[0008] The “Type Allocation Code (TAC) refers to the first 8 digits of the IMEI, which identify the device model and manufacturer.

[0009] The “Serial Number (SNR)” refers to following 6 digits after 8 digits of the IMEI, which provide a unique serial number for each device.

[0010] The “Check Digit (CD)” refers to the final digit of the IMEI, used for error checking to ensure the IMEI is valid.

[0011] An “Access and Mobility Management Function (AMF)” refers to the network function responsible for handling the access and mobility management of devices. It ensures that devices can connect to the network and move between different network areas seamlessly.

[0012] A “Subscription Profile Repository (SPR)” refers to is a network function that stores and manages subscription profiles and related data for users. It holds information necessary for handling user subscriptions and ensuring that network services are delivered according to the user's profile.

[0013] A “Subscriber Identity Module (SIM)” refers to a smart card inserted into a UE or a mobile device (such as a smartphone, tablet, or modem) that stores subscriber information and cryptographic keys. It is essential for authenticating and authorizing the device on the cellular network.

[0014] An “IP Multimedia Subsystem (IMS)” refers to multimedia communication services delivered over Internet Protocol (IP) networks using the IP Multimedia Subsystem (IMS) architecture. The IMS provides a standardized framework for integrating and managing various types of multimedia communication, enabling the delivery of services such as voice, video, and messaging across different network types and technologies.

[0015] A “Packet Data Unit (PDU) establishment” refers to the process of setting up a data session in a mobile network. A PDU session is created to facilitate data transfer between the UE and the network.

[0016] A “Permanent Equipment Identifier (PEI)” refers to a unique identifier assigned to a UE (e.g., mobile device) to differentiate the UE from other devices across networks and throughout their lifecycle. It is used for various purposes, including device identification and management.

[0017] A “Policy application” in the cellular network refers to the process of enforcing and implementing rules and policies that govern network behavior and service delivery. These policies are designed to manage network resources, ensure quality of service (QoS), control user access, and optimize network performance based on various criteria and user requirements.

[0018] A “Device manufacturer” refers to the company or organization responsible for designing, producing, and assembling a device, such as a smartphone, tablet, laptop, or other electronic equipment. The manufacturer is responsible for the overall product design, quality control, and ensuring that the device meets industry standards and regulations.

[0019] A “Result Code 400” refers to hypertext transfer protocol (HTTP) status code used in web and network communications. The result code 400 indicates that the server cannot or will not process the request due to an error.

[0020] An “ERROR REQUEST PARAMETERS” refers to an error indicating that one or more parameters included in the request are invalid, missing, or incorrectly formatted. The system or service is unable to process the request due to issues with these parameters.

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

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

[0023] A “User Equipment (UE) Route Selection Policy (URSP)” is a policy that governs how a UE selects routes within a network for communication. The URSP determines which packet data unit (PDU) session on a network slice a particular service or application should utilize upon activation. The URSP information is used to ensure efficient routing and resource allocation within the 5G network. It allows for theoptimized delivery of services and applications based on their specific requirements and network conditions. If URSP policies are sent to devices that do not support them, it can lead to disruptions in basic services. This underscores the importance of accurately provisioning devices with the appropriate URSP information to ensure smooth operation within the network.

[0024] Currently, the UE does not indicate its capabilities during initial registration, therefore, URSP policies are determined based on the subscriber profile in a subscriber profile repository (SPR). If there are multiple slices, this suggests potential URSP support, prompting an access and mobility management function (AMF) to request URSP policies from a policy control function (PCF). The PCF sends the URSP policies to the AMF / UE based on an international mobile equipment identity (IMSI) and its custom field in the SPR. For instance, if the UE that has a URSP- supported SIM / IMSI receives URSP policies, everything works fine. However, if the SIM is transferred to a non-URSP-supported operating system, the UE may still trigger the sending of the URSP policies due to the network's SIM / IMSI-based checks, potentially causing issues on the non-URSP-supported device. Further, if the SIM is inserted into the UE, the network sends the URSP policies regardless of the device type. This can potentially hinder basic internet or IMS services because the UE may not initiate basic PDU establishment. This issue arises because the current implementation relies on SIM / IMSI information rather than the type of device.

[0025] Therefore, there is a need for systems and methods to determine the URSP policies based on International Mobile Equipment Identity (IMEI) - Type Allocation Code (TAC).

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

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

[0028] An objective of the present disclosure is to provide a system and a method for policy determination using the International Mobile Equipment Identity- Type Allocation Code (IMEI-TAC).

[0029] Another objective of the present disclosure is to maintain a list of UE Route Selection Policy (URSP)-supported devices at a policy control function (PCF) to enable differentiation between the URSP- supported and non-supported devices.

[0030] Yet another objective of the present disclosure is to apply policies (e.g., URSP rules) to the URSP-supported devices based on the IMEI-TAC.

[0031] Yet another objective of the present disclosure is to improve resource utilization and network efficiency by sending the URSP rules / policies only to the URSP-supported devices.

[0032] Yet another objective of the present disclosure is to improve user experience by reducing service disruptions.

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

[0034] In an exemplary embodiment a system for determining a plurality of policies for a plurality of user equipments (UEs) is disclosed. The system includes a policy control function (PCF), the PCF includes a receiving unit configured to receive a policy creation request from at least one UE of the plurality of UEs. The system includes an extraction unit configured to extract information from the received policycreation request, where the information includes international mobile equipment identity (IMEI) corresponding to the at least one UE. The system includes a detection unit configured to detect whether the extracted IMEI is present in a list stored in a database, where the list includes a plurality of IMEI-Type Allocation Codes (TACs). The system includes a processing unit configured to install at least one of the plurality of policies for the at least one UE based on detecting that the extracted IMEI is present in the list stored in the database.

[0035] In an embodiment, responsive to the detection that the extracted IMEI is not present in the list stored in the database, the processing unit is configured to reject the policy creation request from the at least one UE.

[0036] In an embodiment, the plurality of policies includes a plurality of UE route selection policy (URSP) rules.

[0037] In an embodiment, upon detecting that the extracted IMEI is not present in the list stored in the database, a sending unit is configured to send an error message to the at least one UE, where the error message indicates a rejection reason of the policy creation request.

[0038] In an embodiment, the list includes URSP- supported UEs based on the IMEI.

[0039] In an exemplary embodiment, a method for determining a plurality of policies for a plurality of user equipments (UEs) by a policy control function (PCF) is disclosed. The method includes receiving a policy creation request from at least one UE of the plurality of UEs. The method includes extracting information from the received policy creation request, where the information includes international mobile equipment identity (IMEI) corresponding to the at least one UE. The method includes detecting whether the extracted IMEI is present in a list stored in a database, where the list includes a plurality of IMEI-Type Allocation Codes (TACs). The method includesinstalling at least one of a plurality of policies for the at least one UE based on detecting that the extracted IMEI is present in the list stored in the database.

[0040] In an embodiment, the method includes responsive to the detection that the extracted IMEI is not present in the list stored in the database, rejecting the policy creation request from the at least one UE.

[0041] In an embodiment, the plurality of policies including a plurality of UE route selection policy (URSP) rules.

[0042] In an embodiment, upon detecting that the extracted IMEI is not present in the list stored in the database, the method includes sending, by the PCF, an error message to the at least one UE, where the error message indicates a rejection reason of the policy creation request.

[0043] In an embodiment, the list includes URSP- supported UEs based on the IMEI.

[0044] In an exemplary embodiment, a user equipment communicatively coupled with a network is disclosed. The coupling includes receiving, by the network, a connection request. The coupling includes sending, by the network, an acknowledgment of the connection request to the network device. The coupling includes transmitting, by the UE, a policy creation request to a policy control function (PCF) in the network, where upon receiving the policy creation request, determining a plurality of policies for the UE by the PCF using a method for determining a plurality of policies for a plurality of user equipments (UEs) by a policy control function (PCF).

[0045] In an exemplary embodiment, a computer program product includes a non-transitory computer-readable medium including instructions that, when executed by one or more processors, cause the one or more processors to execute a method for determining a plurality of policies for a plurality of user equipments (UEs) by a policycontrol function (PCF) is disclosed. The method includes receiving a policy creation request from at least one UE of the plurality of UEs. The method includes extracting information from the received policy creation request, where the information includes international mobile equipment identity (IMEI) corresponding to the at least one UE. The method includes detecting whether the extracted IMEI is present in a list stored in a database, where the list includes a plurality of IMEI-Type Allocation Codes (TACs). The method includes installing at least one of a plurality of policies for the at least one UE based on detecting that the extracted IMEI is present in the list stored in the database.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

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

[0047] FIG. 1 illustrates an exemplary network architecture for implementing a system for policy determination using International Mobile Equipment Identity-Type Allocation Code (IMEI-TAC), in accordance with an embodiment of the present disclosure.

[0048] FIG. 2A illustrates an exemplary system architecture of the system for policy determination using the IMEI-TAC, in accordance with an embodiment of the present disclosure.

[0049] FIG. 2B illustrates an exemplary block diagram of the system for policy determination using the IMEI-TAC, in accordance with an embodiment of the present disclosure.

[0050] FIG. 3 illustrates an exemplary flow diagram for policy determination using the IMEI-TAC, in accordance with an embodiment of the present disclosure.

[0051] FIG. 4 illustrates an exemplary flow diagram of a method for policy determination using the IMEI-TAC, in accordance with an embodiment of the present disclosure.

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

[0053] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network architecture102-1, 102-2... 102-N - Plurality of Users104-1, 104-2... 104-N - Plurality of User Equipments106 - Network108 - System110 - Policy Control Function (PCF)200A - System Architecture200B - Block Diagram202 - Processor(s)204 - Memory 206 - Plurality of Interfaces208 - Receiving Unit210 - Extraction Unit212 - Processing Unit214 - Detection Unit 216 - Database300 - Flow Diagram400 - Method Flow500 - Flow diagram500 - Computer System 510 - External Storage Device520 - Bus530 - Main Memory540 - Read Only Memory550 - Mass Storage Device560 - Communication Port570 - ProcessorDETAILED DESCRIPTION

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

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

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

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

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

[0059] 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 inat 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.

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

[0061] As used herein, an “electronic device”, or “portable electronic device”, or “user device” or “communication device” or “user equipment” or “device” refers to any electrical, electronic, electromechanical and computing device. The user device is capable of receiving and / or transmitting one or more parameters, performing function / s, communicating with other user devices and transmitting data to the otheruser devices. The user equipment may have a processor, a display, a memory, a battery and an input-means such as a hard keypad and / or a soft keypad. The user equipment may be capable of operating on any radio access technology including but not limited to IP-enabled communication, Zig Bee, Bluetooth, Bluetooth Low Energy, Near Field Communication, Z-Wave, Wi-Fi, Wi-Fi direct, etc. For instance, the user equipment may include, but not limited to, a mobile phone, smartphone, virtual reality (VR) devices, augmented reality (AR) devices, laptop, a general-purpose computer, desktop, personal digital assistant, tablet computer, mainframe computer, or any other device as may be obvious to a person skilled in the art for implementation of the features of the present disclosure.

[0062] Further, the user device may also comprise a “processor” or “processing unit” includes processing unit, wherein processor refers to any logic circuitry for processing instructions. The 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 is a hardware processor.

[0063] As portable electronic devices and wireless technologies continue to improve and grow in popularity, the advancing wireless technologies for data transfer are also expected to evolve and replace the older generations of technologies. In the field of wireless data communications, the dynamic advancement of various generations of cellular technology are also seen. The development, in this respect, has been incremental in the order of second generation (2G), third generation (3G), fourthgeneration (4G), and now fifth generation (5G), and more such generations are expected to continue in the forthcoming time.

[0064] Radio Access Technology (RAT) refers to the technology used by mobile devices / User Equipment (UE) to connect to a cellular network. It refers to the specific protocol and standards that govern the way devices communicate with base stations, which are responsible for providing the wireless connection. Further, each RAT has its own set of protocols and standards for communication, which define the frequency bands, modulation techniques, and other parameters used for transmitting and receiving data. Examples of RATs include a GSM (Global System for Mobile Communications), a Code Division Multiple Access (CDMA), a Universal Mobile Telecommunications System (UMTS), a Long-Term Evolution (LTE), a Fifth Generation (5G) technology, and a Sixth Generation (6G) technology. The choice of RAT depends on a variety of factors, including the network infrastructure, the available spectrum, and the mobile device's / device's capabilities. Mobile devices often support multiple RATs, allowing them to connect to different types of networks and provide optimal performance based on the available network resources.

[0065] 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 a Second Generation (2G) technology was introduced. A Third Generation (3G) technology marked the introduction of high-speed internet access, mobile video calling, and location-based services. A Fourth Generation (4G) technology revolutionized the wireless communication with faster data speeds, improved network coverage, and security. Currently, the 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 ofThings (loT) connectivity, and more efficient use of network resources. The 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 evolving, with the aim of revolutionizing the way of connecting and interacting with technology.

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

[0067] A “User Equipment (UE) Route Selection Policy (URSP)” is a policy that governs how UE selects routes within a network for communication. The URSP determines which packet data unit (PDU) session on a network slice a particular service or application should utilize upon activation. The URSP information is used to ensure efficient routing and resource allocation within the 5G network. It allows for the optimized delivery of services and applications based on their specific requirements and network conditions. If URSP policies are sent to devices that do not support them, it can lead to disruptions in basic services. This underscores the importance of accurately provisioning devices with the appropriate URSP information to ensure smooth operation within the network.

[0068] Currently, the UE does not indicate its capabilities during initial registration; therefore, URSP policies are determined based on the subscriber profile in a subscriber profile repository (SPR). If there are multiple slices, this suggests potential URSP support, prompting an access and mobility management (AMF) torequest URSP policies from a policy control function (PCF). The PCF sends the URSP policies to the AMF / UE based on an international mobile equipment identity (IMSI) and its custom field in the SPR. For instance, if the UE that has a URSP- supported SIM / IMSI receives URSP policies, everything works fine. However, if the SIM is transferred to a non-URSP-supported operating system, the UE may still trigger the sending of the URSP policies due to the network's SIM / IMSI-based checks, potentially causing issues on the non-URSP-supported device. Further, if the SIM is inserted into the UE, the network sends the URSP policies regardless of the device type. This can potentially hinder basic internet or IMS services because the UE may not initiate basic PDU establishment. This issue arises because the current implementation relies on SIM / IMSI information rather than the type of device.

[0069] Therefore, there is a need for systems and methods to determine the URSP policies based on International Mobile Equipment Identity-Type Allocation Code (IMEI-TAC).

[0070] The present disclosure aims to overcome the above-mentioned and other existing problems in this field of technology by providing a system and a method for policy determination using the IMEI-TAC. The system may maintain a list of UEs supporting the URSP policies with corresponding IMEIs (or Permanent Equipment Identifier (PEIs). This enables efficient differentiation between the URSP- supported and the non-supported UEs. On receiving a policy creation request from the UE, the system may check whether IMEI corresponding to the UE is present in the list. On detecting the IMEI corresponding to the UE is present in the list, the PCF may apply the URSP rules to the UE. This ensures a more comprehensive assessment of device compatibility, reducing the risk of service disruptions caused by sending the URSP policies to non-URSP-supported devices.

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

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

[0073] FIG. 1 illustrates an example of a network architecture (100) for implementing a system (108) for policy determination using International Mobile Equipment Identity-Type Allocation Code (IMEI-TAC), in accordance with an embodiment of the present disclosure. As illustrated in FIG. 1 , the network architecture 100 may include one or more computing devices or User Equipments (UEs) (104-1, 104-2... 104-N) associated with one or more users (102-1, 102-2... 102-N) in an environment. A person of ordinary skill in the art will understand that one or more users (102-1, 102-2... 102-N) may be individually referred to as the user (102) and collectively referred to as the users (102). Similarly, a person of ordinary skill in the art will understand that one or more UEs (104-1, 104-2... 104-N) may be individually referred to as the UE (104) and collectively referred to as the UEs (104). A person of ordinary skill in the art will appreciate that the terms “computing device(s)” and “user equipment” may be used interchangeably throughout the disclosure. Although three UEs (104) are depicted in FIG. 1, however, any number of the UEs (104) may be included without departing from the scope of the ongoing description.

[0074] In an embodiment, the UE (104) may include smart devices operating in a smart environment, for example, an Internet of Things (loT) system. In such an embodiment, the UE (104) may include, but is not limited to, smartphones, smart watches, smart sensors (e.g., a mechanical sensor, a thermal sensor, an electrical sensor, a magnetic sensor, etc.), networked appliances, networked peripheral devices, networked lighting system, communication devices, networked vehicle accessories, networked vehicular devices, smart accessories, tablets, smart televisions (TVs), computers, smart security systems, smart home systems, other devices for monitoring or interacting with or for the user (102) and / or entities, or any combination thereof. A person of ordinary skill in the art will appreciate that the UE (104) may include, but isnot limited to, intelligent, multi-sensing, network-connected devices, that can integrate seamlessly with each other and / or with a central server or a cloud-computing system or any other device that is network-connected.

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

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

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

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

[0079] In an embodiment, the network architecture (100) further includes a system (108). The system (108) comprises the PCF (110).

[0080] In an aspect, the PCF (110) may receive a UE-policy creation request from the UE (104). Upon receiving the UE-policy creation request, the PCF (110) may initiate a process to determine the appropriate policy. In an aspect, the PCF (110) may maintain a list of international mobile equipment identity (IMEI) and a type allocation code (TAC) corresponding to the plurality of UEs (104). In an aspect, the list may comprise a list of UE route selection policy (URSP)-supported UEs at the PCF (110). This enables efficient differentiation between the URSP-supported and the nonsupported devices. The PCF (110) may check whether the IMEI received in the UE- Policy creation request matches any IMEI TAC in the list maintained by the PCF (110). The IMEI TAC represents the initial eight digits of the IMEI and signifies the device's manufacturer and model. On detecting a match between the received IMEI and the IMEI TAC in the list, the PCF (110) may proceed to install the appropriate URSP rules for the UE (104). Further, if the IMEI received in the UE-Policy creation request does not match any IMEI TAC defined in the list, the PCF (110) may reject the request. The PCF (110) may reject the UE-Policy creation request to prevent applying URSP rules to the UEs (104) that do not support the URSP rules, thus avoiding potential service disruptions and ensuring policy consistency.

[0081] In an aspect, the PCF (110) may respond with an error code indicating the rejection reason (e.g., result code 400 with error cause "ERROR REQUEST PARAMETERS") in case of rejection due to non-matching IMEI TAC.

[0082] In an exemplary embodiment, the UE (104) communicatively coupled with the network (106) is disclosed. The coupling includes receiving, by the network (106), a connection request. The coupling includes sending, by the network (106), an acknowledgment of the connection request to the network (106). The coupling includestransmitting, by the UE (104), a policy creation request to the PCF (110) in the network (106), where upon receiving the policy creation request, determining a plurality of policies for the UE (104) by the PCF (110) using the method for determining a plurality of policies for a plurality of the UEs (104) by the PCF (110). The system is configured to determine a plurality of policies for the UEs (104), the system comprising the PCF (110), as explained in detail in FIG. 2B.

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

[0084] FIG. 2A illustrates an example of a system architecture (200A) for policy determination using the IMEI-TAC, in accordance with an embodiment of the present disclosure.

[0085] The system architecture (200 A) comprises the UE (104) and the PCF (110). The PCF (110) may maintain a list of URSP-supported UEs based on IMEI. On receiving the UE-Policy creation request, the PCF (110) may check whether the IMEI received in the UE-Policy creation request matches any IMEI TAC in the list maintained by the PCF (110). The IMEI TAC represents the initial eight digits of the IMEI and signifies the device's manufacturer and model. On detecting a match between the received IMEI and the IMEI TAC in the list, the PCF (110) may proceed to install the appropriate URSP rules for the UE (104). Further, if the IMEI received in the UE- Policy creation request does not match any IMEI TAC defined in the list, the PCF (110) may reject the request. The PCF (110) may send an error code 400 with error cause "ERROR REQUEST PARAMETERS”.

[0086] In an aspect, the system (108) may use runtime configurable parameters and command line interface (CLI) commands for managing Permanent Equipment Identifier (PEI)- Type Allocation Code (TACs). This enables precise validation and handling of devices. Furthermore, as the PCF (110) maintains the list of URSP- supported UEs at the PCF (110) based on the IMEI or PEI, this enables efficient differentiation between the URSP-supported and the non-supported UEs. This helps in seamless policy application, minimizing signaling rejections even during any changes of UEs.

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

[0088] FIG. 2B illustrates an exemplary block diagram (200B) of the system (108) configured for determining a plurality of policies for a plurality of the UEs (104), the system (108) includes the PCF (110) using IMEI-TAC, in accordance with an embodiment of the disclosure. FIG. 2B is explained in conjunction with FIG. 1. In an embodiment, the network (106) may be, for example, the 4G network, the 5 G network, the 6G network, and the like.

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

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

[0091] In an embodiment, the system (108) may include the PCF (110) and a database (216). The PCF (110) may include a receiving unit (208), an extraction unit (210), a processing unit (212), and a detection unit (214).

[0092] The receiving unit (208) may receive a policy creation request from at least one UE (104) of the plurality of UEs (104). The extraction unit (210) may extract information from the received policy creation request. The information comprises international mobile equipment identity (IMEI) and a type allocation code (TAC) corresponding to the at least one UE (104). The detection unit (214) may detect whether the extracted IMEI-TAC is present in a list maintained in the database (216). In an aspect, the list may comprise a list of UE route selection policy (URSP)-supported UEs at the PCF (110). This enables efficient differentiation between the URSP-supported and the non-supported devices.

[0093] In response to detecting that the extracted IMEI-TAC is present in the list maintained in the database (216), it may be determined that the at least one UE (104) from which the request is received supports the URSP rules. The processing unit (212) may install at least one of a plurality of policies for the at least one UE (104). The plurality of policies comprises a plurality of UE route selection policy (URSP) rules. Furthermore, in response to the detection the extracted IMEI-TAC is not present in the list maintained in the database (216), the processing unit (212) may reject the policy creation request from at least one UE (104).

[0094] In an aspect, the database (216) is configured to store program instructions. The database (216) is configured to store the data received from the receiving unit (208), extraction unit (210), the processing unit (212) and the detection unit (214). The program instructions include a program that implements the system (108) for determining a plurality of policies for plurality of UEs (104) in accordance with embodiments of the present disclosure and may implement other embodiments described in this specification. The database (216) may be configured to store the list of IMEI-TAC corresponding to the plurality of UEs (104). The database (216) may include any computer-readable medium known in the art including, for example, volatile memory, such as Static Random Access Memory (SRAM) and Dynamic Random Access Memory (DRAM), and / or nonvolatile memory, such as Read Only Memory (ROM), erasable programmable ROM, flash memories, hard disks, optical disks, and magnetic tapes. In an aspect, the database (216) may be implemented inside the PCF (l lO).

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

[0096] FIG. 3 illustrates an example of a flow diagram (300) for policy determination using IMEI-TAC, in accordance with an embodiment of the present disclosure.

[0097] At step 302, the PCF (110) may receive a UE-policy creation request from the UE (104). Upon receiving the UE-policy creation request, the PCF (110) may initiate a process to determine the appropriate policy. The PCF (110) may extract relevant information from the received policy creation request. The relevant information comprises international mobile equipment identity (IMEI) and a type allocation code (TAC) corresponding to the UE (104).

[0098] At step 304, the PCF (110) may check whether the extracted IMEI and TAC of the UE policy creation request is present in a list maintained in the database (216). The list consists of IMEI corresponding to the plurality of UEs (104) (i.e., URSP supported UEs). The TAC represents the initial eight digits of the IMEI and signifies the device's manufacturer and model.

[0099] In an aspect, the type allocation code (TAC) refers to a component of the International Mobile Equipment Identity (IMEI) number used in the UEs (104) (e.g., mobile devices). The IMEI is a unique identifier assigned to the UEs (104) (e.g., mobile phones and other cellular devices). The IMEI consists of 15 digits. The TAC is the first part of the IMEI number and is used to identify the device model and manufacturer. It usually comprises the first 8 digits of the IMEI.

[0100] In an aspect, the IMEI consists of Type Allocation Code (TAC), serial number (SN) and Check Digit (CD). The TAC consists of the first 8 digits of the IMEI. The TAC identifies the device model and manufacturer. The SN consists of the next 6 digits of the IMEI. The SN is unique to each device within the TAC. The CD representsthe last digit. The CD is used for validation purposes. For example, an IMEI number = 490154203237518, 49015420 is the TAC, 323751 is the SN, and 8 is the CD.

[0101] At step 306, on detecting there is a match found between the received IMEI and TAC in the list of IMEI TAC, the PCF (110) may proceed to install the appropriate URSP rules for the UE (104).

[0102] At step 308, on detecting there is no match found between the received IMEI and TAC in the list of IMEI TAC, the PCF (110) may reject the UE-policy creation request. The PCF (110) may reject the UE-policy creation request to prevent applying the URSP rules to the UEs that do not support the URSP rules, thus avoiding potential service disruptions and ensuring policy consistency. In an aspect, in case of rejecting the UE-policy creation request due to non-matching IMEI TAC, the PCF (110) may respond with a “400 error code”. The “400 error code” indicates the rejection reason (e.g., result code 400 with error cause "ERROR REQUEST PARAMETERS").

[0103] In an aspect, a permanent equipment identifier (PEI) may be an IMEI. The PEI is unique code or identifier by which the network identifies the UEs (104) (for example, mobile devices) that are capable of accessing a 3 GPP network.

[0104] FIG. 4 illustrates an exemplary flow diagram of a method 400 for managing the one or more notifications in the network (i.e., the network 106), in accordance with an embodiment of the present disclosure. FIG. 4 is explained in conjunction with FIG. 1, FIG. 2A and FIG.2B and FIG. 3. Each step of the method 400 may be performed by various units (e.g., a receiving unit (208), an extraction unit (210), a processing unit (212), and a detection unit (214)) present within the PCF (110) of the system 108.

[0105] At step (402), the method (400) includes receiving the policy creation request from at least one the UE (104) of the plurality of the UEs (104). The UE (104)refers to devices such as smartphones, tablets, or other connected devices within a communication network. The method (400) implies at least one of these multiple devices (plurality of UEs) sends a request to the central system or network for the creation of the policy.

[0106] At step (404), the method (400) includes extracting the information from the received policy creation request involves identifying the specific data elements, such as the IMEI, which correlates to at least one UE (104). The IMEI is a unique identifier for mobile devices, critical for associating policies with devices in the mobile networks.

[0107] At step (406), the method (400) includes identifying whether the extracted IMEI number matches any entry within the database list. The list consists of multiple IMEI - TACs. The TAC is a critical part of the IMEI structure, representing the first eight digits that identify the device model and manufacturer. The task requires querying the database to determine if the TAC from the extracted IMEI exists in the stored list. The detection step is essential for verifying whether the IMEI is associated with known, registered device types as documented in the database.

[0108] In an embodiment, the method (400) includes, if the extracted IMEI does not match any IMEI- TACs stored in the database, the request for policy creation from the UE (104) is denied. This ensures that devices not verified or recognized according to the database records are not allowed to proceed with policy creation.

[0109] In an embodiment, the method (400) includes, if the extracted IMEI is not found in the database list, the PCF sends an error message to the UE (104). The message communicates the reason for rejecting the policy creation request, may provide feedback to the device about the unsuccessful attempt due to the IMEI absence from the recognized list of TACs.

[0110] In an embodiment, the method (400) includes, the list stored in the database includes UEs (104) that support the URSP based on their IMEI. This implies that the database not only verifies whether the IMEI is present but also checks if the device supports the URSP functionality.

[0111] At step (408), the method (400) includes installing at least one policy from the set of available policies for the UE (104), contingent upon confirming that the extracted IMEI is present in the database list. The step (408) is executed after verifying that the IMEI's TAC is included in the stored list, indicating that the device is recognized and authorized for the policy assignment.

[0112] In an embodiment, the method (400) includes, the plurality of policies includes multiple URSP rules. This implies that once a device is verified by the IMEI in the database, the set of the URSP rules, which govern how the device selects the network routes, can be installed on the UE (104).

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

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

[0115] The main memory (530) may be Random- Access Memory (RAM), or any other dynamic storage device commonly known in the art. The read-only memory (540) may be any static storage device(s) e.g., but not limited to, a Programmable Read Only Memory (PROM) chips for storing static information e.g., start-up or Basic Input / Output System (BIOS) instructions for the processor (570). The mass storage device (550) may be any current or future mass storage solution, which can be used to store information and / or instructions. The mass storage device (550) includes, but is not limited to, Parallel Advanced Technology Attachment (PAT A) or Serial Advanced Technology Attachment (SATA) hard disk drives or solid-state drives (internal or external, e.g., having Universal Serial Bus (USB) and / or Firewire interfaces), one or more optical discs, a Redundant Array of Independent Disks (RAID) storage, e.g. an array of disks.

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

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

[0118] In an exemplary embodiment, the UE (104) communicatively coupled with the network (106). The coupling includes receiving, by the network (106), a connection request and sending, by the network (106), an acknowledgment of the connection request to the network device. The coupling includes transmitting, by the UE (104), the policy creation request to the PCF (110) in the network (106), where upon receiving the policy creation request, determining a plurality of policies for the UE (104) by the PCF (110) using the method (400) for determining a plurality of policies for the plurality of the UEs (104) by the PCF (110).

[0119] In another exemplary embodiment, the present disclosure discloses a computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to perform the method for determining a plurality of policies for a plurality of user equipments (UEs) by a policy control function (PCF) is disclosed. The method includes, receiving a policy creation request from at least one UE of the plurality of UEs. The method includes extracting information from the received policy creation request, where the information includes international mobile equipment identity (IMEI) corresponding to the at least one UE. The method includes detecting whether the extracted IMEI is present in a list stored in a database, where the list includes a plurality of IMEI-Type Allocation Codes (TACs). The method includes installing at least one of a plurality of policies for the at least one UE based on detecting that the extracted IMEI is present in the list stored in the database.

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

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

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

[0123] The present disclosure offers significant for determining a plurality of policies for a plurality of the UEs (104), using the PCF (110). These advancements overcome the limitations of existing solutions by addressing key challenges in managing and applying policies for multiple UEs (104) within the network (106). The present disclosure overcomes issues related to the inefficient assignment of the URSP rules by utilizing the PCF (110) to automate the verification of the IMEI against the database of the TACs. The present disclosure determines whether the specific UEs(104) is supported for particular policies, such the URSP rules. If the IMEI is identified in the database, the system (108) installs the required policies for the UEs (104), if not, it rejects the request and sends an error message elucidating the rejection. The system (108) not only refines the process of policy assignment but also ensures that only eligible devices receive appropriate policy support, thereby optimizing network resource allocation and management. Furthermore, the integration of these operations into a non-transitory computer-readable medium underscores the adaptability and modernity of the approach, allowing for seamless implementation across diverse network infrastructures.ADVANTAGES OF THE PRESENT DISCLOSURE

[0124] The present disclosure provides a method and a system for managing one or more notifications in a network.

[0125] The present disclosure enhances compatibility of the devices by considering international mobile equipment identity-type allocation code (IMEI-TAC). A UE (104) route selection policy (URSP) policies / rules are only sent to compatible devices by differentiating between the URSP-supported and the non-URSP supported devices based on the IMEI-TAC.

[0126] The present disclosure prevents potential service disruptions that may occur when the URSP policies are sent to the devices incapable of supporting them, thereby improving overall service reliability.

[0127] The present disclosure improves resource utilization by sending theURSP policies only to the devices capable of supporting.

[0128] The present disclosure enhances network efficiency. This ensures that network resources are allocated effectively, boosting overall performance and stability.

[0129] The present disclosure reduces unnecessary signaling overhead associated with delivering policies to incompatible devices

[0130] The present disclosure improves UE (104) by ensuring that policies are delivered only to compatible devices, fewer service disruptions and enjoy more seamless connectivity. This enhances overall user satisfaction and loyalty, contributing to better customer retention and a stronger brand reputation in the highly competitive telecommunications market.

Claims

We claim:

1. A system (108) for determining a plurality of policies for a plurality of user equipments (UEs) (104), the system (108) comprising a policy control function (PCF), the PCF comprising: a receiving unit (208) configured to receive a policy creation request from at least one UE (104) of the plurality of UEs (104); an extraction unit (210) configured to extract information from the received policy creation request, wherein the information comprises international mobile equipment identity (IMEI) corresponding to the at least one UE (104); a detection unit (214) configured to detect whether the extracted IMEI is present in a list stored in a database, wherein the list comprises a plurality of IMEI-Type Allocation Codes (TACs); and a processing unit (212) configured to install at least one of the plurality of policies for the at least one UE (104) based on detecting that the extracted IMEI is present in the list stored in the database.

2. The system (108) as claimed in claim 1, wherein responsive to the detection that the extracted IMEI is not present in the list stored in the database, the processing unit is configured to reject the policy creation request from the at least one UE (104).

3. The system (108) as claimed in claim 1, wherein the plurality of policies comprises a plurality of UE (104) route selection policy (URSP) rules.

4. The system (108) as claimed in claim 1, wherein upon detecting that the extracted IMEI is not present in the list stored in the database, a sending unit is configured to send an error message to the at least one UE (104), wherein the error message indicates a rejection reason of the policy creation request.

5. The system (108) as claimed in claim 1, wherein the list includes URSP- supported UEs (104) based on the IMEI.

6. A method (400) for determining a plurality of policies for a plurality of user equipments (UEs) (104) by a policy control function (PCF), the method (400) comprising: receiving a policy creation request from at least one UE (104) of the plurality of UEs (104); extracting information from the received policy creation request, wherein the information comprises international mobile equipment identity (IMEI) corresponding to the at least one UE (104); detecting whether the extracted IMEI is present in a list stored in a database, wherein the list comprises a plurality of IMEI-Type Allocation Codes (TACs); and installing at least one of a plurality of policies for the at least one UE (104) based on detecting that the extracted IMEI is present in the list stored in the database.

7. The method (400) as claimed in claim 6, further comprising: responsive to the detection that the extracted IMEI is not present in the list stored in the database, rejecting the policy creation request from the at least one UE (104).

8. The method (400) as claimed in claim 6, wherein the plurality of policies comprises a plurality of UE (104) route selection policy (URSP) rules.

9. The method (400) as claimed in claim 6 further comprising: upon detecting that the extracted IMEI is not present in the list stored in the database, sending, by the PCF, an error message to the at least one UE (104), wherein the error message indicates a rejection reason of the policy creation request.

10. The method (400) as claimed in claim 6, wherein the list includes URSP- supported UEs (104) based on the IMEI.

11. A user equipment (104) communicatively coupled with a network, the coupling comprising: receiving, by the network (106), a connection request; sending, by the network (106), an acknowledgment of the connection request to the network device; and transmitting, by the UE (104), a policy creation request to a policy control function (PCF) in the network (106), wherein upon receiving the policy creation request, determining a plurality of policies for the UE (104) by the PCF using a method (400) as claimed in claim 6.

12. A computer program product comprising a non-transitory computer-readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method (400) for determining a plurality of policies for a plurality of user equipments (UEs) (104) by a policy control function (PCF), the method comprising: receiving a policy creation request from at least one UE (104) of the plurality of UEs (104); extracting information from the received policy creation request, wherein the information comprises international mobile equipment identity (IMEI) corresponding to the at least one UE (104);detecting whether the extracted IMEI is present in a list stored in a database, wherein the list comprises a plurality of IMEI-Type Allocation Codes (TACs); and installing at least one of a plurality of policies for the at least one UE (104) based on detecting that the extracted IMEI is present in the list stored in the database.

Images