Patent Publication Number: US-2023133781-A1

Title: Predefined policy and charging control rules management

Description:
PRIORITY CLAIM 
     This application claims the benefit of priority to U.S. Provisional Patent Application Ser. No. 63/059,628, filed Jul. 31, 2020, which is incorporated herein by reference in its entirety. 
    
    
     TECHNICAL FIELD 
     Embodiments pertain to wireless communications in 5G, or new radio (NR), systems. Some embodiments related to PCC rule management in 5G networks. 
     BACKGROUND 
     The use and complexity of 3GPP LTE systems (including LTE and LTE-Advanced systems) has increased due to both an increase in the types of devices user equipment (UEs) using network resources as well as the amount of data and bandwidth being used by various applications, such as video streaming, operating on these UEs. With the vast increase in number and diversity of communication devices, the corresponding network environment, including routers, switches, bridges, gateways, firewalls, and load balancers, has become increasingly complicated, especially with the advent of next generation (NG) (or new radio (NR)/5 th  generation (5G)) systems. As expected, a number of issues abound with the advent of any new technology. 
    
    
     
       BRIEF DESCRIPTION OF THE FIGURES 
       In the figures, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The figures illustrate generally, by way of example, but not by way of limitation, various embodiments discussed in the present document. 
         FIG.  1 A  illustrates an architecture of a network, in accordance with some aspects. 
         FIG.  1 B  illustrates a non-roaming 5G system architecture in accordance with some aspects. 
         FIG.  1 C  illustrates a non-roaming 5G system architecture in accordance with some aspects. 
         FIG.  2    illustrates a block diagram of a communication device in accordance with some embodiments. 
         FIG.  3    illustrates a Network Resource Model (NRM) fragment for a predefined PCC rule in accordance with some embodiments. 
         FIG.  4    illustrates an inheritance hierarchy for a predefined PCC rule modeling in accordance with some embodiments. 
         FIG.  5    illustrates a NRM fragment for configurable 5G Quality of Service (QoS) Identifiers (5Qis) in a 5G core network (5GC) in accordance with some embodiments. 
         FIG.  6    illustrates a NRM fragment for dynamic 5QIs in a NG radio access network (NG-RAN) in accordance with some embodiments. 
         FIG.  7    illustrates a NRM fragment for dynamic 5Qis in the 5GC in accordance with some embodiments. 
         FIG.  8    illustrates an inheritance hierarchy for IOC Dynamic5QISet in accordance with some embodiments. 
         FIG.  9    illustrates a method of providing PCC rule information in accordance with some embodiments. 
     
    
    
     DETAILED DESCRIPTION 
     The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of other embodiments. Embodiments set forth in the claims encompass all available equivalents of those claims. 
       FIG.  1 A  illustrates an architecture of a network in accordance with some aspects. The network  140 A includes 3GPP LTE/4G and NG network functions. A network function can be implemented as a discrete network element on a dedicated hardware, as a software instance running on dedicated hardware, and/or as a virtualized function instantiated on an appropriate platform, e.g., dedicated hardware or a cloud infrastructure. 
     The network  140 A is shown to include user equipment (UE)  101  and UE  102 . The UEs  101  and  102  are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks) but may also include any mobile or non-mobile computing device, such as portable (laptop) or desktop computers, wireless handsets, drones, or any other computing device including a wired and/or wireless communications interface. The UEs  101  and  102  can be collectively referred to herein as UE  101 , and UE  101  can be used to perform one or more of the techniques disclosed herein. 
     Any of the radio links described herein (e.g., as used in the network  140 A or any other illustrated network) may operate according to any exemplary radio communication technology and/or standard. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (such as Licensed Shared Access (LSA) in 2.3-2.4 GHz, 3.4-3.6 GHz, 3.6-3.8 GHz, and other frequencies and Spectrum Access System (SAS) in 3.55-3.7 GHz and other frequencies). Different Single Carrier or Orthogonal Frequency Domain Multiplexing (OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier (FBMC), OFDMA, etc.), and in particular 3GPP NR, may be used by allocating the OFDM carrier data bit vectors to the corresponding symbol resources. 
     In some aspects, any of the UEs  101  and  102  can comprise an Internet-of-Things (IoT) UE or a Cellular IoT (CIoT) UE, which can comprise a network access layer designed for low-power IoT applications utilizing short-lived UE connections. In some aspects, any of the UEs  101  and  102  can include a narrowband (NB) IoT UE (e.g., such as an enhanced NB-IoT (eNB-IoT) UE and Further Enhanced (FeNB-IoT) UE). An IoT UE can utilize technologies such as machine-to-machine (M2M) or machine-type communications (MTC) for exchanging data with an MTC server or device via a public land mobile network (PLMN), Proximity-Based Service (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network includes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network. In some aspects, any of the UEs  101  and  102  can include enhanced MTC (eMTC) UEs or further enhanced MTC (FeMTC) UEs. 
     The UEs  101  and  102  may be configured to connect, e.g., communicatively couple, with a radio access network (RAN)  110 . The RAN  110  may be, for example, an Evolved Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or some other type of RAN. 
     The UEs  101  and  102  utilize connections  103  and  104 , respectively, each of which comprises a physical communications interface or layer (discussed in further detail below); in this example, the connections  103  and  104  are illustrated as an air interface to enable communicative coupling, and can be consistent with cellular communications protocols, such as a Global System for Mobile Communications (GSM) protocol, a code-division multiple access (CDMA) network protocol, a Push-to-Talk (PTT) protocol, a PTT over Cellular (POC) protocol, a Universal Mobile Telecommunications System (UMTS) protocol, a 3GPP Long Term Evolution (LTE) protocol, a fifth-generation (5G) protocol, a New Radio (NR) protocol, and the like. 
     In an aspect, the UEs  101  and  102  may further directly exchange communication data via a ProSe interface  105 . The ProSe interface  105  may alternatively be referred to as a sidelink (SL) interface comprising one or more logical channels, including but not limited to a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), a Physical Sidelink Broadcast Channel (PSBCH), and a Physical Sidelink Feedback Channel (PSFCH). 
     The UE  102  is shown to be configured to access an access point (AP)  106  via connection  107 . The connection  107  can comprise a local wireless connection, such as, for example, a connection consistent with any IEEE 802.11 protocol, according to which the AP  106  can comprise a wireless fidelity (WiFi®) router. In this example, the AP  106  is shown to be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). 
     The RAN  110  can include one or more access nodes that enable the connections  103  and  104 . These access nodes (ANs) can be referred to as base stations (BSs), NodeBs, evolved NodeBs (eNBs). Next Generation NodeBs (gNBs), RAN nodes, and the like, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). In some aspects, the communication nodes  111  and  112  can be transmission/reception points (TRPs). In instances when the communication nodes  111  and  112  are NodeBs (e.g., eNBs or gNBs), one or more TRPs can function within the communication cell of the NodeBs. The RAN  110  may include one or more RAN nodes for providing macrocells, e.g., macro RAN node  111 , and one or more RAN nodes for providing femtocells or picocells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low power (LP) RAN node  112 . 
     Any of the RAN nodes  111  and  112  can terminate the air interface protocol and can be the first point of contact for the UEs  101  and  102 . In some aspects, any of the RAN nodes  111  and  112  can fulfill various logical functions for the RAN  110  including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In an example, any of the nodes  111  and/or  112  can be a gNB, an eNB, or another type of RAN node. 
     The RAN  110  is shown to be communicatively coupled to a core network (CN)  120  via an S1 interface  113 . In aspects, the CN  120  may be an evolved packet core (EPC) network, a NextGen Packet Core (NPC) network, or some other type of CN (e.g., as illustrated in reference to  FIGS.  1 B- 1 C ). In this aspect, the S1 interface  113  is split into two parts: the S1-U interface  114 , which carries traffic data between the RAN nodes  111  and  112  and the serving gateway (S-GW)  122 , and the S1-mobility management entity (MME) interface  115 , which is a signaling interface between the RAN nodes  111  and  112  and MMEs  121 . 
     In this aspect, the CN  120  comprises the MMEs  121 , the S-GW  122 , the Packet Data Network (PDN) Gateway (P-GW)  123 , and a home subscriber server (HSS)  124 . The MMEs  121  may be similar in function to the control plane of legacy Serving General Packet Radio Service (GPRS) Support Nodes (SGSN). The MMEs  121  may manage mobility aspects in access such as gateway selection and tracking area list management. The HSS  124  may comprise a database for network users, including subscription-related information to support the network entities&#39; handling of communication sessions. The CN  120  may comprise one or several HSSs  124 , depending on the number of mobile subscribers, on the capacity of the equipment, on the organization of the network, etc. For example, the HSS  124  can provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location dependencies, etc. 
     The S-GW  122  may terminate the S1 interface  113  towards the RAN  110 , and routes data packets between the RAN  110  and the CN  120 . In addition, the S-GW  122  may be a local mobility anchor point for inter-RAN node handovers and also may provide an anchor for inter-3GPP mobility. Other responsibilities of the S-GW  122  may include a lawful intercept, charging, and some policy enforcement. 
     The P-GW  123  may terminate an SGi interface toward a PDN. The P-GW  123  may route data packets between the EPC network  120  and external networks such as a network including the application server  184  (alternatively referred to as application function (AF)) via an Internet Protocol (IP) interface  125 . The P-GW  123  can also communicate data to other external networks  131 A, which can include the Internet, IP multimedia subsystem (IPS) network, and other networks. Generally, the application server  184  may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS Packet Services (PS) domain, LTE PS data services, etc.). In this aspect, the P-GW  123  is shown to be communicatively coupled to an application server  184  via an IP interface  125 . The application server  184  can also be configured to support one or more communication services (e.g., Voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs  101  and  102  via the CN  120 . 
     The P-GW  123  may further be a node for policy enforcement and charging data collection. Policy and Charging Rules Function (PCRF)  126  is the policy and charging control element of the CN  120 . In a non-roaming scenario, in some aspects, there may be a single PCRF in the Home Public Land Mobile Network (HPLMN) associated with a UE&#39;s Internet Protocol Connectivity Access Network (IP-CAN) session. In a roaming scenario with a local breakout of traffic, there may be two PCRFs associated with a UE&#39;s IP-CAN session: a Home PCRF (H-PCRF) within an HPLMN and a Visited PCRF (V-PCRF) within a Visited Public Land Mobile Network (VPLMN). The PCRF  126  may be communicatively coupled to the application server  184  via the P-GW  123 . 
     In some aspects, the communication network  140 A can be an IoT network or a 5G network, including 50 new radio network using communications in the licensed (5G NR) and the unlicensed (5G NR-U) spectrum. One of the current enablers of IoT is the narrowband-IoT (NB-IoT). Operation in the unlicensed spectrum may include dual connectivity (DC) operation and the standalone LTE system in the unlicensed spectrum, according to which LTE-based technology solely operates in unlicensed spectrum without the use of an “anchor” in the licensed spectrum, called MulteFire. Further enhanced operation of LTE systems in the licensed as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations can include techniques for sidelink resource allocation and UE processing behaviors for NR sidelink V2X communications. 
     An NG system architecture can include the RAN  110  and a 5G network core (5GC)  120 . The NG-RAN  110  can include a plurality of nodes, such as gNBs and NG-eNBs. The core network  120  (e.g., a 5G core network or 5GC) can include an access and mobility function (AMF) and/or a user plane function (UPF). The AMF and the UPF can be communicatively coupled to the gNBs and the NG-eNBs via NG interfaces. More specifically, in some aspects, the gNBs and the NG-eNBs can be connected to the AMF by NG-C interfaces, and to the UPF by NG-U interfaces. The gNBs and the NG-eNBs can be coupled to each other via Xn interfaces. 
     In some aspects, the NG system architecture can use reference points between various nodes as provided by 3GPP Technical Specification (TS) 23.501 (e.g., V15.4.0, 2018-12). In some aspects, each of the gNBs and the NG-eNBs can be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so forth. In some aspects, a gNB can be a master node (MN) and NG-eNB can be a secondary node (SN) in a 5G architecture. 
       FIG.  1 B  illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular,  FIG.  1 B  illustrates a 5G system architecture  140 B in a reference point representation. More specifically. UE  102  can be in communication with RAN  110  as well as one or more other 5GC network entities. The 5G system architecture  140 B includes a plurality of network functions (NFs), such as an AMF  132 , session management function (SMF)  136 , policy control function (PCF)  148 , application function (AF)  150 , UPF  134 , network slice selection function (NSSF)  142 , authentication server function (AUSF)  144 , and unified data management (UDM)/home subscriber server (HSS)  146 . 
     The UPF  134  can provide a connection to a data network (DN)  152 , which can include, for example, operator services, Internet access, or third-party services. The AMF  132  can be used to manage access control and mobility and can also include network slice selection functionality. The AMF  132  may provide UE-based authentication, authorization, mobility management, etc., and may be independent of the access technologies. The SMF  136  can be configured to set up and manage various sessions according to network policy. The SMF  136  may thus be responsible for session management and allocation of IP addresses to UEs. The SMF  136  may also select and control the UPF  134  for data transfer. The SMF  136  may be associated with a single session of a UE  101  or multiple sessions of the UE  101 . This is to say that the UE  101  may have multiple 5G sessions. Different SMFs may be allocated to each session. The use of different SMFs may permit each session to be individually managed. As a consequence, the functionalities of each session may be independent of each other. 
     The UPF  134  can be deployed in one or more configurations according to the desired service type and may be connected with a data network. The PCF  148  can be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to PCRF in a 4G communication system). The UDM can be configured to store subscriber profiles and data (similar to an HSS in a 4G communication system). 
     The AF  150  may provide information on the packet flow to the PCF  148  responsible for policy control to support a desired QoS. The PCF  148  may set mobility and session management policies for the UE  101 . To this end, the PCF  148  may use the packet flow information to determine the appropriate policies for proper operation of the AMF  132  and SMF  136 . The AUSF  144  may store data for UE authentication. 
     In some aspects, the 5G system architecture  140 B includes an IP multimedia subsystem (IMS)  168 B as well as a plurality of IP multimedia core network subsystem entities, such as call session control functions (CSCFs). More specifically, the IMS  168 B includes a CSCF, which can act as a proxy CSCF (P-CSCF)  162 BE, a serving CSCF (S-CSCF)  164 B, an emergency CSCF (E-CSCF) (not illustrated in  FIG.  1 B ), or interrogating CSCF (I-CSCF)  166 B. The P-CSCF  162 B can be configured to be the first contact point for the UE  102  within the IM subsystem (IMS)  168 B. The S-CSCF  164 B can be configured to handle the session states in the network, and the E-CSCF can be configured to handle certain aspects of emergency sessions such as routing an emergency request to the correct emergency center or PSAP. The I-CSCF  166 B can be configured to function as the contact point within an operator&#39;s network for all IMS connections destined to a subscriber of that network operator, or a roaming subscriber currently located within that network operator&#39;s service area. In some aspects, the I-CSCF  166 B can be connected to another IP multimedia network  170 E, e.g. an IMS operated by a different network operator. 
     In some aspects, the UDM/HSS  146  can be coupled to an application server  160 E, which can include a telephony application server (TAS) or another application server (AS). The AS  160 B can be coupled to the IMS  168 B via the S-CSCF  164 B or the I-CSCF  166 B. 
     A reference point representation shows that interaction can exist between corresponding NF services. For example,  FIG.  1 B  illustrates the following reference points: N1 (between the UE  102  and the AMF  132 ), N2 (between the RAN  110  and the AMF  132 ), N3 (between the RAN  110  and the UPF  134 ), N4 (between the SMF  136  and the UPF  134 ), N5 (between the PCF  148  and the AF  150 , not shown), N6 (between the UPF  134  and the DN  152 ), N7 (between the SMF  136  and the PCF  148 , not shown), N8 (between the UDM  146  and the AMF  132 , not shown), N9 (between two UPFs  134 , not shown), N10 (between the UDM  146  and the SMF  136 , not shown), N11 (between the AMF  132  and the SMF  136 , not shown), N12 (between the AUSF  144  and the AMF  132 , not shown), N  13  (between the AUSF  144  and the UDM  146 , not shown), N14 (between two AMFs  132 , not shown), N15 (between the PCF  148  and the AMF  132  in case of a non-roaming scenario, or between the PCF  148  and a visited network and AMF  132  in case of a roaming scenario, not shown). N16 (between two SMFs, not shown), and N22 (between AMF  132  and NSSF  142 , not shown). Other reference point representations not shown in  FIG.  1 B  can also be used. 
       FIG.  1 C  illustrates a 5G system architecture  140 C and a service-based representation. In addition to the network entities illustrated in  FIG.  1 B , system architecture  140 C can also include a network exposure function (NEF)  154  and a network repository function (NRF)  156 . In some aspects, 5G system architectures can be service-based and interaction between network functions can be represented by corresponding point-to-point reference points Ni or as service-based interfaces. 
     In some aspects, as illustrated in  FIG.  1 C , service-based representations can be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture  140 C can include the following service-based interfaces: Namf  158 H (a service-based interface exhibited by the AMF  132 ), Nsmf  158 I (a service-based interface exhibited by the SMF  136 ), Nnef  158 B (a service-based interface exhibited by the NEF  154 ), Npcf  158 D (a service-based interface exhibited by the PCF  148 ), a Nudm  158 E (a service-based interface exhibited by the UDM  146 ), Naf  158 F (a service-based interface exhibited by the AF  150 ), Nnrf  158 C (a service-based interface exhibited by the NRF  156 ), Nnssf  158 A (a service-based interface exhibited by the NSSF  142 ), Nausf  158 G (a service-based interface exhibited by the AUSF  144 ). Other service-based interfaces (e.g., Nudr, N5g-eir, and Nudsf) not shown in  FIG.  1 C  can also be used. 
     NR-V2X architectures may support high-reliability low latency sidelink communications with a variety of traffic patterns, including periodic and aperiodic communications with random packet arrival time and size. Techniques disclosed herein can be used for supporting high reliability in distributed communication systems with dynamic topologies, including sidelink NR V2X communication systems. 
       FIG.  2    illustrates a block diagram of a communication device in accordance with some embodiments. The communication device  200  may be a UE such as a specialized computer, a personal or laptop computer (PC), a tablet PC, or a smart phone, dedicated network equipment such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) that specify actions to be taken by that machine. For example, the communication device  200  may be implemented as one or more of the devices shown in  FIGS.  1 A- 1 C . Note that communications described herein may be encoded before transmission by the transmitting entity (e.g., UE, gNB) for reception by the receiving entity (e.g., gNB, UE) and decoded after reception by the receiving entity. 
     Examples, as described herein, may include, or may operate on, logic or a number of components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a certain manner. In an example, circuits may be arranged (e.g., internally or with respect to external entities such as other circuits) in a specified manner as a module. In an example, the whole or part of one or more computer systems (e.g., a standalone, client or server computer system) or one or more hardware processors may be configured by firmware or software (e.g., instructions, an application portion, or an application) as a module that operates to perform specified operations. In an example, the software may reside on a machine readable medium. In an example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations. 
     Accordingly, the term “module” (and “component”) is understood to encompass a tangible entity, be that an entity that is physically constructed, specifically configured (e.g., hardwired), or temporarily (e.g., transitorily) configured (e.g., programmed) to operate in a specified manner or to perform part or all of any operation described herein. Considering examples in which modules are temporarily configured, each of the modules need not be instantiated at any one moment in time. For example, where the modules comprise a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as respective different modules at different times. Software may accordingly configure a hardware processor, for example, to constitute a particular module at one instance of time and to constitute a different module at a different instance of time. 
     The communication device  200  may include a hardware processor (or equivalently processing circuitry)  202  (e.g., a central processing unit (CPU), a GPU, a hardware processor core, or any combination thereof), a main memory  204  and a static memory  206 , some or all of which may communicate with each other via an interlink (e.g., bus)  208 . The main memory  204  may contain any or all of removable storage and non-removable storage, volatile memory or non-volatile memory. The communication device  200  may further include a display unit  210  such as a video display, an alphanumeric input device  212  (e.g., a keyboard), and a user interface (UI) navigation device  214  (e.g., a mouse). In an example, the display unit  210 , input device  212  and UI navigation device  214  may be a touch screen display. The communication device  200  may additionally include a storage device (e.g., drive unit)  216 , a signal generation device  218  (e.g., a speaker), a network interface device  220 , and one or more sensors, such as a global positioning system (GPS) sensor, compass, accelerometer, or other sensor. The communication device  200  may further include an output controller, such as a serial (e.g., universal serial bus (USB), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (NFC), etc.) connection to communicate or control one or more peripheral devices (e.g., a printer, card reader, etc.). 
     The storage device  216  may include a non-transitory machine readable medium  222  (hereinafter simply referred to as machine readable medium) on which is stored one or more sets of data structures or instructions  224  (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions  224  may also reside, completely or at least partially, within the main memory  204 , within static memory  206 , and/or within the hardware processor  202  during execution thereof by the communication device  200 . While the machine readable medium  222  is illustrated as a single medium, the term “machine readable medium” may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions  224 . 
     The term “machine readable medium” may include any medium that is capable of storing, encoding, or carrying instructions for execution by the communication device  200  and that cause the communication device  200  to perform any one or more of the techniques of the present disclosure, or that is capable of storing, encoding or carrying data structures used by or associated with such instructions. Non-limiting machine readable medium examples may include solid-state memories, and optical and magnetic media. Specific examples of machine readable media may include: non-volatile memory, such as semiconductor memory devices (e.g., Electrically Programmable Read-Only Memory (EPROM), Electrically Erasable Programmable Read-Only Memory (EEPROM)) and flash memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disks: Radio access Memory (RAM); and CD-ROM and DVD-ROM disks. 
     The instructions  224  may further be transmitted or received over a communications network using a transmission medium  226  via the network interface device  220  utilizing any one of a number of wireless local area network (WLAN) transfer protocols (e.g., frame relay, internet protocol (IP), transmission control protocol (TCP), user datagram protocol (UDP), hypertext transfer protocol (HTTP), etc.). Example communication networks may include a local area network (LAN), a wide area network (WAN), a packet data network (e.g., the Internet), mobile telephone networks (e.g., cellular networks), Plain Old Telephone (POTS) networks, and wireless data networks. Communications over the networks may include one or more different protocols, such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 family of standards known as Wi-Fi. IEEE 802.16 family of standards known as WiMax, IEEE 802.15.4 family of standards, a Long Term Evolution (LTE) family of standards, a Universal Mobile Telecommunications System (UMTS) family of standards, peer-to-peer (P2P) networks, a next generation (NG)/5 th  generation (5G) standards among others. In an example, the network interface device  220  may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks) or one or more antennas to connect to the transmission medium  226 . 
     Note that the term “circuitry” as used herein refers to, is part of, or includes hardware components such as an electronic circuit, a logic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an Application Specific Integrated Circuit (ASIC), a field-programmable device (FPD) (e.g., a field-programmable gate array (FPGA), a programmable logic device (PLD), a complex PLD (CPLD), a high-capacity PLD (HCPLD), a structured ASIC, or a programmable SoC), digital signal processors (DSPs), etc., that are configured to provide the described functionality. In some embodiments, the circuitry may execute one or more software or firmware programs to provide at least some of the described functionality. The term “circuitry” may also refer to a combination of one or more hardware elements (or a combination of circuits used in an electrical or electronic system) with the program code used to carry out the functionality of that program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuitry. 
     The term “processor circuitry” or “processor” as used herein thus refers to, is part of, or includes circuitry capable of sequentially and automatically carrying out a sequence of arithmetic or logical operations, or recording, storing, and/or transferring digital data. The term “processor circuitry” or “processor” may refer to one or more application processors, one or more baseband processors, a physical central processing unit (CPU), a single- or multi-core processor, and/or any other device capable of executing or otherwise operating computer-executable instructions, such as program code, software modules, and/or functional processes. 
     There are two types of PCC rules in 5G systems, dynamic rules and predefined rules. The predefined PCC rules are configured into the SMF, and referenced by the PCF, and PCF may activate/deactivate the predefined PCC rules in SMF (see TS 23.501, v.16.5.0). The PCC rule may be predefined or dynamically provisioned at establishment and during the lifetime of a PDU Session. The latter is referred to as a dynamic PCC rule. Provisioning and managing the predefined PCC rules is disclosed herein. Note that the management service producer may be co-located with one of the network entities (e.g., PCF, SMF) or may be separate device from the network entities. 
     The PCF may provide QoS control policy data to the SMF based on the pre-configured 5QIs, therefore the PCF should support the configurable 5QIs, (see TS 23.501 and TS 29.512, v. 16.5.0, 2020-07-10). However, the configurable 5QIs are not supported by PCF in the current NRM (in TS 28.541, v. 16.5.0). 
     The 5QIs could be also dynamically assigned by the network (see 23.501). The dynamic 5QI value and characteristics are assigned by the PCF or SMF (e.g., if the PCF is not deployed), and signaled to other relevant NFs as part of the QoS profile. The dynamic 5QIs should be known by the Operations, Administration and Maintenance (OAM), as the OAM should monitor the network performance related to each 5QI. 
     Among other things, embodiments of the present disclosure provide for predefined PCC rule management, for enabling the PCF to support configurable 5Qis, and for monitoring the dynamic 5QIs. 
     1. To define the following IOC and dataTypes in TS 28.541 for predefined PCC rule management. 
     5.3.a PredefinedPccRuleSet 
     5.3.a.1 Definition 
     This IOC specifies the predefined PCC rules, which are configured to SMF and referenced by PCF, see 3GPP TS 23.503, v. 16.5.0. 
     5.3.a.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 predefinedPccRules 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.a.3 Attribute Constraints 
     None. 
     5.3.a.4 Notifications 
     The common notifications defined in subclause 5.5 are valid for this TOC, without exceptions or additions. 
     5.3.b PccRule &lt;&lt;dataType&gt;&gt; 
     5.3.b.1 Definition 
     This data type specifies the PCC rule, see TS 29.512. 
     5.3.b.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 pccRuleId 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 flowInfoList 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 applicationId 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 contentVersion 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 precedence 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 afSigProtocol 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 isAppRelocatable 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 isUeAddrPreserved 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 qosData 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 trafficControlData 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 conditionData 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.b.3 Attribute Constraints 
     
       
         
           
               
               
             
               
                   
               
               
                 Name 
                 Definition 
               
               
                   
               
             
            
               
                 flowInfoList Support Qualifier 
                 Condition: The applicationId is 
               
               
                   
                 not supported. 
               
               
                 applicationId Support Qualifier 
                 Condition: The flowInfoList is 
               
               
                   
                 not supported. 
               
               
                 precedence Support Qualifier 
                 Condition: The flowInfoList is 
               
               
                   
                 provided. 
               
               
                   
               
            
           
         
       
     
     5.3.b.4 Notifications 
     The subclause 4.5 of the &lt;&lt;IOC&gt;&gt; using this &lt;&lt;dataType&gt;&gt; as one of its attributes, shall be applicable. 
     5.3.c FlowInformation &lt;&lt;dataType&gt;&gt; 
     5.3.c.1 Definition 
     This data type specifies the flow information of a PCC rule. 
     5.3.c.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 flowDescription 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 ethFlowDescription 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 packFilterId 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 packetFilterUsage 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 tosTrafficClass 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 Spi 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 flowLabel 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 flowDirection 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.c.3 Attribute Constraints 
     None 
     5.3.c.4 Notifications 
     The subclause 4.5 of the &lt;&lt;IOC&gt;&gt; using this &lt;&lt;dataType&gt;&gt; as one of its attributes, shall be applicable. 
     5.3.d EthFlowDescription &lt;&lt;dataType&gt;&gt; 
     5.3.d.1 Definition 
     This data type describes an Ethernet flow. 
     5.3.d.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 destMacAddr 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 ethType 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 fDesc 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 fDir 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 sourceMacAddr 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 vlanTags 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 srcMacAddrEnd 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 destMacAddrEnd 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.d.3 Attribute Constraints 
     
       
         
           
               
               
               
             
               
                   
                   
               
               
                   
                 Name 
                 Definition 
               
               
                   
                   
               
             
            
               
                   
                 fDesc Suppers Qualifier 
                 Condition: The ethType is IP. 
               
               
                   
                   
               
            
           
         
       
     
     5.3.d.4 Notifications 
     The subclause 4.5 of the &lt;&lt;IOC&gt;&gt; using this &lt;&lt;dataType&gt;&gt; as one of its attributes, shall be applicable. 
     5.3.e QoSData &lt;&lt;dataType&gt;&gt; 
     5.3.e.1 Definition 
     This data type specifies the QoS control policy data for a service flow of a PCC rule. 
     5.3.e.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 qosId 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 fiveQICharacteristics 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 maxbrUl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 maxbrDl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 gbrUl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 gbrDl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 Arp 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 qosNotificationControl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 reflectiveQos 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 sharingKeyDl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 sharingKeyUl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 maxPacketLossRateDl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 maxPackelLossRateUl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.e.3 Attribute Constraints 
     None. 
     5.3.e.4 Notifications 
     The subclause 4.5 of the &lt;&lt;IOC&gt;&gt; using this &lt;&lt;dataType&gt;&gt; as one of its attributes, shall be applicable. 
     5.3.e ARP &lt;&lt;dataType&gt;&gt; 
     5.3.e.1 Definition 
     This data type specifies the allocation and retention priority of a QoS control policy. 
     5.3.e.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 priorityLevel 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 preemptCap 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 preemptVuln 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.e.3 Attribute Constraints 
     None 
     5.3.e.4 Notifications 
     The subclause 4.5 of the &lt;&lt;IOC&gt;&gt; using this &lt;&lt;dataType&gt;&gt; as one of its attributes, shall be applicable. 
     5.3.f TrafficControlData &lt;&lt;dataType&gt;&gt; 
     5.3.f.1 Definition 
     This data type specifies the traffic control data for a service flow of a PCC rule. 
     5.3.f.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 tcId 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 flowStatus 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 redirectInfo 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 muteNotif 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 trafficSteeringPolIdDl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 trafficSteeringPolIdUl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 routeToLocs 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 upPathChgEvent 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 steerFun 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 steerModeDl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 steerModeUl 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.f.3 Attribute Constraints 
     None 
     5.3.f.4 Notifications 
     The subclause 4.5 of the &lt;&lt;IOC&gt;&gt; using this &lt;&lt;dataType&gt;&gt; as one of its attributes, shall be applicable. 
     5.3.g RedirectInformation &lt;&lt;dataType&gt; 
     5.3.g.1 Definition 
     This data type specifies the redirect information for traffic control in the PCC rule. 
     5.3.g.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 redirectEnabled 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 redirectAddressType 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 redirectServerAddress 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.g.3 Attribute Constraints 
     None 
     5.3.g.4 Notifications 
     The subclause 4.5 of the &lt;&lt;IOC&gt;&gt; using this &lt;&lt;dataType&gt;&gt; as one of its attributes, shall be applicable. 
     5.3.h RouteToLocation &lt;&lt;dataType&gt;&gt; 
     5.3.h.1 Definition 
     This data type specifies a list of location which the traffic shall be routed to for the AF request. 
     5.3.h.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 Dnai 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 routeInfo 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 routeProfId 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.h.3 Attribute Constraints 
     
       
         
           
               
               
             
               
                   
               
               
                 Name 
                 Definition 
               
               
                   
               
             
            
               
                 routeInfo Support Qualifier 
                 Condition: The routeProfId is not 
               
               
                   
                 supported. 
               
               
                 routeProfId Support Qualifier 
                 Condition: The routeInfo is not supported. 
               
               
                   
               
            
           
         
       
     
     5.3.h.4 Notifications 
     The subclause 4.5 of the &lt;&lt;IOC&gt;&gt; using this &lt;dataType&gt;&gt; as one of its attributes, shall be applicable. 
     5.3.i RouteInformation &lt;&lt;dataType&gt;&gt; 
     5.3.i.1 Definition 
     This data type specifies the traffic routing information. 
     5.3.i.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 ipv4Addr 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 ipv6Addr 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 portNumber 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.i.3 Attribute Constraints 
     
       
         
           
               
               
             
               
                   
               
               
                 Name 
                 Definition 
               
               
                   
               
             
            
               
                 ipv4Addr Support Qualifier 
                 Condition: The ipv6Addr is not supported. 
               
               
                 ipv6Addr Support Qualifier 
                 Condition: The ipv4Addr is not supported. 
               
               
                   
               
            
           
         
       
     
     5.3.i.4 Notifications 
     The subclause 4.5 of the &lt;&lt;IOC&gt;&gt; using this &lt;&lt;dataType&gt;&gt; as one of its attributes, shall be applicable. 
     5.3.j UpPathChgEvent &lt;&lt;dataType&gt;&gt; 
     5.3.j.1 Definition 
     This data type specifies the information about the AF subscriptions of the UP path change, see TS 29.512. 
     5.3.j.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 notificationUri 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 notifCorreId 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 dnaiChgType 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 afAckInd 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.j.3 Attribute Constraints 
     None 
     5.3.j.4 Notifications 
     The subclause 4.5 of the &lt;&lt;IOC&gt;&gt; using this &lt;&lt;dataType&gt;&gt; as one of its attributes, shall be applicable. 
     5.3.k SteeringMode &lt;&lt;dataType&gt;&gt; 
     5.3.k.1 Definition 
     This data type specifies the traffic distribution rule, see TS 29.512. 
     5.3.k.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 steerModeValue 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 active 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 standby 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 3gLoad 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 prioAcc 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.k.3 Attribute Constraints 
     
       
         
           
               
               
             
               
                   
               
               
                 Name 
                 Definition 
               
               
                   
               
             
            
               
                 active Support Qualifier 
                 Condition: The steerModeValue supports 
               
               
                   
                 “ACTIVE_STANDBY”. 
               
               
                 threeGLoad Support Qualifier 
                 Condition: The steerModeValue supports 
               
               
                   
                 “LOAD_BALANCING”. 
               
               
                 prioAcc Support Qualifier 
                 Condition: The steerModeValue supports 
               
               
                   
                 “PRIORITY_BASED”. 
               
               
                   
               
            
           
         
       
     
     5.3.k.4 Notifications 
     The subclause 4.5 of the &lt;&lt;IOC&gt;&gt; using this &lt;&lt;dataType&gt;&gt; as one of its attributes, shall be applicable. 
     5.3.1 ConditionData &lt;&lt;dataType&gt;&gt; 
     5.3.1.1 Definition 
     This data type specifies the condition data for a PCC rule. 
     5.3.1.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 condId 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 activationTime 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 deactivationTime 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 accessType 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 ratType 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.1.3 Attribute Constraints 
     None 
     5.3.1.4 Notifications 
     The subclause 4.5 of the &lt;&lt;IOC&gt;&gt; using this &lt;&lt;dataType&gt;&gt; as one of its attributes, shall be applicable. 
       FIG.  3    illustrates a NRM fragment for a predefined PCC rule in accordance with some embodiments. 
       FIG.  4    illustrates an inheritance hierarchy for a predefined PCC rule modeling in accordance with some embodiments. 
     5.4.1 Attribute Properties 
     The following table defines the attributes that are present in several Information Object Classes (IOCs) and data types of the present document. 
     
       
         
           
               
               
               
             
               
                   
               
               
                   
                 Documentation and 
                   
               
               
                 Attribute Name 
                 Allowed Values 
                 Properties 
               
               
                   
               
             
            
               
                 predefinedPccRules 
                 It specifies the predefined PCC Rules, see TS 
                 type: PccRule 
               
               
                   
                 25.503. 
                 multiplicity: 1 . . . * 
               
               
                   
                 allowedValues: N/A 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 pccRuleId 
                 It identifies the PCC rule. 
                 type: String 
               
               
                   
                 allowedValues: N/A 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 flowInfoList 
                 It is a list of IP flow packet filter information. 
                 type: 
               
               
                   
                 allowedValues: N/A 
                 FlowInformation 
               
               
                   
                   
                 multiplicity: * 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 applicationId 
                 A reference to the application detection filter 
                 type: String 
               
               
                   
                 configured at the UPF. 
                 multiplicity: 1 
               
               
                   
                 allowedValues: N/A 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 contentVersion 
                 Indicates the content version of the PCC rule. 
                 type: Integer 
               
               
                   
                 allowedValues: N/A 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 precedence 
                 It indicates the order in which this PCC rule is 
                 type: Integer 
               
               
                   
                 applied relative to other PCC rules within the 
                 multiplicity: 1 
               
               
                   
                 same PDU session. 
                 isOrdered: N/A 
               
               
                   
                 allowedValues: 0 . . . 255. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 afSigProtocol 
                 Indicates the protocol used for signalling between 
                 type: ENUM 
               
               
                   
                 the UE and the AF. The default value is 
                 multiplicity: 1 
               
               
                   
                 “NO_INFORMATION”. 
                 isOrdered: N/A 
               
               
                   
                 allowedValues: “NO_INFORMATION”, “SIP”. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: 
               
               
                   
                   
                 “NO_INFORMATION” 
               
               
                   
                   
                 isNullable: False 
               
               
                 isAppRelocatable 
                 It indicates the application relocation possibility. 
                 type: Boolean 
               
               
                   
                 The default value is “NO_INFORMATION. 
                 multiplicity: 1 
               
               
                   
                 allowedValues: “TRUE”, “FALSE”. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 isUeAddrPreserved 
                 It Indicates whether UE IP address should be 
                 type: Boolean 
               
               
                   
                 preserved. 
                 multiplicity: 1 
               
               
                   
                 The default value is “FALSE”. 
                 isOrdered: N/A 
               
               
                   
                 allowedValues: “TRUE”, “FALSE”. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: 
               
               
                   
                   
                 “FALSE” 
               
               
                   
                   
                 isNullable: False 
               
               
                 qosData 
                 It contains the QoS control policy data for a PCC 
                 type: QoSData 
               
               
                   
                 rule. 
                 multiplicity: 1 
               
               
                   
                 allowedValues: N/A 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 trafficControlData 
                 It contains the traffic control policy data for a 
                 type: 
               
               
                   
                 PCC rule. 
                 TrafficControlData 
               
               
                   
                 allowedValues: N/A 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 conditionData 
                 It contains the condition data for a PCC rule. 
                 type: 
               
               
                   
                 allowedValues: N/A 
                 ConditionData 
               
               
                   
                   
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 flowDescription 
                 It defines a packet filter for an IP flow. 
                 type: String 
               
               
                   
                 allowedValues: see TS 29.214. 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 ethFlowDescription 
                 It defines a packet filter for an Ethernet flow. 
                 type: 
               
               
                   
                 allowedValues: see TS 29.514. 
                 EthFlowDescription 
               
               
                   
                   
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 destMacAddr 
                 It specifies the destination MAC address 
                 type: String 
               
               
                   
                 formatted in the hexadecimal notation according 
                 multiplicity: 1 
               
               
                   
                 to clause 1.1 and clause 2.1 of IETF RFC 7042. 
                 isOrdered: N/A 
               
               
                   
                 Pattern: ‘{circumflex over ( )}([0-9a-fA-F]{2})((-[0-9a-fA- 
                 isUnique: N/A 
               
               
                   
                 F]{2}){5})$’. 
                 defaultValue: None 
               
               
                   
                 allowedValues: N/A. 
                 isNullable: False 
               
               
                 ethType 
                 A two-octet string that represents the Ethertype, 
                 type: String 
               
               
                   
                 as described in IEEE 802.3 and IETF RFC 7042 
                 multiplicity: 1 
               
               
                   
                 in hexadecimal representation. 
                 isOrdered: N/A 
               
               
                   
                 Each character in the string shall take a value of 
                 isUnique: N/A 
               
               
                   
                 “0” to “9” or “A” to “F” and shall represent 4 bits. 
                 defaultValue: None 
               
               
                   
                 The most significant character representing the 4 
                 isNullable: False 
               
               
                   
                 most significant bits of the ethType shall appear 
               
               
                   
                 first in the string, and the character representing 
               
               
                   
                 the 4 least significant bits of the ethType shall 
               
               
                   
                 appear last in the string. 
               
               
                   
                 allowedValues: see IEEE 802.3 and 
               
               
                   
                 IETF RFC 7042. 
               
               
                 fDesc 
                 It contains the flow description for the Uplink or 
                 type: String 
               
               
                   
                 Downlink IP flow. It shall be present when the 
                 multiplicity: 1 
               
               
                   
                 ethtype is IP. 
                 isOrdered: N/A 
               
               
                   
                 allowedValues: see flowDescription in 
                 isUnique: N/A 
               
               
                   
                 TS 29.214. 
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 fDir 
                 It indicates the packet filter direction. 
                 type: ENUM 
               
               
                   
                 allowedValues: “DOWNLINK”, “UPLINK”. 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 sourceMacAddr 
                 It specifies the source MAC address formatted in 
                 type: String 
               
               
                   
                 the hexadecimal notation according to clause 1.1 
                 multiplicity: 1 
               
               
                   
                 and clause 2.1 of IETF RFC 7042. 
                 isOrdered: N/A 
               
               
                   
                 Pattern: ‘{circumflex over ( )}([0-9a-fA-F]{2})((-[0-9a-fA- 
                 isUnique: N/A 
               
               
                   
                 F]{2}){5})$’. 
                 defaultValue: None 
               
               
                   
                 allowedValues: N/A. 
                 isNullable: False 
               
               
                 vlanTags 
                 It specifies the Customer-VLAN and/or Service- 
                 type: String 
               
               
                   
                 VLAN tags containing the VID, PCP/DEI fields 
                 multiplicity: * 
               
               
                   
                 as defined in IEEE 802.1Q and IETF RFC 7042. 
                 isOrdered: N/A 
               
               
                   
                 The first/lower instance in the array stands for the 
                 isUnique: N/A 
               
               
                   
                 Customer-VLAN tag and the second/higher 
                 defaultVaiue: None 
               
               
                   
                 instance in the array stands for the Service- 
                 isNullable: False 
               
               
                   
                 VLAN tag. 
               
               
                   
                 Each field is encoded as a two-octet string in 
               
               
                   
                 hexadecimal representation. Each character in the 
               
               
                   
                 string shall take a value of “0” to “9” or “A” to 
               
               
                   
                 “F” and shall represent 4 bits. The most 
               
               
                   
                 significant character representing the PCP/DEI 
               
               
                   
                 field shall appear first in the string, followed by 
               
               
                   
                 character representing the 4 most significant bits 
               
               
                   
                 of the VID field, and the character representing 
               
               
                   
                 the 4 least significant bits of the VID field shall 
               
               
                   
                 appear last in the string. 
               
               
                   
                 If only Service-VLAN tag is provided, empty 
               
               
                   
                 string for Customer-VLAN tag shall be provided. 
               
               
                   
                 allowedValues: see IEEE 802.1Q and 
               
               
                   
                 IETF RFC 7042. 
               
               
                 srcMacAddrEnd 
                 It specifies the source MAC address end. If this 
                 type: String 
               
               
                   
                 attribute is present, the sourceMacAddr attribute 
                 multiplicity: 1 
               
               
                   
                 specifies the source MAC address start. E.g. 
                 isOrdered: N/A 
               
               
                   
                 srcMacAddrEnd with value 00-10-A4-23-3E-FE 
                 isUnique: N/A 
               
               
                   
                 and sourceMacAddr with value 00-10-A4-23-3E- 
                 defaultValue: None 
               
               
                   
                 02 means all MAC addresses from 00-10-A4-23- 
                 isNullable: True 
               
               
                   
                 3E-02 up to and including 00-10-A4-23-3E-FE. 
               
               
                   
                 allowedValues: N/A. 
               
               
                 destMacAddrEnd 
                 It specifies the destination MAC address end. If 
                 type: String 
               
               
                   
                 this attribute is present, the destMacAddr 
                 multiplicity: 1 
               
               
                   
                 attribute specifies the destination MAC address 
                 isOrdered: N/A 
               
               
                   
                 start. 
                 isUnique: N/A 
               
               
                   
                 allowedValues: N/A. 
                 defaultValue: None 
               
               
                   
                   
                 isNullable: True 
               
               
                 packFilterId 
                 It is the identifier of the packet filter. 
                 type: String 
               
               
                   
                 allowedValues: N/A. 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 packetFilterUsage 
                 It indicates if the packet shall be sent to the UE. 
                 type: Boolean 
               
               
                   
                 The default value is “FALSE”. 
                 multiplicity: 1 
               
               
                   
                 allowedValues: TRUE, FALSE 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: 
               
               
                   
                   
                 “FALSE” 
               
               
                   
                   
                 isNullable: False 
               
               
                 tosTrafficClass 
                 It contains the Ipv4 Type-of-Service and mask 
                 type: String 
               
               
                   
                 field or the Ipv6 Traffic-Class field and mask 
                 multiplicity: 1 
               
               
                   
                 field. 
                 isOrdered: N/A 
               
               
                   
                 allowedValues: N/A 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 spi 
                 It is the security parameter index of the IPSec 
                 type: String 
               
               
                   
                 packet, see IETF RFC 4301. 
                 multiplicity: 1 
               
               
                   
                 allowedValues: see IETF RFC 4301. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: True 
               
               
                 flowLabel 
                 It specifies the Ipv6 flow label header field. 
                 type: String 
               
               
                   
                 AllowedValues: N/A 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: True 
               
               
                 flowDirection 
                 It indicates the direction/directions that a filter is 
                 type: ENUM 
               
               
                   
                 applicable. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: “DOWNLINK”, “UPLINK”, 
                 isOrdered: N/A 
               
               
                   
                 “BIDIRECTIONAL”, “UNSPECIFIED”. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: True 
               
               
                 qosId 
                 It identifies the QoS control policy data for a 
                 type: String 
               
               
                   
                 PCC rule. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: N/A 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 fiveQICharacteristics 
                 It specifies the 5QI value and the cooresponding 
                 type: 
               
               
                   
                 QoS characteristics for a 5QI. 
                 FiveQICharacteristics 
               
               
                   
                 AllowedValues: N/A 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 maxbrUl 
                 It represents the maximum uplink bandwidth 
                 type: String 
               
               
                   
                 formatted as follows: 
                 multiplicity: 1 
               
               
                   
                 Pattern: ‘{circumflex over ( )}\d+(\.\d+)? 
                 isOrdered: N/A 
               
               
                   
                 (bps|KbpsMbps|Gbps|Tbps)$’, see TS 29.512. 
                 isUnique: N/A 
               
               
                   
                 Examples: 
                 defaultValue: None 
               
               
                   
                 “125 Mbps”, “0.125 Gbps”, “125000 Kbps” 
                 isNullable: True 
               
               
                   
                 AllowedValues: N/A 
               
               
                 maxbrDl 
                 It represents the maximum downlink bandwidth 
                 type: String 
               
               
                   
                 formatted as follows: 
                 multiplicity: 1 
               
               
                   
                 Pattern: ‘{circumflex over ( )}\d+(\.\d+)? 
                 isOrdered: N/A 
               
               
                   
                 (bps|Kbps|Mbps|Gbps|Tbps)$’, see TS 29.512. 
                 isUnique: N/A 
               
               
                   
                 Examples: 
                 defaultValue: None 
               
               
                   
                 “125 Mbps”, “0.125 Gbps”, “125000 Kbps”. 
                 isNullable: True 
               
               
                   
                 AllowedValues: N/A. 
               
               
                 gbrUl 
                 It represents the guaranteed uplink bandwidth 
                 type: String 
               
               
                   
                 formatted as follows: 
                 multiplicity: 1 
               
               
                   
                 Pattern: ‘{circumflex over ( )}\d+(\.\d+)? 
                 isOrdered: N/A 
               
               
                   
                 (bps|Kbps|Mbps|Gbps|Tbps)$’, see TS 29.512. 
                 isUnique: N/A 
               
               
                   
                 Examples: 
                 defaultValue: None 
               
               
                   
                 “125 Mbps”, “0.125 Gbps”, “12.5000 Kbps”. 
                 isNullable: True 
               
               
                   
                 AllowedValues: N/A. 
               
               
                 gbrDl 
                 It represents the guaranteed downlink bandwidth 
                 type: String 
               
               
                   
                 formatted as follows: 
                 multiplicity: 1 
               
               
                   
                 Pattern: ‘{circumflex over ( )}\d+(\.\d+)? 
                 isOrdered: N/A 
               
               
                   
                 (bps|Kbps|Mbps|Gbps|Tbps)$’, see TS 29.512. 
                 isUnique: N/A 
               
               
                   
                 Examples: 
                 defaultValue: None 
               
               
                   
                 “125 Mbps”, “0.125 Gbps”, “125000 Kbps”. 
                 isNullable: True 
               
               
                   
                 AllowedValues: N/A. 
               
               
                 arp 
                 It indicates the allocation and retention priority. 
                 type: ARP 
               
               
                   
                 AllowedValues: N/A. 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 priorityLevel 
                 It defines the relative importance of a resource 
                 type: Integer 
               
               
                   
                 request. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: 1 . . . 15. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 preemptCap 
                 It defines whether a service data flow may get 
                 type: ENUM 
               
               
                   
                 resources that were already assigned to another 
                 multiplicity: 1 
               
               
                   
                 service data flow with a lower priority level. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: “NOT_PREEMPT”, 
                 isUnique: N/A 
               
               
                   
                 “MAY_PREEMPT”. 
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 preemptVuln 
                 It defines whether a service data flow may lose 
                 type: ENUM 
               
               
                   
                 the resources assigned to it in order to admit a 
                 multiplicity: 1 
               
               
                   
                 service data flow with higher priority level. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: “NOT_PREEMPTABLE”, 
                 isUnique: N/A 
               
               
                   
                 “PREEMPTABLE”. 
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 qosNotificationControl 
                 It indicates whether notifications are requested 
                 type: Boolean 
               
               
                   
                 from 3GPP NG-RAN when the GFBR can no 
                 multiplicity: 1 
               
               
                   
                 longer (or again) be guaranteed for a QoS Flow 
                 isOrdered: N/A 
               
               
                   
                 during the lifetime of the QoS Flow. The default 
                 isUnique: N/A 
               
               
                   
                 value is “FALSE”. 
                 defaultValue: 
               
               
                   
                 AllowedValues: “TRUE”, “FALSE”. 
                 “FALSE” 
               
               
                   
                   
                 isNullable: False 
               
               
                 reflectiveQos 
                 Indicates whether the QoS information is 
                 type: Boolean 
               
               
                   
                 reflective for the corresponding non-GBR service 
                 multiplicity: 1 
               
               
                   
                 data flow. The default value is “FALSE”. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: “TRUE”, “FALSE”. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: 
               
               
                   
                   
                 “FALSE” 
               
               
                   
                   
                 IsNullable: False 
               
               
                 sharingKeyDl 
                 It indicates, by containing the same value, what 
                 type: String 
               
               
                   
                 PCC rules may share resource in downlink 
                 multiplicity: 1 
               
               
                   
                 direction. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: N/A. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: True 
               
               
                 sharingKeyUl 
                 It indicates, by containing the same value, what 
                 type: String 
               
               
                   
                 PCC rules may share resource in uplink direction. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: N/A. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: True 
               
               
                 maxPacketLossRateDl 
                 It indicates the downlink maximum rate for lost 
                 type: Integer 
               
               
                   
                 packets that can be tolerated for the service data 
                 multiplicity: 1 
               
               
                   
                 flow. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: 0 . . . 1000. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: True 
               
               
                 maxPacketLossRateUl 
                 It indicates the uplink maximum rate for lost 
                 type: Integer 
               
               
                   
                 packets that can be tolerated for the service data 
                 multiplicity: 1 
               
               
                   
                 flow. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: 0 . . . 1000. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: True 
               
               
                 tcId 
                 It univocally identifies the traffic control policy 
                 type: String 
               
               
                   
                 data within a PDU session. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: N/A. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 flowStatus 
                 It represents whether the service data flow(s) are 
                 type: ENUM 
               
               
                   
                 enabled or disabled. The default value is 
                 multiplicity: 1 
               
               
                   
                 “ENABLED”. See TS 29.514. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: “ENABLED-UPLINK”, 
                 isUnique: N/A 
               
               
                   
                 “ENABLED-DOWNLINK”, “ENABLED”, 
                 defaultValue: 
               
               
                   
                 “DISABLED”, “REMOVED”. 
                 “ENABLED” 
               
               
                   
                   
                 isNullable: False 
               
               
                 redirectInfo 
                 It indicates whether the detected application 
                 type: 
               
               
                   
                 traffic should be redirected to another controlled 
                 RedirectInformation 
               
               
                   
                 address. 
                 multiplicity: 1 . . . * 
               
               
                   
                 AllowedValues: N/A. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: 
               
               
                   
                   
                 “ENABLED” 
               
               
                   
                   
                 isNullable: False 
               
               
                 redirectEnabled 
                 It indicates whether the redirect instruction is 
                 type: Boolean 
               
               
                   
                 enabled. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: “TRUE”, “FALSE”. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 redirectAddressType 
                 It indicates the type of redirect address, see TS 
                 type: ENUM 
               
               
                   
                 29.512. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: “IPV4_ADDR”, 
                 isOrdered: N/A 
               
               
                   
                 “IPV6_ADDR”, “URL”, “SIP_URI”. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 redirectServerAddress 
                 It indicates the address of the redirect server. 
                 type: String 
               
               
                   
                 AllowedValues: N/A. 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 muteNotif 
                 It indicates whether applicat’on&#39;s start or stop 
                 type: Boolean 
               
               
                   
                 notification is to be muted. The default value is 
                 multiplicity: 1 
               
               
                   
                 “FALSE”. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: “TRUE”, “FALSE”. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: 
               
               
                   
                   
                 “FALSE” 
               
               
                   
                   
                 isNullable: False 
               
               
                 trafficSteeringPolIdDl 
                 It references to a pre-configured traffic steering 
                 type: String 
               
               
                   
                 policy for downlink traffic at the SMF, see TS 
                 multiplicity: 1 
               
               
                   
                 29.512. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: N/A. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 trafficSteeringPolIdUl 
                 It references to a pre-configured traffic steering 
                 type: String 
               
               
                   
                 policy for uplink traffic at the SMF, see TS 
                 multiplicity: 1 
               
               
                   
                 29.512. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: N/A. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 routeToLocs 
                 It provides a list of location which the traffic shall 
                 type: 
               
               
                   
                 be routed to for the AF request. 
                 RouteToLocation 
               
               
                   
                 AllowedValues: N/A. 
                 multiplicity: 1 . . . * 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 dnai 
                 It represents the DNAI (Data network access 
                 type: String 
               
               
                   
                 identifier), see 3GPP TS 23.501. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: N/A. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 routeInfo 
                 It provides the traffic routing information. 
                 type: 
               
               
                   
                 AllowedValues: N/A. 
                 RouteInformation 
               
               
                   
                   
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 ipv4Addr 
                 It defines the Ipv4 address of the tunnel end point 
                 type: String 
               
               
                   
                 in the data network, formatted in the “dotted 
                 multiplicity: 1 
               
               
                   
                 decimal” notation. 
                 isOrdered: N/A 
               
               
                   
                 Pattens: ‘{circumflex over ( )}(([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0-4][0- 
                 isUnique: N/A 
               
               
                   
                 9]|25[0-5])\.){3}([0-9]|[1-9][0-9]|1[0-9][0-9]|2[0- 
                 defaultValue: None 
               
               
                   
                 4][0-9]|25[0-5])$’. 
                 isNullable: False 
               
               
                   
                 AllowedValues: N/A. 
               
               
                 ipv6Addr 
                 It defines the Ipv6 address of the tunnel end point 
                 type: String 
               
               
                   
                 in the data network. 
                 multiplicity: 1 
               
               
                   
                 Pattern: ‘{circumflex over ( )}((:|(0?|([1-9a-f][0-9a- 
                 isOrdered: N/A 
               
               
                   
                 f]{0,3}))):)((0?|([1-9a-f][0-9a- 
                 isUnique: N/A 
               
               
                   
                 f]{0,3})):){0,6}(:|(0?|([1-9a-f][0-9a-f]{0,3})))$’ 
                 defaultValue: None 
               
               
                   
                 and 
                 isNullable: False 
               
               
                   
                 Pattern: 
               
               
                   
                 ‘{circumflex over ( )}((([{circumflex over ( )}:]+:){7}([{circumflex over ( )}:]+))|((([{circumflex over ( )}:]+:)*[{circumflex over ( )}:]+)?::(([{circumflex over ( )}:]+:)* 
               
               
                   
                 [{circumflex over ( )}:]+)?))$’. 
               
               
                   
                 AllowedValues: N/A. 
               
               
                 portNumber 
                 It defines the UDP port number of the tunnel end 
                 type: Integer 
               
               
                   
                 point in the data network, see TS 29.571. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: N/A. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 routeProfId 
                 It identifies the routing profile. 
                 type: String 
               
               
                   
                 AllowedValues: N/A. 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 upPathChgEvent 
                 It contains the information about the AF 
                 type: 
               
               
                   
                 subscriptions of the UP path change. 
                 UpPathChgEvent 
               
               
                   
                 AllowedValues: N/A. 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 notificationUri 
                 It provides notification address (Uri) of AF 
                 type: String 
               
               
                   
                 receiving the event notification. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: N/A. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 notifCorreId 
                 It is used to set the value of Notification 
                 type: String 
               
               
                   
                 Correlation ID in the notification sent by the 
                 multiplicity: 1 
               
               
                   
                 SMF, see TS 29.512. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: N/A. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 dnaiChgType 
                 Indicates the type of DNAI change, see TS 
                 type: ENUM 
               
               
                   
                 29.512. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: “EARLY”, “EARLY_LATE”, 
                 isOrdered: N/A 
               
               
                   
                 “LATE”. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 afAckInd 
                 It identifies whether the AF acknowledgement of 
                 type: Boolean 
               
               
                   
                 UP path event notification is expected. The 
                 multiplicity: 1 
               
               
                   
                 default value is “FALSE”. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: “TRUE”, “FALSE”. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: 
               
               
                   
                   
                 “FALSE” 
               
               
                   
                   
                 isNullable: False 
               
               
                 steerFun 
                 It indicates the applicable traffic steering 
                 type: ENUM 
               
               
                   
                 functionality, see TS 29.512. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: “MPTCP”, “ATSSS_LL”. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 steerModeDl 
                 It provides the traffic distribution rule across 
                 type: SteeringMode 
               
               
                   
                 3GPP and Non-3GPP accesses to apply for 
                 multiplicity: 1 
               
               
                   
                 downlink traffic. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: N/A. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 steerModeUl 
                 It provides the traffic distribution rule across 
                 type: SteeringMode 
               
               
                   
                 3GPP and Non-3GPP accesses to apply for 
                 multiplicity: 1 
               
               
                   
                 uplink traffic. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: N/A. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 steerModeValue 
                 It indicates the value of the steering mode, see TS 
                 type: ENUM 
               
               
                   
                 29.512. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: “ACTIVE_STANDBY”, 
                 isOrdered: N/A 
               
               
                   
                 “LOAD_BALANCING”, 
                 isUnique: N/A 
               
               
                   
                 “SMALLEST_DELAY”, “PRIORITY_BASED”. 
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 active 
                 It indicates the active access, see TS 29.571. 
                 type: ENUM 
               
               
                   
                 AllowedValues: “3GPP_ACCESS”, 
                 multiplicity: 1 
               
               
                   
                 “NON_3GPP_ACCESS”. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 standby 
                 It indicates the Standby access, see TS 29.571. 
                 type: ENUM 
               
               
                   
                 AllowedValues: “3GPP_ACCESS”, 
                 multiplicity: 1 
               
               
                   
                 “NON_3GPP_ACCESS”. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 threeGLoad 
                 It indicates the traffic load to steer to the 3GPP 
                 type: Integer 
               
               
                   
                 Access expressed its one percent. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: 0 . . . 100. 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 prioAcc 
                 It indicates the high priority access, see TS 
                 type: ENUM 
               
               
                   
                 29.571. 
                 multiplicity: 1 
               
               
                   
                 AllowedValues: “3GPP_ACCESS”, 
                 isOrdered: N/A 
               
               
                   
                 “NON_3GPP_ACCESS”. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 condId 
                 It uniquely identifies the condition data. 
                 type: String 
               
               
                   
                 AllowedValues: N/A. 
                 multiplicity: 1 
               
               
                   
                   
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 activationTime 
                 It indicates the time (in date-time format) when 
                 type: String 
               
               
                   
                 the decision data shall be activated, see TS 
                 multiplicity: 1 
               
               
                   
                 29.512. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: N/A. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 deactivationTime 
                 It indicates the time (in date-time format) when 
                 type: String 
               
               
                   
                 the decision data shall be deactivated, see TS 
                 multiplicity: 1 
               
               
                   
                 29.512 and TS 29.571. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: N/A. 
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 accessType 
                 It provides the condition of access type of the UE 
                 type: ENUM 
               
               
                   
                 when the session AMBR shall be enforced, see 
                 multiplicity: 1 
               
               
                   
                 TS 29.512. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: “3GPP_ACCESS”, 
                 isUnique: N/A 
               
               
                   
                 “NON_3GPP_ACCESS”. 
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                 ratType 
                 It provides the condition of RAT type of the UE 
                 type: ENUM 
               
               
                   
                 when the session AMBR shall be enforced, see 
                 multiplicity: 1 
               
               
                   
                 TS 29.512 and TS 29.571. 
                 isOrdered: N/A 
               
               
                   
                 AllowedValues: “NR”, “EUTRA”, “WLAN”, 
                 isUnique: N/A 
               
               
                   
                 “VIRTUAL”, “NBIOT”, “WIRELINE”, 
                 defaultValue: None 
               
               
                   
                 “WIRELINE_CABLE”, “WIRELINE_BBF”, 
                 isNullable: False 
               
               
                   
                 “LTE-M”, “NR_U”, “EUTRA_U”, 
               
               
                   
                 “TRUSTED_N3GA”, “TRUSTED_WLAN”, 
               
               
                   
                 “UTRA”, “GERA”. 
               
               
                   
               
            
           
         
       
     
     To add association relation (by configurable5QISetRef attribute) between PCFFunction IOC and Configurable5QISet IO in TS 28.541 for enabling the PCF to support configurable 5QIs. 
     5.3.5 PCFFunction 
     5.3.5.1 Definition 
     This IOC represents the PCF function in the 5GC. For more information about the PCF, see 3GPP TS 23.501. 
     5.3.5.2 Attributes 
     The PCFFunction IOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622) and the following attributes: 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 pLMNIdList 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 sBIFQDN 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 sNSSAIList 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 managedNFProfile 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 commModelList 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 supportedBMOList 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 Attribute related to role 
               
               
                 configurable5QISetRef 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.5.3 Attribute Constraints 
     
       
         
           
               
               
             
               
                   
               
               
                 Name 
                 Definition 
               
               
                   
               
             
            
               
                 sNSSAIList Support Qualifier 
                 Condition: network slicing feature 
               
               
                   
                 is supported. 
               
               
                   
               
            
           
         
       
     
     5.3.5.4 Notifications 
     The common notifications defined in subclause 5.5 are valid for this IOC, without exceptions or additions. 
       FIG.  5    illustrates a NRM fragment for configurable 5Qis in the 5GC in accordance with some embodiments. 
     3. To define the following IOC, dataTypes or attributes in TS 28.541 for dynamic 5QI monitoring. 
     4.3.2 GNBCUCPFunction 
     4.3.2.1 Definition 
     For non-split NG-RAN deployment scenario, this IOC together with GNBCUUPFunction IOC and GNBDUFunction IOC provide the management representation of gNB defined in clause 6.1.1 in 3GPP TS 38.401. 
     For 2-split NG-RAN deployment scenario, this IOC together with GNBCUUPFunction TOC provide management representation of the gNB-CU defined in clause 6.1.1 in 3GPP TS 38.401. 
     For 3-split NG-RAN deployment scenario, this IOC provides management representation of gNB-CU-CP defined in clause 6.1.2 in 3GPP TS 38.401. 
     The following table identifies the end points for the representation of gNB and en-gNB, of all deployment scenarios. 
     
       
         
           
               
               
               
               
             
               
                   
               
               
                   
                   
                   
                 End point for Non- 
               
               
                 Req 
                 End point for 3-split 
                 End point for 2-split 
                 split deployment 
               
               
                 Role 
                 deployment scenario 
                 deployment scenario 
                 scenario 
               
               
                   
               
             
            
               
                 gNB 
                 &lt;&lt;IOC&gt;&gt;EP_XnC, 
                 &lt;&lt;IOC&gt;&gt;EP_XnC, 
                 &lt;&lt;IOC&gt;&gt;EP_XnC, 
               
               
                   
                 &lt;&lt;IOC&gt;&gt;EP_NgC, 
                 &lt;&lt;IOC&gt;&gt;EP_NgC, 
                 &lt;&lt;IOC&gt;&gt;EP_NgC. 
               
               
                   
                 &lt;&lt;IOC&gt;&gt;EP_F1C, 
                 &lt;&lt;IOC&gt;&gt;EP_F1C 
               
               
                   
                 &lt;&lt;IOC&gt;&gt;EP_E1. 
                 &lt;&lt;IOC&gt;&gt;EP_F1U. 
               
               
                 en- 
                 &lt;&lt;IOC&gt;&gt;EP_X2C, 
                 &lt;&lt;IOC&gt;&gt;EP_X2C, 
                 &lt;&lt;IOC&gt;&gt;EP_X2C. 
               
               
                 gNB 
                 &lt;&lt;IOC&gt;&gt;EP_F1C, 
                 &lt;&lt;IOC&gt;&gt;EP_F1C. 
               
               
                   
                 &lt;&lt;IOC&gt;&gt;EP_E1. 
               
               
                   
               
            
           
         
       
     
     4.3.2.2 Attributes 
     The GNBCUCPFunction TOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622) and the following attributes: 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 gNBId 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 gNBIdLength 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 gNBCUName 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 pLMNId 
                 M 
                 T 
                 T 
                 T 
                 T 
               
               
                 x2BlackList 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 x2WhiteList 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 xnBlackList 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 xnWhiteList 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 x2XnHOBlackList 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 mappingSetIDBackhaulAddressList 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 Attribute related to role 
               
               
                 configurable5QISetRef 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 dynamic5QISetRef 
                 O 
                 T 
                 F 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     4.3.2.3 Attribute Constraints 
     
       
         
           
               
               
             
               
                   
               
               
                 Name 
                 Definition 
               
               
                   
               
             
            
               
                 x2BlackList 
                 Condition: Multi-Radio Dual 
               
               
                   
                 Connectivity with the EPC 
               
               
                   
                 (see TS 37.340 clause 4.1.2) 
               
               
                   
                 is supported. 
               
               
                 x2WhiteList 
                 Condition: Multi-Radio Dual 
               
               
                   
                 Connectivity with the EPC 
               
               
                   
                 (see TS 37.340 clause 4.1.2) 
               
               
                   
                 is supported. 
               
               
                 mappingSetIDBackhaulAddressList 
                 Condition: Remote Interference 
               
               
                   
                 Management function is supported. 
               
               
                   
               
            
           
         
       
     
     4.3.2.4 Notifications 
     The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions. 
     4.3.3 GNBCUUPFunction 
     4.3.3.1 Definition 
     For non-split NG-RAN deployment scenario, this IOC together with GNBCUCPFunction IOC and GNBDUFunction IOC provide the management representation of gNB defined in clause 6.1.1 in 3GPP TS 38.401. 
     For 2-split NG-RAN deployment scenario, this IOC together with GNBCUCPFunction IOC provide management representation of gNB-CU defined in clause 6.1.1 in 3GPP TS 38.401. 
     For 3-split NG-RAN deployment scenario, this TOC provides management representation of gNB-CU-UP defined in clause 6.1.2 in 3GPP TS 38.401. 
     The following table identifies the end points for the representation of gNB and en-gNB, of all deployment scenarios. 
     
       
         
           
               
               
               
               
             
               
                   
               
               
                   
                   
                   
                 End point for Non- 
               
               
                 Req 
                 End point for 3-split 
                 End point for 2-split 
                 split deployment 
               
               
                 Role 
                 deployment scenario 
                 deployment scenario 
                 scenario 
               
               
                   
               
             
            
               
                 gNB 
                 &lt;&lt;IOC&gt;&gt;EP_XnU, 
                 &lt;&lt;IOC&gt;&gt;EP_XnU, 
                 &lt;&lt;IOC&gt;&gt;EP_XnU, 
               
               
                   
                 &lt;&lt;IOC&gt;&gt;EP_NgU, 
                 &lt;&lt;IOC&gt;&gt;EP_NgU, 
                 &lt;&lt;IOC&gt;&gt;EP_NgU. 
               
               
                   
                 &lt;&lt;IOC&gt;&gt;EP_F1U, 
                 &lt;&lt;IOC&gt;&gt;EP_F1U. 
               
               
                   
                 &lt;&lt;IOC&gt;&gt;EP_E1. 
               
               
                 en- 
                 &lt;&lt;IOC&gt;&gt;EP_X2U, 
                 &lt;&lt;IOC&gt;&gt;EP_X2U, 
                 &lt;&lt;IOC&gt;&gt;EP_X2U, 
               
               
                 gNB 
                 &lt;&lt;IOC&gt;&gt;EP_S1U, 
                 &lt;&lt;IOC&gt;&gt;EP_S1U, 
                 &lt;&lt;IOC&gt;&gt;EP_S1U. 
               
               
                   
                 &lt;&lt;IOC&gt;&gt;EP_F1U, 
                 &lt;&lt;IOC&gt;&gt;EP_F1U. 
               
               
                   
                 &lt;&lt;IOC&gt;&gt;EP_E1. 
               
               
                   
               
            
           
         
       
     
     4.3.3.2 Attributes 
     The GNBCUUPFunction IOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622) and the following attributes: 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 gNBCUUPId 
                 M 
                 T 
                 F 
                 T 
                 T 
               
               
                 pLMNInfoList 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 gNBId 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 gNBIdLength 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 Attribute related to role 
               
               
                 configurable5QISetRef 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 dynamic5QISetRef 
                 O 
                 T 
                 F 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     4.3.3.3 Attribute Constraints 
     None. 
     4.3.3.4 Notifications 
     The common notifications defined in subclause 4.5 are valid for this IOC, without exceptions or additions. 
       FIG.  6    illustrates a NRM fragment for dynamic 5QIs in a NG-RAN in accordance with some embodiments. 
     5.3.2 SMFFunction 
     5.3.2.1 Definition 
     This IOC represents the SMF function in the 5GC. For more information about the SMF, see 3GPP TS 23.501. 
     5.3.2.2 Attributes 
     The SMFFunction IOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622) and the following attributes: 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 pLMNIdList 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 nRTAClist 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 sBIFQDN 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 sNSSAIList 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 managedNFProfile 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 commModelList 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 Attribute related to role 
               
               
                 configurable5QISetRef 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 dynamic5QISetRef 
                 O 
                 T 
                 F 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.2.3 Attribute Constraints 
     
       
         
           
               
               
             
               
                   
               
               
                 Name 
                 Definition 
               
               
                   
               
             
            
               
                 sNSSAIList Support Qualifier 
                 Condition: Network slicing feature 
               
               
                   
                 is supported. 
               
               
                   
               
            
           
         
       
     
     5.3.2.4 Notifications 
     The common notifications defined in subclause 5.5 are valid for this IOC, without exceptions or additions. 
     5.3.5 PCFFunction 
     5.3.5.1 Definition 
     This IOC represents the PCF function in the 5GC. For more information about the PCF, see 3GPP TS 23.501. 
     5.3.5.2 Attributes 
     The PCFFunction IOC includes attributes inherited from ManagedFunction IOC (defined in TS 28.622) and the follow % ing attributes: 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 pLMNIdList 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 sBIFQDN 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 sNSSAIList 
                 CM 
                 T 
                 T 
                 F 
                 T 
               
               
                 managedNFProfile 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 commModelList 
                 M 
                 T 
                 T 
                 F 
                 T 
               
               
                 supportedBMOList 
                 O 
                 T 
                 T 
                 F 
                 T 
               
               
                 Attribute related to role 
               
               
                 dynamic5QISetRef 
                 O 
                 T 
                 F 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.5.3 Attribute Constraints 
     
       
         
           
               
               
             
               
                   
               
               
                 Name 
                 Definition 
               
               
                   
               
             
            
               
                 sNSSAIList Support Qualifier 
                 Condition: network slicing feature 
               
               
                   
                 is supported. 
               
               
                   
               
            
           
         
       
     
     5.3.5.4 Notifications 
     The common notifications defined in subclause 5.5 are valid for this IOC, without exceptions or additions. 
     5.3.x Dynamic5QISet 
     5.3.x.1 Definition 
     This IOC specifies the dynamic 5QIs including their QoS characteristics, see 3GPP TS 23.501. The instance of this IOC shall not be created or modified by the MnS consumer. 
     5.3.x.2 Attributes 
     
       
         
           
               
               
               
               
               
               
             
               
                   
               
               
                 Attribute name 
                 Support Qualifier 
                 isReadable 
                 isWritable 
                 isInvariant 
                 isNotifyable 
               
               
                   
               
             
            
               
                 dynamic5QIs 
                 M 
                 T 
                 F 
                 F 
                 T 
               
               
                   
               
            
           
         
       
     
     5.3.x.3 Attribute Constraints 
     None. 
     5.3.x.4 Notifications 
     The common notifications defined in subclause 5.5 are valid for this TOC, without exceptions or additions. 
       FIG.  7    illustrates a NRM fragment for dynamic 5Qis in the 5GC in accordance with some embodiments. 
       FIG.  8    illustrates an inheritance hierarchy for IOC Dynamic5QISet in accordance with some embodiments. 
     5.x.y Attribute Properties 
     The following table defines the attributes that are present in several Information Object Classes (IOCs) and data types of the present document. 
     
       
         
           
               
               
               
             
               
                   
               
               
                   
                 Documentation and 
                   
               
               
                 Attribute Name 
                 Allowed Values 
                 Properties 
               
               
                   
               
             
            
               
                 dynamic5QISetRef 
                 This is the DN of 
                 type: String 
               
               
                   
                 Dynamic5QISet. 
                 multiplicity: 0 . . . 1 
               
               
                   
                 allowedValues: DN of 
                 isOrdered: False 
               
               
                   
                 the Dynamic5QISet 
                 isUnique: True 
               
               
                   
                 MOI. 
                 defaultValue: None 
               
               
                   
                   
                 isNullable: True 
               
               
                 dynamic5QIs 
                 It indicates the dynamic 
                 type: 
               
               
                   
                 5QIs, including their 
                 FiveQICharacteristics 
               
               
                   
                 QoS characteristics. 
                 multiplicity: * 
               
               
                   
                 allowedValues: N/A 
                 isOrdered: N/A 
               
               
                   
                   
                 isUnique: N/A 
               
               
                   
                   
                 defaultValue: None 
               
               
                   
                   
                 isNullable: False 
               
               
                   
               
            
           
         
       
     
       FIG.  9    illustrates a method of providing PCC rule information in accordance with some embodiments. The operations shown in  FIG.  7    are not exclusive; other operations not shown in  FIG.  7    may also be present. The process  900  may include, at operation  902 , determining predefined PCC rule information. The process  900  may further include, at operation  904 , encoding a message including the predefined PCC rule information for transmission to a SMF. 
     A predefined PCC rule is configured in the SMF. When a predefined PCC rule is activated/deactivated by the PCF, the SMF decides what information is to be provided to the UPF to enforce the rule based on where the traffic detection filters (i.e. service data flow filter(s) or application detection filter), traffic steering policy information and the policies used for the traffic handling in the UPF are configured and where they are enforced: If the predefined PCC rule contains an application identifier for which corresponding application detection filters are configured in the UPF, the SMF provides a corresponding application identifier to the UPF; If the predefined PCC rule contains traffic steering policy identifier(s), the SMF provides a corresponding traffic steering policy identifier(s) to the UPF; If the predefined PCC rule contains service data flow filter(s), the SMF provides them to the UPF; If the predefined PCC rule contains some parameters for which corresponding policies for traffic handling in the UPF are configured in the UPF, the SMF activates those traffic handling policies via their rule ID(s). The SMF maintains the mapping between a PCC rule received over Npcf and the flow level PDR rule(s) used on N4 interface. 
     An active PCC rule means that: the service data flow template is used for service data flow detection; the service data flow template shall be used for mapping of downlink packets to the QoS Flow determined by the QoS Flow binding; the service data flow template shall be used for service data flow detection of uplink packets on the PDU Session determined by the QoS Flow binding; usage data for the service data flow shall be recorded; policies associated with the PCC rule, if any, shall be invoked; for service data flow detection with an application detection filter, the start or the stop of the application traffic is reported to the PCF, if applicable and requested by the PCF. In that case, the notification for start may include service data flow filters, (if possible to provide) and the application instance identifier associated with the service data flow filters; and either one of the conditions: a credit has been granted for the service data flow. Applicable w % ben the Charging method is set to “online” and the Service Data Flow handling while requesting credit is set to “blocking”; or a credit has been requested for the service data flow. Applicable when the Charging method is set to “online” and the Service Data Flow handling while requesting credit is set to “non-blocking”. 
     Although an embodiment has been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration, and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This Detailed Description, therefore, is not to be taken in a limiting sense, and the scope of various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled. 
     The subject matter may be referred to herein, individually and/or collectively, by the term “embodiment” merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description. 
     In this document, the terms “a” or “an” are used, as is common in patent documents, to include one or more than one, independent of any other instances or usages of “at least one” or “one or more.” In this document, the term “or” is used to refer to a nonexclusive or, such that “A or B” includes “A but not B,” “B but not A,” and “A and B,” unless otherwise indicated. In this document, the terms “including” and “in which” are used as the plain-English equivalents of the respective terms “comprising” and “wherein.” Also, in the following claims, the terms “including” and “comprising” are open-ended, that is, a system, UE, article, composition, formulation, or process that includes elements in addition to those listed after such a term in a claim are still deemed to fall within the scope of that claim. Moreover, in the following claims, the terms “first,” “second,” and “third,” etc. are used merely as labels, and are not intended to impose numerical requirements on their objects. 
     The Abstract of the Disclosure is provided to comply with 37 C.F.R. § 1.72(b), requiring an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separate embodiment.