5 Functional requirements
22.0973GPPMultiple Subscriber Profile (MSP) Phase 2Release 17Service descriptionStage 1TS
5.1 Handling of the MSP Service
This clause describes the normal procedures for the handling of the MSP service.
5.1.1 Provision
The MSP service shall be provided after prior arrangement with the service provider. If the MSP service is provisioned for the subscriber at the first time the subscriber shall also be provisioned with at least two profiles.
5.1.2 Withdrawal
Withdrawal of the MSP service shall be done by either the service provider at the subscriber’s request or for administrative reasons. The MSP service shall be withdrawn when there is only one profile remaining.
5.1.3 Activation
The MSP service is activated by the service provider as a result of provision.
5.1.4 Deactivation
The MSP service is deactivated by the service provider as a result of withdrawal.
5.1.5 Invocation
The MSP service is invoked by mobile originated and mobile terminating calls.
5.2 Handling of the Profile
This subclause describes the normal procedures for selecting the registered profile for mobile originated calls, short messages and call independent supplementary service related activities. For mobile terminating activities the profile is selected automatically by association with the MSISDN addressed.
5.2.1 Provision
The provision of profiles (up to a maximum of four) is provided by prior arrangement with the service provider. The subscriber may select any provisioned profile on a per call basis or register one of them. The subscriber will nominate one of their provisioned profiles as the default profile to be used when roaming to non-supporting networks. The subscriber may subsequently nominate an alternative default (i.e. roaming) profile, nevertheless the default profile can only be changed by the service provider.
5.2.2 Withdrawal
The Service Provider shall be able to withdraw profiles. The registered profile shall never be withdrawn, and consequently if the registered profile needs to be withdrawn the service provider shall first register the subscriber onto another profile.
5.2.3 Registration
Registration is the procedure by which information is written to the network to allocate a particular profile to be used for all outgoing calls and supplementary service related activities. Registration to a profile shall take place either by the service provider or with an appropriate control procedure by the subscriber as defined in 3GPP TS 22.030 [3]. At all times only one profile shall be registered. The network shall indicate to the user whether an attempt to register a profile has been successful or not.
5.2.4 Selection
The profile to be used for mobile originated calls is selected either implicitly or explicitly:
– Implicit selection occurs if the served subscriber does not indicate a profile ID when initiating a call or short message. In this case the selected profile is the registered profile.
– Explicit selection occurs if the served subscriber does indicate a profile ID when initiating a call or short message.
The control procedure used to select the profile is as defined in 3GPP TS 22.030 [3].
For mobile terminating activities, the profile is selected according to the MSISDN addressed.
5.2.5 Erasure
A previous registration can be erased in the following ways:
– the subscriber can register to another profile which causes the previous registration to be overridden;
– the registered profile is erased as a result of withdrawal of the MSP service.
5.2.6 Interrogation
The subscriber shall be able to interrogate which profile is the registered profile and all other available profile IDs, with an appropriate control procedure as defined in 3GPP TS 22.030 [3].
5.3 Normal operation with successful outcome
5.3.1 Mobile Originating Calls
Mobile originating calls shall be handled according to the selected profile. This shall be the registered profile unless an alternative is explicitly selected by the subscriber. Profiles are registered and selected according to control procedures in 3GPP TS 22.030 [3].
Any activity that is normally chargeable shall be identified against the selected profile.
5.3.2 Mobile Terminating Calls
The MSISDN addressed shall be used to determine the profile to be used. If there are any active supplementary services, which are applicable to the telecommunication service within the profile, then those supplementary services shall apply. For example, if the MS is busy in a call, further incoming call attempts shall be rejected or busy, even if they were on a different profile. This shall not prevent the normal operation of Call Waiting or Call Forwarding if appropriate.
The serving network shall indicate the profile towards the mobile station done by changing the alerting pattern.
Any activity that is normally chargeable shall be identified against the profile used for the mobile terminating activity.
5.3.3 Mobile Originating Call Independent Supplementary Service Activities
The activity shall be handled according to the registered profile.
5.3.4 Call Related Supplementary Service Activities
The handling of call related supplementary service activities is described in clause 7.
5.4 Exceptional procedures or unsuccessful outcome
5.4.1 Roaming into networks not supporting MSP
The default profile shall be used for outgoing traffic when the subscriber roams to a non-supporting network.
Incoming calls and short messages to all profiles will still be received.
5.4.2 Registration or Selection of a profile that is already registered
If there is an attempt to register a profile that is already the registered profile, the registration shall continue uninterrupted and the user shall not be informed.
If there is an attempt to select a profile that is already the registered profile, the selection shall continue uninterrupted and the user shall not be informed.
5.4.3 Registration or Selection of a non-provisioned profile
If there is an attempt to register a profile that has not been provisioned, the registration attempt shall fail and the user shall be informed. The registered profile shall remain unchanged.
If there is an attempt to select a profile that has not been provisioned the selection and associated call activity shall fail. The user shall be informed. The registered profile shall remain unchanged.
5.4.4 Registration or Selection attempts where MSP is not provisioned
If there is an attempt by a subscriber who does not have MSP provisioned to register a profile, the registration attempt shall fail and subscriber shall be informed.
If there is an attempt by a subscriber who does not have MSP provisioned to select a profile, the selection attempt shall fail and subscriber shall be informed.