Typically, each user equipment (UE) supports a maximum of 8 bearers. The increasing network requirements and the demand on
services result in a scarcity of bearers for priority services such as SOS and VoLTE.
To more efficiently manage the creation and use of dedicated and default bearers, CPS provides the following abilities.
Ability to configure the delay in bearer creation: The PCRF is able to tear down lower priority bearers within milliseconds
as long as they are all anchored on the same PCRF. However, if the bearers are spread across multiple datacenters, it can
take up to minutes to tear down the lower priority bearers. To ensure all other events are complete so as to enable the call
to be successfully established, you can configure a delay in bearer creation. CPS provides the ability to configure the delay
in creation of a default bearer and/or dedicated bearer (SOS or any other APN). For more information about configuring the
delay in bearer creation, see the following documents:
Ability to replicate data: LWR provides a replication layer to slice the user profile and share the states and is located
at the edge of each CPS clusters deployed in various datacenters. This helps achieve a faster indication of deletion of the
Active Traffic Management Replication Using LWR
When an Active Traffic Management service is enabled (that is used by a subscriber profiled in UDR), UDC can look up Active
Traffic Management attributes for the subscriber either from UDR or LWR.
With the addition of LWR, these attributes are written and updated in LWR clusters spanning multiple regions.
The Active Traffic Management attribute currently shares status the bearer counts for a subscriber, Services, CNS notification,
LWR is updated for each modification of the Active Traffic Management attribute.
In this release, LWR supports read and write of one user attribute to the replication framework specific to the Active Traffic
Management bearer counting attribute.
In future releases, UDC and other applications will be enhanced to provide support of new attributes or user profile details
that may require replication.
To facilitate Active Traffic Management replication on LWR, an LWR Manager runs on the UDC VM and manages the LWR applications.
The Manager checks whether a topic already exists; if it does not, the Manager uses the LWR Client Plugin Configuration details
to create a topic in the LWR cluster for producer and consumers. The topic is used to decide whether to delay the bearer creation
or not, this service configuration should get added to policy state based on specific use case initiators.
Then the Manager creates a group of LWR Producers that are used for publishing data to the LWR clusters. UDC uses the LWR
Service Configuration details to invoke the LWR Producer for publishing subscriber profile attributes to the LWR cluster for
LWR Manager configures and creates LWR Streamer for each topic. The Streamer is invoked when data needs to looked from LWR
cluster on an ad-hoc basis. User profile fields like MSISDN can be used for the lookup of the existing profiles in LWR from
current or cross-region sites.
LWR Manager also configures and creates LWR Consumer applications. The Consumer subscribes to internal topics created for
filtering user profiles that are cached in the current CPS Cluster.