TS 22.097
MSP —
Multiple Subscriber Profile, Phase 2 –
Stage 1

3GPP‑Page ETSI‑search CONTENT_↓

V18.0.1 (PDF) 2024/03 15 p.

V17.0.0 2022/03 15 p.

V16.0.0 2020/06 15 p.

V15.0.0 2018/06 14 p.

V14.0.0 2017/03 15 p.

V13.0.0 2015/12 15 p.

V12.0.0 2014/10 15 p.

V11.0.0 2012/09 15 p.

V10.0.0 2011/04 15 p.

V9.0.0 2009/12 15 p.

V8.0.0 2009/01 15 p.

V7.0.0 2007/06 15 p.

V6.0.0 2004/12 15 p.

V5.0.0 2002/07 15 p.

V4.1.0 2002/03 15 p.

V3.2.0 2000/10 15 p.

GSM Rel-98 v7.1.0 1998/06 14 p.

Rapporteur:: Mr. Deol, Amar
Huawei Technologies Co. Ltd.

Content for TS 22.097 Word version: 18.0.1

1 Scope p. 6

The present document gives an overall view of how this service shall operate both in the PLMN and within the Mobile Station (MS). This TS defines functionality and is not intended to constrain implementation.

2 References p. 6

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.

References are either specific (identified by date of publication, edition number, version number, etc.) or non specific.
For a specific reference, subsequent revisions do not apply.
For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.

[1]

TR 21.905: "Vocabulary for 3GPP Specifications".

[2]

TS 22.004: "General on supplementary services".

[3]

TS 22.030: "Man-machine Interface (MMI) of the mobile station (MS)".

[4]

TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point (PP)".

[5]

TS 22.135: "Multicall".

[6]

TS 22.001: "Principles of circuit telecommunication services supported by a Public Land Mobile Network (PLMN)".

3 Definitions and abbreviations p. 6

3.1 Definitions p. 6

For the purposes of this TS the following definitions apply:

Subscriber:

The user who is provisioned with the MSP service

Profile:

A profile consists of a set of telecommunications services for the subscriber. In the case of the single numbering scheme there is a unique MSISDN associated with each profile. In the multi-numbering scheme there is the ability to have a unique MSISDN associated with each basic service in each profile.

Service Provider (SP):

The organisation through which the subscriber obtains PLMN telecommunication services. This may be the network operator or possibly a separate body.

Profile Identification (Profile ID):

The profile IDs allow unambiguous identification of each profile. This will allow the subscriber to select the preferred profile for outgoing calls and for subscriber actions. For terminating calls the profile ID shall be part of the notification of the profile.

Registered Profile:

The registered profile is that registered by/for the subscriber

Selected Profile:

For mobile originated calls and short messages this is the registered profile unless the subscriber explicitly selects an alternative profile. For mobile terminating activities, this is the profile associated with the MSISDN addressed.

Mobile Terminating Activities:

These include mobile terminating calls, short messages (SMS MT) and Call Independent Supplementary Services (e.g. NI-USSD).

Default Profile:

Profile to be used when roaming to non-supporting network

3.2 Abbreviations p. 7

For the purposes of this TS the following abbreviations apply, in addition, abbreviations used in this TS are listed in TR 21.905.

MSP

Multiple Subscriber Profile

4 Description p. 7

Multiple Subscriber Profile is an optional service to enable mobile subscribers to have several profiles associated with a single IMSI, with each profile being a subscription option. Each profile may be used for mobile originated and mobile terminated calls.

Up to four different profiles can be provisioned against a subscriber using the MSP feature. This will allow the subscriber to separate her telecommunication service needs into different identities (e.g. business and home).

The charges accrued for services shall be associated with the appropriate profile, allowing separate charging for each profile.

A supporting visited network shall indicate [on the billing record] for charging purposes the profile used.

4.1 Applicability to telecommunication services p. 7

The applicability of this supplementary service is defined in TS 22.004.

5 Functional requirements p. 7

5.1 Handling of the MSP Service p. 7

This clause describes the normal procedures for the handling of the MSP service.

5.1.1 Provision p. 7

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 p. 7

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 p. 7

The MSP service is activated by the service provider as a result of provision.

5.1.4 Deactivation p. 7

The MSP service is deactivated by the service provider as a result of withdrawal.

5.1.5 Invocation p. 8

The MSP service is invoked by mobile originated and mobile terminating calls.

5.2 Handling of the Profile p. 8

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 p. 8

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 p. 8

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 p. 8

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 TS 22.030. 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 p. 8

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 TS 22.030.

For mobile terminating activities, the profile is selected according to the MSISDN addressed.

5.2.5 Erasure p. 8

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 p. 8

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 TS 22.030.

5.3 Normal operation with successful outcome p. 9

5.3.1 Mobile Originating Calls p. 9

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 TS 22.030.

Any activity that is normally chargeable shall be identified against the selected profile.

5.3.2 Mobile Terminating Calls p. 9

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 p. 9

The activity shall be handled according to the registered profile.

5.3.4 Call Related Supplementary Service Activities p. 9

The handling of call related supplementary service activities is described in clause 7.

5.4 Exceptional procedures or unsuccessful outcome p. 9

5.4.1 Roaming into networks not supporting MSP p. 9

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 p. 9

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 p. 9

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 p. 10

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.

6 Interaction with supplementary services p. 10

The profile used when a supplementary service is invoked will be subject to the charging principles and invocation requirements relevant to that supplementary service. The service provider may decide which profiles to charge for the service provision.

6.1 Line Identification Services p. 10

The profile in use for the incoming or outgoing call shall be used for the line identification services.

The Line Identification services will be provisioned on a per subscriber basis. If provisioned, the Line Identification services shall apply over all profiles.

6.2 Call Hold (HOLD) p. 10

The HOLD service can only be invoked if the profile for that active call has the HOLD service provisioned.

6.3 Call Waiting (CW) p. 10

CW for an incoming call can only be invoked if the profile for the ongoing call has the CW service provisioned and active although the incoming call may be on any profile.

6.4 Call Forwarding p. 10

Call Forwarding will be available to the subscriber per-profile. An operator specific control procedure may be used by the subscriber to control the call forwarding service.

The subscriber shall be able to forward calls to from one profile to another profile.

6.5 Multi Party Service (MPTY) p. 10

The MPTY service can only be invoked or an MPTY call controlled or extended if MPTY is provisioned for the served subscriber for each profile(s) associated with the MPTY call leg(s).

6.6 Closed User Group (CUG) p. 10

An MO call shall be treated according to the rules of the CUG service if CUG is provisioned for the selected profile. An MT call shall be treated according to the rules of the CUG service if CUG is provisioned for the profile defined by the called MSISDN.

6.7 Advice of Charge (AoC) p. 10

If subscribed to, AoCI or AoCC shall be applicable to the selected profile. Each profile shall have a separate meter (ACM) and a separate upper limit (ACMmax) when AoCC is subscribed. There shall be an overall meter for all profiles, with its own upper limit for AoCC if subscribed. For normal operation both the individual meter applicable to the selected profile and the overall meter shall be incremented.

When roaming to a non-supporting network, only the overall meter shall be incremented.

6.8 Call Barring p. 11

Call Barring will be available to the subscriber per-profile. An operator specific control procedure may be used by the subscriber to control the call barring service.

6.9 Explicit Call Transfer (ECT) p. 11

ECT can only be invoked if the service is provisioned for each profile which governs a call leg to be joined by the ECT service.

6.10 CCBS p. 11

The CCBS service shall be provisioned per profile. The option not to be a target of CCBS requests shall also apply per profile. When the subscriber is informed of a CCBS recall, the profile in use when the CCBS request was activated shall be used for the CCBS call. If the subscriber activates a CCBS call request on a profile that is not the default profile and subsequently moves to a network not supporting MSP Phase 2, then if the CCBS recall matures, the corresponding CCBS request shall be suspended until the subscriber next registers on a network supporting MSP Phase 2.

The limit to the number of outstanding CCBS requests that can be activated by the subscriber shall apply regardless of the number of profiles.

The limit to the number of outstanding CCBS requests that can be activated against the subscriber shall apply regardless of the number of profiles.

6.11 eMLPP p. 11

eMLPP shall be provisioned per subscriber.

6.12 Multicall p. 11

The multicall supplementary service shall be provisioned on a per subscriber basis. If provisioned, Nbr_SN, Nbr_SB, and Nbr_user shall apply over all profiles. (See TS 22.135 "3.1 Definitions" for detailed information)

7 Interaction with other services p. 11

7.1 The Multi-Numbering Scheme p. 11

Each profile may employ the single-numbering scheme or the multi-numbering scheme. The multi-numbering scheme is described in TS 22.001. For each of the profile(s) defined above, it shall be possible for the subscriber to be allocated different MSISDNs for different basic services.

7.2 The Short Message Service p. 11

The Short Message Service is described in TS 23.040. It will not be possible to indicate the profile used for the MT case. All MO short messages will be sent from the default profile.

MO short messages can be sent from (and charged to) the registered profile or an explicitly selected profile.

Whilst roaming in a network not supporting MSP Phase 2, all MO short messages will be sent from and charged to the default profile.

7.3 Interactions with CAMEL p. 12

CAMEL based services can be provisioned either per subscriber or per profile depending on the operator specific implementation in the CSE.

For call independent supplementary service procedures for CAMEL based services, information to identify the registered profile shall be passed to the CAMEL server.

7.4 Interactions with OR p. 12

No interaction

7.5 Operator Determined Barring p. 12

ODB shall apply either per subscriber or per profile.

7.6 Roaming restrictions p. 12

These will apply on a per subscriber basis.

8 Cross-Phase Compatibility p. 12

The default profile will be sent to the visited network and can be addressed by non-supporting networks.

Mobile terminated calls to a non-supporting MS shall still be accepted but the indication of profile may not be supported.