Content for TR 22.952 Word version: 18.0.1

0… 4… 4.8… 5 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 6… A… B B.1 B.2 B.3 B.4 B.5 B.6 B.7 B.8 B.9 C D…

C Distinguishing Priority Service users and eMLPP users p. 48

As a Service Provider option, it is proposed that the following mechanism be used for distinguishing Priority Service users and eMLPP users.

Networks (HLR's/MSC's/VLR's) that support the hybrid service (eMLPP and Priority Service) are enhanced to support the prioritySubscription parameter in the EMLPP-Info parameter of the Insert Subscriber Data (ISD) message. The prioritySubscription parameter must be included for Priority Service data. For eMLPP data this parameter is not needed.

eMLPP or Priority Service only networks and/or networks that do not support eMLPP or Priority Service do not need to be changed to support the new prioritySubscription parameter in the ISD message. That is, network operators that do not want to offer the hybrid service (eMLPP and Priority Service) do not have to upgrade their networks.

For outbound roamers (roamers from hybrid networks), the hybrid HLR would make the determination on whether data should be sent to the MSC/VLR. For example, if an eMLPP subscriber defined in the hybrid HLR roams to a Priority Service MSC/VLR, the HLR would not send the EMLPP-Info parameter to the MSC/VLR.

For inbound roamers (roamers to hybrid networks), the hybrid MSC/VLR would make the determination of how to treat the EMLPP-Info parameter if received in the ISD message.

When the MSC/VLR is operating in hybrid mode (i.e., supporting both services), the MSC would need to map eMLPP priorities B - 4 to 48.008 priorities 8-13 respectively as shown in Table C-1.

Table C-1: eMLPP Priority Levels Mapping

eMLPP Priority Levels (in HLR)	48.008 Priority Levels
A	1 (used for Service Technicians)
B	8 (used for Service Technicians)
0	9
1	10
2	11
3	12
4	13

TS 29.002 (ASN.1):

EMLPP-Info ::= SEQUENCE {
  maximumentitledPriority     EMLPP-Priority,
  defaultPriority             EMLPP-Priority,
  extensionContainer          ExtensionContainer  OPTIONAL,
  ... ,
  prioritySubscription        [0]  NULL  OPTIONAL}

Copy of original 3GPP image for 3GPP TS 22.952, Fig. C.2: Hybrid HLR

Figure C.2: Hybrid HLR
(⇒ copy of original 3GPP image)

The following Table summarizes the roaming scenarios of a Service User from a hybrid network.

Table C-2: Priority Service user Roaming from a Hybrid Network

MSC/VLR capability	ISD with PrioritySubscription parameter	Comments
Hybrid	Yes	When a Service User roams from one hybrid to another hybrid network, the HLR includes the PrioritySubscription parameter with the subscriber's priority service profile.
Priority Service only	Yes	When a Service User roams from a hybrid to a Priority Service only network, the HLR may include the PrioritySubscription parameter with the Service User's profile, but this parameter is ignored by the Priority Service only MSC/VLR as it does not recognize it. Alternatively the hybrid HLR may (through screening) block the inclusion of the PrioritySubscription parameter in the ISD message as it knows through datafill that it is communicating with a Priority Service only MSC/VLR.
eMLPP only	No	When a Service User roams from a hybrid to a eMLPP only network, the HLR does not send the Service User's profile as through datafill it knows that it is communicating with an eMLPP only MSC/VLR. The roamer will be treated as a normal (non-priority service) user.

Copy of original 3GPP image for 3GPP TS 22.952, Fig. C.3: Non-Hybrid HLR

Figure C.3: Non-Hybrid HLR
(⇒ copy of original 3GPP image)

The following Table summarizes the roaming scenario of a Service User roaming to a Hybrid network.

Table C-3: Priority Service user Roaming to a Hybrid Network

MSC/VLR capability	ISD with PrioritySubscription parameter	Comments
Hybrid	Not Applicable	When a Service User roams from a Priority Service only network to a hybrid network, the Priority Service only HLR sends the Service User's profile without the PrioritySubscription parameter as it does not support it. The hybrid MSC/VLR knows through datafill that it is communicating with a Priority Service only HLR and treats the roamer as a Service User.

The following Table summarizes the roaming scenarios of an eMLPP user from a hybrid network.

Table C-4: eMLPP User Roaming from a Hybrid Network

MSC/VLR capability	ISD with PrioritySubscription parameter	Comments
Hybrid	Not Applicable	When an eMLPP user roams from one hybrid to another hybrid network, the HLR sends the subscriber's eMLPP profile without the PrioritySubscription parameter as its not needed.
Priority Service only	Not Applicable	When an eMLPP user roams from a hybrid network to a Priority Service only network the HLR will not send the subscriber's eMLPP profile. The roamer will be treated as a normal (non-priority service) user.
eMLPP only	Not Applicable	When an eMLPP user roams from a hybrid network to an eMLPP only network the HLR sends the subscriber's eMLPP profile without the PrioritySubscription parameter as its not needed.

The following Table summarizes the roaming scenarios of an eMLPP user to a hybrid network.

Table C-5: eMLPP User Roaming to a Hybrid Network

MSC/VLR capability	ISD with PrioritySubscription parameter	Comments
Hybrid	Not Applicable	When an eMLPP user roams from eMLPP only network to a Hybrid network, the eMLPP only HLR sends the subscriber's eMLPP profile. The hybrid MSC/VLR knows through datafill that it is communicating with an eMLPP only HLR and treats the roamer as an eMLPP roamer.