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…

 

1  Calling line identification presentation (CLIP)p. 8

1.1  Handling of calling line identification presentationp. 8

1.1.1  Interrogationp. 8

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

1.2  Functions and information flowsp. 9

The following Mobile Additional Functions have been identified for the PLMN:
MAF001
Determination of the calling line identification presentation subscription
The ability of a PLMN component to determine whether the supplementary service is provisioned for the mobile subscriber. See Figure 1.2.
Location: VLR.
MAF002
Determination of the calling party number for offering to the called party
The ability of a PLMN component to determine and to forward the calling line identity and related indications to the called party. See Figure 1.3.
Location: destination MSC.
The information flow is shown in Figure 1.9.
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 1.2: MAF001 Determination of calling line identification presentation subscription (VLR)
Up
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 1.3: MAF002 Determination of the information for offering to the called party (destination MSC)
Up
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 1.4: Procedure Cause_of_no_CLI
Figure 1.4: Procedure Cause_of_no_CLI
(⇒ copy of original 3GPP image)
Up
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 1.5: Addition of line identification information to Send Routeing Info message.
Up
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 1.6: Addition of line identification information to Provide Roaming Number message.
Up
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 1.7: Storing of Line Identification in destination VLR
Up
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 1.8: Addition of line identification information to Complete Call/Process Call Waiting message.
Up
Copy of original 3GPP image for 3GPP TS 23.081, Fig. 1.9: Information flow for calling line identification presentation: mobile station or fixed terminal to mobile station
Up

1.2.1  Optional capability to carry calling line identificationp. 19

When GMSC is performing Send Routing Info query it may pass calling line identification to the HLRb. The calling line identification shall be in international format. If the HLRb receives calling line identification within Send Routing Info it may pass unmodified calling line identification within Provide Roaming Number to the VLRb. HLR shall not pass calling line identification in the HPLMN nor in the case where sending of the CLI information is explicitly denied to the destination network..
If MSCb receives calling line identification only from signalling it shall use that parameter for presentation purposes i.e. normal handling as described in the previous clause applies.
If MSCb receives Cause of no CLI from signalling it shall be sent to the VLRb by Send Info for Incoming Call query.
If MSCb receives calling line identification and/or Cause of no CLI from VLRb and it supports the feature it shall use that parameter for presentation purposes. In this case calling line identification is stored in the VLRb and when the set-up message is processed the handling described in the previous clause is done using the stored calling line identification.
Up

1.2.2  Information elements used in the messagesp. 20

Information Element Logical Information element name Information element Required Information element description
Calling Party NumberSIMCalling Party Number contains screening indicator (SI), presentation indicator (PI) and line identity (LI) as mandatory information.
PIM
LIM
Generic NumberaSIMGeneric Number contains additional screening indicator (aSI), additional presentation indicator (aPI) and additional line identity (aLI) as mandatory information.
aPIM
aLIM
Cause of no CLIunavailableMCause of no CLI contains detailed Cause of no CLI (unavailable, reject by user, interaction with other service, coin line/payphone) as mandatory information.
reject by userM
interaction with other serviceM
coin line/payphoneM
Up

1.2.3  Parameters in Send Routeing Info and Provide Roaming Number for CLIp. 20

Message Message sender Information element name Information element Required Information element description
Send Routeing InfoGMSC--Refer to TS 23.018.
In addition:
Calling Party NumberCThe information element is present if GMSC received calling party number from originating network; otherwise it shall be absent.
Generic NumberCThe information element is present if GMSC received additional calling party number from originating network or from gsmSCF because of a CAMEL service; otherwise it shall be absent.
Message Message sender Information element name Information element Required Information element description
Provide Roaming NumberHLR--Refer to TS 23.018.
In addition:
Calling Party NumberCThe information element is present if HLR received calling party number from GMSC and MS B is outside of home country; otherwise it shall be absent.
Generic NumberCThe information element is present if HLR received additional calling party number from GMSC and MS B is outside of home country; otherwise it shall be absent.
Up

1.2.4  Messages between MSC and VLR in destination networkp. 21

Message Message sender Information element name Information element Required Information element description
Complete CallVLR--Refer to TS 23.018.
In addition:
Calling Party NumberCThe information element is present if it is stored in VLR; otherwise it shall be absent.
Generic NumberCThe information element is present if it is stored in VLR; otherwise it shall be absent.
Cause of no CLICThe information element is present if it is stored in VLR; otherwise it shall be absent.
Process Call WaitingVLR--Refer to TS 23.018.
Calling Party NumberCThe information element is present if it is stored in VLR; otherwise it shall be absent.
Generic NumberCThe information element is present if it is stored in VLR; otherwise it shall be absent.
Cause of no CLICThe information element is present if it is stored in VLR; otherwise it shall be absent.
Send Info for Incoming CallMSC--Refer to TS 23.018. In addition:
Cause of no CLICThe information element is present if MSC received Cause of no CLI; otherwise it shall be absent.
Up

1.3  Information stored in the HLRp. 21

CLIP 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 CLIP (which shall be one of the valid states listed above) on a per subscriber basis.
The HLR shall also store the subscription option "override category" on a per subscriber basis.
This parameter takes one of the following values:
1.
yes;
2.
no.
Up

1.4  State transition modelp. 22

The following Figure shows the successful cases of transition between the applicable logical states of CLIP. 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. 1.9x: State transition model for CLIP
Figure 1.9x: State transition model for CLIP
(⇒ copy of original 3GPP image)
Up

1.5  Transfer of information from HLR to VLRp. 22

If the provisioning state for CLIP is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of CLIP. The HLR shall send the override category if the VLR is in the HPLMN country. The HLR may send the override category if the VLR is outside the HPLMN country.
If the logical state of CLIP or the override category is changed while a subscriber is registered on a VLR then the HLR shall inform the VLR of the new logical state of CLIP. If the override category is changed and the provisioning state of CLIP is "Provisioned" then the HLR shall inform the VLR about the new override category when the VLR is in the HPLMN country. The HLR may inform the VLR about the new override category when the VLR is outside the HPLMN country.
Up

1.6  Information stored in the VLRp. 22

For CLIP, the VLR shall store the service state information and override category received from the HLR.
If not received from the HLR (case of roaming outside the HPLMN country), the override category shall be set to the default value "no".

1.7  Handoverp. 23

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

1.8  Interactions with other supplementary servicesp. 23


Up   Top   ToC