8 Information storage

03.693GPPStage 2TSVoice Broadcast Service (VBS)

8.1 Information stored in the GCR

8.1.1 Information used for routing of service subscriber originated voice broadcast calls

The GCR shall hold for a related MSC area for each group ID and cell from which voice broadcast calls can be established by service subscribers the broadcast call reference to be used for a voice broadcast call to be established and an indication whether the originating MSC is the group call anchor MSC.

If the originating MSC is the group call anchor MSC, the GCR shall provide the broadcast call attributes related to that broadcast call reference as defined in subclause 8.1.2 to the originating MSC and the originating MSC shall establish the voice broadcast call.

If the originating MSC is not the anchor MSC, the GCR shall provide the broadcast call reference plus the routing information identifying the anchor MSC to the originating MSC and the originating MSC shall route the voice broadcast call to the anchor MSC.

NOTE: In case the GCR function is distributed over different physical entities, each may hold only the information needed to treat requests coming from the MSCs connected to the physical GCR entity.

8.1.2 Broadcast call attributes

Each MSC involved in a voice broadcast call requests its proper broadcast call attributes from its related GCR. For any broadcast call reference the GCR shall provide the corresponding broadcast call attributes to the requesting MSC. These lists shall be programmed by the service provider at registration of the network specific service configuration.

The contents of each list related to requests of the group call anchor MSC is as follows:

– a list of cells inside the MSC area of the group call anchor MSC into which the call is to be sent (part of the group call area), see subclause 8.1.2.1;

– a list of group call relay MSCs into which the call is to be sent;

– information on the cipher algorithm and the group key to be used for this voice broadcast call;

– information on the codecs allowed for this voice broadcast call;

– a list of identities of dispatchers to which a dedicated link is to be established, see subclause 8.1.2.2;

– a list of identities of dispatchers which are allowed to initiate the voice broadcast call, see subclause 8.1.2.2;

– a list of identities of dispatchers which are allowed to terminate the voice broadcast call, see subclause 8.1.2.2;

– the default priority level related to that voice broadcast call if eMLPP applies, see subclause 8.1.2.3;

– a status flag indicating if a voice broadcast call with the related group call reference is on-going, see subclause 11.3.1.1.1.

The contents of each list related to requests of a group call relay MSC is as follows:

– A list of cells inside the MSC area of the requesting MSC into which the call is to be sent (part of the group call area), see subclause 8.1.2.1;

– Identity of the group call anchor MSC;

– a status flag indicating if a voice broadcast call with the related group call reference is on-going, see subclause 11.3.1.1.1.

8.1.2.1 Group call area

The group call area is defined as a list of cells inside the network. The cells shall be defined by their cell identification consisting of the Location Area Code and the Cell Identity as defined in 3GPP TS 08.08 and are therefore uniquely identified in the network.

In the case the group call area extends over several MSCs, only the cells belonging to the requesting MSC are included in the broadcast call attributes.

8.1.2.2 Dispatcher identities

Dispatcher identities shall be ISDN numbers or MSISDN numbers with the structure according to CCITT Recommendation E.164. They shall correspond both to the number to be used to establish a call toward the dispatcher and the number provided as calling line identification when the call is originated by a dispatcher.

The list of dispatcher identities to which a dedicated link is to be established shall be passed to the MSC so that the distribution function can be set up.

The list of dispatcher identities which are allowed to initiate voice broadcast calls is used by the anchor MSC for verification for a voice broadcast call establishment by a dispatcher.

The list of dispatcher identities which are allowed to terminate voice broadcast calls is used by the anchor MSC for verification for a voice broadcast call release by a dispatcher.

8.1.2.3 Priorities

If the eMLPP supplementary service is applied to a voice broadcast call, the priority level shall be stored in the GCR.

For further details see 3GPP TS 23.067.

8.2 Information managed per subscriber

8.2.1 Stored in the HLR

The following additional information shall be stored in the HLR:

– the subscription option for voice broadcast calls which can be made in the HPLMN only or also in case of roaming;

– a list of all the group IDs for which a service subscriber has a subscription;

– an indication whether the subscriber is entitled to establish a voice broadcast call to one or more group IDs of his subscription.

The group IDs are defined in subclause 9.1.

A service subscriber shall not be provided with more than 50 group IDs.

8.2.2 Stored in the VLR

The list of all the group IDs a service subscriber is entitled to use and the entitlement to establish a voice broadcast call to a group ID shall be brought forward to a VLR at the same time as other subscriber information is copied, and VLR entries shall be modified when corresponding HLR records are changed.

8.2.3 Stored in the SIM

The information detailed in subclause 8.2.1 also needs to be stored on the SIM. The service subscriber shall be able to deactivate or reactivate a group ID by MMI interaction so that the mobile station does ignore notification messages to this group ID.

For each group ID where data confidentiality may be applied, the SIM needs to store the cipher algorithm to be used and the possible group keys.

8.3 Information used for routing of dispatcher originated broadcast calls

Routing of dispatcher originated calls shall be performed on the MSISDN number received at a GMSC in the Initial_Address_Message.

– Because the group call reference is included in the called MSISDN number as defined in subclause 9.2d the routing information can be derived by the routing function of the GMSC. The GMSC afterwards directly routes the call request to the group call anchor MSC without requesting an HLR.