WO2021245063A1

WO2021245063A1 - Policy decision error report to pcf

Info

Publication number: WO2021245063A1
Application number: PCT/EP2021/064636
Authority: WO
Inventors: Yumei SONG; Hong Zhang; Susana Fernandez Alonso; Fuencisla Garcia Azorero
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2020-06-01
Filing date: 2021-06-01
Publication date: 2021-12-09

Abstract

Disclosed herein is a method performed by first network function (208) in a core network (110) of a cellular communications system (100), the method comprising: receiving (406); (502) a first message from a second network function (210) in the core network (110), the first message comprising a Session Management, SM, policy decision; determining (408); (504) that there is an error associated with the SM policy decision, the error being either a validation error or an enforcement failure other than a PCC rule error and a session rule error; and sending (410); (506) a second message to the second network function (210), the second message comprising an error report that indicates the determined error.

Description

POLICY DECISION ERROR REPORT TO PCF BACKGROUND [0001] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features, and advantages of the enclosed embodiments will be apparent from the following description. [0002] Third Generation Partnership Project (3GPP) Technical Specification (TS) 29.512 V16.4.0 has the following chapters for the error report to the Policy Control Function (PCF): 1) Chapter 4.2.3.16 describes the Policy and Charging Control (PCC) rule error report for the PCC rule validation/enforcement error for Npcf_SMPolicyControl_UpdateNotify Service Operation; 2) Chapter 4.2.3.20 describes the Session Rule Error Report for the PCC rule validation/enforcement error for Npcf_SMPolicyControl_UpdateNotify Service Operation; 3) Chapter 4.2.4.15 describes the PCC rule error report for the PCC rule validation/enforcement error for Npcf_SMPolicyControl_Update and Npcf_SMPolicyControl_Create Service Operation; and 4) Chapter 4.2.4.21 describes the Session Rule Error Report for the PCC rule validation/enforcement error for Npcf_SMPolicyControl_Update and Npcf_SMPolicyControl_Create Service Operation. [0003] But there is no description about the how to handle the other policy decision errors, e.g., the PCF may provision wrong praInfos, chgDecs, umDecs, etc. For Npcf_SMPolicyControl_UpdateNotify Service Operation, the Session Management Function (SMF) can respond with error status code back to PCF, but the reason is unspecified. For Npcf_SMPolicyControl_Update Service Operation, there is no option for SMF to report error to PCF, which results unspecified behavior for such cases. SUMMARY [0004] There currently exist certain challenge(s). The current 3GPP specifications do not have the option for the SMF to report an error to the PCF when a policy decision error, other than a PCC rule error and a session rule error happens, for Npcf_SMPolicyControl_Update Service Operation. When such an error occurs, there are currently two options for the SMF: 1) the SMF may terminate the user session, but the solution to terminate the whole user session when such error happens will lead to bad end user experience; 2) the SMF can ignore the error and continue the user session with the previous policy decision, in this case the wrong policy/charging decision may be applied. [0005] Certain aspects of the present disclosure and their embodiments may provide solutions to the aforementioned or other challenges. Embodiments of a solution(s) are proposed herein for introducing an option for the SMF to report an error to the PCF when a validation and enforcement error happens on the PCF provisioned policy decisions other than PCC rules and session rules. [0006] Embodiments of the solution(s) disclosed herein enable the SMF to report an error to the PCF when the policy decision validation error or enforcement failure occurs. [0007] There are, proposed herein, various embodiments which address one or more of the issues disclosed herein. [0008] Certain embodiments may provide one or more of the following technical advantage(s). Using embodiments of the solution(s) disclosed herein, for errors of policy decision from a PCF, a SMF can notify the PCF about the error, and the PCF can take actions based on reported errors, e.g., and operator policy(ies). [0009] Several scenarios are described below in which support of such an error report is beneficial: 1) In one scenario, there is a semantical/validation error in chgDecs, umDecs, etc. The PCF can receive the error report immediately and take the corresponding action. Currently, the SMF behavior is unspecified. The SMF may terminate the user session when such error policy decision is received, which results in service interruption for the end user; or the SMF may keep the previous policy decision, but the consequence is the SMF continues to use the wrong charging/usage monitoring policy and report to the PCF, and the PCF is not aware that the new decision is not enforced, which leads to wrong end user experience or wrong charging. 2) In another scenario, there is an enforcement error in chgDecs which are connected to PCC rules, umDecs and qosDecs which are connected to PCC rules/session rules, which can be error reported back to the PCF by PCC/session rule error report. But in regard to ChargingData which can be on session level, if the UPF returns an error when enforcing the session level charging decision, there is no way to report the error to the PCF. The SMF either terminates user session or keeps the previous charging decision. If the SMF keeps the previous charging decision, then the charging information is not correct/PCF wanted. 3) In another scenario, there is a validation error of the praInfos. If the PCF wants to modify existing Presence Reporting Area (PRA) list of the UE dedicated PRA, but error happens, e.g. the PRA element list is missing due to errors in the PCF. Then, the SMF does not know if it is a core network PRA or UE dedicated PRA. Then, the SMF will not modify it or treat it as core network PRA, then UE reported PRA is not what the PCF wanted. This will lead to wrong policy, charging, and Quality of Service (QoS) decisions based on wrong PRA report. Again, it will in the end lead to bad end user experience and wrong charging. 4) In another scenario, there is an enforcement error of praInfos, no error report to PCF, and the SMF either terminates user session or no action is taken. Then the UE will continue to report the old PRA information to the PCF, or the scenario will lead to no PRA change report from UE at all during the session life time. This again may lead to bad user experience and wrong charging BRIEF DESCRIPTION OF THE DRAWINGS [0010] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in a constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings: Figure 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented; Figure 2 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs) using point-to-point interfaces, which 5G network architecture may be seen as a particular implementation of the system 100 of Figure 1; Figure 3 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point interfaces; Figure 4 illustrates the operation of a SMF 208 and a PCF 210 in accordance with one embodiment of the present disclosure; Figure 5 illustrates the operation of the SMF 208 and the PCF 210 in accordance with one embodiment of the present disclosure; Figure 6 is a schematic block diagram of a network node 600 according to some embodiments of the present disclosure; Figure 7 is a schematic block diagram that illustrates a virtualized embodiment of the network node 600 according to some embodiments of the present disclosure; Figure 8 is a schematic block diagram of the network node 600 according to some other embodiments of the present disclosure. DETAILED DESCRIPTION [0011] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed herein, the disclosed subject matter should not be construed as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. [0012] Radio Node: As used herein, a “radio node” is either a radio access node or a wireless communication device. [0013] Radio Access Node: As used herein, a “radio access node” or “radio network node” or “radio access network node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. Some examples of a radio access node include, but are not limited to, a base station (e.g., a New Radio (NR) base station (gNB) in a Third Generation Partnership Project (3GPP) Fifth Generation (5G) NR network or an enhanced or evolved Node B (eNB) in a 3GPP Long Term Evolution (LTE) network), a high-power or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), a relay node, a network node that implements part of the functionality of a base station (e.g., a network node that implements a gNB Central Unit (gNB-CU) or a network node that implements a gNB Distributed Unit (gNB-DU)) or a network node that implements part of the functionality of some other type of radio access node. [0014] Core Network Node: As used herein, a “core network node” is any type of node in a core network or any node that implements a core network function. Some examples of a core network node include, e.g., a Mobility Management Entity (MME), a Packet Data Network Gateway (P-GW), a Service Capability Exposure Function (SCEF), a Home Subscriber Server (HSS), or the like. Some other examples of a core network node include a node implementing a Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), an Authentication Server Function (AUSF), a Network Slice Selection Function (NSSF), a Network Exposure Function (NEF), a Network Function (NF) Repository Function (NRF), a Policy Control Function (PCF), a Unified Data Management (UDM), or the like. [0015] Communication Device: As used herein, a “communication device” is any type of device that has access to an access network. Some examples of a communication device include, but are not limited to: mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or Personal Computer (PC). The communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless or wireline connection. [0016] Wireless Communication Device: One type of communication device is a wireless communication device, which may be any type of wireless device that has access to (i.e., is served by) a wireless network (e.g., a cellular network). Some examples of a wireless communication device include, but are not limited to: a User Equipment device (UE) in a 3GPP network, a Machine Type Communication (MTC) device, and an Internet of Things (IoT) device. Such wireless communication devices may be, or may be integrated into, a mobile phone, smart phone, sensor device, meter, vehicle, household appliance, medical appliance, media player, camera, or any type of consumer electronic, for instance, but not limited to, a television, radio, lighting arrangement, tablet computer, laptop, or PC. The wireless communication device may be a portable, hand-held, computer-comprised, or vehicle-mounted mobile device, enabled to communicate voice and/or data via a wireless connection. [0017] Network Node: As used herein, a “network node” is any node that is either part of the RAN or the core network of a cellular communications network/system. [0018] Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP terminology or terminology similar to 3GPP terminology is oftentimes used. However, the concepts disclosed herein are not limited to a 3GPP system. [0019] Note that, in the description herein, reference may be made to the term “cell”; however, particularly with respect to 5G NR concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams. Figure 1 [0020] Figure 1 illustrates one example of a cellular communications system 100 in which embodiments of the present disclosure may be implemented. In the embodiments described herein, the cellular communications system 100 is a 5G system (5GS) including a Next Generation RAN (NG-RAN) and a 5G Core (5GC); however, the solution(s) proposed herein are not limited thereto. In this example, the RAN includes base stations 102-1 and 102-2, which in the 5GS include NR base stations (gNBs) and optionally next generation eNBs (ng-eNBs), controlling corresponding (macro) cells 104-1 and 104-2. The base stations 102-1 and 102-2 are generally referred to herein collectively as base stations 102 and individually as base station 102. Likewise, the (macro) cells 104-1 and 104-2 are generally referred to herein collectively as (macro) cells 104 and individually as (macro) cell 104. The RAN may also include a number of low power nodes 106-1 through 106-4 controlling corresponding small cells 108-1 through 108-4. The low power nodes 106-1 through 106-4 can be small base stations (such as pico or femto base stations) or Remote Radio Heads (RRHs), or the like. Notably, while not illustrated, one or more of the small cells 108-1 through 108-4 may alternatively be provided by the base stations 102. The low power nodes 106-1 through 106-4 are generally referred to herein collectively as low power nodes 106 and individually as low power node 106. Likewise, the small cells 108-1 through 108-4 are generally referred to herein collectively as small cells 108 and individually as small cell 108. The cellular communications system 100 also includes a core network 110, which in the 5G System (5GS) is referred to as the 5GC. The base stations 102 (and optionally the low power nodes 106) are connected to the core network 110. [0021] The base stations 102 and the low power nodes 106 provide service to wireless communication devices 112-1 through 112-5 in the corresponding cells 104 and 108. The wireless communication devices 112-1 through 112-5 are generally referred to herein collectively as wireless communication devices 112 and individually as wireless communication device 112. In the following description, the wireless communication devices 112 are oftentimes UEs, but the present disclosure is not limited thereto. Figure 2 [0022] Figure 2 illustrates a wireless communication system represented as a 5G network architecture composed of core Network Functions (NFs), where interaction between any two NFs is represented by a point- to-point reference point/interface. Figure 2 can be viewed as one particular implementation of the system 100 of Figure 1. [0023] Seen from the access side the 5G network architecture shown in Figure 2 comprises a plurality of UEs 112 connected to either a RAN 102 or an Access Network (AN) as well as an AMF 200. Typically, the R(AN) 102 comprises base stations, e.g. such as eNBs or gNBs or similar. Seen from the core network side, the 5GC NFs shown in Figure 2 include a NSSF 202, an AUSF 204, a UDM 206, the AMF 200, a SMF 208, a PCF 210, and an Application Function (AF) 212. [0024] Reference point representations of the 5G network architecture are used to develop detailed call flows in the normative standardization. The N1 reference point is defined to carry signaling between the UE 112 and AMF 200. The reference points for connecting between the AN 102 and AMF 200 and between the AN 102 and UPF 214 are defined as N2 and N3, respectively. There is a reference point, N11, between the AMF 200 and SMF 208, which implies that the SMF 208 is at least partly controlled by the AMF 200. N4 is used by the SMF 208 and UPF 214 so that the UPF 214 can be set using the control signal generated by the SMF 208, and the UPF 214 can report its state to the SMF 208. N9 is the reference point for the connection between different UPFs 214, and N14 is the reference point connecting between different AMFs 200, respectively. N15 and N7 are defined since the PCF 210 applies policy to the AMF 200 and SMF 208, respectively. N12 is required for the AMF 200 to perform authentication of the UE 112. N8 and N10 are defined because the subscription data of the UE 112 is required for the AMF 200 and SMF 208. [0025] The 5GC network aims at separating UP and CP. The UP carries user traffic while the CP carries signaling in the network. In Figure 2, the UPF 214 is in the UP and all other NFs, i.e., the AMF 200, SMF 208, PCF 210, AF 212, NSSF 202, AUSF 204, and UDM 206, are in the CP. Separating the UP and CP guarantees each plane resource to be scaled independently. It also allows UPFs to be deployed separately from CP functions in a distributed fashion. In this architecture, UPFs may be deployed very close to UEs to shorten the Round Trip Time (RTT) between UEs and data network for some applications requiring low latency. [0026] The core 5G network architecture is composed of modularized functions. For example, the AMF 200 and SMF 208 are independent functions in the CP. Separated AMF 200 and SMF 208 allow independent evolution and scaling. Other CP functions like the PCF 210 and AUSF 204 can be separated as shown in Figure 2. Modularized function design enables the 5GC network to support various services flexibly. [0027] Each NF interacts with another NF directly. It is possible to use intermediate functions to route messages from one NF to another NF. In the CP, a set of interactions between two NFs is defined as service so that its reuse is possible. This service enables support for modularity. The UP supports interactions such as forwarding operations between different UPFs. Figure 3 [0028] Figure 3 illustrates a 5G network architecture using service-based interfaces between the NFs in the CP, instead of the point-to-point reference points/interfaces used in the 5G network architecture of Figure 2. However, the NFs described above with reference to Figure 2 correspond to the NFs shown in Figure 3. The service(s) etc. that a NF provides to other authorized NFs can be exposed to the authorized NFs through the service-based interface. In Figure 3 the service based interfaces are indicated by the letter “N” followed by the name of the NF, e.g. Namf for the service based interface of the AMF 200 and Nsmf for the service based interface of the SMF 208, etc. The NEF 300 and the NRF 302 in Figure 3 are not shown in Figure 2 discussed above. However, it should be clarified that all NFs depicted in Figure 2 can interact with the NEF 300 and the NRF 302 of Figure 3 as necessary, though not explicitly indicated in Figure 2. [0029] Some properties of the NFs shown in Figures 2 and 3 may be described in the following manner. The AMF 200 provides UE-based authentication, authorization, mobility management, etc. A UE 112 even using multiple access technologies is basically connected to a single AMF 200 because the AMF 200 is independent of the access technologies. The SMF 208 is responsible for session management and allocates Internet Protocol (IP) addresses to UEs. It also selects and controls the UPF 214 for data transfer. If a UE 112 has multiple sessions, different SMFs 208 may be allocated to each session to manage them individually and possibly provide different functionalities per session. The AF 212 provides information on the packet flow to the PCF 210 responsible for policy control in order to support QoS. Based on the information, the PCF 210 determines policies about mobility and session management to make the AMF 200 and SMF 208 operate properly. The AUSF 204 supports authentication function for UEs or similar and thus stores data for authentication of UEs or similar while the UDM 206 stores subscription data of the UE 112. The Data Network (DN), not part of the 5GC network, provides Internet access or operator services and similar. [0030] An NF may be implemented either as a network element on a dedicated hardware, as a software instance running on a dedicated hardware, or as a virtualized function instantiated on an appropriate platform, e.g., a cloud infrastructure. [0031] Now, a description of embodiments of the solution(s) disclosed herein is provided. In general, embodiments of the solution(s) described herein provide a mechanism(s) for an SMF (e.g., SMF 208) to report an error to a PCF (e.g., PCF 210) when a validation and enforcement error happens on the PCF provisioned policy decisions other than PCC rules and session rules. Figure 4 [0032] In this regard, Figure 4 illustrates the operation of the SMF 208 and the PCF 210 in accordance with one embodiment of the present disclosure. Optional steps are represented by dashed lines/boxes. The steps of the process of Figure 4 are described below. [0033] Step 400: N7 policy association is established (e.g., in the conventional manner). [0034] Step 402: Any event(s) trigger a Policy Update procedure on the SMF 208. [0035] Step 404: The SMF 208 sends a SM Policy Control Update Request to the PCF 210 (e.g., in the conventional manner). [0036] Step 406: The PCF 210 responds with an SM Policy Control Update Response including a SM Policy Decision. [0037] Step 408: The SMF 208 determines that there is a validation error(s) or an enforcement failure for the SM Policy Decision received in step 406. [0038] Step 410: Responsive to determining that there is a validation error(s) or an enforcement failure for the SM Policy Decision received in step 406, the SMF 208 sends a SM Policy Control Update Request including a policy decision error report(s) to the PCF 210. In other words, the SM Policy Control Update Request reports the error determined for the SM Policy Decision received by the SMF 208 in step 406. In one embodiment, the policy decision error report includes an indication (e.g., error code) that indicates a cause of the policy decision error report. For example, the error may be one of a predefined set of possible errors (i.e., validation and/or enforcement errors that happen for the SM Policy Decision other than PCC rules and session rules) and the policy decision error report includes a value (sometimes referred to herein as a “error code”) that indicates one of the predefined set of possible errors as the cause of the policy decision error report. In one embodiment, the predefined set of possible errors includes a QoS decision error, a charging decision error, a usage monitoring decision error, and/or a PRA information error. [0039] Step 412: Responsive to the SM Policy Control Update Request including the policy decision error report(s), the PCF 210 responds to the SMF 208 with an SM Policy Control Update Response that includes a new and/or correct SM Policy Decision. The SMF 208 then performs one or more actions using the new and/or correct SM Policy Decision. Figure 5 [0040] Figure 5 illustrates the operation of the SMF 208 and the PCF 210 in accordance with one embodiment of the present disclosure. Optional steps are represented by dashed lines/boxes. The steps of the process of Figure 5 are described below. [0041] Step 500: N7 policy association is established (e.g., in the conventional manner). [0042] Step 502: The PCF 210 sends an SM Policy Control Update Notify Request to the SMF 208. The SM Policy Control Update Notify Request includes an SM Policy Decision. [0043] Step 504: The SMF 208 determines that there is a validation error(s) for the SM Policy Decision received in step 502. In other words, the SMF 208 validates the SM Policy Decision and finds a syntax error or semantic error. [0044] Step 506: Responsive to determining that there is a validation error(s) for the SM Policy Decision received in step 502, the SMF 208 sends a SM Policy Control Update Notify Response including a policy decision error report(s) to the PCF 210. In other words, the SM Policy Control Update Request reports the error determined for the SM Policy Decision received by the SMF 208 in step 502. In one embodiment, the policy decision error report includes an indication (e.g., error code) that indicates a cause of the policy decision error report. For example, the error may be one of a predefined set of possible errors (i.e., validation error(s) that happen for the SM Policy Decision other than PCC rules and session rules) and the policy decision error report includes a value (sometimes referred to herein as a “error code”) that indicates one of the predefined set of possible errors as the cause of the policy decision error report. In one embodiment, the predefined set of possible errors includes a QoS decision error, a charging decision error, a usage monitoring decision error, and/or a PRA information error. [0045] Step 508: The PCF 210 provisions a new and/or corrected SM Policy Decision. [0046] Step 510: The PCF 210 sends a SM Policy Control Update Notify Request to the SMF 208. The SM Policy Control Update Notify Request includes the new/correct SM Policy Decision. [0047] 512: The SMF 208 responds with a SM Policy Control Update Notify Response. [0048] Details regarding some example embodiments related to the policy decision error report of step 410 or step 506. In one embodiment, Data Type policyDecisionErrorReport is added in Table 5.5.2.2-2 of 3GPP TS 29.512: Data structures supported by the POST Response Body on this resource, as follows:

[0049] In one embodiment, in 3GPP TS 29.512 chapter 5.6.2.19, an attribute is added in Table 5.6.2.19-1: Definition of type SmPolicyUpdateContextData as follows:

[0050] In one embodiment, data type policyDecisionErrorReport is added in Table 5.6.2.33-1: Definition of type PartialSuccessReport, as follows:

[0051] In another embodiment, a new chapter 5.6.2.xx Type PolicyDecisionErrorReport is added to 3GPP TS 29.512, as described in the example implementation described below. [0052] In one embodiment, Table 5.6.2.xx-1 of new Chapter 5.6.2.xx: Definition of type PolicyDecisionErrorReport, is as follows:

[0053] In one embodiment, a new chapter 5.6.3.xx, Enumeration: PolicyDecisionFailureCode, is added to 3GPP TS 29.512 as described in the example implementation described below. In one embodiment, Table 5.6.3.xx-1: Enumeration PolicyDecisionFailureCode, of new chapter 5.6.3.xx is as follows:

Example Implementation [0054] The following description is a description of an example implementation of at least some aspects of the embodiments described above provided as a change request to 3GPP TS 29.512 V16.4.0 (changes are show with underlining and strike-throughs). [0055] Reason for the Changes: Currently, it is allowed to provision or keep the policy decision and condition data at the SMF without any PCC rule referring to them. But it may happen that the policy decision data and condition can’t be provisioned successfully or kept any longer. In this case, the SMF can’t report the status of the policy decision and/or condition to the PCF according to current specification. [0056] Summary of the Changes: A summary of the changes to 3GPP TS 29.512 V16.4.0 is as follows: 1) Define the procedure to report the status of the policy decision and/or condition. As the policy decision and condition data which are not referred by any PCC rule and session rule is not excited, the report is used to make the PCF to know the status. 2) The report is included in the response message directly, in the ErrorReport, in the PartialSuccessReport and the SmPolicyUpdateContextData. 3) New feature is defined. *************************FIRST CHANGE TO 3GPP TS 29.512 V16.4.0************************* 4.2.3.1 General The UpdateNotify service operation provides updated Session Management related policies to the NF service consumer (SMF) or triggers the deletion of the context of SM related policies. The POST method is used for both, update and delete operations. The following procedures using the Npcf_SMPolicyControl_UpdateNotify service operation are supported: - PCF initiated update of the policies associated with the PDU session. - PCF initiated deletion of SM Policy Association of a PDU session. - Provisioning of PCC rules. - Provisioning of policy control request triggers. - Provisioning of revalidation time. - Policy provisioning and enforcement of authorized AMBR per PDU session. - Policy provisioning and enforcement of authorized default QoS. - Provisioning of PCC rule for Application Detection and Control. - 3GPP PS Data Off Support. - IMS Emergency Session Support. - Request Access Network Information. - Request Usage Monitoring Control. - Request for the result of PCC rule removal. - Access Network Charging Identifier request. - Request for the successful resource allocation notification. - IMS Restoration Support. - P-CSCF Restoration Enhancement Support. - Access traffic steering, switching and splitting support. - Policy provisioning and enforcement of the AF session with required QoS. - Forwarding of TSN information received from AF. - Provisioning of TSCAI input information and TSC QoS related data. - Policy provisioning and enforcement of the AF session with required QoS. - Policy decision and condition data status report. ***************************************END FIRST CHANGE *************************************** ************************SECOND CHANGE TO 3GPP TS 29.512 V16.4.0*********************** 4.2.3.x Policy decision and condition data status report If the "DataStatusHandling" feature is supported and if the SMF receives one or more policy decisions and/or condition datas which are not referred by any PCC rules or session rules as defined in subclause 4.2.3.1 but the storage of the policy decisions and/or condition datas were unsuccessful (e.g. the policy decision could not be successfully stored due to a limitation of resources at the SMF), the SMF shall include an HTTP "200 OK" status code and one or more DataReport structures for the affected policy decisions and/or condition datas to report the status in the response message if the SMF does not need to report any other information, or include an HTTP "400 Bad Request" status code and the "dataReports" attribute for the affected policy decisions and/or condition datas to report the status within the ErrorReport data structure in the response message if the SMF needs to reject the request or include an HTTP "200 OK" status code and the "dataReports" attribute for the affected policy decisions and/or condition datas to report the status within the PartialSuccessReport data structure in the response message if the SMF needs to report partial success. Within each DataReport instance, the SMF shall identify the failed policy decision data and/or condition data by including the type(s) of affected policy decision data and/or condition data within the "decTypes" attribute, the identifier(s) of affected policy decision data and/or condition data within the "dataIds" attribute, and the data status within the "dataStatus" attribute with the value as described below. If the storage of one or more new policy decisions and/or condition datas (i.e. policy decision data and/or condition data which were not previously provisioned) fail, the SMF shall set the "dataStatus" to REMOVAL. If the modification of a currently provisioned policy decisions and/or condition datas, the SMF shall retain the existing policy decisions and/or condition datas as kept without any modification unless the reason for the failure has an impact also on the existing policy decisions and/or condition datas. The removal of a policy decisions and/or condition datas shall not fail, even if the PDU session procedures with the UE fail. The SMF shall retain information on the removal and conduct the necessary PDU session procedures with the UE when it is possible. *************************************END SECOND CHANGE ************************************* *************************THIRD CHANGE TO 3GPP TS 29.512 V16.4.0************************* 4.2.4.1 General The Npcf_SMPolicyControl_Update service operation provides means for the NF service consumer to inform the PCF that a policy control request trigger condition has been met and for the PCF to inform the NF service consumer of any resulting update of the Session Management related policies. The following procedures using the Npcf_SMPolicyControl_Update service operation are supported: - Provisioning of PCC rules. - Provisioning of policy control request triggers. - Request the policy based on revalidation time. - Policy provisioning and enforcement of authorized AMBR per PDU session. - Policy provisioning and enforcement of authorized default QoS. - Application detection information reporting. -^{Indication of QoS Flow Termination Implications.} - 3GPP PS Data Off Support. - Request and report Access Network Information. - Request Usage Monitoring Control and report Accumulated Usage. - Ipv6 Multi-homing support. - Request and report the result of PCC rule removal. - Access Network Charging Identifier Request and report. - Request and report the successful resource allocation notification. - Negotiation of the QoS flow for IMS signalling. - Notification about Service Data Flow QoS target enforcement. -^{Request the termination of SM Policy association.} - Reporting of TSN information. - QoS Monitoring Report. - Policy decision and condition data status report. ***************************************END THIRD CHANGE ************************************** ************************FOURTH CHANGE TO 3GPP TS 29.512 V16.4.0*********************** 4.2.4.x Policy decision and condition data status report If the "DataStatusHandling" feature is supported and one or more policy decisions and/or condition datas which are not referred by any PCC rules or session rule is provisioned using the procedure as defined in subclauses 4.2.2.1, 4.2.3.1 or 4.2.4.1 but the storage were unsuccessful (e.g. the policy decision could not be successfully stored due to a limitation of resources at the SMF), the SMF shall include the "dataReports" attribute for the affected policy decisions and/or condition datas to report the status within the SmPolicyUpdateContextData data structure. Within each DataReport instance, the SMF shall identify the failed policy decisions and/or condition datas by including the type(s) of affected policy decisions and/or condition datas within the "decTypes" attribute, the identifier(s) of affected policy decisions and/or condition datas within the "dataIds" attribute, and the data status within the "dataStatus" attribute with the value as described below. If the storage of one or more new policy decisions and/or condition datas (i.e. policy decision data and/or condition data which were not previously provisioned) fail, the SMF shall set the "dataStatus" to REMOVAL. The removal of a policy decisions and/or condition datas shall not fail, even if the PDU session procedures with the UE fail. The SMF shall retain information on the removal and conduct the necessary PDU session procedures with the UE when it is possible. If the modification of a currently stored policy decisions and/or condition datas, the SMF shall retain the existing policy decisions and/or condition datas without any modification unless the reason for the failure has an impact also on the existing policy decisions and/or condition datas. The SMF shall report the modification failure to the PCF. If policy decisions data and/or condition data were successfully stored, but can no longer be kept by the SMF, the SMF ^{shall set the "dataStatus" attribute to REMOVAL.} NOTE: When the PCF receives "dataStatus" set to REMOVAL, the PCF does not need request the SMF to remove the policy decision data and/or condition data. *************************************END FOURTH CHANGE ************************************* ***************************FIFTH CHANGE TO 3GPP TS 29.512 V16.4.0************************ 5.5.2.2 Operation Definition This operation shall support the request data structures specified in table 5.5.2.2-1 and the response data structure and response codes specified in table 5.5.2.2-2. Table 5.5.2.2-1: Data structures supported by the POST Request Body on this resource

Table 5.5.2.2-2: Data structures supported by the POST Response Body on this resource

***************************************END FIFTH CHANGE *************************************** **************************SIXTH CHANGE TO 3GPP TS 29.512 V16.4.0************************ 5.6.1 General This subclause specifies the application data model supported by the API. The Npcf_SMPolicyControl API allows the SMF to retrieve the session management related policy from the PCF as defined in 3GPP TS 23.503 [6]. Table 5.6.1-1 specifies the data types defined for the Npcf_SMPolicyControl service based interface protocol. Table 5.6.1-1: Npcf_SMPolicyControl specific Data Types

Table 5.6.1-2 specifies data types re-used by the Npcf_SMPolicyControl service based interface protocol from other specifications, including a reference to their respective specifications and when needed, a short description of their use within the Npcf_SMPolicyControl service based interface. Table 5.6.1-2: Npcf_SMPolicyControl re-used Data Types

***************************************END SIXTH CHANGE ************************************** *************************SEVENTH CHANGE TO 3GPP TS 29.512 V16.4.0********************* 5.6.2.19 Type SmPolicyUpdateContextData Table 5.6.2.19-1: Definition of type SmPolicyUpdateContextData

************************************END SEVENTH CHANGE ************************************* *************************EIGHTH CHANGE TO 3GPP TS 29.512 V16.4.0********************* 5.6.2.36 Type ErrorReport Table 5.6.2.36-1: Definition of type ErrorReport

************************************END EIGHTH CHANGE ************************************* ****************************NINTH CHANGE TO 3GPP TS 29.512 V16.4.0********************** 5.6.2.33 Type PartialSuccessReport Table 5.6.2.33-1: Definition of type PartialSuccessReport

************************************END NINTH CHANGE ***************************************** ****************************TENTH CHANGE TO 3GPP TS 29.512 V16.4.0********************* 5.6.2.x Type DataReport Table 5.6.2.37-1: Definition of type DataReport

************************************END TENTH CHANGE ****************************************

*************************ELEVENTH CHANGE TO 3GPP TS 29.512 V16.4.0******************* 5.6.3.x Enumeration: DecisionType Table 5.6.3.x-1: Enumeration DecisionType

**********************************END ELEVENTH CHANGE ************************************* **************************TWELFTH CHANGE TO 3GPP TS 29.512 V16.4.0******************* 5.6.3.y Enumeration: DataStatus Table 5.6.3.y-1: Enumeration DataStatus

**********************************END TWELFTH CHANGE *************************************** *************************THIRTEENTH CHANGE TO 3GPP TS 29.512 V16.4.0***************** 5.8 Feature negotiation The optional features in table 5.8-1 are defined for the Npcf_SMPolicyControl API. They shall be negotiated using the extensibility mechanism defined in subclause 6.6 of 3GPP TS 29.500 [4]. Table 5.8-1: Supported Features

Applicant’s Ref. P081370WO01 27 30 ADCmultiRedirection This feature indicates support for multiple redirection information in application detection and control. It requires

END THIRTEENTH CHANGE ** ***********************FOURTEENTH CHANGE TO 3GPP TS 29.512 V16.4.0***************** 5 A.2 Npcf_SMPolicyControl API openapi: 3.0.0 info: title: Npcf_SMPolicyControl API version: 1.1.1.alpha-5 10 description: | Session Management Policy Control Service © 2020, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI, TTA, TTC). All rights reserved. externalDocs: 15 description: 3GPP TS 29.512 V16.4.0; 5G System; Session Management Policy Control Service. url: 'http://www.3gpp.org/ftp/Specs/archive/29_series/29.512/' security: - {} - oAuth2Clientcredentials: 20 ^{- npcf-smpolicycontrol} servers: - url: '{apiRoot}/npcf-smpolicycontrol/v1' variables: apiRoot: 25 default: https://example.com description: apiRoot as defined in subclause 4.4 of 3GPP TS 29.501 paths: /sm-policies: post: 30 summary: Create a new Individual SM Policy operationId: CreateSMPolicy tags: - SM Policies (Collection) requestBody: 35 ^{required: true} content: application/json: schema: $ref: '#/components/schemas/SmPolicyContextData' 40 responses: '201': description: Created content: application/json: schema: $ref: '#/components/schemas/SmPolicyDecision' headers: Location: description: 'Contains the URI of the newly created resource' required: true schema: type: string '308': d^{escription: Permanent Redirect} headers: Location: description: 'Contains the URI of the PCF within the existing PCF binding information stored in the BSF for the same UE ID, S-NSSAI and DNN combination ' r^{equired: true} schema: type: string '400': $ref: 'TS29571_CommonData.yaml#/components/responses/400' '401': $ref: 'TS29571_CommonData.yaml#/components/responses/401' '403': $ref: 'TS29571_CommonData.yaml#/components/responses/403' '404': description: Not Found '411': $ref: 'TS29571_CommonData.yaml#/components/responses/411' '413': $ref: 'TS29571_CommonData.yaml#/components/responses/413' '^415': $ref: 'TS29571_CommonData.yaml#/components/responses/415' '429': $ref: 'TS29571_CommonData.yaml#/components/responses/429' '500': $ref: 'TS29571_CommonData.yaml#/components/responses/500' '503': $ref: 'TS29571_CommonData.yaml#/components/responses/503' default: $ref: 'TS29571_CommonData.yaml#/components/responses/default' callbacks: SmPolicyUpdateNotification: '{$request.body#/notificationUri}/update': post: requestBody: r^{equired: true} content: application/json: schema: $ref: '#/components/schemas/SmPolicyNotification' responses: '200': description: OK. The current applicable values corresponding to the policy control request trigger is reported content: application/json: schema: oneOf: - $ref: '#/components/schemas/UeCampingRep' - type: array i^tems: $ref: '#/components/schemas/PartialSuccessReport' minItems: 1 - type: array items: $ref: '#/components/schemas/DataReport' minItems: 1 '204': description: No Content, Notification was succesfull '400': description: Bad Request. content: application/json: schema: $ref: '#/components/schemas/ErrorReport' '401': $ref: 'TS29571_CommonData.yaml#/components/responses/401' '403': $ref: 'TS29571_CommonData.yaml#/components/responses/403' '404': $ref: 'TS29571_CommonData.yaml#/components/responses/404' '411': $ref: 'TS29571_CommonData.yaml#/components/responses/411' '^413': $ref: 'TS29571_CommonData.yaml#/components/responses/413' '415': $ref: 'TS29571_CommonData.yaml#/components/responses/415' '429': $^{ref: 'TS29571_CommonData.yaml#/components/responses/429'} '500': $ref: 'TS29571_CommonData.yaml#/components/responses/500' '503': $ref: 'TS29571_CommonData.yaml#/components/responses/503' default: $ref: 'TS29571_CommonData.yaml#/components/responses/default' SmPolicyControlTerminationRequestNotification: '{$request.body#/notificationUri}/terminate': post: requestBody: required: true content: application/json: schema: $^{ref: '#/components/schemas/TerminationNotification'} responses: '204': description: No Content, Notification was succesful '400': $ref: 'TS29571_CommonData.yaml#/components/responses/400' '401': $ref: 'TS29571_CommonData.yaml#/components/responses/401' '403': $ref: 'TS29571_CommonData.yaml#/components/responses/403' '404': $ref: 'TS29571_CommonData.yaml#/components/responses/404' '411': $ref: 'TS29571_CommonData.yaml#/components/responses/411' '413': $^{ref: 'TS29571_CommonData.yaml#/components/responses/413'} '415': $ref: 'TS29571_CommonData.yaml#/components/responses/415' '429': $ref: 'TS29571_CommonData.yaml#/components/responses/429' '500': $ref: 'TS29571_CommonData.yaml#/components/responses/500' '503': $ref: 'TS29571_CommonData.yaml#/components/responses/503' default: $ref: 'TS29571_CommonData.yaml#/components/responses/default' /sm-policies/{smPolicyId}: get: summary: Read an Individual SM Policy operationId: GetSMPolicy t^ags: - Individual SM Policy (Document) parameters: - name: smPolicyId in: path description: Identifier of a policy association required: true schema: type: string responses: '200': description: OK. Resource representation is returned content: application/json: schema: $ref: '#/components/schemas/SmPolicyControl' '400': $ref: 'TS29571_CommonData.yaml#/components/responses/400' '401': $ref: 'TS29571_CommonData.yaml#/components/responses/401' '403': $ref: 'TS29571_CommonData.yaml#/components/responses/403' '404': $^{ref: 'TS29571_CommonData.yaml#/components/responses/404'} '406': $ref: 'TS29571_CommonData.yaml#/components/responses/406' '429': $ref: 'TS29571_CommonData.yaml#/components/responses/429' '^500': $ref: 'TS29571_CommonData.yaml#/components/responses/500' '503': $ref: 'TS29571_CommonData.yaml#/components/responses/503' default: $ref: 'TS29571_CommonData.yaml#/components/responses/default' /sm-policies/{smPolicyId}/update: post: summary: Update an existing Individual SM Policy operationId: UpdateSMPolicy tags: - Individual SM Policy (Document) requestBody: required: true content: a^{pplication/json:} schema: $ref: '#/components/schemas/SmPolicyUpdateContextData' parameters: - name: smPolicyId in: path description: Identifier of a policy association required: true schema: type: string responses: '200': description: OK. Updated policies are returned content: application/json: s^chema: $ref: '#/components/schemas/SmPolicyDecision' '400': $ref: 'TS29571_CommonData.yaml#/components/responses/400' '401': $ref: 'TS29571_CommonData.yaml#/components/responses/401' '403': $ref: 'TS29571_CommonData.yaml#/components/responses/403' '404': $ref: 'TS29571_CommonData.yaml#/components/responses/404' '411': $ref: 'TS29571_CommonData.yaml#/components/responses/411' '413': $ref: 'TS29571_CommonData.yaml#/components/responses/413' '415': $^{ref: 'TS29571_CommonData.yaml#/components/responses/415'} '429': $ref: 'TS29571_CommonData.yaml#/components/responses/429' '500': $ref: 'TS29571_CommonData.yaml#/components/responses/500' '503': $ref: 'TS29571_CommonData.yaml#/components/responses/503' default: $ref: 'TS29571_CommonData.yaml#/components/responses/default' /sm-policies/{smPolicyId}/delete: post: summary: Delete an existing Individual SM Policy operationId: DeleteSMPolicy tags: - Individual SM Policy (Document) requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/SmPolicyDeleteData' parameters: - name: smPolicyId i^{n: path} description: Identifier of a policy association required: true schema: type: string r^esponses: '204': description: No content '400': $ref: 'TS29571_CommonData.yaml#/components/responses/400' '401': $ref: 'TS29571_CommonData.yaml#/components/responses/401' '403': $ref: 'TS29571_CommonData.yaml#/components/responses/403' '404': $ref: 'TS29571_CommonData.yaml#/components/responses/404' '411': $ref: 'TS29571_CommonData.yaml#/components/responses/411' '413': $ref: 'TS29571_CommonData.yaml#/components/responses/413' '^415': $ref: 'TS29571_CommonData.yaml#/components/responses/415' '429': $ref: 'TS29571_CommonData.yaml#/components/responses/429' '500': $ref: 'TS29571_CommonData.yaml#/components/responses/500' '503': $ref: 'TS29571_CommonData.yaml#/components/responses/503' default: $ref: 'TS29571_CommonData.yaml#/components/responses/default' components: securitySchemes: oAuth2Clientcredentials: type: oauth2 flows: c^{lientCredentials:} tokenUrl: '{nrfApiRoot}/oauth2/token' scopes: npcf-smpolicycontrol: Access to the Npcf_SMPolicyControl API schemas: SmPolicyControl: type: object properties: context: $ref: '#/components/schemas/SmPolicyContextData' policy: $ref: '#/components/schemas/SmPolicyDecision' required: - context - policy S^{mPolicyContextData:} type: object properties: accNetChId: $ref: '#/components/schemas/AccNetChId' chargEntityAddr: $ref: '#/components/schemas/AccNetChargingAddress' gpsi: $ref: 'TS29571_CommonData.yaml#/components/schemas/Gpsi' supi: $ref: 'TS29571_CommonData.yaml#/components/schemas/Supi' interGrpIds: type: array items: $ref: 'TS29571_CommonData.yaml#/components/schemas/GroupId' minItems: 1 pduSessionId: $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSessionId' pduSessionType: $ref: 'TS29571_CommonData.yaml#/components/schemas/PduSessionType' chargingcharacteristics: type: string dnn: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/Dnn'} dnnSelMode: $ref: 'TS29502_Nsmf_PDUSession.yaml#/components/schemas/DnnSelectionMode' notificationUri: $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' a^ccessType: $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' ratType: $ref: 'TS29571_CommonData.yaml#/components/schemas/RatType' addAccessInfo: $ref: '#/components/schemas/AdditionalAccessInfo' servingNetwork: $ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnIdNid' userLocationInfo: $ref: 'TS29571_CommonData.yaml#/components/schemas/UserLocation' ueTimeZone: $ref: 'TS29571_CommonData.yaml#/components/schemas/TimeZone' pei: $ref: 'TS29571_CommonData.yaml#/components/schemas/Pei' ipv4Address: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr'} ipv6AddressPrefix: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix' ipDomain: type: string description: Indicates the IPv4 address domain subsSessAmbr: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ambr' authProfIndex: type: string description: Indicates the DN-AAA authorization profile index subsDefQos: $ref: 'TS29571_CommonData.yaml#/components/schemas/SubscribedDefaultQos' numOfPackFilter: type: integer d^{escription: Contains the number of supported packet filter for signalled QoS rules.} online: type: boolean description: If it is included and set to true, the online charging is applied to the PDU session. offline: type: boolean description: If it is included and set to true, the offline charging is applied to the PDU session. 3gppPsDataOffStatus: type: boolean description: If it is included and set to true, the 3GPP PS Data Off is activated by the UE. refQosIndication: type: boolean d^{escription: If it is included and set to true, the reflective QoS is supported by the UE.} traceReq: $ref: 'TS29571_CommonData.yaml#/components/schemas/TraceData' sliceInfo: $ref: 'TS29571_CommonData.yaml#/components/schemas/Snssai' qosFlowUsage: $ref: '#/components/schemas/QosFlowUsage' servNfId: $ref: '#/components/schemas/ServingNfIdentity' suppFeat: $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' smfId: $ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId' recoveryTime: $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' maPduInd: $ref: '#/components/schemas/MaPduIndication' atsssCapab: $ref: '#/components/schemas/AtsssCapability' required: - supi - pduSessionId - pduSessionType -^dnn - notificationUri - sliceInfo SmPolicyDecision: type: object p^roperties: sessRules: type: object additionalProperties: $ref: '#/components/schemas/SessionRule' minProperties: 1 description: A map of Sessionrules with the content being the SessionRule as described in subclause 5.6.2.7. pccRules: type: object additionalProperties: $ref: '#/components/schemas/PccRule' minProperties: 1 description: A map of PCC rules with the content being the PCCRule as described in subclause 5.6.2.6. n^{ullable: true} pcscfRestIndication: type: boolean description: If it is included and set to true, it indicates the P-CSCF Restoration is requested. qosDecs: type: object additionalProperties: $ref: '#/components/schemas/QosData' minProperties: 1 description: Map of QoS data policy decisions. chgDecs: type: object additionalProperties: $ref: '#/components/schemas/ChargingData' m^{inProperties: 1} description: Map of Charging data policy decisions. nullable: true chargingInfo: $ref: '#/components/schemas/ChargingInformation' traffContDecs: type: object additionalProperties: $ref: '#/components/schemas/TrafficControlData' minProperties: 1 description: Map of Traffic Control data policy decisions. umDecs: type: object additionalProperties: $ref: '#/components/schemas/UsageMonitoringData' m^{inProperties: 1} description: Map of Usage Monitoring data policy decisions. nullable: true qosChars: type: object additionalProperties: $ref: '#/components/schemas/QosCharacteristics' minProperties: 1 description: Map of QoS characteristics for non standard 5QIs. This map uses the 5QI values as keys. qosMonDecs: type: object additionalProperties: $ref: '#/components/schemas/QosMonitoringData' minProperties: 1 description: Map of QoS Monitoring data policy decisions. nullable: true reflectiveQoSTimer: $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' conds: type: object additionalProperties: $ref: '#/components/schemas/ConditionData' m^{inProperties: 1} description: A map of condition data with the content being as described in subclause 5.6.2.9. nullable: true revalidationTime: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime'} offline: type: boolean description: Indicates the offline charging is applicable to the PDU session or PCC rule. online: type: boolean description: Indicates the online charging is applicable to the PDU session or PCC rule. policyCtrlReqTriggers: type: array items: $ref: '#/components/schemas/PolicyControlRequestTrigger' minItems: 1 description: Defines the policy control request triggers subscribed by the PCF. nullable: true lastReqRuleData: t^{ype: array} items: $ref: '#/components/schemas/RequestedRuleData' minItems: 1 description: Defines the last list of rule control data requested by the PCF. lastReqUsageData: $ref: '#/components/schemas/RequestedUsageData' praInfos: type: object additionalProperties: $ref: 'TS29571_CommonData.yaml#/components/schemas/PresenceInfoRm' minProperties: 1 description: Map of PRA information. nullable: true ipv4Index: $^{ref: 'TS29519_Policy_Data.yaml#/components/schemas/IpIndex'} ipv6Index: $ref: 'TS29519_Policy_Data.yaml#/components/schemas/IpIndex' qosFlowUsage: $ref: '#/components/schemas/QosFlowUsage' relCause: $ref: '#/components/schemas/SmPolicyAssociationReleaseCause' suppFeat: $ref: 'TS29571_CommonData.yaml#/components/schemas/SupportedFeatures' tsnPortManContDstt: $ref: '#/components/schemas/PortManagementContainer' tsnPortManContNwtts: type: array items: $ref: '#/components/schemas/PortManagementContainer' m^{inItems: 1} SmPolicyNotification: type: object properties: resourceUri: $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' smPolicyDecision: $ref: '#/components/schemas/SmPolicyDecision' PccRule: type: object properties: flowInfos: type: array items: $ref: '#/components/schemas/FlowInformation' minItems: 1 description: An array of IP flow packet filter information. appId: type: string description: A reference to the application detection filter configured at the UPF. contVer: $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/ContentVersion' pccRuleId: t^{ype: string} description: Univocally identifies the PCC rule within a PDU session. precedence: $ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger' afSigProtocol: $^{ref: '#/components/schemas/AfSigProtocol'} appReloc: type: boolean description: Indication of application relocation possibility. refQosData: type: array items: type: string minItems: 1 maxItems: 1 description: A reference to the QoSData policy type decision type. It is the qosId described in subclause 5.6.2.8. refAltQosParams: type: array items: t^{ype: string} minItems: 1 description: A Reference to the QoS Data policy decision type for the Alternative QoS parameter sets of the service data flow. refTcData: type: array items: type: string minItems: 1 maxItems: 1 description: A reference to the TrafficControlData policy decision type. It is the tcId described in subclause 5.6.2.10. refChgData: type: array items: t^{ype: string} minItems: 1 maxItems: 1 description: A reference to the ChargingData policy decision type. It is the chgId described in subclause 5.6.2.11. nullable: true refChgN3gData: type: array items: type: string minItems: 1 maxItems: 1 description: A reference to the ChargingData policy decision type only applicable to Non- 3GPP access if "ATSSS" feature is supported. It is the chgId described in subclause 5.6.2.11. nullable: true r^efUmData: type: array items: type: string minItems: 1 maxItems: 1 description: A reference to UsageMonitoringData policy decision type. It is the umId described in subclause 5.6.2.12. nullable: true refUmN3gData: type: array items: type: string minItems: 1 maxItems: 1 description: A reference to UsageMonitoringData policy decision type only applicable to Non-3GPP access if "ATSSS" feature is supported. It is the umId described in subclause 5.6.2.12. nullable: true refCondData: type: string description: A reference to the condition data. It is the condId described in subclause 5.6.2.9. nullable: true r^efQosMon: type: array items: type: string minItems: 1 m^{axItems: 1} description: A reference to the QosMonitoringData policy type decision type. It is the qmId described in subclause 5.6.2.40. nullable: true addrPreserInd: type: boolean nullable: true tscaiInputDl: $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer' tscaiInputUl: $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/TscaiInputContainer' required: - pccRuleId nullable: true SessionRule: t^{ype: object} properties: authSessAmbr: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ambr' authDefQos: $ref: '#/components/schemas/AuthorizedDefaultQos' sessRuleId: type: string description: Univocally identifies the session rule within a PDU session. refUmData: type: string description: A reference to UsageMonitoringData policy decision type. It is the umId described in subclause 5.6.2.12. nullable: true refUmN3gData: t^{ype: string} description: A reference to UsageMonitoringData policy decision type to apply for Non-3GPP access. It is the umId described in subclause 5.6.2.12. nullable: true refCondData: type: string description: A reference to the condition data. It is the condId described in subclause 5.6.2.9. nullable: true required: - sessRuleId nullable: true QosData: type: object properties: q^osId: type: string description: Univocally identifies the QoS control policy data within a PDU session. 5qi: $ref: 'TS29571_CommonData.yaml#/components/schemas/5Qi' maxbrUl: $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' maxbrDl: $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' gbrUl: $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' gbrDl: $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' arp: $ref: 'TS29571_CommonData.yaml#/components/schemas/Arp' qnc: type: boolean description: Indicates whether notifications are requested from 3GPP NG-RAN when the GFBR can no longer (or again) be guaranteed for a QoS Flow during the lifetime of the QoS Flow. priorityLevel: $ref: 'TS29571_CommonData.yaml#/components/schemas/5QiPriorityLevelRm' averWindow: $ref: 'TS29571_CommonData.yaml#/components/schemas/AverWindowRm' m^{axDataBurstVol:} $ref: 'TS29571_CommonData.yaml#/components/schemas/MaxDataBurstVolRm' reflectiveQos: type: boolean description: Indicates whether the QoS information is reflective for the corresponding ^{service data flow.} sharingKeyDl: type: string description: Indicates, by containing the same value, what PCC rules may share resource in downlink direction. sharingKeyUl: type: string description: Indicates, by containing the same value, what PCC rules may share resource in uplink direction. maxPacketLossRateDl: $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketLossRateRm' maxPacketLossRateUl: $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketLossRateRm' defQosFlowIndication: type: boolean d^{escription: Indicates that the dynamic PCC rule shall always have its binding with the QoS} Flow associated with the default QoS rule extMaxDataBurstVol: $ref: 'TS29571_CommonData.yaml#/components/schemas/ExtMaxDataBurstVolRm' required: - qosId nullable: true ConditionData: type: object properties: condId: type: string description: Uniquely identifies the condition data within a PDU session. activationTime: $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTimeRm' d^{eactivationTime:} $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTimeRm' accessType: $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' ratType: $ref: 'TS29571_CommonData.yaml#/components/schemas/RatType' required: - condId nullable: true TrafficControlData: type: object properties: tcId: type: string description: Univocally identifies the traffic control policy data within a PDU session. f^lowStatus: $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/FlowStatus' redirectInfo: $ref: '#/components/schemas/RedirectInformation' addRedirectInfo: type: array items: $ref: '#/components/schemas/RedirectInformation' minItems: 1 muteNotif: type: boolean description: Indicates whether applicat'on's start or stop notification is to be muted. trafficSteeringPolIdDl: type: string description: Reference to a pre-configured traffic steering policy for downlink traffic at the SMF. nullable: true trafficSteeringPolIdUl: type: string description: Reference to a pre-configured traffic steering policy for uplink traffic at the SMF. nullable: true routeToLocs: t^{ype: array} items: $ref: 'TS29571_CommonData.yaml#/components/schemas/RouteToLocation' minItems: 1 description: A list of location which the traffic shall be routed to for the AF request t^{raffCorreInd:} type: boolean upPathChgEvent: $ref: '#/components/schemas/UpPathChgEvent' steerFun: $ref: '#/components/schemas/SteeringFunctionality' steerModeDl: $ref: '#/components/schemas/SteeringMode' steerModeUl: $ref: '#/components/schemas/SteeringMode' mulAccCtrl: $ref: '#/components/schemas/MulticastAccessControl' required: - tcId nullable: true C^hargingData: type: object properties: chgId: type: string description: Univocally identifies the charging control policy data within a PDU session. meteringMethod: $ref: '#/components/schemas/MeteringMethod' offline: type: boolean description: Indicates the offline charging is applicable to the PCC rule. online: type: boolean description: Indicates the online charging is applicable to the PCC rule. sdfHandl: t^{ype: boolean} description: Indicates whether the service data flow is allowed to start while the SMF is waiting for the response to the credit request. ratingGroup: $ref: 'TS29571_CommonData.yaml#/components/schemas/RatingGroup' reportingLevel: $ref: '#/components/schemas/ReportingLevel' serviceId: $ref: 'TS29571_CommonData.yaml#/components/schemas/ServiceId' sponsorId: type: string description: Indicates the sponsor identity. appSvcProvId: type: string description: Indicates the application service provider identity. a^{fChargingIdentifier:} $ref: 'TS29571_CommonData.yaml#/components/schemas/ChargingId' afChargId: $ref: 'TS29571_CommonData.yaml#/components/schemas/ApplicationChargingId' required: - chgId nullable: true UsageMonitoringData: type: object properties: umId: type: string description: Univocally identifies the usage monitoring policy data within a PDU session. volumeThreshold: $ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm' volumeThresholdUplink: $ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm' volumeThresholdDownlink: $ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm' timeThreshold: $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' monitoringTime: $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTimeRm' n^{extVolThreshold:} $ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm' nextVolThresholdUplink: $ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm' nextVolThresholdDownlink: $^{ref: 'TS29122_CommonData.yaml#/components/schemas/VolumeRm'} nextTimeThreshold: $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' inactivityTime: $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' exUsagePccRuleIds: type: array items: type: string minItems: 1 description: Contains the PCC rule identifier(s) which corresponding service data flow(s) shall be excluded from PDU Session usage monitoring. It is only included in the UsageMonitoringData instance for session level usage monitoring. nullable: true required: -^umId nullable: true RedirectInformation: type: object properties: redirectEnabled: type: boolean description: Indicates the redirect is enable. redirectAddressType: $ref: '#/components/schemas/RedirectAddressType' redirectServerAddress: type: string description: Indicates the address of the redirect server. FlowInformation: type: object p^roperties: flowDescription: $ref: '#/components/schemas/FlowDescription' ethFlowDescription: $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/EthFlowDescription' packFiltId: type: string description: An identifier of packet filter. packetFilterUsage: type: boolean description: The packet shall be sent to the UE. tosTrafficClass: type: string description: Contains the Ipv4 Type-of-Service and mask field or the Ipv6 Traffic-Class field and mask field. n^{ullable: true} spi: type: string description: the security parameter index of the IPSec packet. nullable: true flowLabel: type: string description: the Ipv6 flow label header field. nullable: true flowDirection: $ref: '#/components/schemas/FlowDirectionRm' SmPolicyDeleteData: type: object properties: userLocationInfo: $ref: 'TS29571_CommonData.yaml#/components/schemas/UserLocation' ueTimeZone: $ref: 'TS29571_CommonData.yaml#/components/schemas/TimeZone' servingNetwork: $ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnIdNid' userLocationInfoTime: $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' ranNasRelCauses: t^{ype: array} items: $ref: '#/components/schemas/RanNasRelCause' minItems: 1 description: Contains the RAN and/or NAS release cause. a^{ccuUsageReports:} type: array items: $ref: '#/components/schemas/AccuUsageReport' minItems: 1 description: Contains the usage report pduSessRelCause: $ref: '#/components/schemas/PduSessionRelCause' QosCharacteristics: type: object properties: 5qi: $ref: 'TS29571_CommonData.yaml#/components/schemas/5Qi' resourceType: $ref: 'TS29571_CommonData.yaml#/components/schemas/QosResourceType' p^{riorityLevel:} $ref: 'TS29571_CommonData.yaml#/components/schemas/5QiPriorityLevel' packetDelayBudget: $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketDelBudget' packetErrorRate: $ref: 'TS29571_CommonData.yaml#/components/schemas/PacketErrRate' averagingWindow: $ref: 'TS29571_CommonData.yaml#/components/schemas/AverWindow' maxDataBurstVol: $ref: 'TS29571_CommonData.yaml#/components/schemas/MaxDataBurstVol' extMaxDataBurstVol: $ref: 'TS29571_CommonData.yaml#/components/schemas/ExtMaxDataBurstVol' required: - 5qi - resourceType -^{priorityLevel} - packetDelayBudget - packetErrorRate ChargingInformation: type: object properties: primaryChfAddress: $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' secondaryChfAddress: $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' primaryChfSetId: $ref: 'TS29571_CommonData.yaml#/components/schemas/NfSetId' primaryChfInstanceId: $ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId' secondaryChfSetId: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/NfSetId'} secondaryChfInstanceId: $ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId' required: - primaryChfAddress - secondaryChfAddress AccuUsageReport: type: object properties: refUmIds: type: string description: An id referencing UsageMonitoringData objects associated with this usage report. volUsage: $ref: 'TS29122_CommonData.yaml#/components/schemas/Volume' volUsageUplink: $ref: 'TS29122_CommonData.yaml#/components/schemas/Volume' volUsageDownlink: $ref: 'TS29122_CommonData.yaml#/components/schemas/Volume' timeUsage: $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec' nextVolUsage: $ref: 'TS29122_CommonData.yaml#/components/schemas/Volume' n^{extVolUsageUplink:} $ref: 'TS29122_CommonData.yaml#/components/schemas/Volume' nextVolUsageDownlink: $ref: 'TS29122_CommonData.yaml#/components/schemas/Volume' nextTimeUsage: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSec'} required: - refUmIds SmPolicyUpdateContextData: type: object properties: repPolicyCtrlReqTriggers: type: array items: $ref: '#/components/schemas/PolicyControlRequestTrigger' minItems: 1 description: The policy control reqeust trigges which are met. accNetChIds: type: array items: $^{ref: '#/components/schemas/AccNetChId'} minItems: 1 description: Indicates the access network charging identifier for the PCC rule(s) or whole PDU session. accessType: $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' ratType: $ref: 'TS29571_CommonData.yaml#/components/schemas/RatType' addAccessInfo: $ref: '#/components/schemas/AdditionalAccessInfo' relAccessInfo: $ref: '#/components/schemas/AdditionalAccessInfo' servingNetwork: $ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnIdNid' userLocationInfo: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/UserLocation'} ueTimeZone: $ref: 'TS29571_CommonData.yaml#/components/schemas/TimeZone' relIpv4Address: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' ipv4Address: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' ipDomain: type: string description: Indicates the IPv4 address domain ipv6AddressPrefix: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix' relIpv6AddressPrefix: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix' addIpv6AddrPrefixes: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix'} addRelIpv6AddrPrefixes: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Prefix' relUeMac: $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' ueMac: $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' subsSessAmbr: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ambr' authProfIndex: type: string description: Indicates the DN-AAA authorization profile index subsDefQos: $ref: 'TS29571_CommonData.yaml#/components/schemas/SubscribedDefaultQos' numOfPackFilter: type: integer description: Contains the number of supported packet filter for signalled QoS rules. accuUsageReports: type: array items: $ref: '#/components/schemas/AccuUsageReport' minItems: 1 description: Contains the usage report 3^{gppPsDataOffStatus:} type: boolean description: If it is included and set to true, the 3GPP PS Data Off is activated by the UE. appDetectionInfos: t^{ype: array} items: $ref: '#/components/schemas/AppDetectionInfo' minItems: 1 description: Report the start/stop of the application traffic and detected SDF descriptions if applicable. ruleReports: type: array items: $ref: '#/components/schemas/RuleReport' minItems: 1 description: Used to report the PCC rule failure. sessRuleReports: type: array items: $^{ref: '#/components/schemas/SessionRuleReport'} minItems: 1 description: Used to report the session rule failure. qncReports: type: array items: $ref: '#/components/schemas/QosNotificationControlInfo' minItems: 1 description: QoS Notification Control information. qosMonReports: type: array items: $ref: '#/components/schemas/QosMonitoringReport' userLocationInfoTime: $ref: 'TS29571_CommonData.yaml#/components/schemas/DateTime' r^epPraInfos: type: object additionalProperties: $ref: 'TS29571_CommonData.yaml#/components/schemas/PresenceInfo' minProperties: 1 description: Reports the changes of presence reporting area. ueInitResReq: $ref: '#/components/schemas/UeInitiatedResourceRequest' refQosIndication: type: boolean description: If it is included and set to true, the reflective QoS is supported by the UE. If it is included and set to false, the reflective QoS is revoked by the UE. qosFlowUsage: $ref: '#/components/schemas/QosFlowUsage' creditManageStatus: $^{ref: '#/components/schemas/CreditManagementStatus'} servNfId: $ref: '#/components/schemas/ServingNfIdentity' traceReq: $ref: 'TS29571_CommonData.yaml#/components/schemas/TraceData' maPduInd: $ref: '#/components/schemas/MaPduIndication' atsssCapab: $ref: '#/components/schemas/AtsssCapability' tsnBridgeInfo: $ref: '#/components/schemas/TsnBridgeInfo' tsnPortManContDstt: $ref: '#/components/schemas/PortManagementContainer' tsnPortManContNwtts: type: array items: $ref: '#/components/schemas/PortManagementContainer' minItems: 1 mulAddrInfos: type: array items: $ref: '#/components/schemas/IpMulticastAddressInfo' minItems: 1 d^ataReports: type: array items: $ref: '#/components/schemas/DataReport' minItems: 1 d^{escription: Contains the status report of policy decision and/or condition data.} UpPathChgEvent: type: object properties: notificationUri: $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' notifCorreId: type: string description: It is used to set the value of Notification Correlation ID in the notification sent by the SMF. dnaiChgType: $ref: 'TS29571_CommonData.yaml#/components/schemas/DnaiChangeType' afAckInd: type: boolean required: -^{notificationUri} - notifCorreId - dnaiChgType nullable: true TerminationNotification: type: object properties: resourceUri: $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' cause: $ref: '#/components/schemas/SmPolicyAssociationReleaseCause' required: - resourceUri - cause AppDetectionInfo: t^{ype: object} properties: appId: type: string description: A reference to the application detection filter configured at the UPF instanceId: type: string description: Identifier sent by the SMF in order to allow correlation of application Start and Stop events to the specific service data flow description, if service data flow descriptions are deducible. sdfDescriptions: type: array items: $ref: '#/components/schemas/FlowInformation' minItems: 1 d^{escription: Contains the detected service data flow descriptions if they are deducible.} required: - appId AccNetChId: type: object properties: accNetChaIdValue: $ref: 'TS29571_CommonData.yaml#/components/schemas/ChargingId' refPccRuleIds: type: array items: type: string minItems: 1 description: Contains the identifier of the PCC rule(s) associated to the provided Access Network Charging Identifier. sessionChScope: type: boolean description: When it is included and set to true, indicates the Access Network Charging Identifier applies to the whole PDU Session required: - accNetChaIdValue AccNetChargingAddress: d^{escription: Describes the network entity within the access network performing charging} type: object anyOf: - required: [anChargIpv4Addr] - required: [anChargIpv6Addr] p^roperties: anChargIpv4Addr: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' anChargIpv6Addr: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Addr' RequestedRuleData: type: object properties: refPccRuleIds: type: array items: type: string minItems: 1 description: An array of PCC rule id references to the PCC rules associated with the control data. r^eqData: type: array items: $ref: '#/components/schemas/RequestedRuleDataType' minItems: 1 description: Array of requested rule data type elements indicating what type of rule data is requested for the corresponding referenced PCC rules. required: - refPccRuleIds - reqData RequestedUsageData: type: object properties: refUmIds: type: array i^tems: type: string minItems: 1 description: An array of usage monitoring data id references to the usage monitoring data instances for which the PCF is requesting a usage report. This attribute shall only be provided when allUmIds is not set to true. allUmIds: type: boolean description: Th44ooleanean indicates whether requested usage data applies to all usage monitoring data instances. When it's not included, it means requested usage data shall only apply to the usage monitoring data instances referenced by the refUmIds attribute. UeCampingRep: type: object properties: accessType: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType'} ratType: $ref: 'TS29571_CommonData.yaml#/components/schemas/RatType' servNfId: $ref: '#/components/schemas/ServingNfIdentity' servingNetwork: $ref: 'TS29571_CommonData.yaml#/components/schemas/PlmnIdNid' userLocationInfo: $ref: 'TS29571_CommonData.yaml#/components/schemas/UserLocation' ueTimeZone: $ref: 'TS29571_CommonData.yaml#/components/schemas/TimeZone' RuleReport: type: object properties: pccRuleIds: type: array items: type: string minItems: 1 description: Contains the identifier of the affected PCC rule(s). ruleStatus: $ref: '#/components/schemas/RuleStatus' contVers: t^{ype: array} items: $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/ContentVersion' minItems: 1 description: Indicates the version of a PCC rule. f^ailureCode: $ref: '#/components/schemas/FailureCode' finUnitAct: $ref: 'TS32291_Nchf_ConvergedCharging.yaml#/components/schemas/FinalUnitAction' ranNasRelCauses: type: array items: $ref: '#/components/schemas/RanNasRelCause' minItems: 1 description: indicates the RAN or NAS release cause code information. required: - pccRuleIds - ruleStatus RanNasRelCause: type: object p^roperties: ngApCause: $ref: 'TS29571_CommonData.yaml#/components/schemas/NgApCause' 5gMmCause: $ref: 'TS29571_CommonData.yaml#/components/schemas/5GMmCause' 5gSmCause: $ref: '#/components/schemas/5GSmCause' UeInitiatedResourceRequest: type: object properties: pccRuleId: type: string ruleOp: $ref: '#/components/schemas/RuleOperation' precedence: t^{ype: integer} packFiltInfo: type: array items: $ref: '#/components/schemas/PacketFilterInfo' minItems: 1 reqQos: $ref: '#/components/schemas/RequestedQos' required: - ruleOp - packFiltInfo PacketFilterInfo: type: object properties: packFiltId: t^{ype: string} description: An identifier of packet filter. packFiltCont: $ref: '#/components/schemas/PacketFilterContent' tosTrafficClass: type: string description: Contains the Ipv4 Type-of-Service and mask field or the Ipv6 Traffic-Class field and mask field. spi: type: string description: The security parameter index of the IPSec packet. flowLabel: type: string description: The Ipv6 flow label header field. flowDirection: $ref: '#/components/schemas/FlowDirection' RequestedQos: type: object properties: 5qi: $ref: 'TS29571_CommonData.yaml#/components/schemas/5Qi' gbrUl: $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' g^brDl: $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRate' required: - 5qi QosNotificationControlInfo: t^{ype: object} properties: refPccRuleIds: type: array items: type: string minItems: 1 description: An array of PCC rule id references to the PCC rules associated with the QoS notification control info. notifType: $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/QosNotifType' contVer: $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/ContentVersion' altQosParamId: type: string r^equired: - refPccRuleIds - notifType PartialSuccessReport: type: object properties: failureCause: $ref: '#/components/schemas/FailureCause' ruleReports: type: array items: $ref: '#/components/schemas/RuleReport' minItems: 1 description: Information about the PCC rules provisioned by the PCF not successfully installed/activated. s^{essRuleReports:} type: array items: $ref: '#/components/schemas/SessionRuleReport' minItems: 1 description: Information about the session rules provisioned by the PCF not successfully installed. ueCampingRep: $ref: '#/components/schemas/UeCampingRep' dataReports: type: array items: $ref: '#/components/schemas/DataReport' minItems: 1 description: Contains the status report of policy decision and/or condition data. r^equired: - failureCause AuthorizedDefaultQos: type: object properties: 5qi: $ref: 'TS29571_CommonData.yaml#/components/schemas/5Qi' arp: $ref: 'TS29571_CommonData.yaml#/components/schemas/Arp' priorityLevel: $ref: 'TS29571_CommonData.yaml#/components/schemas/5QiPriorityLevelRm' averWindow: $ref: 'TS29571_CommonData.yaml#/components/schemas/AverWindowRm' maxDataBurstVol: $ref: 'TS29571_CommonData.yaml#/components/schemas/MaxDataBurstVolRm' maxbrUl: $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' maxbrDl: $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' gbrUl: $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' gbrDl: $ref: 'TS29571_CommonData.yaml#/components/schemas/BitRateRm' q^nc: type: boolean description: Indicates whether notifications are requested from 3GPP NG-RAN when the GFBR can no longer (or again) be guaranteed for a QoS Flow during the lifetime of the QoS Flow. extMaxDataBurstVol: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/ExtMaxDataBurstVolRm'} ErrorReport: type: object properties: error: $ref: 'TS29571_CommonData.yaml#/components/schemas/ProblemDetails' ruleReports: type: array items: $ref: '#/components/schemas/RuleReport' minItems: 1 description: Used to report the PCC rule failure. sessRuleReports: type: array items: $^{ref: '#/components/schemas/SessionRuleReport'} minItems: 1 description: Used to report the session rule failure. dataReports: type: array items: $ref: '#/components/schemas/DataReport' minItems: 1 description: Contains the status report of policy decision and/or condition data SessionRuleReport: type: object properties: ruleIds: type: array items: t^{ype: string} minItems: 1 description: Contains the identifier of the affected session rule(s). ruleStatus: $ref: '#/components/schemas/RuleStatus' sessRuleFailureCode: $ref: '#/components/schemas/SessionRuleFailureCode' required: - ruleIds - ruleStatus ServingNfIdentity: type: object properties: servNfInstId: $ref: 'TS29571_CommonData.yaml#/components/schemas/NfInstanceId' g^uami: $ref: 'TS29571_CommonData.yaml#/components/schemas/Guami' anGwAddr: $ref: 'TS29514_Npcf_PolicyAuthorization.yaml#/components/schemas/AnGwAddress' SteeringMode: type: object properties: steerModeValue: $ref: '#/components/schemas/SteerModeValue' active: $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' standby: $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' 3gLoad: $ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger' prioAcc: $ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType' required: - steerModeValue AdditionalAccessInfo: type: object properties: accessType: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/AccessType'} ratType: $ref: 'TS29571_CommonData.yaml#/components/schemas/RatType' required: - accessType Q^{osMonitoringData:} type: object properties: qmId: type: string description: Univocally identifies the QoS monitoring policy data within a PDU session. reqQosMonParams: type: array items: $ref: '#/components/schemas/RequestedQosMonitoringParameter' minItems: 1 maxItems: 3 description: indicates the UL packet delay, DL packet delay and/or round trip packet delay between the UE and the UPF is to be monitored when the QoS Monitoring for URLLC is enabled for the service data flow.. r^epFreqs: type: array items: $ref: '#/components/schemas/ReportingFrequency' minItems: 1 repThreshDl: type: integer description: Unsigned integer identifying a period of time in units of miliiseconds for DL packet delay. nullable: true repThreshUl: type: integer description: Unsigned integer identifying a period of time in units of miliiseconds for UL packet delay. nullable: true r^epThreshRp: type: integer description: Unsigned integer identifying a period of time in units of miliiseconds for round trip packet delay. nullable: true waitTime: $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' repPeriod: $ref: 'TS29571_CommonData.yaml#/components/schemas/DurationSecRm' notifyUri: $ref: 'TS29571_CommonData.yaml#/components/schemas/Uri' notifyCorreId: type: string required: - qmId n^{ullable: true} QosMonitoringReport: type: object properties: refPccRuleIds: type: array items: type: string minItems: 1 description: An array of PCC rule id references to the PCC rules associated with the QoS monitoring report. ulDelays: type: array items: type: integer dlDelays: type: array items: type: integer rtDelays: type: array items: type: integer r^equired: - refPccRuleIds # TsnBridgeInfo: type: object p^roperties: bridgeName: type: string description: Name of the bridge. bridgeMac: $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' nwttPorts: type: array items: $ref: '#/components/schemas/TsnPortIdentifier' minItems: 1 description: NW-TT ports available for a PDU session. dsttPort: $ref: '#/components/schemas/TsnPortIdentifier' dsttResidTime: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger'} # TsnPortIdentifier: type: object properties: portMac: $ref: 'TS29571_CommonData.yaml#/components/schemas/MacAddr48' portNumber: $ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger' required: - portMac # PortManagementContainer: type: object properties: p^ortManCont: $ref: 'TS29571_CommonData.yaml#/components/schemas/Bytes' portIdentifier: $ref: '#/components/schemas/TsnPortIdentifier' required: - portManCont - portIdentifier IpMulticastAddressInfo: type: object properties: srcIpv4Addr: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' ipv4MulAddr: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv4Addr' srcIpv6Addr: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Addr'} ipv6MulAddr: $ref: 'TS29571_CommonData.yaml#/components/schemas/Ipv6Addr' # DataReport: type: object properties: decType: $ref: '#/components/schemas/DecisionType' dataIds: type: array items: type: string minItems: 1 description: Contains the identifier of the affected policy decision and/or condition data. dataStatus: $ref: '#/components/schemas/DataStatus' required: - decType - dataIds - dataStatus # 5GSmCause: $^{ref: 'TS29571_CommonData.yaml#/components/schemas/Uinteger'} PacketFilterContent: type: string description: Defines a packet filter for an IP flow. Refer to subclause 5.3.54 of 3GPP TS 29.212 for encoding. F^{lowDescription:} type: string description: Defines a packet filter for an IP flow. Refer to subclause 5.4.2 of 3GPP TS 29.212 for encoding. FlowDirection: anyOf: - type: string enum: - DOWNLINK - UPLINK - BIDIRECTIONAL - UNSPECIFIED - type: string description: > This string provides forward-compatibility with future e^{xtensions to the enumeration but is not used to encode} content defined in the present version of this API. description: > Possible values are - DOWNLINK: The corresponding filter applies for traffic to the UE. - UPLINK: The corresponding filter applies for traffic from the UE. - BIDIRECTIONAL: The corresponding filter applies for traffic both to and from the UE. - UNSPECIFIED: The corresponding filter applies for traffic to the UE (downlink), but has no specific direction declared. The service data flow detection shall apply the filter for uplink traffic as if the filter was bidirectional. The PCF shall not use the value UNSPECIFIED in filters created by the network in NW-initiated procedures. The PCF shall only include the value UNSPECIFIED in filters in UE-initiated procedures if the same value is received from the SMF. FlowDirectionRm: anyOf: - $ref: '#/components/schemas/FlowDirection' -^{$ref: 'TS29571_CommonData.yaml#/components/schemas/NullValue'} ReportingLevel: anyOf: - type: string enum: - SER_ID_LEVEL - RAT_GR_LEVEL - SPON_CON_LEVEL - $ref: 'TS29571_CommonData.yaml#/components/schemas/NullValue' - type: string description: > This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API. description: > P^{ossible values are} - SER_ID_LEVEL: Indicates that the usage shall be reported on service id and rating group combination level. - RAT_GR_LEVEL: Indicates that the usage shall be reported on rating group level. - SPON_CON_LEVEL: Indicates that the usage shall be reported on sponsor identity and rating group combination level. MeteringMethod: anyOf: - type: string enum: - DURATION - VOLUME - DURATION_VOLUME - EVENT - $ref: 'TS29571_CommonData.yaml#/components/schemas/NullValue' - type: string description: > This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API. description: > Possible values are - DURATION: Indicates that the duration of the service data flow traffic shall be metered. -^{VOLUME: Indicates that volume of the service data flow traffic shall be metered.} - DURATION_VOLUME: Indicates that the duration and the volume of the service data flow traffic shall be metered. - EVENT: Indicates that events of the service data flow traffic shall be metered. PolicyControlRequestTrigger: a^nyOf: - type: string enum: - PLMN_CH - RES_MO_RE - AC_TY_CH - UE_IP_CH - UE_MAC_CH - AN_CH_COR - US_RE - APP_STA - APP_STO - AN_INFO - CM_SES_FAIL - PS_DA_OFF -^DEF_QOS_CH - SE_AMBR_CH - QOS_NOTIF - NO_CREDIT - REALLO_OF_CREDIT - PRA_CH - SAREA_CH - SCNN_CH - RE_TIMEOUT - RES_RELEASE - SUCC_RES_ALLO - RAT_TY_CH - REF_QOS_IND_CH - NUM_OF_PACKET_FILTER - UE_STATUS_RESUME -^UE_TZ_CH - AUTH_PROF_CH - QOS_MONITORING - SCELL_CH - EPS_FALLBACK - MA_PDU - TSN_ETHER_PORT - TSN_CONTAINER - 5G_RG_JOIN - 5G_RG_LEAVE - type: string description: > This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API. d^{escription: >} Possible values are - PLMN_CH: PLMN Change - RES_MO_RE: A request for resource modification has been received by the SMF. The SMF always reports to the PCF. - AC_TY_CH: Access Type Change - UE_IP_CH: UE IP address change. The SMF always reports to the PCF. - UE_MAC_CH: A new UE MAC address is detected or a used UE MAC address is inactive for a specific period - AN_CH_COR: Access Network Charging Correlation Information - US_RE: The PDU Session or the Monitoring key specific resources consumed by a UE either reached the threshold or needs to be reported for other reasons. - APP_STA: The start of application traffic has been detected. - APP_STO: The stop of application traffic has been detected. - AN_INFO: Access Network Information report - CM_SES_FAIL: Credit management session failure - PS_DA_OFF: The SMF reports when the 3GPP PS Data Off status changes. The SMF always reports to the PCF. - DEF_QOS_CH: Default QoS Change. The SMF always reports to the PCF. - SE_AMBR_CH: Session AMBR Change. The SMF always reports to the PCF. - QOS_NOTIF: The SMF notify the PCF when receiving notification from RAN that QoS targets of the QoS Flow cannot be guranteed or gurateed again. - NO_CREDIT: Out of credit -^{REALLO_OF_CREDIT: Reallocation of credit} - PRA_CH: Change of UE presence in Presence Reporting Area - SAREA_CH: Location Change with respect to the Serving Area - SCNN_CH: Location Change with respect to the Serving CN node - RE_TIMEOUT: Indicates the SMF generated the request because there has been a PCC ^{revalidation timeout} - RES_RELEASE: Indicate that the SMF can inform the PCF of the outcome of the release of resources for those rules that require so. - SUCC_RES_ALLO: Indicates that the requested rule data is the successful resource allocation. - RAT_TY_CH: RAT Type Change. - REF_QOS_IND_CH: Reflective QoS indication Change - NUM_OF_PACKET_FILTER: Indicates that the SMF shall report the number of supported packet filter for signalled QoS rules - UE_STATUS_RESUME: Indicates that the UE’s status is resumed. - UE_TZ_CH: UE Time Zone Change - AUTH_PROF_CH: The DN-AAA authorization profile index has changed - QOS_MONITORING: Indicate that the SMF notifies the PCF of the QoS Monitoring information. - SCELL_CH: Location Change with respect to the Serving Cell. Only applicable to the interworking scenario as defined in Annex B. -^{EPS_FALLBACK: EPS Fallback report is enabled in the SMF.} - MA_PDU: UE Indicates that the SMF notifies the PCF of the MA PDU session request - TSN_ETHER_PORT: Manageable Ethernet port detected - TSN_CONTAINER: Port management container detected. - 5G_RG_JOIN: The 5G-RG has joined to an IP Multicast Group. - 5G_RG_LEAVE: The 5G-RG has left an IP Multicast Group. RequestedRuleDataType: anyOf: - type: string enum: - CH_ID - MS_TIME_ZONE - USER_LOC_INFO - RES_RELEASE - SUCC_RES_ALLO -^EPS_FALLBACK - type: string description: > This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API. description: > Possible values are - CH_ID: Indicates that the requested rule data is the charging identifier. - MS_TIME_ZONE: Indicates that the requested access network info type is the UE's timezone. - USER_LOC_INFO: Indicates that the requested access network info type is the UE's location. - RES_RELEASE: Indicates that the requested rule data is the result of the release of resource. - SUCC_RES_ALLO: Indicates that the requested rule data is the successful resource allocation. -^{EPS_FALLBACK: Indicates that the requested rule data is the report of QoS flow rejection} due to EPS fallback. RuleStatus: anyOf: - type: string enum: - ACTIVE - INACTIVE - type: string description: > This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API. description: > Possible values are - ACTIVE: Indicates that the PCC rule(s) are successfully installed (for those provisioned from PCF) or activated (for those pre-defined in SMF), or the session rule(s) are successfully installed - INACTIVE: Indicates that the PCC rule(s) are removed (for those provisioned from PCF) or inactive (for those pre-defined in SMF) or the session rule(s) are removed. FailureCode: anyOf: - type: string e^num: - UNK_RULE_ID - RA_GR_ERR - SER_ID_ERR - NF_MAL -^RES_LIM - MAX_NR_QoS_FLOW - MISS_FLOW_INFO - RES_ALLO_FAIL - UNSUCC_QOS_VAL - INCOR_FLOW_INFO - PS_TO_CS_HAN - APP_ID_ERR - NO_QOS_FLOW_BOUND - FILTER_RES - MISS_REDI_SER_ADDR - CM_END_USER_SER_DENIED - CM_CREDIT_CON_NOT_APP - CM_AUTH_REJ - CM_USER_UNK -^{CM_RAT_FAILED} - UE_STA_SUSP - type: string description: > This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API. description: > Possible values are - UNK_RULE_ID: Indicates that the pre-provisioned PCC rule could not be successfully activated because the PCC rule identifier is unknown to the SMF. - RA_GR_ERR: Indicate that the PCC rule could not be successfully installed or enforced because the Rating Group specified within the Charging Data policy decision which the PCC rule refers to is unknown or, invalid. - SER_ID_ERR: Indicate that the PCC rule could not be successfully installed or enforced ^{because the Service Identifier specified within the Charging Data policy decision which the PCC rule} refers to is invalid, unknown, or not applicable to the service being charged. - NF_MAL: Indicate that the PCC rule could not be successfully installed (for those provisioned from the PCF) or activated (for those pre-defined in SMF) or enforced (for those already successfully installed) due to SMF/UPF malfunction. - RES_LIM: Indicate that the PCC rule could not be successfully installed (for those provisioned from PCF) or activated (for those pre-defined in SMF) or enforced (for those already successfully installed) due to a limitation of resources at the SMF/UPF. - MAX_NR_QoS_FLOW: Indicate that the PCC rule could not be successfully installed (for those provisioned from PCF) or activated (for those pre-defined in SMF) or enforced (for those already successfully installed) due to the fact that the maximum number of QoS flows has been reached for the PDU session. - MISS_FLOW_INFO: Indicate that the PCC rule could not be successfully installed or enforced because neither the "flowInfos" attribute nor the "appId" attribute is specified within the PccRule data structure by the PCF during the first install request of the PCC rule. -^{RES_ALLO_FAIL: Indicate that the PCC rule could not be successfully installed or} maintained since the QoS flow establishment/modification failed, or the QoS flow was released. - UNSUCC_QOS_VAL: indicate that the QoS validation has failed or when Guaranteed Bandwidth > Max-Requested-Bandwidth. - INCOR_FLOW_INFO: Indicate that the PCC rule could not be successfully installed or modified at the SMF because the provided flow information is not supported by the network (e.g. the provided IP address(es) or Ipv6 prefix(es) do not correspond to an IP version applicable for the PDU session). - PS_TO_CS_HAN: Indicate that the PCC rule could not be maintained because of PS to CS handover. - APP_ID_ERR: Indicate that the rule could not be successfully installed or enforced because the Application Identifier is invalid, unknown, or not applicable to the application required for detection. - NO_QOS_FLOW_BOUND: Indicate that there is no QoS flow which the SMF can bind the PCC rule(s) to. - FILTER_RES: Indicate that the Flow Information within the "flowInfos" attribute cannot be handled by the SMF because any of the restrictions defined in subclause 5.4.2 of 3GPP TS 29.212 was not met. - MISS_REDI_SER_ADDR: Indicate that the PCC rule could not be successfully installed or enforced at the SMF because there is no valid Redirect Server Address within the Traffic Control Data policy decision which the PCC rule refers to provided by the PCF and no preconfigured redirection address for this PCC rule at the SMF. -^{CM_END_USER_SER_DENIED: Indicate that the charging system denied the service request due} to service restrictions (e.g. terminate rating group) or limitations related to the end-user, for example the end-user's account could not cover the requested service. - CM_CREDIT_CON_NOT_APP: Indicate that the charging system determined that the service can be granted to the end user but no further credit control is needed for the service (e.g. service is ^{free of charge or is treated for offline charging).} - CM_AUTH_REJ: Indicate that the charging system denied the service request in order to terminate the service for which credit is requested. - CM_USER_UNK: Indicate that the specified end user could not be found in the charging system. - CM_RAT_FAILED: Indicate that the charging system cannot rate the service request due to insufficient rating input, incorrect AVP combination or due to an attribute or an attribute value that is not recognized or supported in the rating. - UE_STA_SUSP: Indicates that the UE is in suspend state. AfSigProtocol: anyOf: - type: string enum: - NO_INFORMATION - SIP -^{$ref: 'TS29571_CommonData.yaml#/components/schemas/NullValue'} - type: string description: > This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API. description: > Possible values are - NO_INFORMATION: Indicate that no information about the AF signalling protocol is being provided. - SIP: Indicate that the signalling protocol is Session Initiation Protocol. RuleOperation: anyOf: - type: string enum: -^{CREATE_PCC_RULE} - DELETE_PCC_RULE - MODIFY_PCC_RULE_AND_ADD_PACKET_FILTERS - MODIFY_ PCC_RULE_AND_REPLACE_PACKET_FILTERS - MODIFY_ PCC_RULE_AND_DELETE_PACKET_FILTERS - MODIFY_PCC_RULE_WITHOUT_MODIFY_PACKET_FILTERS - type: string description: > This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API. description: > Possible values are - CREATE_PCC_RULE: Indicates to create a new PCC rule to reserve the resource requested by the UE. -^{DELETE_PCC_RULE: Indicates to delete a PCC rule corresponding to reserve the resource} requested by the UE.. - MODIFY_PCC_RULE_AND_ADD_PACKET_FILTERS: Indicates to modify the PCC rule by adding new packet filter(s). - MODIFY_ PCC_RULE_AND_REPLACE_PACKET_FILTERS: Indicates to modify the PCC rule by replacing the existing packet filter(s). - MODIFY_ PCC_RULE_AND_DELETE_PACKET_FILTERS: Indicates to modify the PCC rule by deleting the existing packet filter(s). - MODIFY_PCC_RULE_WITHOUT_MODIFY_PACKET_FILTERS: Indicates to modify the PCC rule by modifying the QoS of the PCC rule. RedirectAddressType: anyOf: - type: string enum: - IPV4_ADDR - IPV6_ADDR - URL - SIP_URI - type: string description: > This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API. d^{escription: >} Possible values are - IPV4_ADDR: Indicates that the address type is in the form of "dotted-decimal" IPv4 address. - IPV6_ADDR: Indicates that the address type is in the form of IPv6 address. - URL: Indicates that the address type is in the form of Uniform Resource Locator. -^{SIP_URI: Indicates that the address type is in the form of SIP Uniform Resource Identifier.} QosFlowUsage: anyOf: - type: string enum: - GENERAL - IMS_SIG - type: string description: > This string provides forward-compatibility with future extensions to the enumeration but is not used to encode content defined in the present version of this API. description: > Possible values are - GENERAL: Indicate no specific QoS flow usage information is available. -^{IMS_SIG: Indicate that the QoS flow is used for IMS signalling only.} FailureCause: anyOf: - type: string enum: - PCC_RULE_EVENT - PCC_QOS_FLOW_EVENT - RULE_PERMANENT_ERROR - RULE_TEMPORARY_ERROR - type: string CreditManagementStatus: anyOf: - type: string enum: - END_USER_SER_DENIED -^{CREDIT_CTRL_NOT_APP} - AUTH_REJECTED - USER_UNKNOWN - RATING_FAILED - type: string SessionRuleFailureCode: anyOf: - type: string enum: - NF_MAL - RES_LIM - UNSUCC_QOS_VAL - UE_STA_SUSP - type: string description: > T^{his string provides forward-compatibility with future} extensions to the enumeration but is not used to encode content defined in the present version of this API. description: > Possible values are - NF_MAL: Indicate that the PCC rule could not be successfully installed (for those provisioned from the PCF) or activated (for those pre-defined in SMF) or enforced (for those already successfully installed) due to SMF/UPF malfunction. - RES_LIM: Indicate that the PCC rule could not be successfully installed (for those provisioned from PCF) or activated (for those pre-defined in SMF) or enforced (for those already successfully installed) due to a limitation of resources at the SMF/UPF. - UNSUCC_QOS_VAL: indicate that the QoS validation has failed. - UE_STA_SUSP: Indicates that the UE is in suspend state. SteeringFunctionality: anyOf: - type: string enum: - MPTCP - ATSSS_LL - type: string description: > This string provides forward-compatibility with future extensions to the enumeration but is not used to encode c^{ontent defined in the present version of this API.} description: > Possible values are - MPTCP: Indicates that PCF authorizes the MPTCP functionality to support traffic steering, switching and splitting. -^{ATSSS_LL: Indicates that PCF authorizes the ATSSS-LL functionality to support traffic} steering, switching and splitting. SteerModeValue: anyOf: - type: string enum: - ACTIVE_STANDBY - LOAD_BALANCING - SMALLEST_DELAY - PRIORITY_BASED - type: string MulticastAccessControl: anyOf: - type: string enum: -^ALLOWED - NOT_ALLOWED - type: string RequestedQosMonitoringParameter: anyOf: - type: string enum: - DOWNLINK - UPLINK - ROUND_TRIP - type: string ReportingFrequency: anyOf: - type: string enum: -^{EVENT_TRIGGERED} - PERIODIC - SESSION_RELEASE - type: string SmPolicyAssociationReleaseCause: anyOf: - type: string enum: - UNSPECIFIED - UE_SUBSCRIPTION - INSUFFICIENT_RES - VALIDATION_CONDITION_NOT_MET - type: string PduSessionRelCause: anyOf: -^{type: string} enum: - PS_TO_CS_HO - type: string MaPduIndication: anyOf: - type: string enum: - MA_PDU_REQUEST - MA_PDU_ NETWORK_UPGRADE ALLOWED - type: string AtsssCapability: anyOf: - type: string enum: - MPTCP_ATSSS_LL_WITH_ASMODE_UL - MPTCP_ATSSS_LL_WITH_ASMODE_DLUL - ATSSS_LL - MPTCP_ATSSS_LL - type: string DecisionType: anyOf: - type: string e^num: - TRAFFIC_CTRL - QOS - CHARGING - USAGE_MON -^QOS_MON - CONDITION - type: string DataStatus: anyOf: - type: string enum: - KEPT - REMOVAL - type: string # *******************************END FOURTEENTH CHANGE ************************************ Figure 6 [0057] Figure 6 is a schematic block diagram of a network node 600 according to some embodiments of the present disclosure. Optional features are represented by dashed boxes. The network node 600 may be, for example, a network node that implements all or part of the functionality of a core NF such as, e.g., the SMF 208 and PCF 210 described above. As illustrated, the network node 600 includes one or more processors 604 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like), memory 606, and a network interface 608. The one or more processors 604 are also referred to herein as processing circuitry. The one or more processors 604 operate to provide one or more functions of the network node 600 as described herein (e.g., one or more functions of a SMF (e.g., SMF 208) or a PCF (e.g., PCF 210) as described herein, e.g., with respect to Figure 4 and/or Figure 5). In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 606 and executed by the one or more processors 604. Figure 7 [0058] Figure 7 is a schematic block diagram that illustrates a virtualized embodiment of the network node 600 according to some embodiments of the present disclosure. As used herein, a “virtualized” network node is an implementation of the network node 600 in which at least a portion of the functionality of the network node 600 is implemented as a virtual component(s) (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the network node 600 includes one or more processing nodes 700 coupled to or included as part of a network(s) 702. Each processing node 700 includes one or more processors 704 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 706, and a network interface 708. [0059] In this example, functions 710 of the network node 600 described herein (e.g., one or more functions of a SMF (e.g., SMF 208) or a PCF (e.g., PCF 210) as described herein, e.g., with respect to Figure 4 and/or Figure 5) are implemented at the one or more processing nodes 700 or distributed across the two or more processing nodes 700 in any desired manner. In some particular embodiments, some or all of the functions 710 of the network node 600 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 700. [0060] In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the network node 600 or a node (e.g., a processing node 700) implementing one or more of the functions 710 of the network node 600 in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory). Figure 8 [0061] Figure 8 is a schematic block diagram of the network node 600 according to some other embodiments of the present disclosure. The network node 600 includes one or more modules 800, each of which is implemented in software. The module(s) 800 provide the functionality of the network node 600 described herein (e.g., one or more functions of a SMF (e.g., SMF 208) or a PCF (e.g., PCF 210) as described herein, e.g., with respect to Figure 4 and/or Figure 5). This discussion is equally applicable to the processing node 700 of Figure 7 where the modules 800 may be implemented at one of the processing nodes 700 or distributed across multiple processing nodes 700. [0062] Any appropriate steps, methods, features, functions, or benefits disclosed herein may be performed through one or more functional units or modules of one or more virtual apparatuses. Each virtual apparatus may comprise a number of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include Digital Signal Processor (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as Read Only Memory (ROM), Random Access Memory (RAM), cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions according one or more embodiments of the present disclosure. [0063] While processes in the figures may show a particular order of operations performed by certain embodiments of the present disclosure, it should be understood that such order is exemplary (e.g., alternative embodiments may perform the operations in a different order, combine certain operations, overlap certain operations, etc.).

SOME EMBODIMENTS Some embodiments that have been described above can be summarized in the following manner: 1. A method performed by first network function (208) in a core network (110) of a cellular communications system (100), the method comprising: receiving (406; 502) a first message from a second network function (210) in the core network (110), the first message comprising a Session Management, SM, policy decision; determining (408; 504) that there is an error associated with the SM policy decision, the error being either a validation error or an enforcement failure other than a PCC rule error and a session rule error; and sending (410; 506) a second message to the second network function (210), the second message comprising an error report that indicates the determined error. 2. The method of embodiment 1 further comprising receiving (412; 510) a third message from the second network function (210), the third message comprising a new SM policy decision and/or a corrected SM policy decision. 3. The method of embodiment 1 or 2 wherein the first network function (208) is a Session Management Function, SMF, (208), and the second network function (210) is a Policy Control Function, PCF, (210). 4. The method of embodiment 3 wherein the first message is a SM Policy Control Update Response, and the second message is a SM Policy Control Update Request. 5. The method of embodiment 4 further comprising, prior to receiving (406) the first message, sending (404), to the second network function, a SM Policy Control Update Request. 6. The method of embodiment 3 wherein the first message is an SM Policy Control Update Notify Request, and the second message is an SM Policy Control Update Notify Response. 7. The method of any of embodiments 1 to 6 wherein the determined error is one of a plurality of predefined possible errors, and the error report is an SM policy decision error report that comprises a value that indicates the one of the plurality of predefined possible errors. 8. The method of embodiment 7 wherein the plurality of predefined possible errors comprise: a. a Quality of Service, QoS, decision error; b. a charging decision error; c. a usage monitoring decision error; d. a Presence Reporting Area, PRA, error; or e. a combination of any two or more of (a)-(d). 9. A method performed by second network function (210) in a core network (110) of a cellular communications system (100), the method comprising: sending (406; 502) a first message to a first network function (208) in the core network (110), the first message comprising a Session Management, SM, policy decision; and receiving (410; 506) a second message from the first network function (208), the second message comprising an error report that indicates the determined error. 10. The method of embodiment 9 further comprising sending (412; 510) a third message to the first network function (208), the third message comprising a new SM policy decision and/or a corrected SM policy decision. 11. The method of embodiment 9 or 10 wherein the first network function (208) is a Session Management Function, SMF, (208), and the second network function (210) is a Policy Control Function, PCF, (210). 12. The method of embodiment 11 wherein the first message is a SM Policy Control Update Response, and the second message is a SM Policy Control Update Request. 13. The method of embodiment 12 further comprising, prior to sending (406) the first message, receiving (404), from the first network function, a SM Policy Control Update Request. 14. The method of embodiment 11 wherein the first message is an SM Policy Control Update Notify Request, and the second message is an SM Policy Control Update Notify Response. 15. The method of any of embodiments 9 to 14 wherein the determined error is one of a plurality of predefined possible errors, and the error report is an SM policy decision error report that comprises a value that indicates the one of the plurality of predefined possible errors. 16. The method of embodiment 15 wherein the plurality of predefined possible errors comprise: a. a Quality of Service, QoS, decision error; b. a charging decision error; c. a usage monitoring decision error; d. a Presence Reporting Area, PRA, error; or e. a combination of any two or more of (a)-(d). 17. A network node (600) that implements a first network function (208) for a core network (110) of a cellular communications system (100), the network node (600) adapted to perform the method of any of embodiments 1 to 8. 18. A network node (600) that implements a first network function (208) for a core network (110) of a cellular communications system (100), the network node (600) comprising processing circuitry (604; 704) configured to cause the network node (600) to perform the method of any of embodiments 1 to 8. 19. A network node (600) that implements a second network function (210) for a core network (110) of a cellular communications system (100), the network node (600) adapted to perform the method of any of embodiments 9 to 16. 20. A network node (600) that implements a second network function (210) for a core network (110) of a cellular communications system (100), the network node (600) comprising processing circuitry (604; 704) configured to cause the network node (600) to perform the method of any of embodiments 9 to 16.

Abbreviations At least some of the following abbreviations may be used in this disclosure. If there is an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s). • 3GPP Third Generation Partnership Project • 5G Fifth Generation • 5GC Fifth Generation Core • 5GS Fifth Generation System • AF Application Function • AMF Access and Mobility Management Function • AN Access Network • AUSF Authentication Server Function • DN Data Network • gNB New Radio Base Station • HSS Home Subscriber Server • NEF Network Exposure Function • NF Network Function • NR New Radio • NRF Network Function Repository Function • NSSF Network Slice Selection Function • PCF Policy Control Function • QoS Quality of Service • RAN Radio Access Network • SCEF Service Capability Exposure Function • SMF Session Management Function • UDM Unified Data Management • UE User Equipment • UPF User Plane Function

Claims

CLAIMS What is claimed is: 1. A method performed by first network function (208) in a core network (110) of a cellular communications system (100), the method comprising: receiving (406; 502) a first message from a second network function (210) in the core network (110), the first message comprising a Session Management, SM, policy decision; determining (408; 504) that there is an error associated with the SM policy decision, the error being either a validation error or an enforcement failure other than a PCC rule error and a session rule error; and sending (410; 506) a second message to the second network function (210), the second message comprising an error report that indicates the determined error.

2. The method of claim 1 further comprising receiving (412; 510) a third message from the second network function (210), the third message comprising a new SM policy decision and/or a corrected SM policy decision.

3. The method of claim 1 or 2 wherein the first network function (208) is a Session Management Function, SMF, (208), and the second network function (210) is a Policy Control Function, PCF, (210).

4. The method of claim 3 wherein the first message is a SM Policy Control Update Response, and the second message is a SM Policy Control Update Request.

5. The method of claim 4 further comprising, prior to receiving (406) the first message, sending (404), to the second network function, a SM Policy Control Update Request.

6. The method of claim 3 wherein the first message is an SM Policy Control Update Notify Request, and the second message is an SM Policy Control Update Notify Response.

7. The method of any one of claim 1 to 6 wherein the determined error is one of a plurality of predefined possible errors, and the error report is an SM policy decision error report that comprises a value that indicates the one of the plurality of predefined possible errors.

8. The method of claim 7 wherein the plurality of predefined possible errors comprise: a. a Quality of Service, QoS, decision error; b. a charging decision error; c. a usage monitoring decision error; d. a Presence Reporting Area, PRA, error; or e. a combination of any two or more of (a)-(d).

9. A method performed by second network function (210) in a core network (110) of a cellular communications system (100), the method comprising: sending (406; 502) a first message to a first network function (208) in the core network (110), the first message comprising a Session Management, SM, policy decision; and receiving (410; 506) a second message from the first network function (208), the second message comprising an error report that indicates the determined error.

10. The method of claim 9 further comprising sending (412; 510) a third message to the first network function (208), the third message comprising a new SM policy decision and/or a corrected SM policy decision.

11. The method of claim 9 or 10 wherein the first network function (208) is a Session Management Function, SMF, (208), and the second network function (210) is a Policy Control Function, PCF, (210).

12. The method of claim 11 wherein the first message is a SM Policy Control Update Response, and the second message is a SM Policy Control Update Request.

13. The method of claim 12 further comprising, prior to sending (406) the first message, receiving (404), from the first network function, a SM Policy Control Update Request.

14. The method of claim 11 wherein the first message is an SM Policy Control Update Notify Request, and the second message is an SM Policy Control Update Notify Response.

15. The method of any one of claims 9 to 14 wherein the determined error is one of a plurality of predefined possible errors, and the error report is an SM policy decision error report that comprises a value that indicates the one of the plurality of predefined possible errors.

16. The method of claim 15 wherein the plurality of predefined possible errors comprise: a. a Quality of Service, QoS, decision error; b. a charging decision error; c. a usage monitoring decision error; d. a Presence Reporting Area, PRA, error; or e. a combination of any two or more of (a)-(d).

17. A network node (600) that implements a first network function (208) for a core network (110) of a cellular communications system (100), the network node (600) adapted to perform the method of any one of claim 1 to 8.

18. A network node (600) that implements a first network function (208) for a core network (110) of a cellular communications system (100), the network node (600) comprising processing circuitry (604; 704) configured to cause the network node (600) to perform the method of any one of claim 1 to 8.

19. A network node (600) that implements a second network function (210) for a core network (110) of a cellular communications system (100), the network node (600) adapted to perform the method of any one of claim 9 to 16.

20. A network node (600) that implements a second network function (210) for a core network (110) of a cellular communications system (100), the network node (600) comprising processing circuitry (604; 704) configured to cause the network node (600) to perform the method of any one of claim 9 to 16.