Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 23.081  Word version:  17.0.0

Top   Top   Up   Prev   Next
0…   1…   2…   3…   4…   A…

 

4  Connected line identification restriction (COLR)p. 41

4.1  Handling of connected line identification restrictionp. 41

4.1.1  Generalp. 41

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  Interrogationp. 41

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.
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 4.1: Interrogation of connected line identification restriction
Up

4.2  Functions and information flowsp. 42

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 Figure 4.4.
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 4.2: MAF040  Determination of connected line identification restriction subscription (VLR)
Up
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 4.3: MAF041  Determination of the presentation indicator
Up
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 4.4: Information flow for connected line identification restriction: mobile station or fixed terminal to mobile station
Up

4.3  Information stored in the HLRp. 46

COLR may have the following logical states (refer to 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.
Up

4.4  State transition modelp. 47

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.
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 4.5: State transition model for COLR
Figure 4.5: State transition model for COLR
(⇒ copy of original 3GPP image)
Up

4.5  Transfer of information from HLR to VLRp. 47

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 VLRp. 47

For COLR, the VLR shall store the service state information received from the HLR.

4.7  Handoverp. 47

Handover will have no impact on the control procedures and the operation of the service.

4.8  Interworkingp. 47

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:
  1. the HPLMN supports COLR, and COLR is provisioned for the subscriber;
  2. the HPLMN supports COLR, but COLR is not provisioned for the subscriber;
  3. 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.
Up

Up   Top   ToC