The following tables show the maximum Subscriber Capacity and the maximum Transactions Per Second of SAPC 1 per each network scenario. The number of TPS supported for all releases of the Gx interface when executing similar functions is about the same.

The concept of Transaction in this document means a service request and the corresponding reply. The related capacity term is Transactions Per Second (TPS).

PNF BSP 8100 HW

PNF NSP 6.1 HW

External Database Access

The impact of storing subscriber profiles in an external database is determined by the performance of the external database, the parts of the subscriber profile externally stored and the operator data model. According to estimations, the impact in performance using LDAP interface is as follows:

• 15% reduction in the number of TPS supported, when both subscriber profile and usage accumulators are stored in external database, which needs a write operation to external database.

• 10% reduction in the number of TPS supported, when no accumulators are stored in the external database.

Mobility Based Policy for Overlay Deployments

Smp is a new interface that requires dimensioning. This feature has no impact in the performance for those scenarios where the Smp interface is not used. The performance of the Smp operations is better than the performance of Gx operations as the functionality provided is lighter.

The impact on the performance of the feature mostly depends on:

• Subscribers that are using the Smp interface.

• Traffic model: the frequencies of some operations can become high depending on especially those related to location change.

No information is available for this document release.

For performance information of the SAPC 1 deployed as VNF, refer to SAPC 1 Network Impact Report.

The SAPC 1 introduces new provisioning and configuration databases available through new interfaces. As a consequence, it is not possible to provide a direct upgrade from SAPC 16B CP04 to SAPC 1 PNF. The SAPC 16B to SAPC 1 upgrade implies a SW reinstallation. The procedure also includes data migration.

The overall reinstallation time and out-of-service impact depends on the execution time of the project.

The SAPC 1 VNF deployments are considered new network deployments. No upgrade alternative is available in such case.

The SAPC 1 can be deployed as VNF on top of either OpenStack or VMware based NFVI.

The impacts on traffic interfaces are summarized for in Table 9 and Table 10.

Diameter Base Protocol Impacts

• SAPC Diameter Base Protocol Errors not supported: DIAMETER_LIMITED_SUCCESS (2002), DIAMETER_UNABLE_TO_DELIVER (3002), DIAMETER_REALM_NOT_SERVED (3003).

SCTP Impacts

SCTP bundling is disabled (default value at installation time). So, the SAPC sends Diameter outgoing messages over SCTP faster.

EBM Impacts

The Event-Based Monitoring (EBM) interface has the following impact on SAPC 1:

• BEARER_MBR_UL, BEARER_MBR_DL, BEARER_GBR_UL, and BEARER_GBR_DL change the Type and Value Range from UINT: 24 bits to UINT: 32 bits.

Gx Impacts

The 3GPP Gx interface has the following impacts on SAPC 1:

• SAPC supports Gx Rel9 version 9.7.0 or higher versions.

• Gx Rel7 and Gx Rel8 support is phased-out. If the PCEF requests session establishment with Gx interface Release 8 or previous, the SAPC returns the error code DIAMETER_INVALID_AVP_VALUE (5004).

• Gx Diameter Redirection Agent (DRA) functionality is not available.

• Credit-Control-Request (CCR):

  • Event-Trigger value not supported: CHARGING_CORRELATION_EXCHANGE.

  • 3GPP2-BSID AVP is not supported.

  • IP-CAN-Type AVP adds support for FBA value.

  • Access-Network-Charging-Identifier-Gx AVP is not supported.

  • The TWAN-Identifier, UE-Local-IP-Address, TCP-Source-Port, UDP-Source-Port AVPs are added.

  • Support added for bit 30 (Netloc-Untrusted-WLAN) in the Supported-Features AVP.

  • The TDF-Information AVP is added in CCR-Initial for the support of Sd for Application Detection and Control.

• Charging-Rule-Install AVP

  • Charging-Correlation-Indicator AVP is not supported.

• Charging-Rule-Definition AVP

  • Monitoring-Key AVP is not supported.

  • Flow-Description AVP uplink (direction 'in') inside Flow-Information AVP is not supported in Gx Rel9 versions 9.7.0 and higher. It is supported in Gx Rel9 versions 9.0.0 and 9.1.0.

  • Flow-Direction AVP is not supported in Gx Rel9 versions 9.0.0 and 9.1.0. It is supported in Gx Rel9 versions 9.7.0 and higher.

  The support of Gx Rel9 versions 9.0.0 and 9.1.0 can be configured for each PCEF (see Configuration Guide for Access and Charging Control (Gx))

• Charging-Rule-Report AVP

  • Rule-Failure-Code AVP adds support of the following values: RATING_GROUP_ERROR (2), SERVICE_IDENTIFIER_ERROR (3), GWPCEF_MALFUNCTION (4), RESOURCES_LIMITATION (5), MAX_NR_BEARERS_REACHED (6), UNKNOWN_BEARER_ID (7), MISSING_BEARER_ID (8), MISSING_FLOW_INFORMATION (9), UNSUCCESSFUL_QOS_VALIDATION (11), INCORRECT_FLOW_INFORMATION (12), and NO_BEARER_BOUND (15).

• Application Detection and Control (ADC) error handling:

  • When a CCR-U is received with APPLICATION_START or APPLICATION_STOP event trigger, but not Application-Detection-Information AVP or with Application-Detection-Information AVP but not TDF-Application-Identifier AVP inside, the SAPC returns a CCA with error code DIAMETER_MISSING_AVP (5005).

  • When a CCR-U is received with APPLICATION_START or APPLICATION_STOP event trigger, with Application-Detection-Information AVP including a Flow-Information AVP, but no corresponding TDF-Application-Instance-Identifier AVP, the SAPC returns a CCA with error code DIAMETER_MISSING_AVP (5005).

• Emergency services error handling:

  • When the SAPC receives an initial CCR for an emergency session and the emergency subscriber is not provisioned, the SAPC processes the request (does not return DIAMETER_USER_UNKNOWN 5030).

• Re-Auth-Answer (RAA):

  • The IP-CAN-Type, RAT-Type, AN-Trusted, and AN-GW-Address AVPs add support for IP-CAN Type Change Notification.

• Re-Auth-Request (RAR):

  • The AF-Signalling-Protocol AVP is added.

  • Support added for bit 2 (ProvAFsignalFlow) in the Supported-Features AVP.

Rx Impacts

The Rx interface has the following impacts on SAPC 1:

• Rx Rel7 and Rx Rel8 support is phased-out.

  • If the AF only supports Rx Rel7 standard, and therefore the Supported-Features AVP is absent from the AAR command, the SAPC returns DIAMETER_MISSING_AVP (5005).

  • If the AF requests session establishment with Rx interface Rel 8 standard, the SAPC returns DIAMETER_INVALID_AVP_VALUE (5004).

• AA-Request (AAR):

  • If there are no policies defined in the SAPC to match the information received in the AA-Request command and classify the relevant dynamic services, then the SAPC responds to the AF with an AA-Answer command including the Experimental-Result-Code AVP set to the value REQUESTED_SERVICE_NOT_AUTHORIZED (5063).

  • Specific-Action AVP values CHARGING_CORRELATION_EXCHANGE (1) not supported.

  • If an IMS emergency call binds to a non-emergency IP-CAN session, the SAPC does not ignore the value of Service-URN AVP.

  • Support added for bit 16 (Netloc-Untrusted-WLAN) in the Supported-Features AVP.

  • The AF-Signalling-Protocol AVP is added.

  • Support added for bit 2 (ProvAFsignalFlow) in the Supported-Features AVP.

  • Support added for the AF_SIGNALLING(2) value in the Flow-Usage AVP.

• Re-Auth-Request (RAR):

  • Access-Network-Charging-Identifier AVP not supported.

  • The TWAN-Identifier, UE-Local-IP-Address, TCP-Source-Port, UDP-Source-Port AVPs are added.

  • AN-GW-Address AVP is supported.

• Session-Termination-Answer (STA):

  • The TWAN-Identifier, UE-Local-IP-Address, TCP-Source-Port, UDP-Source-Port AVPs are added.

Smp Impacts

The Smp interface has the following impacts on SAPC 1:

• CCR not supported AVPs:

  • Event-Trigger

  • Presence-Reporting-Area-Information

  • Session-Linking-Indicator

• CCA not supported AVPs:

  • Event-Trigger

  • Presence-Reporting-Area-Information

• CCA modified AVPs

  • MIP6-Agent-Info: multiple AVPs are supported

• RARs are not supported

• When a CCR-U or CCR-T is received, the SAPC does not perform any control. In case there is no error in the request it returns a CCA with result code DIAMETER_SUCCESS (2001)

• Unsupported result codes:

  • DIAMETER_LIMITED_SUCCESS (2002)

  • DIAMETER_UNABLE_TO_DELIVER (3002)

  • DIAMETER_REALM_NOT_SERVED (3003)

  • DIAMETER_AUTHORIZATION_REJECTED (5003)

• New result codes:

  • DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE (4011)

Sd Impacts

The Sd interface is a new interface in SAPC 1 between the TDF and the SAPC to provide Application Detection and Control.

The impacts on operation and maintenance interfaces are detailed in Table 11 and Table 12:

The SAPC 16B CP04 LDAP provisioning and configuration interface is deprecated. As a consequence, all LDAP-based operator provisioning configurations and node configurations must be adapted to support the SAPC 1 available provisioning and configuration data models through the new available interfaces.

The SAPC 1 measures report file is based on 3GPP TS 32.435 v10.0.0, XSD type XML file format definition.

The main differences with SAPC 16B CP04 TSP nPMF XSD type XML (3GPP TS 32.435 v6.0.0) are the following:

• Newly supported XML elements and attributes: elementType, userLabel, swVersion, job, jobId, repPeriod, suspect, p, r, and measInfoId.

• XML element not supported: measResults.

DTD type XML file format support is phased-out in SAPC 1. XSD type XML must be used instead.

SAPC 1 does not push to an external system, the PM files. OSS/BSS has to pull the PM files, For more information refer to SAPC Measurements.

The SAPC 1 alarm information model, configuration, and operation are described in Fault Management. The SAPC 1 alarms follow the Ericsson Alarm MIB. This section compares both SAPC 16B CP04 and SAPC 1 based on the common Specific Problem Object type.

The SAPC 1 and the SAPC 16B CP04 equivalent alarms are listed in Table 37, the SAPC 1 new alarms are listed in Table 38, and the SAPC 16B CP04 alarms not available in SAPC 1 are listed in Table 39.

The SAPC 16B CP04 TSP-related alarms are not available. To check additional SAPC 1 alarms introduced with the platform components, refer to the Fault Management folder in library.

The SAPC 1 notifications (stateless alarms compliant with Ericsson Alarm MIB) defined by the platform components, are described in the Notifications folder in CPI library.

The SAPC 16B CP04 notifications not available in SAPC 1 are listed in Table 40.

The SAPC 16B CP04 TSP-related notifications are not available.

The SAPC 1 logging events impacts are listed below. Compatible logging events are listed in Table 41, new logging events are listed in Table 42, and logging events available both in SAPC 1 and SAPC 16B CP04 are listed in Table 43. The logging events not available in SAPC 1 are listed in Table 44. For additional information, refer to Logging Events.

SAPC 1 does not support LDAP authentication.

The SAPC 1 backup and restore functions are provided by the Backup and Restore Management (BRM) Component. For details on the backup and restore operation procedures, refer to Backup and Restore.

The SAPC 1 backup has been improved to remove dynamic information that is considered obsolete if restored. The database backup does not store the following information:

• IP-CAN sessions.

• Time Trigger events.

Only one URI is possible to be used by backup scheduler when automatically exporting a scheduled backup.

The SAPC 1 controls the activation of the purchased functionality by license keys using License Manager (LM) Common Component.

The SAPC 1 geographical redundancy function is based on the replication capability provided by the Database Service (DBS). Any data not stored in the DBS is not replicated. The following data is not stored in DBS and not replicated:

• The node configuration data that is provided through COM. Therefore, the configuration data must be provided to each SAPC node individually.

• The licensing information. Therefore license information must be managed in each SAPC individually.

The geographical redundancy function is managed using NETCONF or the ECLI. For additional details on the operation of geographical redundancy function, refer to Geographical Redundancy folder.

The SAPC 1 introduces the following impacts on the graphical user interface:

• The Policy Studio replaces the Business Studio and SAPC GUI. For information, see Policy Studio.

• The Ericsson NETCONF browser (ENB) presents configuration data graphically, allowing users to navigate the configuration structure and perform add, modify, and delete operations on configuration elements. The ENB is an Ericsson separate product not directly provided with the SAPC. For more information, refer to Ericsson NETCONF Browser documentation.

• The Provisioning Tools document provides an introduction to the Postman Chrome plug-in to interact graphically with the REST API.

• TSP-based Node Management Toolbox (and all its associated services including TelORB Manager, Alarm Viewer, Notification Viewer, Redundancy GUI, License Manager, and so on), Load Viewer tool, and Signaling Manager are not available.

The SAPC 1 impacts affecting Policy Types are the following:

• The Policy Locator 'Action' concept is removed.

• Policy Locator 'Contexts', Policy Locator 'Resources' and Policy Locator 'Output Attributes' are modeled differently in REST provisioning API. The Policy Locator naming equivalences between SAPC 16B CP04 and SAPC 1 are summarized in Table 45, Table 47, and Table 49. Refer to Configuration Guide for Subscription and Policies.

• Rule combining algorithms equivalences are summarized in Table 51.

The 3GPP Gx function has the following impacts on SAPC 1:

• Dispersion on reauthorization: The dispersion range mechanism for reauthorization owing to time of day conditions and related configuration variables, are no longer applicable. The reauthorizations are sent as soon as possible limited by a throttling mechanism that can be configured based on network traffic model, and the SAPC capacity.

• Subscriber basic session clean up mechanism: When the SAPC receives an IP-CAN session activation request for a subscriber including an APN and an IPv4 or IPv6 prefix address, the SAPC does not check if an IP-CAN session exists for the same subscriber identifier, the same APN, different IP address value of the same type (IPv4 or IPv6 prefix) and same traffic identifier as the received in the activation request. In such a case, both sessions coexist.

For 3GPP Gx interface impacts, refer to Gx Impacts.

The Basic Policy Control function has the following impacts on SAPC 1:

• Clustered diameter systems are defined based on a common pattern associated to the received origin host, not a logical node identifier.

• Temporarily inactive PCC rule status not available.

The 3GPP standard QCIs defined for Vehicle-to-Everything (V2X) services are supported.

The SAPC supports operator-specific QCI values in the range from 128 to 254 that can be configured as either GBR or non-GBR.

The 3GPP standard QCIs defined for Vehicle-to-Everything (V2X) services are supported.

The SAPC supports operator-specific QCI values in the range from 128 to 254 that can be configured as either GBR or non-GBR.

No impacts.

The SAPC Policy Studio replaces SAPC 16B CP04 Business Studio. The SAPC Policy Studio is deployed in an external Linux server. For additional details, refer to Policy Studio.

This is a new provisioning interface. The SAPC provisioning is executed through REST operations, defined in the Provisioning REST API. For additional information on the description of the configuration and provisioning data model, refer to Managed Object Model (MOM).

The Usage Reporting function has the following impacts on SAPC 1:

• Association between preconfigured or dynamic services and their monitoring key is not supported. As a consequence, the monitoring key policy type is not available.

• Interaction with external database: Collisions Detection Counter (CDC) mechanism, based on a CDC attribute, not available.

• The fair usage validity time dispersion logic is reworked. The configuration variable to add a random number of seconds to the calculated validity time is no longer applicable.

• Accumulated usage information is now accessed through REST API.

The Flexible Output Protocol function has the following impacts on SAPC 1:

• Transformations are applied at command level and at service level.

• Flexible Output Protocol language syntax has been modified.

• Transformations are now provided by Entity Data Targets.

• Only Gx protocol is supported.

• Only AVPs not part of Gx dictionary are configured in Flexible Output Protocol specific dictionary.

This function has the following impacts on SAPC 1:

• On Diameter Gx race condition, after the SAPC sends a RAR command to request the IP-CAN session termination, any incoming CCR-U request for the same Gx session from the PCEF is answered with a CCA-U Result-Code AVP set to DIAMETER_SUCCESS value, instead of DIAMETER_USER_UNKNOWN. No IP-CAN session reauthorization is done.

• On Rx race condition, after the SAPC sends a Gx RAR command to request the IP-CAN session termination due to subscription removal, any incoming AAR-U for an Rx session bound with this Gx session is answered with an AAA Result-Code AVP set to DIAMETER_SUCCESS value instead of DIAMETER_UNABLE_TO_COMPLY. No IP-CAN session reauthorization is done.

• On Sy race condition, after the SAPC sends a Gx RAR command to request the IP-CAN session termination due to subscription removal, any incoming SNR for an Sy session bound with this IP-CAN session is answered with an SNA Result-Code AVP set to DIAMETER_SUCCESS value instead of DIAMETER_UNABLE_TO_COMPLY. No IP-CAN session reauthorization is done.

• On massive subscription removal, when the sending of RAR commands is disabled by the SAPC configuration, any incoming CCR-U from the removed subscribers is answered with a CCA-U Result-Code AVP set to DIAMETER_AUTHORIZATION_REJECTED value, instead of DIAMETER_USER_UNKNOWN, to force the IP-CAN session termination on the PCEF.

This is a new function added to SAPC 1:

• The SAPC provides an automatic cleanup mechanism to remove all the Gx sessions that have been inactive (no request has been received or sent for them in a period of time).

The Core Network Operations Manager (CNOM) is an Ericsson separate product, not directly provided with the SAPC. The SAPC 1 provides support to integrate the following applications of CNOM:

• Network monitor

• Alarm monitor

• Health check

• UE Trace

• Traffic Analysis

Session context published and session removal mechanisms in SAPC 1 and cSAPC are different, the details are the following:

• Newly supported session context elements in SAPC 1: PCC rule list, QoS information of the default bearer, RAT type, PRA, MCC and MNC.

• Session context elements not supported in SAPC 1 but supported in cSAPC: IMEI and SGSN addresses.

• Newly supported the closed session context retrieval from both external and internal database in SAPC 1.

• Newly supported the ongoing session context retrieval from external database in SAPC 1.

• Removing subscriber sessions manually not supported in SAPC 1 but supported in cSAPC.

This is a new function added to SAPC 1:

• The REST API to translate session IP address to IMSI function enables the operator to query an IMSI list of ongoing sessions by IP address, APN (if available) and PCEF (if available).

This is a new function added to SAPC 1:

• The Session Handler tool enables the operator to access relevant information regarding the sessions of a specific subscriber, for all the applicable protocols. The tool also allows the termination of retrieved sessions for the Gx and Rx protocols.

For a detailed description of the tool, refer to SAPC Troubleshooting Guide.

• Cisco SCE

• E4 Interface

• OAM via WEB Services

• Multivendor BNG Support

• RADIUS / RADIUS COA

• Usage Reporting for RADIUS

• 3GPP Gxa

• Subordinated PCEFs

• HTTPS support for SOAP notifications is not available.

• A load balancing mechanism is introduced to distribute the delivery of notifications among the set of configured Notification Addresses, belonging to a Notification Server, using round robin algorithm. When the SAPC detects one of the configured Notification Addresses is not available, it stops sending further notifications towards that Notification Address. When the connection towards a Notification Address is restored, the SAPC starts again sending notifications towards this Notification Address.

• Connection handling changes:

  • The default maximum number of connections per process, between the SAPC and the SOAP notification server are doubled (50).

  • The default maximum size of the SOAP notifications queue is doubled (2000).

  • The default time period to check the SOAP connection status has doubled to (6000 ms)

  • If a connection is not established after the connection reattempts, or the connection is established but the notification delivery fails (an error is received at protocol level), the SAPC inserts this notification in the notification queue at the last position if there is room for one more notification. For the list of specific HTTP supported errors refer to User Notifications.

• EBM events are not logged.

• Detected mistakes are corrected in the sapc_ebm.xml file:

  • Typo fixed in the name of the FAMILY_ID parameter.

  • Typo fixed in the SUBSCRIPTION_TYPE parameter inside the ACCUMULATED_USAGE_RESET and ACCUM_USAGE_LIMIT_SURPASSED events.

• Support for N-EBM Servers is available in SAPC 1.

• In SAPC 1, more than one Specific-Action can be sent in an Rx RAR message. In SAPC 16B CP04, SPECIFIC_ACTION inside RX_RAR_RAA_TRANSACTION was not defined as an array. Because of this, a new array, SPECIFIC_ACTIONS, is added at the end of the RX_RAR_RAA_TRANSACTION event.

• The RAT_TYPE parameter has two new values:

  • VIRTUAL (value 11)

  • EUTRAN-NB-IOT (value 12)

Fixed and convergence policy control is provided through Gx interface. The SAPC supports all Subscription-Id-Type values, so it is possible to use END_USER_NAI or END-USER_PRIVATE traffic identity (for example with a MAC address) for fixed PCC. Radius interface support is phased-out.

The SAPC 1 provides a new geographical redundancy solution, following the "Primary / Standby" (1+1 redundancy) replication model available in SAPC 16B CP04. For additional details on the geographical redundancy function refer to the Geographical Redundancy Facility Description.

This is a new function added to SAPC 1:

• A new, full geographical redundancy deployment in active-active mode has been added where both active SAPC nodes are able to handle traffic simultaneously.

• Node states are managed in the GeoRedManager MO and have different values than TelORB states.

• The Redundancy Control Mechanism is not based on the NetRed software of TSP.

• The Diameter Redirection Agent (DRA) or Diameter clients shall distribute traffic homogeneously between the two mated pairs of SAPC nodes. The distribution must ensure subscriber and session stickness.

• Upgrade with active replication

Refer to Dynamic Policy Control.

Refer to SOAP Notifications.

No impact.

• MASC

The 3GPP Sy function has the following impacts on SAPC 1:

• The SAPC 1 expects to receive SNR messages according to 3GPP, including only the Policy Counters that change their status. The existing Sy session Policy Counters not received in an SNR message, are not changed.

No Impacts.

No Impacts.

See impacts in EBM.

The function managing External Database access has the following impacts on SAPC 1:

• The Uniform Resource Locator (URL)-path of the SOAP server managing the notifications request is "/sapc/v1/notifications".

• LDAPS support for LDAP operations is not available.

• Connection handling changes:

  • Single pool of connections for read and write operations.

  • An IP address is considered unreachable if SAPC detects consecutive time-outs in at least 30% of the LDAP sessions.

  • Maximum of 64 LDAP sessions towards the External Database (IP address) per PL.

  • Maximum of 20 outstanding LDAP requests per LDAP session.

• SQL External Repositories not supported.

• Collision Detection mechanism is not available.

The function managing Mobility-Based Policy has the following impacts on SAPC 1:

• No controls are executed on session modification, subscriber profile update or ToD session reauthorization. This means:

  • Smp RARs are not supported

  • Smp CCR-Us are always answered with DIAMETER_SUCCESS (2001)

• No Smp session is maintained on the SAPC.

• Smp Session Access Control supports a new scenario, where SAPC 1 allows returning DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE (4011) to notify the SGSN-MME to continue the IP-CAN session but drop the Smp session. Other Smp Session Access Control scenarios not supported.

• PDN-GW selection allows to define lists of PDN-GWs.

• Smp-presence Reporting Area not supported.

• Integration with Online Charging System not supported.

• Event Triggers not supported.

• User Notifications not supported.

• Flexible Output Protocol not supported.

• Session-Linking-Indicator AVP ignored.

• Flexible Smp Protocol

• Mobility-Based Policy for PCRF

No impacts.

The Enhanced Policy Control function has the following impacts on SAPC 1:

• Gx Diameter Redirection Agent (DRA) functionality is not available.

• Ericsson Gx+: Dispersion on reauthorization and Subscriber basic session clean up mechanism impacts affect this interface just as it affects regular 3GPP Gx interface.

Refer to Enhanced Subscription Handling.

No impacts.

The Shared Data Plans function has the following impacts on SAPC 1:

• Quota Reservation functionality not available.

• External Database support is not available.

Refer to SOAP Notifications.

The User Notifications function has the following impacts on SAPC 1:

• Email message notifications are phased-out.

• Connection handling changes:

  • The default maximum number of connections per process, between the SAPC and the SMS notification server are doubled (50).

  • The default maximum size of the SMS notifications queue is doubled (2000).

  • If a connection is not established after the connection reattempts, or the connection is established but the notification delivery fails (an error is received at protocol level), the SAPC inserts this notification in the notification queue at the last position if there is room for one more notification. For the list of specific SMPP supported errors refer to User Notifications.

  • The maximum waiting time for the acknowledgment of the SMPP connection attempt is not configurable.

The Presence Reporting Area function has the following impacts on SAPC 1:

• During the establishment of the session the presence status of the UE in the presence reporting area is by default outside the area until the first CCR-U is received with the actual presence.

This is a new function added to SAPC 1:

• The SAPC supports aggregation of a subscriber’s absolute usage limits from different subscriber groups and performs fair usage control for the aggregated limits. The SAPC combines respectively the uplink, downlink, bidirectional volume limits and time limits from aggregable Reporting Groups of the subscriber groups associated with the subscriber.

The subscription-based Multimedia Priority Services (MPS) have the following impact on SAPC 1:

• To prioritize Gx MPS events, it is mandatory to configure the APNs corresponding to MPS types defined in the MPS profiles.

This is a new function added to SAPC 1:

• The support of Sd for Application Detection and Control (ADC) introduces the Sd interface between the SAPC and the Traffic Detection Function (TDF) that enables PCC decisions based on the reporting of detected applications from the TDF.

The Quota Rollover function has the following impact on SAPC 1:

• The currentRolloverPercentage tag is added to access the value of the current rollover usage accumulator expressed as percentage of the corresponding rollover quota from the previous period limit.

This is a new function added to SAPC 1:

The SAPC enables the operator to activate automatically multiple vouchers with the same absolute volume or time limits for prepaid subscriptions. This is enabled by defining multiple sets of start date and end date in the association of subscriber and subscriber group. Therefore, the subscriber can use multiple times the same usage limits from the prepaid subscriptions associated with multiple instances.

The Dynamic Policy Control function has the following impacts on SAPC 1:

• The access network charging identifier per service data flow is not available.

• On reception of SIP Forking, the SAPC updates the existing PCC rules with additional IP flows and bandwidth, as required. However if a forking leg contains additional media components, then new PCC rules are generated.

• The support of ServiceId.MediaComponentId has been deprecated. The output of the Dynamic Service Classification is simply a ServiceId, a string that can have any characters such as ".", "_", and so on. Similarly, the input for the Dynamic Service Qualification (Resource) is simply a ServiceId (a string, not an entity).

• The dynamic PCC rule random name generation is improved. It follows a specific format of four elements, delimited by the "@" character, with a maximum size of 63 characters. The PCC rule name begins with the service identifier that results from the dynamic service classification process, then continues with the Media-Component-Number and the Flow-Number, and finally includes a pseudo-random portion derived from the Rx diameter Session-Id.

• If an IMS emergency call binds to a non-emergency IP-CAN session, the SAPC does not ignore the value of Service-URN AVP.

• A new provision_rules_on_preliminary_info configuration parameter has been added. It supports the installation of PCC rules for preliminary service information, or delaying the installation until the status of the service information is final.

No impacts.

The Smart Policy Control for Wi-Fi Calling function has the following impacts on SAPC 1:

• Fair Usage based Wi-Fi calling functionality is not available, as association between dynamic services and their monitoring key is not supported.

This function has the following impacts on SAPC 1:

• The SAPC reports the release of signalling path from the PCEF to the AF through a RAR message. The RAR does not contain the Abort-Cause AVP.

• The default AF signalling service must be configured in the AF signalling path profile. It is possible to configure a different AF signalling service per APN.

This function has the following impacts on SAPC 1:

• The SAPC automatically subscribes to the IP-CAN_CHANGE and RAT_CHANGE event triggers when the Specific-Action AVP with IP-CAN_CHANGE value is received in an Rx AAR-I message. It is not needed to configure event trigger selection policy for IP-CAN type change notification.

• If the AF does not subscribe to IP-CAN type notification, the SAPC reports IP-CAN Type, RAT Type and AN-Trusted to the AF in an Rx AAA-I/U message only when the SAPC subscribed to the IP-CAN_CHANGE event trigger before.

This is a new function added to SAPC 1:

• The Network Location Information (NetLoc) for Untrusted WLAN function enables the SAPC to report the network provided location for Untrusted WLAN information to the AF during session establishment, modification and termination, and IP-CAN session termination and bearer release.

  The network provided WLAN location information includes:

  • WLAN location information and location information age

  • UE local IP address, User Datagram Protocol (UDP) source port, Transmission Control Protocol (TCP) source port

  • UE time zone

This is a new function added to SAPC 1

The Provisioning of AF Signalling Flow Information is a supported feature, it is part of the IMS Restoration Procedures, specified in 3GPP TS 23.380, to handle a Proxy Call Session Control Function (P-CSCF) service interruption scenario with minimum impact to the service to the end user.

After UE registration to IMS, the AF (P-CSCF) sends information to the SAPC about the AF signalling flows between the UE and the AF. The SAPC installs the corresponding dynamic PCC rules (if not installed before) by triggering a RAR message in order to convey the AF address the UE is using to the PCEF. The PCEF monitors all P-CSCF nodes being used by the UEs and if a P-CSCF becomes unresponsive, the PCEF requests all UEs using this P-CSCF to do a new registration against another P-CSCF.

No impacts.

Refer to Multimedia Priority Services - Rx (On-Demand).

Extended bandwidth AVPs representing bit rates in kbps are introduced to manage bandwidth values higher than 2³²-1 bps (4,3 Gbps), to support EPC Dual Connectivity (E-UTRAN and 5G NR).