4 Connected line identification restriction (COLR)
23.0813GPPLine Identification supplementary servicesRelease 17Stage 2TS
4.1 Handling of connected line identification restriction
4.1.1 General
If the terminating party has connected line identification restriction provisioned and it is impossible to indicate to the originating network (due to interworking) that the number should not be presented to the originating party, the connected line identity shall not be delivered to the originating network.
4.1.2 Interrogation
Status check
The mobile subscriber can request the status of the supplementary service and be informed if the service is provided to him/her. This procedure is illustrated in figure 4.1.
Figure 4.1: Interrogation of connected line identification restriction
4.2 Functions and information flows
The following Mobile Additional Functions have been identified for the PLMN:
MAF040
Determination of the connected line identification restriction subscription
The ability of a PLMN component to determine whether the supplementary service is provisioned for the mobile subscriber. See figure 4.2.
Location: VLR.
MAF041
Determination of the connected party number for offering to the calling party
The ability of a PLMN component to determine and to forward the connected line identity and related indications to the calling party. See figure 4.3.
Location: terminating MSC.
The information flow is shown in figures 4.4.
Figure 4.2: MAF040 Determination of connected line identification restriction subscription
(VLR)
Figure 4.3: MAF041 Determination of the presentation indicator
Figure 4.4: Information flow for connected line identification restriction:
mobile station or fixed terminal to mobile station
NOTE: OR1: COLR provisioned Y: yes N: no
OR2: Presentation Indicator Value a: allowed
b: restricted
OR3: Override category
**: A subaddress may be received from the MS
info: information SI: screening indicator
req: request PI: presentation indicator
ack: acknowledge LI: line identity
4.3 Information stored in the HLR
COLR may have the following logical states (refer to 3GPP TS 23.011 for an explanation of the notation):
Provisioning State Registration State Activation State HLR Induction State
(Not Provisioned, Not Applicable, Not Active, Not Induced)
(Provisioned, Not Applicable, Active and Operative, Not Induced)
The HLR shall store the logical state of COLR (which shall be one of the valid states listed above) on a per subscriber basis.
4.4 State transition model
The following figure shows the successful cases of transition between the applicable logical states of COLR. The state changes are caused by actions of the service provider.
Note that error cases are not shown in the diagram as they normally do not cause a state change. Additionally, some successful requests may not cause a state change. Hence they are not shown in the diagram.
Figure 4.5: State transition model for COLR
4.5 Transfer of information from HLR to VLR
When the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of COLR.
If the logical state of COLR is changed while a subscriber is registered on a VLR then the HLR shall inform the VLR of the new logical state of COLR.
4.6 Information stored in the VLR
For COLR, the VLR shall store the service state information received from the HLR.
4.7 Handover
Handover will have no impact on the control procedures and the operation of the service.
4.8 Interworking
The VPLMN needs to distinguish three cases in order to meet data privacy requirements in an environment where support of COLP and COLR is optional:
a) the HPLMN supports COLR, and COLR is provisioned for the subscriber;
b) the HPLMN supports COLR, but COLR is not provisioned for the subscriber;
c) the HPLMN does not support COLR.
In case a) the VPLMN must apply the COLR subscription as indicated by the data sent by the HPLMN.
In case b) the VPLMN must not apply COLR.
In case c) the VPLMN must apply an implicit COLR subscription.
To allow the VPLMN to make this distinction, the HLR and VLR behave as follows:
‑ If the HLR supports COLR, but COLR is not provisioned for the subscriber, the HLR shall inform the VLR that COLR is not provisioned.
‑ If the VLR supports COLR, but the HLR does not support COLR, the VLR shall behave in the same way as if COLR was provisioned for the subscriber, i.e. the connected line identity shall not be displayed to the calling subscriber unless the calling subscriber has COLR override capability. When interrogating the service status the subscriber shall be informed that COLR is provided to him and is active.
Annex A (informative):
Mapping of CLI
This annex defines the mapping rules of CLI parameters received via the NW-NW interface to CLI parameters to be sent to the MS.
|
Information received over the NW-NW interface |
Information sent to the MS |
|||||||
|---|---|---|---|---|---|---|---|---|
|
presentation indicator |
line identity |
additional presentation indicator |
additional line identity |
Cause of No CLI |
presentation indicator |
line identity |
Cause of No CLI |
|
|
CLIP not pro-vision-ed |
* |
* |
* |
* |
* |
– |
– |
– |
|
CLIP provisioned without override category |
– |
– |
– |
– |
– |
not available |
– |
– |
|
not available |
– |
– |
– |
– |
not available |
– |
– |
|
|
allowed |
digits |
– |
– |
– |
allowed |
digits of line identity |
– |
|
|
allowed |
digits |
+ |
digits |
– |
allowed |
digits of additional line identity |
– |
|
|
restricted |
digits |
* |
* |
– |
restricted |
– |
– |
|
|
restricted |
digits |
* |
* |
unavailable |
restricted |
– |
unavailable |
|
|
restricted |
digits |
* |
* |
reject by user |
restricted |
– |
reject by user |
|
|
restricted |
digits |
* |
* |
interaction with other service |
restricted |
– |
interaction with other service |
|
|
restricted |
digits |
* |
* |
payphone |
restricted |
– |
payphone |
|
|
restricted by network |
digits |
– |
– |
– |
not available |
– |
– |
|
|
restricted by network |
digits |
allowed |
digits |
– |
allowed |
digits of additional line identity |
– |
|
|
Information received over the NW-NW interface |
Information sent to the MS |
|||||||
|---|---|---|---|---|---|---|---|---|
|
presentation indicator |
line identity |
additional presentation indicator |
additional line identity |
Cause of No CLI |
presentation indicator |
line identity |
Cause of No CLI |
|
|
CLIP provisioned with override category |
– |
– |
– |
– |
– |
not available |
– |
– |
|
not available |
– |
– |
– |
– |
not available |
– |
– |
|
|
allowed |
digits |
– |
– |
– |
allowed |
digits of line identity |
– |
|
|
allowed |
digits |
+ |
digits |
– |
allowed |
digits of additional line identity |
– |
|
|
restricted |
digits |
– |
– |
– |
restricted |
digits of line identity |
– |
|
|
restricted |
digits |
+ |
digits |
– |
restricted |
NOTE 1 |
– |
|
|
restricted |
digits |
+ |
digits |
unavailable |
restricted |
NOTE 1 |
unavailable |
|
|
restricted |
digits |
+ |
digits |
reject by user |
restricted |
NOTE 1 |
reject by user |
|
|
restricted |
digits |
+ |
digits |
interaction with other service |
restricted |
NOTE 1 |
interaction with other service |
|
|
restricted |
digits |
+ |
digits |
payphone |
restricted |
NOTE 1 |
payphone |
|
|
restricted |
digits |
– |
– |
unavailable |
restricted |
digits of line identity |
unavailable |
|
|
restricted |
digits |
– |
– |
reject by user |
restricted |
digits of line identity |
reject by user |
|
|
restricted |
digits |
– |
– |
interaction with other service |
restricted |
digits of line identity |
interaction with other service |
|
|
restricted |
digits |
– |
– |
payphone |
restricted |
digits of line identity |
payphone |
|
|
restricted by network |
digits |
– |
– |
– |
restricted |
digits of line identity |
– |
|
|
restricted by network |
digits |
allowed |
digits |
– |
allowed |
digits of additional line identity |
– |
|
– parameter not present
* parameter absent or present, if present it may have any value
+ parameter present, it may have any value
NOTE 1: Network Option to send either digits of the line identity or digits of additional line identity applies.
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
Apr 1999 |
Transferred to 3GPP CN1 |
||||||
|
CN#03 |
Approved at CN#03 |
3.0.0 |
|||||
|
Upgrade of references from 2G to 3G |
3.0.1 |
||||||
|
CN#08 |
Enhanced handling of presentation indicators for CLIP |
3.1.0 |
|||||
|
CN#11 |
Release 4 after CN#11 |
4.0.0 |
|||||
|
CN#16 |
Release 5 after CN#16 |
5.0.0 |
|||||
|
CN#17 |
0006 |
Correction of ‘Cause of no CLI’ handling in SDLs |
5.1.0 |
||||
|
CN#19 |
0007r1 |
Correction to interworking between CLIP enhancement and CAMEL |
5.2.0 |
||||
|
CN#25 |
0008 |
Editorial correction of table definition |
6.0.0 |
||||
|
CT#36 |
Upgraded unchanged from Rel-6 |
7.0.0 |
|||||
|
CT#42 |
Upgraded unchanged from Rel-7 |
8.0.0 |
|||||
|
CT#46 |
– |
Update to Rel-9 version (MCC) |
9.0.0 |
||||
|
2011-03 |
– |
Update to Rel-10 version (MCC) |
10.0.0 |
||||
|
2011-12 |
0009 |
CLI interactions with ACR |
11.0.0 |
||||
|
2014-09 |
– |
Update to Rel-12 version (MCC) |
12.0.0 |
||||
|
2015-12 |
– |
Update to Rel-13 version (MCC) |
13.0.0 |
||||
|
2017-03 |
– |
Update to Rel-14 version (MCC) |
14.0.0 |
||||
|
2018-06 |
– |
Update to Rel-15 version (MCC) |
15.0.0 |
||||
|
2020-07 |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
||||
|
2022-03 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |