How it Works
The Message Priority (MP) mechanism functions are:
-
MP (gtp, pfcp) is copied to transactions created for handling an incoming message and the same is copied to child transactions. These priority values are also copied into IPC metadata to send it across to destination pods.
-
Protocol pods (protocol, gtp) detect the incoming messages as WPS messages based on the message priority available in the incoming message. These message protocol pods use priority IPC streams toward a service pod.
Message Priority Profile Selection Logic
The following conditions apply for Message Priority Profiles selection:
-
Subscriber-policy must define group of subscriber and associated Operator policy.
-
Operator policy must define the associated DNN policy.
-
DNN policy must define a list of DNN and the associated DNN profile.
-
DNN profile must have an associated QoS profile name and WPS Profile name.
-
QoS Profile must have an associated message-priority-profile.
-
If the message-priority-profile is configured in WPS Profile and in S-GW QoS Profile for DNN, then the message-priority-profile configured in WPS profile takes priority.
-
If any message priority configuration is changed at run time, it is applicable for the new calls. For existing calls, new configuration is applicable when the Bearer is updated or a new Bearer is added.
-
The existing Message Priority gets displayed in outbound messages that are selftriggered, for example, DDN.
-
If an incoming PDN level GTP message such as CSReq, MBReq, DSReq, CBReq, DBReq, UBReq is received with valid message priority and if copy-incoming is set to true for any of the Bearers in that PDN, then the received messages priority gets copied in all the outgoing GTP/PFCP messages that are triggered by that incoming message.
-
If an incoming UE level GTP message such as HO DSReq, RAB is received with valid message priority and copy-incoming is set to true for any of the bearers in the PDN, then the received message priority will be copied in all outgoing GTP/PFCP messages(for that PDN) triggered by that incoming message.
-
If an incoming PFCP message such as Session report is received with valid messages priority and copy-incoming is set to true for any of the Sx bearer in that Sx session, then received messages priority gets copied in outgoing response messages.
-
Messages priority value is displayed in outgoing messages based on the following logic:
-
For GTP Messages:
-
For PDN level messages: If a PDN have multiple bearers which are marked as WPS (having different GTP message priorities), in that case highest messages priority (0 is highest and 15 is lowest) will be copied into outgoing GTP messages.
-
For UE level GTP messages: If UE have multiple bearers which are marked as WPS (having different GTP message priorities), in that case the highest messages priority(0 is highest and 15 is lowest) will be copied into outgoing GTP messages.
-
-
For PFCP Messages, if a Sx session has multiple bearers, which are marked as WPS (having different PFCP message priorities), in that case the highest messages priority (0 is highest and 15 is lowest) gets copied into outgoing PFCP messages.
-