Enables the operator
to apply a priority for different paging-profiles based
on traffic type. When the MME service is associated with
a paging map, the system checks the profile map to determine
which paging-profile to adopt for a given paging trigger.
Mode:
Exec > Global Configuration
> LTE Policy Configuration > LTE Paging Map Configuration
configure > lte-policy
> paging-map map_name
Entering the above
command sequence results in the following prompt:
[local]host_name(paging-map)#
Syntax
precedence priority traffic-type { cs | ps } paging-profile paging_profile_name
no precedence precedence
no
Remove the paging map
from the system.
precedence priority
precedence: For
StarOS releases 16.5 and higher, enter an integer
from 1 to 19, where 1 is the highest priority and 19 is
the lowest priority. For StarOS releases
prior to 16.5, enter an integer from 1 to 7, where
1 is the highest priority and 7 is the lowest priority.
traffic-type { cs | ps}
Defines the type of
traffic of the incoming call.
-
cs (Circuit
Switched) - All data and control activities that
involve CSFB. Paging requests from the MSC for mobile-terminated
calls alone are treated as CS type. Paging requests for
SMS are treated as PS type.
If a sub-traffic-type
is not configured then paging-profile configured for CS (with
no sub traffic-type qualification) is applied. If
no such entry exists, then default heuristics based paging behavior
is applied.
-
ps (Packet
Switched) - All data and control activities that involve
packet services. SRVCC is also mapped to this traffic-type
as the voice is carried using PS service.
paging-profile paging_profile_name
The paging-profile
to apply for paging UE.
IMPORTANT:
If the associated paging-map
does not exist or does not have an entry matching the paging-trigger, the
MME performs paging as outlined in 'Default Heuristics Paging Behavior'
in the Heuristic and
Intelligent Paging chapter in the MME Administration Guide.
Usage:
Use this command to
apply different paging-profiles based on traffic types.
The command defines
the order (1 - highest, 7 - lowest) in
which the MME checks the entries in this paging-map. If
the paging trigger (like Downlink Data Notification or
MSC request) matches the traffic-type of that
entry, then the corresponding paging-profile is
used for paging the UE. If the paging trigger does not
match, then the next entry in the precedence order is picked
and checked for a match. If no match is found in the entire
paging-map table then default heuristic paging profile
is adopted.
If the MME receives
another paging trigger (for example from the MSC for CSFB) while paging
is already in progress, the MME checks whether a higher
precedence paging profile can be applied. If the new trigger
has a paging-map entry with a higher precedence, the
MME restarts the paging process using the paging-profile
associated with the new map entry.
Paging is typically
triggered when either the MSC indicates that there is an incoming
call to the UE (Call Service, CS), or
when the S-GW sends a Downlink Data Notification (Packet Service, PS) to
the MME, or when there is a bearer/PDN request
coming from the P-GW/S-GW.
Refer
to the Heuristic and
Intelligent Paging chapter in the MME Administration Guide for
more information.
Related Commands
Refer to the paging-profile command
in the LTE Policy Configuration
Commands chapter to create the paging profiles used in this command.