System and method for initiating of a user equipment (UE) policy association in a network

Abstract

The present disclosure relates to a system (108) and a method (500) for initiating a user equipment (UE) policy association in a network (106). The method (500) includes receiving (502) a request from a user equipment (UE) (104) by an access and mobility management function (AMF) (214), deriving (504) a type allocation code (TAC) from an international mobile equipment identity (IMEI) associated with the UE (104) by the AMF (214), determining (506) based on the derived TAC whether the UE (104) supports a UE policy by mapping the derived TAC with UE policies, and initiating (508) the UE policy association by the AMF (214) if the UE (104) is determined to support the UE policy.

Description

SYSTEM AND METHOD FOR INITIATING A USER EQUIPMENT (UE) POLICY ASSOCIATION IN A NETWORKRESERVATION OF RIGHTS

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

[0002] The present disclosure relates to mobile communication systems. In particular, the present disclosure relates to a method and a system for managing policy association procedures for user equipment in a network.DEFINITIONS

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

[0004] The expression “User Equipment (UE)” used hereinafter in the specification refers to any mobile or wireless communication device capable of connecting to a network, including but not limited to smartphones, tablets, laptops, loT devices, or any other terminal equipment that communicates with the network to access services.

[0005] The expression “Next Generation Node B (gNodeB)” used hereinafter in the specification refers to a next-generation Node B, which is a base station in a 5G network responsible for connecting User Equipment (UE) to the 5G core network. The gNodeB handles radio communications with the UE, including the transmission and reception of data over the air interface, and forwards therequests received from the UE to the Access and Mobility Management Function (AMF) via the N2 interface.

[0006] The expression “International Mobile Equipment Identity (IMEI)” used hereinafter in the specification refers to a unique digit identifier assigned to the UE. The IMEI is used to identify the UE on the network.

[0007] The expression “International Mobile Equipment Identity and Software Version (IMEISV)” used hereinafter in the specification refers to a 16- digit identifier that extends the IMEI by including a 2-digit software version number. The IMEISV provides both the hardware identity and the software version of the User Equipment (UE), enabling the network to distinguish between different firmware versions of the same device model for purposes such as policy enforcement, security, or compatibility assessment.

[0008] The expression “Type Allocation Code (TAC)” used hereinafter in the specification refers to the first 8 digits of the IMEI or IMEISV (International Mobile Equipment Identity and Software Version), which uniquely identifies the make and model of the UE. The TAC is essential for determining the capabilities of the UE, including support for specific network policies.

[0009] The expression “Access and Mobility Management Function (AMF)” used hereinafter in the specification refers to a key component of the 5G core network that manages the registration, connection, and mobility of User Equipment (UE). The AMF is responsible for tasks such as authenticating UEs, managing sessions, and initiating UE policy associations based on capabilities of the UE.

[0010] The expression “UE Policy” used hereinafter in the specification refers to network rules or configurations that dictate how the UE interacts with the network. These policies may include prioritization of certain services, allocation of network resources, or specific handling of network traffic based on the capabilities of the UE.

[0011] The expression “UE Policy Association” used hereinafter in the specification refers to a process of establishing a connection between the UE and the network where specific UE policies are applied. The policy association is configured to control the UE to adhere to defined network rules, or receive services based on the defined policies.

[0012] The expression “Network Slices” used hereinafter in the specification refers to logically separate network partitions that operate on the same physical network infrastructure. Each slice is tailored to meet specific requirements for different types of network traffic, such as enhanced mobile broadband, ultrareliable low-latency communication, or massive loT, thereby enabling differentiated services.

[0013] The expression “Internal Database” used hereinafter in the specification refers to a database managed by the AMF that stores TAC mappings to their corresponding UE policies. The internal database allows the AMF to quickly determine whether the UE supports specific network policies based on its TAC.

[0014] The expression “External Device Database” used hereinafter in the specification refers to a database external to the AMF containing a comprehensive TAC mapping to their respective UE policy support information. The AMF may query the external database to obtain policy support information when it is unavailable in its internal database.

[0015] The expression “Registration Request” used hereinafter in the specification refers to a message sent by the UE to the network, specifically the AMF, to initiate or re-establish a connection with the network. The request triggers the AMF to perform various procedures, including deriving the TAC and determining UE policy support.

[0016] The expression “Signalling Overhead” used hereinafter in the specification refers to the additional communication load on the network caused bythe transmission of control or signalling messages that are not directly related to user data traffic. Excessive signalling overhead can reduce network efficiency and performance, especially when unnecessary policies are applied to the UE that does not support them.

[0017] The expression “Policy Support Information” used hereinafter in the specification refers to data that indicates whether the UE supports certain network policies. “UE support” in this context refers to the capability of the User Equipment (UE) to recognize, interpret, and act upon policy rules provisioned by the network. This includes the ability of the UE to receive a UE policy container, apply traffic routing rules, prioritize services based on policy parameters, or interact with network slices in accordance with defined policy behavior. The AMF uses the information to determine whether to initiate a UE policy association during the registration process.

[0018] The expression “UE Policy Container” used hereinafter in the specification refers to an information element optionally included by the UE in registration or service requests to indicate support for receiving and applying network-provided policy rules. The UE Policy Container may include identifiers, flags, or capability indicators that enable the network — particularly the AMF and PCF — to determine whether and how to deliver UE policy. The presence of the UE Policy Container serves as an explicit trigger for the AMF to initiate a UE policy association, while its absence may lead the AMF to apply internal logic or fallback mechanisms to assess UE eligibility for policy enforcement. The UE Policy Container thus plays a significant role in enabling device-specific and context- aware policy treatment across differentiated network slices.

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

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

[0021] In recent years, there has been a significant advancement in wireless communication technologies, with the advent of 5G networks offering enhanced capabilities and flexibility. Network slicing enables creating and dynamic management of logically and functionally discrete end-to-end networks over a common physical infrastructure. The network slicing allows network operators to offer multiple 5G networks, each tailored to individual customer needs, without the need for dedicated physical hardware for each network. As a result, operators can deliver customized services more flexibly and cost-effectively, with each logical network being deployed, managed, and released as required on the same shared hardware.

[0022] For effectively utilizing the network slices, the concept of User Equipment (UE) policy has been introduced. The UE policy enables the network to deliver specific UE policy rules to the UE, informing it about the conditions and criteria for utilizing different network slices. For instance, the UE may use one slice for video streaming, another for voice calls, and yet another for remaining traffic, thereby providing specialized treatment for each type of traffic and enhancing the overall user experience.

[0023] However, the practical implementation of the UE policy faces significant challenges. According to current standards, the Access and Mobility Management Function (AMF) in the 5G core network establishes a UE policy association with the Policy Control Function (PCF). Such process of establishing the UE policy may be initiated based on an indication from the UE, known as the UE policy container, sent during registration or when transitioning from a 4G to a 5G network.

[0024] The issue arises because many UEs in the current ecosystem do notsupport the UE policy. Moreover, even among the UEs that do support it, many do not indicate the support by including the UE policy container when requesting network services. The lack of visibility can lead to situations where the AMF does not initiate UE policy for the UEs that support it, resulting in a suboptimal user experience. Conversely, initiating the UE policy for all users, regardless of their capabilities, could lead to unnecessary signalling overhead, particularly for the UEs that do not support the UE policy.

[0025] There is, therefore, a need in the art to provide a method and a system that can overcome the shortcomings of the existing solutions.OBJECTIVES OF THE DISCEOSURE

[0026] Some of the objects of the present disclosure, which at least one embodiment herein satisfies, are as listed herein below:

[0027] An object of the present disclosure is to provide a system and a method for optimizing network signalling in 5G networks by initiating UE policy based on a Type Allocation Code (TAC) of a user equipment (UE), ensuring that UE policy is only established for the UE that supports the feature.

[0028] Another object of the present disclosure is to provide the system and the method for enhancing the user experience in the 5G networks by ensuring that only the UE capable of supporting UE policy receives tailored network treatments through the appropriate initiation of UE policy based on the TAC of the UE.

[0029] Another object of the present disclosure is to provide the system and the method that prevents the unnecessary initiation of UE policy for the UE that do not support the UE policy feature, thus maintaining network efficiency.

[0030] Another object of the present disclosure is to provide the system and the method for reducing signalling overhead within the network.SUMMARY

[0031] The present disclosure relates to systems and methods for initiating a user equipment (UE) policy association in a communication network, particularly in a Fifth Generation (5G) or next-generation mobile network. The disclosure enables intelligent determination and initiation of UE policy association based on device capability, even when explicit support is not signaled by the UE.

[0032] In an embodiment, a method is disclosed wherein an Access and Mobility Management Function (AMF) receives a request from a UE, such as during registration or handover. The request includes an identifier associated with the UE, for example, an International Mobile Equipment Identity (IMEI) or an International Mobile Equipment Identity and Software Version (IMEISV). The AMF extracts a Type Allocation Code (TAC) from the identifier and performs a check to determine whether the UE supports at least one UE policy feature. The support determination is achieved by mapping the extracted TAC to a list of preconfigured TAC entries stored in a local AMF database . If the mapping confirms that the UE supports UE policy, such as routing rule containers, application-level traffic descriptors, or slice routing via Universal Slice Routing Policy (URSP), the AMF proceeds with the UE registration and initiates a UE policy association with a Policy Control Function (PCF).

[0033] In one embodiment, if the extracted TAC is not found in the list of configured TACs stored in the AMF’s internal database, the AMF proceeds with the registration of the UE without initiating the UE policy association. The registration ensures that devices whose capability support is unknown or not preconfigured do not undergo unnecessary policy signaling procedures, thereby optimizing control plane operations.

[0034] In another embodiment, if the extracted TAC is not available in the internal database, the AMF transmits the TAC to an external database configured to maintain an updated and comprehensive mapping of device TACs to their associated policy support attributes. The external query mechanism ensures that newly released or uncommon device models can still be evaluated for policy capability using an external reference source.

[0035] In an implementation, upon receiving a response from the external database indicating that the UE supports the UE policy, the AMF initiates the UE policy association with the PCF. If the response indicates that the UE does not support the policy, the AMF continues the registration process without initiating policy association. Such fallback logic enables the network to apply policy enforcement only where functionally meaningful while ensuring smooth registration for unsupported devices.

[0036] In a further embodiment, the request received by the AMF may correspond to either a registration request or a handover request. The disclosed mechanism applies to both connection scenarios, thereby ensuring consistent and intelligent UE policy control whether the device is connecting initially or moving across access boundaries.

[0037] In another embodiment, the identifier used by the AMF to derive the TAC comprises either the IMEI or IMEISV of the UE. The TAC is embedded in the first eight digits of these identifiers and is parsed by the AMF as part of the registration signaling flow.

[0038] In an implementation, a system is disclosed comprising an AMF configured to perform the above operations. The AMF is further configured to interact with internal and external databases and one or more PCF instances to enable device-aware UE policy enforcement. The system supports dynamic decision-making for policy association and is agnostic to the explicit signaling capability of the UE.

[0039] Additionally, in scenarios where the UE does not include a UE Policy Container in the request, the AMF may refer to its local configuration to determine whether policy association should be initiated. The expression “UE Policy Container” used hereinafter in the specification refers to a signaling parameter included in the registration or service request messages transmitted by the User Equipment (UE) to the network. The UE Policy Container indicates that the UE is capable of supporting network-defined policy rules and is willing toengage in UE policy association procedures. It may carry identifiers or capability indicators that assist the Access and Mobility Management Function (AMF) in determining whether to initiate a UE policy association with a Policy Control Function (PCF). Absence of the UE Policy Container typically implies that the UE does not explicitly signal policy support, prompting the AMF to rely on alternative mechanisms such as local configuration or TAC-based inference. The local configuration may include conditional logic based on device IMEI, TAC, or subscribed network slice profiles.

[0040] In another embodiment, a UE is disclosed that is communicatively coupled with the system. The coupling comprises the system receiving a connection request from the UE, sending an acknowledgment in response, and transmitting a plurality of signals necessary for connection establishment and policy negotiation. The system may initiate a policy association based on internal checks or local configurations, even when no policy capability is signaled by the UE.

[0041] In yet another embodiment, a computer program product is disclosed comprising anon-transitory computer-readable medium storing instructions. When executed by one or more processors, the instructions cause execution of the steps of receiving the UE request, extracting the TAC, checking support against a configured database, and initiating the policy association with the PCF based on the result of the check.

[0042] The proposed solution enables intelligent and efficient UE policy association that adapts to real-world limitations in UE signaling behavior. The invention minimizes signaling overhead, ensures proper service treatment, and maintains high levels of compatibility and scalability across a diverse UE ecosystem.BRIEF DESCRIPTION OF THE ACCOMPANYING DRAWING

[0043] The accompanying drawings, which are incorporated herein, and constitute a part of this disclosure, illustrate exemplary embodiments of thedisclosed 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 the disclosure of electrical components, electronic components or circuitry commonly used to implement such components.

[0044] FIG. 1 illustrates an exemplary architecture for implementing a system for initiating a user equipment (UE) policy association in a network, in accordance with embodiments of the present disclosure.

[0045] FIG. 2A illustrates an exemplary block diagram of the system for initiating the UE policy association in the network, in accordance with embodiments of the present disclosure.

[0046] FIG. 2B illustrates a system architecture for initiating the UE policy association in the network, in accordance with embodiments of the present disclosure.

[0047] FIG. 3 illustrates an exemplary flowchart of a process for initiating the UE policy association in the network in accordance with embodiments of the present disclosure.

[0048] FIG. 4 illustrates another exemplary flowchart of another process for initiating the UE policy association in the network in accordance with embodiments of the present disclosure

[0049] FIG. 5 illustrates an exemplary flowchart of a method for initiating the UE policy association in the network in accordance with embodiments of the present disclosure.

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

[0051] FIG. 7 illustrates another flowchart of a process for initiating a user equipment (UE) policy association in a network under conditions where the UE does not explicitly signal support for UE policies using a UE Policy Container in accordance with embodiments of the present disclosure.

[0052] The foregoing shall be more apparent from the following more detailed description of the disclosure.LIST OF REFERENCE NUMERALS100 - Network Architecture102-1, 102-2 - Users104-1, 104-2 - User equipment112-1, 112-2- Base stations106 - Network108 - System200A - Block diagram202 - Processors204 - Memory206 - Interface(s)208 - Processing engine209 - Other module(s)210 - Database200B - System architecture212 - gNodeB214 - Access and Mobility Management Function (AMF)216 - Policy Control Function (PCF)220 - External database300 - Flow diagram400 - Flow diagram500 - Method flow diagram600 - Computer system610 - External storage device620 - Bus630 - Main memory640 - Read only memory650 - Mass storage device660 - Communication port(s)670 - Processor700 - Flow diagramDETAILED DESCRIPTION

[0053] In the following description, for the purposes of explanation, various specific details are set forth in order to provide a thorough understanding of embodiments of the present disclosure. It will be apparent, however, thatembodiments 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 all 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.

[0054] The ensuing description provides exemplary embodiments only, and is not intended to limit the scope, applicability, or configuration of the disclosure. Rather, the ensuing description of the exemplary embodiments will provide those skilled in the art with an enabling description for implementing an exemplary embodiment. It 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.

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

[0056] Also, it is noted that individual embodiments may be described as a process 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 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 callingfunction or the main function.

[0057] The word “exemplary” and / or “demonstrative” is used herein to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter disclosed herein is not limited by such examples. In addition, any aspect or design described herein as “exemplary” and / or “demonstrative” is not necessarily to be constmed 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.

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

[0059] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly 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 and all combinations of one or more of the associated listed items.

[0060] In the current ecosystem, the majority of user equipments (UEs) do not support a user equipment (UE) policy. Moreover, the UEs that support the UE policy fail to indicate this capability by including the UE policy container when requesting network services. Without the capability indication, the Access and Mobility Management Function (AMF) lacks visibility into whether the UE supports the UE policy. The lack of visibility leads to scenarios where the UE policy is not initiated for the UE that does support it, depriving the user of the specialized network treatment intended for different services. Conversely, if the AMF initiates the UE policy for all users without verifying support, it may result in unnecessary signalling overhead for the UE that does not support the UE policy.

[0061] To address these discrepancies, the UE policy within the AMF must be initiated only for the UEs that support the feature. The proposed solution is for the AMF to establish the UE policy with the Policy Control Function (PCF) based on a Type Allocation Code (TAC) of the UE. The TAC is an 8 -digit number that forms the first part of the 15 -digit International Mobile Equipment Identity (IMEI) or 16-digit International Mobile Equipment Identity and Software Version (IMEISV). The TAC uniquely identifies each connected manufacture and model of the UE. Manufacturers use the TAC to create a unique identifier for the UE, and the IMEI is embedded into the UE during manufacture, ensuring it cannot be modified.

[0062] By leveraging the TAC, the AMF can determine whether the UE supports the UE policy, enabling the AMF to initiate the UE policy association only when appropriate, thereby optimizing network signalling and enhancing user experience.

[0063] The present disclosure relates to a system and a method for initiating at least one user equipment (UE) policy association in a network. Various embodiments throughout the disclosure will be explained in more detail with reference to FIGS. 1-6.

[0064] FIG. 1 illustrates an exemplary network architecture (100) forimplementing a system (108) for initiating a user equipment (UE) policy association in a network (106), in accordance with embodiments of the present disclosure. In an embodiment, the UE policy association defines and manages rules governing how user equipments (UEs) access and utilize network resources. These rules may include quality of service (QoS) configurations, application-specific routing, and service prioritization based on user profile or traffic type. The UE policy association further supports authentication and authorization mechanisms and enables dynamic policy enforcement based on real-time network state or device behavior. It also supports compatibility across different access networks during mobility or roaming and may integrate feedback mechanisms to optimize policy delivery and enforcement.

[0065] Referring to FIG. 1, the network architecture (100) includes one or more users (102-1, 102-2), one or more user equipments (104-1, 104-2), one or more base stations (112-1, 112-2), a network (106), and a system (108). Each user (102) is associated with at least one user equipment (104), which may include a wide range of network-enabled devices. In an embodiment, each user equipment (104) includes a unique device identifier, such as an International Mobile Equipment Identity (IMEI) or International Mobile Equipment Identity and Software Version (IMEISV), from which a Type Allocation Code (TAC) can be derived. The TAC comprises the first eight digits of the IMEI or IMEISV and uniquely identifies the make and model of the user equipment.

[0066] In an embodiment, the user equipment (104) may include smart devices operating in a smart environment, such as smartphones, tablets, smart sensors, connected appliances, networked automotive devices, augmented or virtual reality headsets, or other intelligent devices capable of wireless communication. The user equipment (104) may operate within an Internet of Things (loT) framework or within conventional mobile broadband environments. The network (106) may include a 5G or 6G access network, capable of supporting advanced slicing and policy delivery mechanisms as specified in 3GPP standards. The network (106) enables communication between the user equipment (104), the basestations (112), and the system (108).

[0067] In operation, when a user equipment (104) attempts to access the network (106), it initiates a request, such as a registration request or a handover request, which is received by an access and mobility management function (AMF) residing within the system (108). The request includes the identifier associated with the UE. The AMF extracts the TAC from the identifier and checks whether the corresponding device model supports at least one UE policy. Support for UE policy is defined by the device’s capability to receive, interpret, and enforce policy rules such as routing rule containers, traffic descriptors, and application identifiers according to the Universal Slice Routing Policy (URSP) or equivalent specifications under 3 GPP standards.

[0068] In an embodiment, a check is performed by mapping the extracted TAC with a list of configured TACs stored in a database associated with the AMF. Each TAC entry in the database includes metadata indicating whether the device model identified by the TAC supports at least one UE policy feature. For instance, a configured TAC entry may indicate that a particular device supports interpretation of traffic descriptor rules for application-based slice selection. If the TAC is found in the database and the support flag is set, the AMF proceeds with UE registration and initiates a UE policy association with a Policy Control Function (PCF). The PCF is responsible for generating and delivering the corresponding UE policy rules to the UE.

[0069] If the extracted TAC is not found in the list of configured TACs or if no support indication is present, the AMF may proceed with the registration of the UE without initiating the UE policy association. In another embodiment, if the TAC is not found locally, the AMF may transmit the extracted TAC to an external database to verify whether the corresponding device supports the UE policy. Upon receiving a response from the external database, the AMF acts conditionally based on the response: if the device is confirmed to support the policy, the AMF proceeds to initiate the UE policy association with the PCF; otherwise, the AMF completes the UE registration without initiating the policy association.

[0070] Referring to FIG. 1 again, the UE (104) communicates with the system (108) via the network (106). The system (108) is configured to leverage TAC information to ascertain the compatibility of the UE models with specific UE policy features. By extracting the TAC, the system (108) can accurately determine the capabilities of the UE utilized by the end user. Upon successful identification, the system initiates the UE policy association process within the core network architecture, thereby establishing a connection between the UE and a relevant policy framework. The process involves generating and delivering tailored UE policy rules to the UE based on its capabilities and the operational requirements of the network. Generating and delivering tailored UE policy rules to the UE based on its capabilities and the operational requirements allows the network to change policies automatically without requiring specific signals from the UE to indicate UE policy support. As a result, the network may better manage resources, maintain quality of service (QoS), and handle traffic more effectively, irrespective of the variation in device types or models.

[0071] The UE (104) is communicatively coupled with the network (106). The communicative coupling includes receiving a connection request from the UE (104) by the network (106), sending an acknowledgment to the UE (104), and exchanging signaling messages thereafter. The network (106) may support multiple communication paradigms including wide area networks (WANs), local area networks (LANs), mobile access networks, wireless links, and secure tunnels such as VPNs. The communication may occur over standardized protocols and interfaces compliant with 3GPP-defmed core network interfaces.

[0072] In an embodiment, the user equipment (104) may be communicatively coupled with the system (108) via the network (106). The communicative coupling enables the user equipment (104) to establish and maintain signaling exchanges with the system (108) during connection and service procedures. The communication flow may begin with the user equipment (104) initiating a connection request as part of a registration or handover event. Upon receiving the connection request, the system (108), via the access and mobilitymanagement function, responds by sending an acknowledgment message to the user equipment (104), confirming the receipt and processing of the connection request.

[0073] Following acknowledgment, the system (108) may transmit a plurality of signals to the user equipment (104) as part of the ongoing registration or mobility management procedures. These signals may include authentication vectors, security setup instructions, identity requests or confirmations, and configuration parameters required for completing the initial attach process. The signaling may also include session management directives, redirection notices, or any context information required for continued service delivery. For example, during registration, the system (108) may transmit a security mode command, a registration accept message, or a session creation instruction to facilitate the integration of the UE (104) into the network (106).

[0074] In an implementation, the system (108) is configured to initiate at least one UE policy association procedure in the network based on the received connection request and subsequent identification processing. The initiation is conditional on evaluating whether the UE (104), identified via its IMEI or IMEISV, supports policy-based network features such as application-level traffic routing, slice prioritization, or differentiated quality of service. By embedding the policy association logic within the broader signaling flow rather than treating it as a separate, delayed transaction, the system (108) ensures seamless integration of UE- specific policies during the network registration.

[0075] Although FIG. 1 illustrates a specific arrangement of components in the network architecture (100), in other embodiments, the architecture may include additional, fewer, or differently arranged components. Moreover, various functional components of the system (108) may be integrated or distributed, depending on deployment choices such as cloud-native NFV environments or centralized network cores.

[0076] FIG. 2A illustrates an exemplary block diagram (200A) of thesystem (108) for initiating the UE policy association in the network (106), in accordance with embodiments of the present disclosure. 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, edge or fog microcontrollers, digital signal processors, central processing units, logic circuitries, and / or any devices that process data based on operational instructions. Among other capabilities, the one or more processor(s) (202) may be configured to fetch and execute computer-readable instructions stored in a memory (204) of the system (108). The memory (204) may be configured to store one or more computer-readable instructions or routines in a non-transitory computer- readable storage medium, which may be fetched and executed to create or share data packets over a network service. The memory (204) may include any non- transitory storage device including, for example, volatile memory such as Random Access Memory (RAM), or non-volatile memory such as Erasable Programmable Read-Only Memory (EPROM), flash memory, and the like. In operation, the processor(s) (202) and memory (204) jointly enable the system (108) to perform functions such as receiving a request from a UE (104), extracting an identifier such as IMEI or IMEISV, and deriving a TAC from the same for policy-related decisionmaking.

[0077] Referring to FIG. 2A, the system (108) may include an interface(s) (206). The interface (206) may also be referred to as a web platform. The interface(s) (206) may include a variety of interfaces, for example, interfaces for data input and output devices, referred to as I / O devices, storage devices, and the like. The interface(s) (206) may facilitate communication to / from 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, processing engine(s) (208) and adatabase (210). The database (210) here may also be referred to as an internal database (210), which stores a list of configured TAC values mapped to UE policy support metadata. Each TAC entry in the database (210) is associated with a capability flag or indicator specifying whether the corresponding device model supports at least one UE policy. Forexample, the TAC “35012345” may map to a device model that supports URSP- based slice routing rules, while another TAC may indicate no support. The internal lookup mechanism enables fast, deterministic evaluation of UE capabilities without requiring explicit signaling from the UE itself.

[0078] In an embodiment, the processing engine(s) (208) may be implemented as a combination of hardware and programming (for example, programmable instructions) to implement one or more functionalities of the processing engine(s) (208). In the examples described herein, such combinations of hardware and programming may be implemented in several different ways. For example, the programming for the processing engine(s) (208) may be processorexecutable instructions stored on a non-transitory machine -readable storage medium and the hardware for the processing engine(s) (208) may include a processing resource (for example, one or more processors), to execute such instructions. In the present examples, the machine-readable storage medium may store instructions that, when executed by the processing resource, implement the processing engine(s) (208). In such examples, the system (108) may include the machine-readable storage medium storing the instructions and the processing resource to execute the instructions, or the machine-readable storage medium may be separate but accessible to the system (108) and the processing resource. In other examples, the processing engine(s) (208) may be implemented by electronic circuitry. The processing engine (208) implements the decision logic for verifying UE policy support based on the TAC. Upon positive confirmation of support, the processing engine (208) is configured to proceed with UE registration and initiate a policy association session with the PCF (216). If support is not detected, the processing engine (208) bypasses the policy association logic and allows the UE to proceed with basic registration.

[0079] In an embodiment, the processing engine (208) may further comprise other modules (209). The processing engine (208) may include multiple sub-components responsible for different functionalities related to managing the Access and Mobility Management Function (AMF). These may include a TACextraction module, a capability lookup module that queries the internal database (210), a fallback handler that interfaces with an external database (220), and a policy association controller that manages signaling with the PCF. Each of these modules contributes to an intelligent evaluation of whether the UE is capable of processing UE policy rules, such as, traffic descriptors and application identifiers, which are part of standard URSP containers. For example, if the derived TAC maps to a device known to support URSP, the policy association controller triggers the AMF-PCF interaction to retrieve slice assignment policies for different applications like streaming, voice, and background data.

[0080] In an embodiment, the processing engine (208) may be communicatively coupled to the AMF for implementing the system (108) and a method of the present disclosure. The coupling enables the AMF to operate in a device-aware manner, using the TAC to conditionally initiate or skip UE policy association, thereby conserving network signaling when a device is incapable of enforcing policy rules.

[0081] FIG. 2B illustrates a system architecture (200B) for initiating the UE policy association in the network (106), in accordance with embodiments of the present disclosure. In an embodiment, the system architecture (200B) further comprises a user equipment (104), a Next Generation Node B (gNodeB) (212), an AMF (214), a Policy Control Function (PCF) (216), and an external database (220).

[0082] In an embodiment, the UE (104) is configured to communicate with the network (106) or a 5G network through the gNodeB (212) (acting as a base station). The UE (104) may support multiple communication protocols and may operate on different frequency bands depending on the configuration of the network (106). The UE (104) ability to seamlessly connect to the network (106) is crucial for accessing various services such as voice, data, and multimedia. Further, the UE (104) is uniquely identified within the network (106) by its International Mobile Equipment Identity (IMEI). The IMEI is a 15 -digit number (or 16 digits in the case of International Mobile Equipment Identity and Software Version (IMEISV), which includes the software version) that is embedded into the UE (104) during itsmanufacturing. The first 8 digits of the IMEI represent the Type Allocation Code (TAC), a unique identifier assigned to the UE (104). The TAC specifies the make and model of the UE (104), allowing the network ( 106) to determine the capabilities of the UE (104). For instance, the network (106) may use the TAC to ascertain whether the UE (104) supports certain advanced features like a predefined UE policy, which enables the network (106) to provide services based on the characteristics of the UE (104). When the UE (104) attempts to connect to the 5G network, the UE (104) initiates a registration process by sending a request to the gNodeB (212). In an aspect, the request may be a registration request or a handover request. The registration / handover request contains crucial information about the UE (104), including IMEI ofthe UE (104). The gNodeB (212) forwards the request to the AMF (214), which uses the IMEI to derive the TAC and determines the capabilities of the UE (104), including its support for the UE policy. In the 5G network, different network slices can be allocated to specific services or applications.

[0083] In an embodiment, the gNodeB (212) is the 5G base station that provides radio access to the UE (104). The gNodeB (212) handles communication between the UE (104) and the 5G core network. The gNodeB (212) forwards the connection request from the UE (104) to the AMF via an N2 interface. The gNodeB (212) acts as an intermediary, relaying messages and instructions between the UE (104) and the components of the 5G core network.

[0084] In an embodiment, the AMF (214) manages both the access to and mobility within the network (106) for the UE (104). The AMF (214) is responsible for ensuring that the UEs (104) successfully connect to the network (106) and maintain their connections as the UEs move across different geographical areas. The AMF (214) also facilitates various features, such as UE policy management, by coordinating with other network functions. Further, the AMF (214) may handle the registration or handover requests initiated by the UE (104) via the gNodeB (212). Upon receiving the request, the AMF (214) extracts the IMEI from the registration request of the UE (104). The IMEI contains crucial information aboutthe UE (104), including the TAC, which is derived from the IMEI. By deriving the TAC, the AMF (214) through the IMEI may identify capabilities of the UE (104), including its support for specific network features like the UE policy. After deriving the TAC, the AMF (214) must determine whether the UE (104) supports the UE policy. To make the determination, the AMF (214) may first check an internal database (210), which stores information about the UE (104) and their corresponding support for UE policy based on the TAC. If the internal database (210) ofthe AMF (214) does not contain the necessary information for the specific TAC, the AMF (214) queries an external database (220). The external database (220) holds comprehensive records of the UE (104), enabling the AMF (214) to confirm whether the UE (104) in question supports the UE policy. In one example implementation, the transmission of the extracted TAC to the external database may be performed via a service-based interface or API endpoint exposed by the external system. The AMF may construct a query message including the TAC in a predefined schema or message format — such as JSON, XML, or a protocol buffer — and transmit it using a secure transport protocol, for example, HTTPS or Diameter. The request may be directed to a policy information server, device capability repository, or manufacturer-certified equipment database integrated into the operator’s backend. Upon receipt, the external database performs a lookup and returns a response indicating whether the corresponding UE supports the UE policy. The response may be formatted in a binary flag, capability descriptor, or structured attribute list. This interaction enables the AMF to make an informed decision on whether to initiate a UE policy association, even in cases where the TAC is previously unknown or unlisted in the local configuration. The two-step process ensures that the AMF (214) identifies the UE (104) that may benefit from the UE policy, thus optimizing network resource allocation and enhancing user experience. Once the AMF (214) has verified that the UE (104) supports the UE policy, the AMF (214) proceeds to initiate the UE policy association. Initiating involves establishing a connection with the PCF (216) for managing and enforcing network policies. Further, if the UE (104) does not support the UE policy, the AMF (214) may continue with the registration or handover process without initiating the policyassociation. For the UE (104) that does support the UE policy, the AMF (214) communicates with the PCF (216) via the N15 interface. The N15 interface facilitates the exchange of policy-related information between the AMF (214) and the PCF (216). Upon establishing communication, the AMF (214) relays the TAC to the PCF (216), which then formulates the appropriate policy rules tailored to a specific UE (104). These policy rules may include instructions on which network slices to use for different types of traffic, ensuring optimal performance and service quality for the user (102). Once the PCF (216) has provided the necessary policy rules, the AMF (214) forwards the information back to the UE (104) through the gNodeB (212). Said step completes the policy association process, enabling the UE (104) to benefit from the advanced capabilities of the 5G network.

[0085] In an embodiment, there may be two approaches for validating the relayed TAC associated with the UE (104). These two approaches ensure that the AMF (214) can accurately determine whether to initiate UE policy association, thereby optimizing network signalling and enhancing the user experience. In a first approach, the AMF (214) receives a registration request from the UE (104) when the UE attempts to connect to the 5G network via the gNodeB (212). During the registration procedure, the AMF (214) extracts the IMEI from the UE (104) messages, such as the registration request, identity response, or security mode complete, sent by the UE during the registration procedure. In an aspect, the AMF may derive the TAC from the IMEISV of the UE. The AMF (214) then derives the TAC from the extracted IMEI. The AMF (214) checks the internal database (210), including a mapping of the TAC to its corresponding support for UE policy rules. The internal mapping allows the AMF (214) to determine if the UE (104) supports the UE policy. The mapping may include detailed information about each of the UE (104) and its capabilities regarding supporting UE policy. If the UE (104) supports the UE policy, the AMF (214) proceeds with the registration process, including initiating the UE policy. If the UE (104) does not support the UE policy, the registration continues without initiating the UE policy.

[0086] In a second approach, the AMF (214) receives the registrationrequest from the UE (104) as it attempts to connect to the 5G network via the gNodeB (212). During the procedure, the AMF (214) extracts the IMEI from the UE’s (104) registration message. The AMF (214) derives the TAC from the IMEI. If the AMF (214) does not have the necessary information in the internal database (210) regarding the TAC for UE policy of the UE (104), the AMF (214) queries an external database (220). The external database (220) contains a comprehensive mapping of the TAC to the corresponding UE policy. Upon receiving confirmation from the external database (220) that the UE (104) supports the UE policy, the AMF (214) continues with the registration procedure, including initiating the UE policy. If the external database (220) indicates that the UE (104) does not support the UE policy, the registration process proceeds without initiating the UE policy.

[0087] In an embodiment, the PCF (216) manages and enforces network policies. The PCF (216) provides the AMF (214) with the appropriate policy rules based on the capability and the network requirements of the UE (104). Once the AMF (214) determines that at least one of the UE (104) supports the UE policy, it contacts the PCF (216) to retrieve the relevant policy information, which is then sent back to the UE (104).

[0088] In an embodiment, the external database (220), which may also be referred to as the external device database, is an component that stores the mapping of the TAC to its corresponding UE policy. If the AMF (214) does not have the necessary information internally in the internal database (210), the AMF (214) sends the TAC to the external database (220) for verification. The external database (220) then responds with whether the UE (104) associated with the TAC supports the UE policy. The response step ensures that the AMF (214) has accurate data before proceeding with associating the UE policy.

[0089] FIG. 3 illustrates an exemplary flowchart of a first approach (process) (300) for initiating the user equipment (UE) policy association in the network (106), in accordance with embodiments of the present disclosure.

[0090] At step 302, the user equipment (UE) (104) attempts to connect tothe Fifth Generation (5G) network. The attempt to connect may be initiated during initial registration when the UE (104) is powered on or enters a coverage area of the 5G system, or during a handover when the UE (104) transitions from one serving cell or radio access technology to another. The UE (104) transmits a connection request toward the gNodeB (212), which operates as the access point within the 5G radio access network. Upon receiving the connection request, the gNodeB (212) forwards the message to the Access and Mobility Management Function (AMF) (214) over the N2 interface to initiate core network registration procedures. In accordance with 5G architecture, registration and UE policy association are treated as distinct procedures. Registration enables the UE (104) to access the network, while UE policy association allows the retrieval and application of UE-specific policies from the Policy Control Function (PCF) (216). However, when applicable, UE policy association is initiated during the registration flow itself and not as a post-registration operation. If policy association is not applicable for a given device, registration proceeds to completion without initiating that additional procedure.

[0091] At step 304, the AMF (214) begins processing the forwarded message by extracting an identifier associated with the UE (104). The identifier may be an International Mobile Equipment Identity (IMEI) or International Mobile Equipment Identity and Software Version (IMEISV), which uniquely identify the device and embed within them a Type Allocation Code (TAC). The TAC comprises the first eight digits of the identifier and provides information regarding the make and model of the UE (104). By parsing the identifier and extracting the TAC, the AMF (214) is able to classify the UE (104) in terms of its capability to support one or more UE policy features. The extraction process may occur through multiple signaling exchanges such as the registration request message, an identity response initiated by the AMF (214), or a security mode complete message following authentication. For instance, if the UE (104) presents an IMEI such as “352620107654321,” the AMF (214) parses the value and isolates the TAC “35262010” for further evaluation.

[0092] At step 306, the AMF (214) performs a capability check by mapping the extracted TAC with a list of configured TACs stored in a database, specifically an internal device database (210). Each configured TAC entry in the database corresponds to a known device model and its associated capability attributes. The AMF (214), by performing the mapping operation, determines whether the UE (104) corresponding to the extracted TAC supports at least one UE policy. In the context, support for at least one UE policy is established if the device model associated with the TAC possesses the functional ability to receive, interpret, and apply UE policy rules, including policies structured according to the Universal Slice Routing Policy (URSP) framework. These capabilities may include parsing routing rule containers, recognizing application identifiers, and handling traffic descriptors as defined by 3GPP specifications. The database (210) may maintain detailed records for known TAC entries, including information on whether a given device model is capable of interpreting per-application policy rules or managing slice-level traffic routing. For example, the TAC “35262010” may be associated with a UE model supporting differentiated treatment for video, voice, and background data, while a TAC such as “35678092” may correspond to a device lacking such capabilities. Through the TAC-to-feature mapping, the AMF (214) establishes whether the UE (104) is eligible for a UE policy association session during the ongoing registration.

[0093] At step 308, when the internal database confirms that the UE (104) identified by the TAC is capable of supporting the UE policy, the AMF (214) proceeds with the registration of the UE (104) and initiates a UE policy association with the Policy Control Function (PCF) (216) over the N15 interface. By initiating the association during the registration flow, the AMF (214) enables the PCF (216) to generate and transmit UE-specific policy rules based on the identified capabilities of the UE (104) and the network operator’s configuration. The PCF (216) may deliver routing instructions that assign video streaming traffic to an enhanced mobile broadband (eMBB) slice, voice-over-IP (VoIP) calls to a slice configured for ultra-reliable low latency communication (URLLC), and background traffic such as email synchronization to a slice designated for best-effort service. Thesepolicy rules are transmitted from the PCF (216) to the AMF (214), which relays them to the UE (104) via the gNodeB (212). By receiving and applying these policies, the UE (104) is able to classify application flows and direct them to corresponding slices in accordance with network policies, thereby benefiting from enhanced user experience and service-level guarantees.

[0094] At step 310, when the internal database (210) indicates that the TAC corresponds to a UE (104) that does not support UE policy, the AMF (214) continues the registration procedure without initiating policy association with the PCF (216). By excluding policy signaling for unsupported devices, the AMF (214) reduces signaling load, prevents unnecessary interactions with the PCF (216), and avoids errors that may arise due to incompatible device behavior. For example, if the derived TAC is linked to a basic device that cannot parse routing rule containers or does not support traffic classification by application ID, initiating a policy session would not provide meaningful service enhancement and could introduce instability. By filtering such devices based on TAC at the AMF (214), the network ensures policy enforcement is applied only to capable devices while maintaining efficient resource usage across the control plane.

[0095] By performing these steps in a structured sequence beginning with TAC extraction from the UE (104), performing a capability check using the internal database (210), and conditionally initiating policy association with the PCF (216) during the registration flow, the system dynamically manages the UE policy framework in an optimized manner. Said approach allows only qualified UEs to participate in slice-based traffic differentiation while simplifying registration for other devices, thereby achieving a scalable and intelligent UE policy control strategy across heterogeneous device populations.

[0096] FIG. 4 illustrates an exemplary flowchart of a second approach (process 400) for initiating user equipment (UE) policy association in the network (106), in accordance with embodiments of the present disclosure.

[0097] At step 402, the UE (104) attempts to connect to the 5G core networkby transmiting either a registration request or a handover request. Such a connection request may occur during a cold start, re-registration, or mobility- triggered handover scenario . The request is transmitted to the gNodeB (212), which serves as the radio access interface between the UE (104) and the core network infrastructure. By receiving the request, the gNodeB (212) is able to relay it to the Access and Mobility Management Function (AMF) (214) using the standardized N2 interface, thereby triggering subsequent mobility and policy handling procedures in the core network.

[0098] At step 404, upon receiving the request from the gNodeB (212), the AMF (214) proceeds to extract the International Mobile Equipment Identity (IMEI) from the UE (104). The IMEI may be carried within several types of Non-Access Stratum (NAS) messages exchanged during the initial connection procedure. For example, the AMF (214) may obtain the IMEI from the registration request directly if the UE includes it voluntarily or may trigger an identity request prompting the UE to respond with the IMEI. Alternatively, the identifier may be conveyed as part of a security mode complete message in later stages of NAS signaling. After obtaining the IMEI, the AMF (214) derives the Type Allocation Code (TAC), which corresponds to the first eight digits of the IMEI. For instance, in the IMEI value “861051045612789”, the TAC is “86105104”. By performing the TAC derivation, the AMF (214) is able to uniquely identify the make and model of the UE (104), thereby facilitating a classification of the device's capabilities, particularly in relation to whether the device supports UE policy features such as routing rule parsing or slice-aware traffic classification.

[0099] At step 406, when the AMF (214) does not locate a corresponding entry for the derived TAC in the internal device database (210), the AMF (214) initiates a query to an external database (220). The internal database may lack certain TAC entries due to limitations in local updates or infrequent refresh cycles, particularly when newly released or region-specific devices atempt to register. By performing an external query in such cases, the AMF (214) ensures access to a broader and more current repository of TAC-to-capability mappings maintainedoutside the core network domain.

[0100] At step 408, the external database (220) responds to the query by evaluating whether the TAC associated with the UE (104) corresponds to a device that supports UE policy. The external database (220) may include comprehensive mappings for thousands of TAC entries, maintained by industry aggregators, device manufacturers, or mobile alliance registries. These mappings may include attributes such as support for Universal Slice Routing Policy (URSP), traffic descriptor parsing, and support for dynamic policy rule containers. For example, the TAC “86105104” may be associated with a UE capable of segmenting traffic based on application identifiers and implementing slice selection logic based on received policies, whereas a TAC like “35076288” may be flagged as not supporting these features due to limited firmware or chipset compatibility. By retrieving and analyzing these mappings, the external database (220) enables the AMF (214) to make informed decisions on initiating or bypassing UE policy association.

[0101] At step 410, the AMF (214) analyzes the response received from the external database (220) to determine whether the UE (104) supports UE policy. The response may include a binary support flag, a capabilities profile, or a metadata record indicating support for specific policy control features. By interpreting the support indicators provided by the external database (220), the AMF (214) is able to reach a reliable conclusion about the device’s compatibility with policy rules and decide whether to invoke the Policy Control Function (PCF).

[0102] At step 412, when the external database (220) confirms that the UE (104) supports UE policy, the AMF (214) continues with the registration procedure and initiates UE policy association with the PCF (216). The association allows the PCF (216) to generate policy rules tailored to the UE (104), such as directing VoIP calls to a low -latency URLLC slice, and multimedia streaming to a high-throughput eMBB slice. The policies are transmitted to the AMF (214) and delivered to the UE (104) through the gNodeB (212), allowing the UE (104) to implement application- aware traffic steering based on the received rules.

[0103] If, however, at step 412, the response from the external database (220) indicates that the UE ( 104) identified by the TAC does not support UE policy, the AMF (214) proceeds with completing the registration procedure without initiating a policy association session. By excluding incompatible devices from policy signaling, the network avoids unnecessary signaling overhead and ensures robust operation across a diverse set of user devices. For instance, a low-end loT device identified via TAC as lacking support for URSP interpretation would not benefit from policy enforcement and is thus processed through the standard registration path.

[0104] By incorporating a fallback mechanism to an external TAC database when local TAC mappings are unavailable, the AMF (214) is able to extend its visibility into device capability in real-time. Through said design, the system improves policy decision accuracy, minimizes erroneous policy activation, and maximizes network efficiency across heterogeneous and evolving device ecosystems.

[0105] FIG. 5 illustrates an exemplary flowchart of a method (500) for initiating the user equipment (UE) policy association in the network (106), in accordance with embodiments of the present disclosure.

[0106] At step 502, the method (500) is configured to receive a request from a user equipment (UE) (104). The request is typically initiated when the UE (104) attempts to connect to a Fifth Generation (5G) network through a gNodeB (212). The gNodeB (212), acting as a base station, forwards the received registration or handover request to an Access and Mobility Management Function (AMF) (214), which is responsible for managing registration, session handling, and mobility procedures of the UE (104) within the 5G core network. The connection request generally includes the International Mobile Equipment Identity (IMEI) or IMEISV of the UE (104), which allows the AMF (214) to uniquely identify the device and assess its capability for supporting specific network features. By receiving the connection request, the AMF (214) is able to begin device-specific processing, including authentication, feature support assessment, and determination of whetherthe UE (104) qualifies for UE policy association. For instance, when the UE (104) is powered on in a coverage area, the UE (104) transmits a registration request that is routed through the gNodeB (212) to the AMF (214). The AMF (214), upon receiving the message, initiates procedures to evaluate whether the UE (104) can support advanced policies such as slice-based traffic steering, which depend on device capabilities.

[0107] At step 504, the method (500) proceeds with the AMF (214) deriving the Type Allocation Code (TAC) from the IMEI associated with the UE (104). The TAC comprises the first eight digits of the IMEI and encodes the device’s make and model. For example, for an IMEI “12345678XXXXXX”, the TAC is “12345678”, which may correspond to a specific manufacturer and device variant. By parsing the IMEI and extracting the TAC, the AMF (214) obtains metadata indicative of the hardware and firmware profile of the UE (104), including its potential to support User Equipment Policy (UE policy) rules. Through the derived TAC, the AMF (214) gains visibility into the class of device attempting to register, and whether such a device is likely to support features such as URSP (User Equipment Route Selection Policy), application-level traffic routing, or rule container parsing for slice enforcement.

[0108] At step 506, the AMF (214) uses the derived TAC to determine whether the UE (104) supports UE policy features. The determination is performed by mapping the derived TAC to a repository of known TAC entries that correspond to device capabilities. The mapping may include information regarding support for multiple traffic handling behaviors such as slice -specific routing, differentiated treatment for real-time vs. background flows, offloading to Wi-Fi, or network congestion-based routing prioritization. The repository of TAC-to-policy support mappings may be maintained in either or both of the following forms:

[0109] Internal Database (210): The AMF (214) may be configured to access an internal database (210) storing a curated list of TACs and corresponding support indicators. Each entry in the internal database (210) maps a TAC to a set of UE policy support attributes. For example, the TAC “87654321” may be mappedinternally to a device that supports optimized video streaming, in which traffic from applications such as media players or streaming clients is routed through a high throughput eMBB slice. The internal database (210) enables rapid, low-latency decision-making without involving external entities.

[0110] External Database (220): When the internal database (210) does not include an entry for the derived TAC, the AMF (214) may transmit a query to an external database (220), which may be managed by a third-party repository or global device registry. The external database (220) typically offers a more comprehensive listing of device TACs, including newly launched or less commonly used devices. For instance, upon receiving a query for the TAC “87654321”, the external database (220) may respond with information confirming that the device model supports policies such as slice-aware routing or Wi-Fi fallback. Upon receiving such confirmation, the AMF (214) may locally cache the result and proceed accordingly.

[0111] At step 508, based on the outcome of the TAC capability check, the AMF (214) either initiates a UE policy association or skips it. If the derived TAC indicates that the UE (104) supports at least one UE policy, the AMF (214) triggers a policy association session with the Policy Control Function (PCF). Triggering may involve communicating the TAC, subscriber profile, or access type to the PCF, which in turn formulates UE-specific policy rules that are delivered back to the UE (104) via the gNodeB (212). These rules may include slice assignment for application identifiers, latency prioritization for VoIP, or offloading instructions for background sync services. If, however, the derived TAC indicates that the UE (104) lacks support for such policies either due to missing rule container handling or limited firmware capabilities, the AMF (214) proceeds with standard registration without invoking the PCF or delivering slice routing policies. By executing the conditional decision-making step, the AMF (214) ensures that UE policy associations are initiated only for compatible UEs, thereby reducing unnecessary signaling load and enhancing network performance.

[0112] By incorporating TAC-based capability checks using both internal and external databases and conditionally triggering UE policy association based on the result, the method (500) enables intelligent, device-aware policy delivery in heterogeneous 5G environments. Said approach ensures optimal use of network slices and application-level differentiation, while preserving backward compatibility with legacy or low-capability devices.

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

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

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

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

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

[0118] FIG. 7 illustrates a flowchart (700) that represents a method for initiating a user equipment (UE) policy association in a network (106) under conditions where the UE does not explicitly signal support for UE policies using a UE Policy Container.

[0119] The procedure begins at step (702), where an Access and Mobility Management Function (AMF) (214) receives a request from at least one UE (104) to connect to the network. The request may be a registration request during initial access when the UE (104) powers on, or a handover request when the UE (104) transitions between cells or between different access technologies, such as from 4G to 5G. The UE (104) sends the request through the gNodeB (212), which functions as the base station interface to the core network. Upon receiving the request over the N2 interface, the AMF (214) begins processing the connection attempt.

[0120] At step (704), the AMF (214) determines whether a UE Policy Container has been included in the request. The UE Policy Container, as defined in 3GPP TS 24.501, is used by UEs to indicate their support for per-application traffic routing and policy enforcement features, such as Universal Slice Routing Policy (URSP). The container includes routing rule containers, traffic descriptors, and application identifiers, which allow the network to deliver differentiated treatment to traffic types such as video, voice, and background synchronization. However, in many operational deployments, a large number of UEs do not include the container in the initial message. Lack of inclusion of container may happen because the UE may not support URSP, because the device manufacturer did not enable the feature in firmware, or because the container was not included due to user settings or network conditions.

[0121] In response to the absence of the UE Policy Container, the flow advances to step (706), where the AMF (214) initiates a UE policy association based on locally stored configuration parameters. The local configuration enables the AMF (214) to apply predefined rules that infer whether a UE (104) should be associated with a policy framework, even in the absence of an explicit indication. The configuration logic may reference the UE’s International Mobile Equipment Identity (IMEI), from which the Type Allocation Code (TAC) is derived. For example, a TAC value of "35262010" may correspond to a particular device model known to support URSP features, based on manufacturer declarations or field testing. The AMF (214) may consult an internal device capability table that maps such TAC values to UE policy support indicators. If the TAC is listed in the table as supporting URSP, the AMF (214) proceeds to initiate a UE policy association.

[0122] In another example, the local configuration may be based on the UE’s slice subscription profile. Suppose a UE (104) is provisioned to access multiple network slices, for instance, a slice for voice services, another for video streaming, and a third for general-purpose data. Even if the UE does not indicate support through a policy container, the AMF (214) may be configured to assume policy support based on the presence of these slice subscriptions, particularly whenthe operator’s service design relies on application-aware routing.

[0123] Once the AMF (214) determines that a UE policy association should be initiated, the AMF (214) identifies an appropriate Policy Control Function (PCF) instance with which to establish the policy session. In a non-roaming scenario, where the UE (104) is operating within its Home Public Land Mobile Network (H- PLMN), the AMF (214) establishes the policy association with the Home PCF (H- PCF). In contrast, in a roaming scenario where the UE is registered in a Visited PLMN (V-PLMN), the AMF (214) establishes the policy association with a Visited PCF (V-PCF). The AMF (214) determines whether to use the H-PCF or the V-PCF based on the serving PLMN ID and subscriber profile data obtained from Unified Data Repository (UDR) or from network functions such as the Subscription Data Management Function (SDM). In certain embodiments, in a roaming scenario, a configuration of the AMF (214) may specify whether delivery of the UE policy is to be performed based on a roaming agreement established between a H-PLMN associated with the UE and the V -PLMN. In some implementations, the AMF (214) configuration may further specify whether initiation of a UE policy association procedure is to be performed based on at least one of an IMEI, a TAC of the UE, and a network slice subscription associated with the UE.

[0124] By applying such logic within the registration procedure, as opposed to deferring policy decisions until registration completes, the AMF (214) enables early and accurate policy enforcement. The initiation of the UE policy association is embedded within the registration call flow itself. If the AMF (214) determines that the UE (104) qualifies for policy-based treatment, it initiates the N15 interface interaction with the PCF (216) during registration, ensuring that the resulting policy rules are applied to the UE (104) before it begins data transfer.

[0125] By supporting the initiation of policy association through AMF local configuration in the absence of UE Policy Container signaling, the system ensures compatibility with a wide range of devices, improves signaling efficiency, and maintains robust network policy control. The method enables network operators to offer advanced service differentiation even when UE capability signaling isincomplete or absent, thereby enhancing the quality of experience (QoE) across both legacy and advanced UEs.

[0126] In some embodiments, a method is disclosed for initiating a user equipment (UE) policy association in a communication network. The method comprises receiving, by a network control function configured to manage access and mobility — such as, but not limited to, an Access and Mobility Management Function (AMF) — a signaling message or request from a UE, the request containing at least one identifier that is associated with the UE. The identifier may take the form of a unique device identity, such as an International Mobile Equipment Identity (IMEI), or any equivalent parameter that encodes device-specific information. From this identifier, the control function extracts a model-identifying portion, such as a Type Allocation Code (TAC), which is then used to assess the capability of the UE to support one or more network policies, referred to generally as UE policy. The assessment involves referencing a stored repository, database, or mapping table that contains preconfigured TAC entries and their corresponding policy support indicators. Based on the outcome of this capability check, the method proceeds to determine whether to initiate a policy association procedure with a policy management function — such as a Policy Control Function (PCF) — as part of the UE’s registration or connection process. The policy association may involve, for example, the configuration of traffic handling rules, slice access control, service prioritization, or other quality-of-service parameters tailored to the capabilities of the UE. This method enables network-initiated policy handling even in cases where the UE does not explicitly signal policy support, thereby providing enhanced flexibility and device-aware policy enforcement across a diverse population of terminal devices. Variations of the method may include equivalent operations performed by derivative control functions or support for alternative identifiers, databases, or signaling formats, depending on implementation requirements or evolving standardization.

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

[0128] The present disclosure provides a technical advancement in the field of mobile network policy control by introducing a device-aware mechanism for initiating UE policy association without relying on explicit signaling from the user equipment. By leveraging the Type Allocation Code (TAC) derived from standard identifiers such as IMEI or IMEISV, the Access and Mobility Management Function (AMF) is able to determine whether the UE supports at least one policy feature, such as application-specific routing, traffic classification, or slice-based prioritization.

[0129] The present disclosure further advances the efficiency and scalability of next-generation networks by optimizing signaling procedures. The AMF avoids unnecessary interactions with the Policy Control Function (PCF) for unsupported devices, reducing control plane load and improving registration performance. Additionally, the fallback to external database verification and support for local AMF configuration ensures robust and adaptive policy initiation, even in cases where UE support is not explicitly indicated. Said process results in enhanced interoperability, better utilization of network slicing features, and improved user experience through targeted policy enforcement.ADVANTAGES OF THE PRESENT DISCLOSURE

[0130] The present disclosure provides a method and a system for mobile network policy control that enables a network-side function to autonomously initiate a user equipment (UE) policy association based on the device’s capability profile, without requiring explicit signaling of support from the UE. By extracting the Type Allocation Code (TAC) from standard device identifiers such as IMEI orIMEISV, the Access and Mobility Management Function (AMF) can determine whether the requesting UE supports policy functionalities including applicationbased traffic routing, slice-specific service differentiation, or dynamic traffic steering. The extraction of TAC from standard device obviates a need for the UE to transmit a UE Policy Container and eliminates the dependency on client-side compliance, thereby improving coverage across heterogeneous UE populations.

[0131] The present disclosure provides a method and a system for optimizing control plane efficiency and network scalability in 5G and nextgeneration core networks by eliminating redundant or unnecessary signaling. The AMF selectively initiates UE policy association only for UEs confirmed to support policy-based routing, thereby reducing signaling traffic toward the Policy Control Function (PCF) and avoiding resource expenditure on unsupported devices. The selective approach reduces network load, minimizes registration latency, and enhances system responsiveness, particularly in scenarios involving high UE densities or deployments with mixed support capabilities.

[0132] The present disclosure provides a method and a system for ensuring reliability in policy-driven network slicing by restricting policy delivery to only those UEs that demonstrate verified support for receiving and enforcing network policies. The approach mitigates the risk of misconfigured or inoperative policy enforcement that may otherwise result from indiscriminate delivery of policy instructions. By activating policy association based on explicit device capability matching, the system preserves end-to-end service consistency and enhances policy integrity.

[0133] The present disclosure provides a method and a system for robust and adaptive device capability verification through a two-tiered evaluation mechanism. If the AMF does not find TAC capability mapping in its local database, the system supports querying an external device capability database to determine the support status of the UE model. Such querying may enable policy association decisions to be made accurately even for new, unregistered, or low-volume devices, thereby supporting uninterrupted service delivery and enhancing compatibilitywithout compromising policy enforcement logic.

[0134] The present disclosure provides a method and a system for enabling dynamic and configuration-driven policy association through AMF-local heuristics. In scenarios where UE policy support is not signaled through the UE Policy Container, the AMF may refer to locally configured decision logic that uses parameters such as TAC, IMEI ranges, or subscribed network slice profiles. Such approach allows the AMF to make intelligent policy association decisions even in the absence of UE-side indications, thus enabling targeted service delivery and consistent user experience across both compliant and non-compliant devices, without necessitating device-specific provisioning or customization.

Claims

We Claim:

1. A method for initiating a user equipment (UE) policy association in a network, the method comprising: receiving, by an access and mobility management function (AMF), a request from at least one user equipment (UE), wherein the request comprises an identifier associated with the at least one UE; extracting, by the AMF, a type allocation code (TAC) from the identifier associated with the at least one UE; checking, by the AMF, whether the at least one UE corresponding to the extracted TAC supports at least one UE policy, wherein the checking is performed by mapping the extracted TAC with a list of configured TACs stored in a database; and based on the checking, proceeding, by the AMF, with a registration of the UE including initiating a UE policy association with a Policy Control Function (PCF) if the at least one UE supports the at least one UE policy.

2. The method as claimed in claim 1, further comprises: if the extracted TAC is not found in the list of configured TACs stored in the database, proceeding, by the AMF, with the registration of the UE without initiating the at least one UE policy association.

3. The method as claimed in claim 1, further comprises: if the extracted TAC is not found in the list of configured TACs stored in the database, transmitting, by the AMF, the extracted TAC to an external database to verify whether the at least one UE supports the at least one UE policy.

4. The method as claimed in claim 3, further comprises: upon receiving a response from the external database indicating that the at least one UE supports the UE policy, initiating by the AMF, the at least one UE policy association with the PCF; andupon receiving a response from the external database indicating that the at least one UE does not support the at least one UE policy, proceeding, by the AMF, with registration of the at least UE without initiating the UE policy association.

5. The method as claimed in claim 1, wherein the request is one of a registration request and a handover request.

6. The method as claimed in claim 1 , wherein the identifier associated with the at least one UE is an IMEI (International Mobile Equipment Identity) or an IMEISV (International Mobile Equipment Identity and Software Version).

7. A system for initiating a user equipment (UE) policy association in a network, the system comprising: an access and mobility management function (AMF) configured to: receive a request from at least one user equipment (UE), wherein the request comprises an identifier associated with the at least one UE; extract a type allocation code (TAC) from the identifier associated with the at least one UE; check whether the at least one UE corresponding to the extracted TAC supports at least one UE policy, wherein the checking is performed by mapping the extracted TAC with a list of configured TACs stored in a database of the AMF; and based on the checking, proceeding with a registration of the UE including initiating a UE policy association with a Policy Control Function (PCF) if the at least one UE supports the at least one UE policy.

8. The system as claimed in claim 7, further comprises:if the extracted TAC is not mapped with the list of configured TACs, proceed with a UE registration without initiating the at least one UE policy association if the at least one UE does not support the at least one UE policy.

9. The system as claimed in claim 7, further comprises: if the extracted TAC is not mapped with the list of configured TACs stored in the database, transmit the extracted TAC to an external database to verify whether the at least one UE supports the at least one UE policy.

10. The system as claimed in claim 9, further comprises: upon receiving a response from the external database indicating that the at least one UE supports the UE policy, the AMF initiates the at least one UE policy association with the PCF; and upon receiving a response from the external database indicating that the at least one UE does not support the at least one UE policy, proceed by the AMF, with registration of the at least UE without initiating the UE policy association.

11. The system as claimed in claim 7, wherein the request is one of a registration request and a handover request.

12. The system as claimed in claim 7, wherein the identifier associated with the at least one UE is an IMEI (International Mobile Equipment Identity) or an IMEISV (International Mobile Equipment Identity and Software Version).

13. A user equipment (UE) communicatively coupled with a system, the coupling comprises of: receiving, by the system, a connection request from at least one UE; sending, by the system, an acknowledgment of the connection request to the at least one UE; andtransmitting a plurality of signals in response to the connection request, wherein the system is configured to initiate at least one user equipment (UE) policy association in a network, as claimed in claim 1.

14. A computer program product comprising a non-transitory computer- readable medium comprising instructions that, when executed by one or more processors, cause the one or more processors to execute a method for initiating a user equipment (UE) policy association in a network, the method comprising steps of: receiving, by an access and mobility management function (AMF), a request from at least one user equipment (UE), wherein the request comprises an identifier associated with the at least one UE; extracting, by the AMF, a type allocation code (TAC) from the identifier associated with the at least one UE; checking, by the AMF, whether the at least one UE corresponding to the extracted TAC supports at least one UE policy, wherein the checking is performed by mapping the extracted TAC with a list of configured TACs stored in a database of the AMF; and based on the checking, proceeding, by the AMF, with a registration of the UE including initiating a UE policy association with a Policy Control Function (PCF) if the at least one UE supports the at least one UE policy.

15. A method for initiating a user equipment (UE) policy association in a network, the method comprising: receiving, by an Access and Mobility Management Function (AMF), a request from at least one UE to connect to the network; determining, by the AMF from the received request, that a UE Policy Container is not received from the at least one UE; and in response to determining that the UE policy container is not received from the at least one UE, initiating, by the AMF, the UE policy association for the at least one UE based on an AMF local configuration.

16. The method as claimed in claim 15, wherein the AMF local configuration indicates whether to initiate the UE policy association based on at least one of device IMEI, Type Allocation Code (TAC), and UE slice subscription.

17. The method as claimed in claim 15, wherein, in anon-roaming scenario, the AMF establishes the UE policy association with a Policy Control Function (PCF) in the Home PLMN (H-PCF).

18. The method as claimed in claim 15, wherein, in a roaming scenario, theAMF establishes the UE Policy Association with a Visited Policy Control Function (V-PCF).

Images