SMPolicy Data Model
The UDRs in the PCF.SMPolicy data model store information about different rules regarding the session management in 5G networks.
The main objects of PCF.SMPolicy are:
Object | Description |
---|---|
RulesMapping | A flexible mapping table used to map from an external representation to a list of rules. The mapping should not include any information related to a specific subscriber. |
Target | The different rules used by the mapping object, see the sections |
PCCRule | Rules contains the rule settings regarding session management that should be applied for the subscribers. |
SessionRule | A session rule consists of policy information elements associated with PDU session. A session rule is dynamically provisioned by the PCF to the SMF (i.e., there are only dynamic session rules). |
This page contains the following sections:
Overview of the SMPolicy Data Model
The different UDRs within the SMPolicy data model are connected as follows:
Overview of the PCF Rules Data Model
RulesMapping UDR
In the RulesMapping
UDR you set up the priority for the rules mapping, the PCF rules to be applied, products to connect to, etc that the RulesMapping
should use.
Field | Description |
---|---|
| The unique ID of the |
| The priority of the mapping item. A low value indicates a high priority. The priority determines the order in which the matched mapping objects are returned. |
| The arguments of a mapping object, for example the product. The arguments are stated with regular expressions, which means that entering "Products [2-5]" will match Products 2, 3, 4, or 5. |
| A list of A rule is a set of policy information elements associated with a PDU session, or with service data flows (i.e., with a PCC rule). Two types of rules are defined:
Both Session rules and PCC rules are composed of embedded information elements as well as information elements that are part of the referenced objects, for example condition data, or usage monitoring policy data. |
| Used in the rules selection process. If several rules apply, but the one with highest priority has been configured with |
Below is a screenshot of the UDR Assistance displaying the RulesMapping
UDR:
RulesMapping UDR
Target UDR
With the Target
UDR you define different SMPolicyDecisions, according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The unique ID of the |
| The name of the target. |
| The |
| A list of This attribute shall not be removed if it was provisioned. |
| A list of |
| A list of of This attribute shall not be removed if it was provisioned. |
| A list of |
| A list of This attribute shall not be removed if it was provisioned. |
| A list of |
| A list of |
| A list of QosMonitoringData UDRs with policy decisions that should be used. |
| "Indicates if the offline charging is applicable to the PDU session when it is included and set to true. This attribute may only be supplied by the PCF in the response to the POST request that requested the creation of an individual SM policy resource. If both the "offline" attribute and the "online" attribute is omitted by the PCF, the default charging method pre-configured at the SMF if available shall be applied to the PDU session. If both offline and online charging methods are pre-configured at the SMF, the SMF shall determine either of them to be applied to the PDU session based on local policy. The “offline” attribute and the “online” attribute shall not be simultaneously present with the same value, i.e., both set to true or both set to false." |
| "Indicates the online charging is applicable to the PDU session when it is included and set to true. This attribute may only be supplied by the PCF in the response to the POST request that requested the creation of an individual SM policy resource. If both the "offline" attribute and the "online" attribute is omitted by the PCF, the default charging method pre- configured at the SMF if available shall be applied to the PDU session. If both offline and online charging methods are pre-configured at the SMF, the SMF shall determine either of them to be applied to the PDU session based on local policy. The “offline” attribute and the “online” attribute shall not be simultaneously present with the same value, i.e., both set to true or both set to false." |
| A list of |
Below is a screenshot of the UDR Assistance displaying the Target
UDR:
Target UDR
SessionRule UDR
The SessionRule
UDR contains session level policy information, according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
A session rule consists of policy information elements associated with PDU session. A session rule is dynamically provisioned by the PCF to the SMF (i.e., there are only dynamic session rules).
Field | Description |
---|---|
| The unique ID of the |
| The name of the session rule. |
| The |
| The |
sessRuleID (string) | "The identifier for the session rule used within the PDU session." |
| "A reference to the UsageMonitoringData policy decision type." |
| "A reference to the UsageMonitoringData policy decision type to apply for Non- 3GPP access. If |
| "A reference to the condition data." |
Below is a screenshot of the UDR Assistance displaying the SessionRule
UDR:
SessionRule UDR
Ambr UDR
The Ambr
UDR defines the Aggregate Maximum Bit Rate , according to 3GPP specification TS 29.512 v. 16.8.0 and 3GPP specification TS 29.571 v. 15.3.0. Descriptions from these specifications are in quotation marks.
Field | Description |
---|---|
| The unique ID of the |
Name (string) | The name of the |
| "Defines the AMBR for uplink." |
| "Defines the AMBR for downlink. |
| "Determines whether the resource type is:
|
| "Unsigned integer indicating the 5QI Priority Level, within a range of 1 to 127." |
| "Defines the Packet Delay Budget, expressed in milliseconds. |
| "Defines the Packet Error Rate, expressed as a "scalar x 10-k" where the scalar and the exponent k are each encoded as one decimal digit.. Pattern: '^([0-9]E-[0-9])$' Examples: |
| "Defines the Averaging Window, expressed in milliseconds. |
| "Defines the Maximum Data Burst Volume, expressed in Bytes. |
Below is a screenshot of the UDR Assistance displaying the Ambr
UDR:
Ambr UDR
AuthorizedDefaultQos UDR
In the AuthorizedDefaultQos
UDR contains the Authorized Default QoS information according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The unique ID of the |
| The name of the |
| "5G QoS Identifier. It shall be included when the Authorized Default QoS is initially provisioned." |
| "The Arp UDR defining the allocation and retention priority to be used. It shall be included when the Authorized Default QoS is initially provisioned." |
| "Unsigned integer indicating the 5QI Priority Level, within a range of 1 to 127." |
| "Indicates the averaging window. This IE can be present only for GBR QoS flow or a Delay Critical GBR QoS flow." |
| "Unsigned integer indicating the maximum data burst volume. Either the maxDataBurstVol IE or the extMaxDataBurstVol IE may be present for a Delay Critical GBR QoS flow. If the maximum data burst volume value to be transmitted is lower than or equal to 4095 Bytes, the maxDataBurst Vol IE is used. If the EMDBV feature is supported by both the PCF and the SMF, the extMaxDataBurstVol IE is used to transmit maximum data burst volume values higher than 4095 Bytes." |
| "Indicates the guaranteed bandwidth in uplink. This attribute is only applicable to GBR type or delay critical GBR type 5QI." |
| "Indicates the guaranteed bandwidth in downlink. This attribute is only applicable to GBR type or delay critical GBR type 5QI." |
| "Indicates the max bandwidth in uplink. This attribute is only applicable to GBR type or delay critical GBR type 5QI." |
| "Indicates the max bandwidth in downlink. This attribute is only applicable to GBR type or delay critical GBR type 5QI." |
| "The QNC, QoS Notification Control, according to 3GPP 23.503 v. 15.2.0, indicates whether notifications are requested from 3GPP RAN when the GFBR can no longer (or again) be fulfilled for a QoS Flow during the lifetime of the QoS Flow." |
| "Unsigned integer indicating the maximum data burst volume. Either the maxDataBurstVol IE or the extMaxDataBurstVol IE may be present for a Delay Critical GBR QoS flow. If the maximum data burst volume value to be transmitted is lower than or equal to 4095 Bytes, the maxDataBurst Vol IE is used. If the EMDBV feature is supported by both the PCF and the SMF, the extMaxDataBurstVol IE is used to transmit maximum data burst volume values higher than 4095 Bytes. " |
Below is a screenshot of the UDR Assistance displaying the AuthorizedDefaultQos
UDR:
AuthorizedDefaultQos UDR
Arp UDR
In the Arp
UDR you define the Allocation and Retention Priority, according to 3GPP specification TS 29.571 v. 15.3.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The unique ID of the |
| "Defines the relative importance of a resource request." |
| "Defines whether a service data flow may get resources that were already assigned to another service data flow with a lower priority level." |
| "Defines whether a service data flow may lose the resources assigned to it in order to admit a service data flow with higher priority level." |
Below is a screenshot of the UDR Assistance displaying the Arp
UDR:
Arp UDR
PCCRule UDR
The PCCRule UDR contains the PCC rule information according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
"A PCC rule is a set of information elements enabling the detection of a service data flow and providing parameters for policy control and/or charging control.
There are two different types of PCC rules as defined in 3GPP TS 23.503:
Dynamic PCC rules
PCC rules that are dynamically provisioned by the PCF to the SMF. These PCC rules may be either predefined or dynamically generated in the PCF. Dynamic PCC rules can be installed, modified and removed at any time.Predefined PCC rules
PCC rules that are preconfigured in the SMF. Predefined PCC rules can be activated or deactivated by the PCF at any time. Predefined PCC rules within the PCF may be grouped allowing the PCF to dynamically activate a set of PCC rules.
Additionally, predefined PCC rules may be grouped within the SMF as predefined PCC rule bases which allow the PCF to dynamically activate these sets of rules. In this case, the PCC rule identifier is used to hold the predefined PCC rule base identifier."
Field | Description |
---|---|
| The unique ID of the PCC rule. |
| The name of the PCC rule. |
| "A list of The property is only applicable for the NEF." |
| "A reference to the application detection filter configured at the UPF. The property is only applicable for the NEF." |
| "ATSSS rule application descriptor. It shall be present when the PDU session is a MA PDU session and the SDF template contains an Application Identifier (i.e. when the "appId" attribute is present)." |
| "Indicates the content version of the PCC rule." |
| "Univocally identifies the PCC rule within a PDU session. The PCC Rule Id uniquely identifies the PCC rule, within a PDU Session. It is used between PCF and SMF for referencing PCC rules." |
| "Determines the order in which this PCC rule is applied relative to other PCC rules within the same PDU session. It shall be included if the "flowInfos" attribute is included or may be included if the "appId" attribute is included when the PCF initially provisions the PCC rule. One of "ueIpv4Addr", "ueIpv6Addr" or "macAddr" shall be included. If ipv4 or ipv6 address is provided, IP flow information shall be provided. If MAC address is provided and the AppId feature is not supported, Ethernet flow information (either "ethFlowInfo", or if the feature EnEthAsSessionQoS_5G is supported, "enEthFlowInfo")shall be provided. If the AppId feature is supported, one of IP flow information, Ethernet flow information (if EthAsSessionQoS_5G and/or EnEthAsSessionQoS_5G is supported) or External Application Identifier shall be provided." |
| "Indicates the protocol used for signalling between the UE and the AF. The default value "NO_INFORMATION" shall apply, if the attribute is not present and has not been supplied previously." |
| "It indicates that the application cannot be relocated once a location of the application is selected by the 5GC when it is included and set to "true". Indication of application relocation possibility. The default value "false" shall apply, if the attribute is not present and has not been supplied previously." |
| "Indicates whether UE IP address should be preserved. |
| "A reference to the QoSData policy type decision type. Properties marked with a feature are applicable. If no features are indicated, the related property applies for all the features." |
| "A Reference to the QoS Data policy decision type for the Alternative QoS parameter sets of the service data flow. Only the "qosId" attribute, "5qi" attribute, "maxbrUl" attribute, "maxbrDl" attribute, "gbrUl" attribute and "gbrDl" attribute are applicable within the QosData data type. This data type represents an ordered list, where the lower the index of the array for a given entry, the higher the priority." |
| "A reference to the TrafficControlData policy decision type. Properties marked with a feature are applicable. If no features are indicated, the related property applies for all the features." |
| "A reference to the ChargingData policy decision type. Properties marked with a feature are applicable. If no features are indicated, the related property applies for all the features." |
| "A reference to the ChargingData policy decision type only applicable to Non-3GPP access. Properties marked with a feature are applicable. If no features are indicated, the related property applies for all the features. The attributes "reqGbrDl", "reqGbrUl", "reqMbrDl", "reqMbrUl", "maxTscBurstSize", "req5Gsdelay", "reqPer" (if the ExtQoS_5G feature is supported), and "priority" within the "tscQosReq" attribute may be provided only if the "qosReference" attribute is not provided." |
| "A reference to UsageMonitoringData policy decision type. Properties marked with a feature are applicable. If no features are indicated, the related property applies for all the features." |
| "A reference to UsageMonitoringData policy decision type only applicable to Non-3GPP access. When the Ethernet flow information is provided and, the EthAsSessionQoS_5G and EnEthAsSessionQoS_5G features are supported, either the "ethFlowInfo" or the "enEthFlowInfo" shall be provided, but not both simultenously." |
| "A reference to the condition data." |
| "A reference to QoSMonitoringData policy decision type. Properties marked with a feature are applicable. If no features are indicated, the related property applies for all the features." |
| "The |
| "The |
| "The first |
| "The second |
| "Indicates whether to disable QoS flow parameters signalling to the UE when the SMF is notified by the NG-RAN of changes in the fulfilled QoS situation. The fulfilled situation is either the QoS profile or an Alternative QoS Profile. - true: the QoS flow parameters signalling to the UE is disabled; - false (default): the QoS flow parameters signalling to the UE is not disabled." |
Below is a screenshot of the UDR Assistance displaying the PccRules
UDR:
PccRules UDR
FlowInformation UDR
The FlowInformation
UDR contains the flow information, according to 3GPP specification TS 29.512 v. 16.8.0 and 3GPP TS 24.008 v. 13.7.0. Descriptions from these specifications are in quotation marks.
Field | Description |
---|---|
| The unique ID of the |
| "Contains the packet filters of the IP flow(s)." |
| "Defines the |
| "An identifier of packet filter." |
| "The packet shall be sent to the UE. The default value "FALSE" shall apply, if the attribute is not present and has not been supplied previously." |
| "2-octet string. The first octet contains the Ipv4 Type-of-Service or the Ipv6 Traffic-Class field and the second octet contains the ToS/Traffic mask field in hexadecimal representation. Each character in the string shall take a value of "0" to "9" or "A" to "F" and shall represent 4 bits. One example is that of a TFT packet filter as defined in 3GPP 3GPP TS 24.008 v. 13.7.0." |
| "4 octet string, representing the security parameter index of the IPSec packet in hexadecimal representation. Each character in the string shall take a value of "0" to "9" or "A" to "F" and shall represent 4 bits. One example is that of a TFT packet filter as defined in 3GPP TS 24.008 v. 13.7.0." |
| "3-octet string, representing the Ipv6 flow label header field in hexadecimal representation. Each character in the string shall take a value of "0" to "9" or "A" to "F" and shall represent 4 bits. One example is that of a TFT packet filter as defined in 3GPP 3GPP TS 24.008 v. 13.7.0." |
| "Indicates the direction/directions that a filter is applicable, downlink only, uplink only or both down- and uplink (bidirectional)." |
Below is a screenshot of the UDR Assistance displaying the FlowInformation
UDR:
FlowInformation UDR
EthFlowDescription UDR
The EthFlowDescription
UDR defines a packet filter for an Ethernet flow, according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The unique ID of the |
| "Destination MAC address." |
| "Contains the flow description for the Uplink or Downlink IP flow. It shall be present when the Ethertype is IP." |
| "Contains the packet filter direction. Only the "DOWNLINK" or "UPLINK" value is applicable." |
| "Source MAC address." |
| "Source MAC address end. If this attribute is present, the sourceMacAddr attribute specifies the source MAC address start. E.g. srcMacAddrEnd with value 00-10-A4-23-3E-FE and sourceMacAddr with value 00-10-A4-23-3E-02 means all MAC addresses from 00-10-A4-23-3E-02 up to and including 00-10-A4-23-3E-FE." |
| "Customer-VLAN and/or Service-VLAN tags containing the VID, PCP/DEI fields as defined in IEEE 802.1Q [17] and IETF RFC 7042 [18]. The first/lower instance in the array stands for the Customer-VLAN tag and the second/higher instance in the array stands for the Service-VLAN tag. Each field is encoded as a two-octet string in hexadecimal representation. Each character in the string shall take a value of "0" to "9" or "A" to "F" and shall represent 4 bits. The most significant character representing the PCP/DEI field shall appear first in the string, followed by character representing the 4 most significant bits of the VID field, and the character representing the 4 least significant bits of the VID field shall appear last in the string. If only Service-VLAN tag is provided, empty string for Customer-VLAN tag shall be provided." |
| "Destination MAC address end. If this attribute is present, the destMacAddr attribute specifies the destination MAC address start." |
Below is a screenshot of the UDR Assistance displaying the EthFlowDescription
UDR:
EthFlowDescription UDR
TscaiInputContainer UDR
The TscaiInputContainer contains TSCAI (Time Sensitive Communication Assistance Information) input information, according to 3GPP specification TS 29.514 v. 16.6.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The unique ID of the |
| The name of the |
| Indicates the arrival time of the data burst in reference to the external GM. |
| Unsigned 64-bit integer identifying a period of time in units of microseconds, i.e. 0 to (2^64)-1. Minimum = 0. Maximum = 18446744073709551615. Identifications of the time period between the start of two bursts in reference to the external GM. |
Below is a screenshot of the UDR Assistance displaying the TscaiInputContainer
UDR:
TascaiInputContainer UDR
DownlinkDataNotificationControl UDR
In the DowlinkDataNotificationControl
UDR you determine whether notification of DDD (Downlink Data Delivery) Status is required with related information as well as whether notification of DDN Failure is requested, according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The unique ID of the DownlinkDataNotificationControl UDR. |
| "Determines the event notification(s) requested. In this release of the specification the maximum number of elements in the array is 2." |
| "Contains the type of notification of DDD Status. In this release of the specification the maximum number of elements in the array is 2." |
Below is a screenshot of the UDR Assistance displaying the DownlinkDataNotificationControl
UDR:
DownlinkDataNotificationControl UDR
QosData UDR
The QosData
UDR contains various QoS parameters, according to according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The unique ID of the |
| "Univocally identifies the QoS control policy data within a PDU session." |
| "Identifier for the authorized QoS parameters for the service data flow. It shall be included when the QoS data decision is initially provisioned and "defQosFlowIndication" is not included or is included and set to false." |
| "Indicates the max bandwidth in uplink." |
| "Indicates the max bandwidth in downlink." |
| "Indicates the guaranteed bandwidth in uplink." |
| "Indicates the guaranteed bandwidth in downlink." |
| "Defines the Arp UDR to be used." |
| "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. Default value "FALSE" is used, if not present and has not been supplied previously." |
| "Indicates whether the QoS information is reflective for the corresponding non- GBR service data flow. Default value "FALSE" is used, if not present and has not been supplied previously." |
| "Indicates, by containing the same value, what PCC rules may share resource in downlink direction." |
| "Indicates, by containing the same value, what PCC rules may share resource in uplink direction." |
| "Indicates a priority in scheduling resources among QoS Flows. Applicable only when a value different from the standardized value for this 5QI." |
| "Represents the duration over which the guaranteed and maximum bitrate shall be calculated. Applicable only when a value different from the standardized value for this 5QI." |
| "Denotes the largest amount of data that is required to be transferred within a period of 5G-AN PDB. Applicable only when a value different from the standardized value for this 5QI. Either the maxDataBurstVol IE or the extMaxDataBurstVol IE may be present. If the maximum data burst volume value to be transmitted is lower than or equal to 4095 Bytes, the maxDataBurst Vol IE is used. If the EMDBV feature is supported by both the PCF and the SMF, the extMaxDataBurstVol IE is used to transmit maximum data burst volume values higher than 4095 Bytes." |
| "Indicates the downlink maximum rate for lost packets that can be tolerated for the service data flow." |
| "Indicates the uplink maximum rate for lost packets that can be tolerated for the service data flow." |
| "Indicates that the dynamic PCC rule shall always have its binding with the QoS Flow associated with the default QoS rule. Default value "FALSE" is used, if not present and has not been supplied previously." |
| "Denotes the largest amount of data that is required to be transferred within a period of 5G-AN PDB. Applicable only when a value different from the standardized value for this 5QI. Either the maxDataBurstVol IE or the extMaxDataBurstVol IE may be present. If the maximum data burst volume value to be transmitted is lower than or equal to 4095 Bytes, the maxDataBurst Vol IE is used. If the EMDBV feature is supported by both the PCF and the SMF, the extMaxDataBurstVol IE is used to transmit maximum data burst volume values higher than 4095 Bytes." |
| "Unsigned integer indicates the packet delay budget. Packet Delay Budget expressed in milliseconds." |
| "String indicating the packet error rate. Examples: Packet Error Rate 10-2 shall be encoded as"1E-2"." |
Below is a screenshot of the UDR Assistance displaying the QosData
UDR:
QosData UDR
ChargingData UDR
The ChargingData
UDR contains charging related parameters, according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The unique ID of the |
| "Univocally identifies the charging control policy data within a PDU session." |
| "Defines what parameters shall be metered for offline charging. If the attribute is not present but it has been supplied previously, the previous information remains valid. If the attribute is not present and it has not been supplied previously or the attribute has been supplied previously but the attribute is set to NULL, the metering method pre-configured at the SMF is applicable as default metering method." |
| "Indicates the offline charging is applicable to the PCC rule when it is included and set ot true. The absence of both the "offline" attribute and "online" attribute or only one attribute is present and set to false within a Charging Data decision instance indicates that the default charging method of the PDU session is applicable to the PCC rule referring to the Charging Data decision. Either "offline" attribute or "online" attribute set to true shall be provisioned initially if there is no default charging method applied to the PDU session. The “offline” attribute and the “online” attribute shall not be simultaneously present with the same value, i.e., both set to true or both set to false." |
| "Indicates the online charging is applicable to the PCC rule when it is included and set ot true. The absence of both the "offline" attribute and "online" attribute or only one attribute is present and set to false within a Charging Data decision instance indicates that the default charging method of the PDU session is applicable to the PCC rule referring to the Charging Data decision. Either "offline" attribute or "online" attribute set to true shall be provisioned initially if there is no default charging method applied to the PDU session. The “offline” attribute and the “online” attribute shall not be simultaneously present with the same value, i.e., both set to true or both set to false." |
| "Indicates whether the service data flow is allowed to start while the SMF is waiting for the response to the credit request. The default value "FALSE" (blocking) shall apply, if the attribute is not present. The "sdfHandl" attribute shall not be present when the online charging method does not apply for the PCC rule referring to the Charging Data decision (i.e., when the "online" attribute is present and set to false, or is absent and the online default charging method does not apply for the PDU session, or is absent and there is no online default charging method defined)." |
| "The charging key for the PCC rule used for rating purposes." |
| "Defines on what level the SMF reports the usage for the related PCC rule. If the attribute is not present but it has been supplied previously, the previous information remains valid. If the attribute is not present and it has not been supplied previously or the attribute has been supplied previously but it is set to NULL, the reporting level pre-configured at the SMF is applicable as default reporting level." |
| "Indicates the identifier of the service or service component the service data flow in a PCC rule relates to." |
| "Indicates the sponsor identity." |
| "Indicates the application service provider identity." |
| "An identifier, provided from the AF, correlating the measurement for the Charging key/Service identifier values in this PCC rule with application level reports. The "afChargingIdentifier" attribute shall not be present when the "AF_Charging_Identifier" feature is supported. When the "AF_Charging_Identifier" feature is not supported it is out of the scope of the specification what the behaviour of the PCF is when the AF provides charging identifier values that are out of ChargingId data type value range." |
| "A character string identifier, provided from the AF, correlating the measurement for the Charging key/Service identifier values in this PCC rule with application level reports. The "afChargId" attribute shall be used instead of the "afChargingIdentifier" attribute when the "AF_Charging_Identifier" feature is supported." |
Below is a screenshot of the UDR Assistance displaying the ChargingData
UDR:
ChargingData UDR
TrafficControlData UDR
The TrafficControlData
UDR contains parameters determining how flows associated with a PCCRule are treated (blocked, redirected, etc), according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The unique ID of the |
| The name of the |
| "Univocally identifies the traffic control policy data within a PDU session." |
| "Enum determining what action to perform on traffic. Possible values are: [enable, disable, enable_uplink, enable_downlink]. The default value "ENABLED" shall apply, if the attribute is not present and has not been supplied previously." |
| "It indicates whether the detected application traffic should be redirected to another controlled address defined in the |
| "Additional redirection information. Each element indicates whether the detected application traffic should be redirected to another controlled address and is stated by a list of |
| "Indicates whether application's start or stop notification is to be muted. The default value "FALSE" shall apply, if the attribute is not present and has not been supplied previously." |
| "Reference to a pre-configured traffic steering policy for downlink traffic at the SMF. Traffic steering policy identifier(s) (i.e. "trafficSteeringPolldDI" attribute and/or "trafficSteeringPolldUI" attribute) and N6 traffic routing requirements (i.e. "routeToLocs" attribute) are mutually exclusive." |
| "Reference to a pre-configured traffic steering policy for uplink traffic at the SMF. Traffic steering policy identifier(s) (i.e. "trafficSteeringPolldDI" attribute and/or "trafficSteeringPolldUI" attribute) and N6 traffic routing requirements (i.e. "routeToLocs" attribute) are mutually exclusive." |
| "A list of routeToLocs UDRs which the traffic shall be routed to for the AF request. Traffic steering policy identifier(s) (i.e. "trafficSteeringPolldDI" attribute and/or "trafficSteeringPolldUI" attribute) and N6 traffic routing requirements (i.e. "routeToLocs" attribute) are mutually exclusive." |
| "Indication of traffic correlation. If it is included and set to "true", traffic should be correlated; The default value "false" applies, if the attribute is not present and has not been supplied previously. The TSC feature shall be supported in order to support this attribute." |
| "Contains the information about the AF subscriptions of the UP path change." |
| "Indicates the applicable traffic steering functionality." |
| "Determines the traffic distribution rule across 3GPP and Non-3GPP accesses to apply for downlink traffic." |
| "Determines the traffic distribution rule across 3GPP and Non-3GPP accesses to apply for uplink traffic." |
| "Indicates whether the service data flow, corresponding to the service data flow template, is allowed or not allowed. The default value "NOT_ALLOWED" applies, if the attribute is not present and has not been supplied previously." |
Below is a screenshot of the UDR Assistance displaying the TrafficControlData
UDR:
TrafficControlData UDR
RedirectInformation UDR
The RedirectInformation
UDR contains the redirect information, according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The ID of the |
| The name of the |
| "This attribute indicates whether the redirect instruction is enable. It shall be included and set to true when the redirect instruction is provisioned initially and may be included subsequently to disable or re-enable the redirect instruction. If the attribute omitted, the previous value shall apply." |
| "Indicates the type of redirect address contained within the "redirectServerAddress" attribute." |
| "Indicates the address of the redirect server. |
Below is a screenshot of the UDR Assistance displaying the RedirectInformation
UDR:
RedirectInformation UDR
UpPathChgEvent UDR
The UpPathChgEvent
UDR contains the redirect information, according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The ID of the |
| "Notification address of AF receiving the event notification." |
| "It is used to set the value of Notification Correlation ID in the notification sent by the SMF." |
| "Indicates the type of DNAI change." |
| "Identifies whether the AF acknowledgement of UP path event notification is expected. Set to "true" if the AF acknowledge is expected; otherwise set to "false". Default value is "false" if omitted." |
Below is a screenshot of the UDR Assistance displaying the UpPathChgEvent
UDR:
UpPathChgEvent UDR
SteeringMode UDR
The SteeringMode
UDR contains the redirect information, according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The ID of the |
| "Indicates the value of the steering mode." |
| "Indicates the Active access. It shall be included when the "steerModeValue" attribute is set to "ACTIVE_STANDBY"." |
| "Indicates the Standby access. It may be included when the "steerModeValue" attribute is set to "ACTIVE_STANDBY"." |
| "Indicates the traffic load to steer to the 3GPP Access expressed in one percent. It shall be set to 0, 10, 20, 30, 40, 50, 60, 70, 80, 90 or 100. It shall be included when the "steerModeValue" attribute is set to "LOAD_BALANCING"." |
| "Indicates the high priority access. It shall be included when the "steerModeValue" attribute is set to "PRIORITY_BASED"." |
Below is a screenshot of the UDR Assistance displaying the SteeringMode
UDR:
SteeringMode UDR
UsageMonitoringData UDR
The UsageMonitoringData
UDR contains usage monitoring related control information, according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The ID of the |
| "Univocally identifies the usage monitoring policy data within a PDU session." |
| "Indicates the total volume threshold." |
| "Indicates a volume threshold in uplink." |
| "Indicates a volume threshold in downlink." |
| "Indicates a time threshold." |
| "Indicates the time at which the UP function is expected to reapply the next thresholds (e.g. nextVolThreshold)." |
| "Indicates a volume threshold after the Monitoring Time." |
| "Indicates a volume threshold in uplink after the Monitoring Time." |
| "Indicates al volume threshold in downlink after the Monitoring Time." |
| "Indicates a time threshold after the Monitoring." |
| "Defines the period of time after which the time measurement shall stop, if no packets are received." |
| "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." |
Below is a screenshot of the UDR Assistance displaying the UsageMonitoringData
UDR:
UsageMonitoringData UDR
QosCharacteristics UDR
The QosCharacteristics
UDR contains QoS characteristics for a non- standardized or non-configured 5QI, according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The ID of the |
| "Identifier for the authorized QoS parameters for the service data flow. Applies to PCC rule and PDU session level." |
| "Indicates whether the resource type is GBR, delay critical GBR, or non-GBR." |
| "Unsigned integer indicating the 5QI Priority Level, within a range of 1 to 127." |
| "Unsigned integer indicates the packet delay budget. Packet Delay Budget expressed in milliseconds." |
| "String indicating the packet error rate. Packer Error Rate 10-2 shall be encoded as"1E-2"." |
| "Indicates the averaging window. This IE shall be present only for a GBR QoS flow or a Delay Critical GBR QoS flow." |
| "Unsigned Integer. Indicates the maximum data burst volume. Either the maxDataBurstVol IE or the extMaxDataBurstVol IE may be present for a Delay Critical GBR QoS flow. If the maximum data burst volume value to be transmitted is lower than or equal to 4095 Bytes, the maxDataBurst Vol IE is used. If the EMDBV feature is supported by both the PCF and the SMF, the extMaxDataBurstVol IE is used to transmit maximum data burst volume values higher than 4095 Bytes." |
| "Unsigned Integer. Indicates the maximum data burst volume. Either the maxDataBurstVol IE or the extMaxDataBurstVol IE may be present for a Delay Critical GBR QoS flow. If the maximum data burst volume value to be transmitted is lower than or equal to 4095 Bytes, the maxDataBurst Vol IE is used. If the EMDBV feature is supported by both the PCF and the SMF, the extMaxDataBurstVol IE is used to transmit maximum data burst volume values higher than 4095 Bytes." |
Below is a screenshot of the UDR Assistance displaying the QosCharacteristics
UDR:
QosCharacteristics UDR
QosMonitoringData UDR
The QosMonitoringData
UDR contains QoS monitoring related control information, according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The ID of the |
| "Univocally identifies the QoS monitoring policy data within a PDU session." |
| "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. In this release of the specification the maximum number of elements in the array is 3." |
| "Indicates the frequency for the reporting, such as event triggered, periodic, when the PDU Session is released, and/or any combination." |
| "Unsigned integer identifying a threshold in units of milliseconds for DL packet delay. Only applicable when the "reqQosMonParams" attribute includes the "DOWNLINK" value and the "repFreqs" attribute includes the value "EVENT_TRIGGERED"." |
| "Unsigned integer identifying a threshold in units of milliseconds for UL packet delay. Only applicable when the "reqQosMonParams" attribute includes the "UPLINK" value and the "repFreqs" attribute includes the value "EVENT_TRIGGERED"." |
| "Unsigned integer identifying a threshold in units of milliseconds for round trip packet delay. Only applicable when the "reqQosMonParams" attribute includes the "ROUND_TRIP" value and the "repFreqs" attribute includes the value "EVENT_TRIGGERED"." |
| "Indicates the minimum waiting time between subsequent reports. Only applicable when the "repFreqs" attribute includes the value "EVENT_TRIGGERED"." |
| "Indicates the reporting period. Only applicable when the "repFreqs" attribute includes the value "PERIODIC"." |
| "Notification address of AF receiving the event notification. It shall be included if the PCF determines that the notification shall be sent to the AF directly from the SMF." |
| "It is used to set the value of Notification Correlation ID in the notification sent by the SMF. It may be included if the PCF determines that the notification shall be sent to the AF directly from the SMF." |
Below is a screenshot of the UDR Assistance displaying the QosMonitoringData
UDR:
QosMonitoringData UDR
ConditionData UDR
The ConditionData
UDR contains conditions for applicability of a rule, according to 3GPP specification TS 29.512 v. 16.8.0. Descriptions from this specification are in quotation marks.
Field | Description |
---|---|
| The ID of the |
| "Uniquely identifies the condition data within a PDU session." |
| "The time when the decision data shall be activated." |
| "The time when the decision data shall be deactivated." |
| "The condition of access type of the UE when the session AMBR shall be enforced." |
| "The condition of RAT type of the UE when the session AMBR shall be enforced." |
Below is a screenshot of the UDR Assistance displaying the ConditionData
UDR:
ConditionData UDR