Add files using upload-large-folder tool

marked/Rel-11/23_series/23072/raw.md

@@ -0,0 +1,587 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                             |    |
+|-----------------------------------------------------------------------------|----|
+| Foreword .....                                                              | 4  |
+| 1 Scope.....                                                                | 5  |
+| 2 Normative references .....                                                | 5  |
+| 3 Definitions and abbreviations .....                                       | 5  |
+| 3.1 Abbreviations .....                                                     | 5  |
+| 4 Information flow .....                                                    | 6  |
+| 5 Messages and their Contents.....                                          | 6  |
+| 5.1 Messages between the MS and the MSC .....                               | 6  |
+| 5.1.1 CD Request.....                                                       | 6  |
+| 5.1.2 CD Request ack .....                                                  | 7  |
+| 5.1.3 CD Request negative response .....                                    | 7  |
+| 5.2 Messages between the MSC and the VLR.....                               | 7  |
+| 5.2.1 Process Call Waiting negative response.....                           | 7  |
+| 5.2.2 Complete Call negative response .....                                 | 7  |
+| 5.2.3 Send Info for Incoming Call negative response .....                   | 8  |
+| 6 Functions of the serving MSC .....                                        | 8  |
+| 6.1 Procedure Handling_CD_MSC.....                                          | 8  |
+| 6.2 Procedure CD_Reject.....                                                | 8  |
+| 6.3 Procedure CD_Failure.....                                               | 8  |
+| 6.4 Procedure CD_UUS_Interaction.....                                       | 8  |
+| 6.5 Procedure CD_Success .....                                              | 8  |
+| 6.6 Procedure CD_Notify_SS_Invocation .....                                 | 8  |
+| 7 Functions of the serving VLR.....                                         | 15 |
+| 7.1 Procedure CD_Authorization.....                                         | 15 |
+| 7.2 Procedure CAMEL_Check_CD_Interaction.....                               | 15 |
+| 8 Interaction with other supplementary services.....                        | 18 |
+| 8.1 Line Identification services .....                                      | 18 |
+| 8.2 Call Forwarding services.....                                           | 18 |
+| 8.3 Call Waiting .....                                                      | 18 |
+| 8.4 Call Hold .....                                                         | 18 |
+| 8.5 Multi Party (MPTY).....                                                 | 18 |
+| 8.6 Closed User Group .....                                                 | 18 |
+| 8.7 Advice of Charge (AoC).....                                             | 18 |
+| 8.8 Call Barring Services .....                                             | 18 |
+| 8.9 Explicit call transfer (ECT).....                                       | 18 |
+| 8.10 Completion of Calls to Busy Subscriber (CCBS).....                     | 18 |
+| 9 Interaction with other network features .....                             | 19 |
+| 9.1 Customised Applications for Mobile network Enhanced Logic (CAMEL) ..... | 19 |
+| 9.2 Support of Optimal Routeing .....                                       | 19 |
+| 10 Information stored in the HLR.....                                       | 19 |
+| 11 State transition model.....                                              | 20 |
+| 12 Transfer of information from HLR to VLR.....                             | 20 |
+| 13 Information stored in the VLR.....                                       | 20 |
+| 14 Handover.....                                                            | 20 |
+| Annex A (informative): Change history.....                                  | 21 |
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3GPP.
+
+This specification describes the technical realization of the Call Deflection supplementary service within the 3GPP system.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version 3.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 Indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the specification;
+
+# --- 1 Scope
+
+This Technical Specification gives the stage 2 description of the Call Deflection supplementary service.
+
+# --- 2 Normative references
+
+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] 3GPP TR 21.905: "3GPP Vocabulary".
+- [2] 3GPP TS 23.011: "Technical realization of supplementary services".
+- [3] 3GPP TS 23.018: "Basic call handling; Technical realization".
+- [4] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 2; Stage 2"
+- [5] 3GPP TS 23.079: "Support of Optimal Routeing (SOR); Technical realisation"
+- [6] 3GPP TS 23.081: "Line identification supplementary services - Stage 2".
+- [7] 3GPP TS 23.085: "Closed User Group (CUG) supplementary services - Stage 2".
+- [8] 3GPP TS 23.091: "Explicit Call Transfer (ECT) supplementary service - Stage 2".
+- [9] 3GPP TS 23.093: "Technical Realisation of Completion of Calls to Busy Subscriber (CCBS)".
+
+# --- 3 Definitions and abbreviations
+
+## 3.1 Abbreviations
+
+Abbreviations used in this specification are listed in TR 21.905.
+
+For the purpose of this specification the following abbreviations apply:
+
+CD: Call Deflection
+
+# 4 Information flow
+
+![Flowchart for Call Deflection authorization procedure. It starts with a decision 'neg. resp. = CD?'. If No, Result := Abort. If Yes, GAMEL_CHECK_SII2_CDTI is called (See TS 23.078). Then 'Result = Pass?' is checked. If No, CD provisioned? is checked. If No, Number of max diversions reached? is checked. If Yes, BAOC A&O is checked. If No, GAMEL_Check_CD_Interaction is called. Then 'Result = Pass?' is checked. If No, DTN valid? is checked. If Yes, DTN is a special service code? is checked. If Yes, set negative resp: DTN is a special service code. If No, DTN is own basic MSISDN is checked. If Yes, set negative resp: DTN is own number. If No, set negative resp: number invalid. All negative response boxes lead to Result := Fail. If Result = Pass? at any point, the flow proceeds to connector 2.](f6d72d7c790e7f585532140f3971639a_img.jpg)
+
+Procedure CD\_Authorization 1(1)
+
+Call Deflection related authorization
+
+DTN: Deflected-To Number  
+BAOC: Barring of All Outgoing Calls  
+A&O: Active and Operative
+
+```
+
+graph TD
+    Start([ ]) --> D1{neg. resp. = CD?}
+    D1 -- No --> R1[Result := Abort]
+    R1 --> E1(( ))
+    D1 -- Yes --> G1[GAMEL_CHECK_SII2_CDTI]
+    G1 -.-> S1[See TS 23.078]
+    G1 --> D2{Result = Pass?}
+    D2 -- No --> D3{CD provisioned?}
+    D3 -- No --> D4{Number of max diversions reached?}
+    D4 -- Yes --> D5{BAOC A&O}
+    D5 -- Yes --> R2[set negative resp: call barred]
+    D5 -- No --> G2[GAMEL_Check_CD_Interaction]
+    G2 --> D6{Result = Pass?}
+    D6 -- No --> D7{DTN valid?}
+    D7 -- Yes --> D8{DTN is a special service code?}
+    D8 -- Yes --> R3[set negative resp: DTN is a special service code]
+    D8 -- No --> D9{DTN is own basic MSISDN}
+    D9 -- Yes --> R4[set negative resp: DTN is own number]
+    D9 -- No --> R5[set negative resp: number invalid]
+    R3 --> R6[Result := Fail]
+    R4 --> R6
+    R5 --> R6
+    R6 --> E2(( ))
+    D2 -- Yes --> C2((2))
+    D3 -- Yes --> C2
+    D4 -- No --> C2
+    D5 -- No --> C2
+    D6 -- Yes --> C2
+    D7 -- No --> C2
+    D8 -- No --> C2
+    D9 -- No --> C2
+  
+```
+
+Flowchart for Call Deflection authorization procedure. It starts with a decision 'neg. resp. = CD?'. If No, Result := Abort. If Yes, GAMEL\_CHECK\_SII2\_CDTI is called (See TS 23.078). Then 'Result = Pass?' is checked. If No, CD provisioned? is checked. If No, Number of max diversions reached? is checked. If Yes, BAOC A&O is checked. If No, GAMEL\_Check\_CD\_Interaction is called. Then 'Result = Pass?' is checked. If No, DTN valid? is checked. If Yes, DTN is a special service code? is checked. If Yes, set negative resp: DTN is a special service code. If No, DTN is own basic MSISDN is checked. If Yes, set negative resp: DTN is own number. If No, set negative resp: number invalid. All negative response boxes lead to Result := Fail. If Result = Pass? at any point, the flow proceeds to connector 2.
+
+Figure 4.1: Information flow for Call Deflection
+
+# 5 Messages and their Contents
+
+## 5.1 Messages between the MS and the MSC
+
+### 5.1.1 CD Request
+
+The CD Request message is sent from the MS to MSC direction.
+
+| Information element name | Required | Description                                                                                                            |
+|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------|
+| Deflected-to number      | M        | Number of the C subscriber as entered by the served subscriber.                                                        |
+| Deflected-to subaddress  | C        | Subaddress of the C subscriber; shall be present if it was entered by the served subscriber; otherwise shall be absent |
+
+### 5.1.2 CD Request ack
+
+The CD Request ack message is sent from the MSC to MS direction. This message contains no information elements.
+
+### 5.1.3 CD Request negative response
+
+CD Request negative response message is sent from the MSC to MS direction. The negative response information element can take the following values:
+
+- service not subscribed;
+- deflected-to number is own number;
+- deflected-to number is a special service code;
+- number invalid;
+- call barred;
+- SS incompatibility;
+- forwarding violation;
+- forwarding failure.
+
+## 5.2 Messages between the MSC and the VLR
+
+### 5.2.1 Process Call Waiting negative response
+
+For the description of the Process Call Waiting negative response message refer to TS 23.018. The negative response information element can take the following additional value:
+
+- Call Deflection.
+
+**For the purpose of the CD supplementary service the following additional information elements for the Process Call Waiting negative response message are required.**
+
+| Information element name | Required | Description                                                                                                            |
+|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------|
+| Deflected-to number      | M        | Number of the C subscriber as entered by the served subscriber.                                                        |
+| Deflected-to subaddress  | C        | Subaddress of the C subscriber; shall be present if it was entered by the served subscriber; otherwise shall be absent |
+
+### 5.2.2 Complete Call negative response
+
+For the description of the Complete Call negative response message refer to TS 23.018. The negative response information element can take the following additional value:
+
+- Call Deflection.
+
+**For the purpose of the CD supplementary service the following additional information elements for the Complete Call negative response message are required.**
+
+| Information element name | Required | Description                                                                                                            |
+|--------------------------|----------|------------------------------------------------------------------------------------------------------------------------|
+| Deflected-to number      | M        | Number of the C subscriber as entered by the served subscriber.                                                        |
+| Deflected-to subaddress  | C        | Subaddress of the C subscriber; shall be present if it was entered by the served subscriber; otherwise shall be absent |
+
+### 5.2.3 Send Info for Incoming Call negative response
+
+For the description of the Send Info for Incoming Call negative response message refer to TS 23.018. The negative response information element can take the following additional values:
+
+- service not subscribed;
+- deflected-to number is own number;
+- deflected-to number is a special service code;
+
+- number invalid;
+- call barred.
+
+# --- 6 Functions of the serving MSC
+
+The functions of the serving MSC are specified in TS 23.018. The procedures specific to the CD supplementary service are specified in this subclause.
+
+## 6.1 Procedure Handling\_CD\_MSC
+
+This procedure is called when a CD request is received from the MS.
+
+## 6.2 Procedure CD\_Reject
+
+This procedure is called if the CD request was treated unsuccessful in the VLR.
+
+## 6.3 Procedure CD\_Failure
+
+This procedure is called if the CD request was treated unsuccessful in the serving MSC.
+
+## 6.4 Procedure CD\_UUS\_Interaction
+
+This procedure is called if the CD request was treated unsuccessful in the serving MSC due to the interaction with the UUS supplementary service.
+
+## 6.5 Procedure CD\_Success
+
+This procedure is called if the CD request was treated successful in the serving MSC.
+
+## 6.6 Procedure CD\_Notify\_SS\_Invocation
+
+This procedure is called by the procedures CD\_OR\_Clear and CD\_Success to send notification of the CD invocation to the gsmSCF if required.
+
+The output signal SS Invocation Notify is sent if the SS-CSI was received in the SIFIC ack. The SS-CSI will only be included in the SIFIC ack if there is a requirement to notify the gsmSCF that CD has been invoked.
+
+![Flowchart for Procedure CAMEL_Check_CD_Interaction. It starts with a connector symbol, followed by a decision diamond 'TIF-CSI provided'. If 'No', it goes to 'Result:= Fail'. If 'Yes', it goes to 'Result:= Pass'. Both results lead to a merge point and then to an exit connector symbol.](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+### Procedure CAMEL\_Check\_CD\_Interaction
+
+1(1)
+
+Procedure in the VLR to Check the Provision of TIF\_CSI
+
+```
+graph TD; Start([ ]) --> Decision{TIF-CSI provided}; Decision -- No --> Fail[Result:= Fail]; Decision -- Yes --> Pass[Result:= Pass]; Fail --> Merge(( )); Pass --> Merge; Merge --> End((X))
+```
+
+Flowchart for Procedure CAMEL\_Check\_CD\_Interaction. It starts with a connector symbol, followed by a decision diamond 'TIF-CSI provided'. If 'No', it goes to 'Result:= Fail'. If 'Yes', it goes to 'Result:= Pass'. Both results lead to a merge point and then to an exit connector symbol.
+
+Figure 6.1: Procedure Handling\_CD\_MSC
+
+![A state transition diagram with two circular states. The left state contains the text '(Not Provisioned, Not Applicable, Not Active, Not Induced)'. The right state contains the text '(Provisioned, Not Applicable, Active and Operative, Not Induced)'. A curved arrow labeled 'Provision' points from the left state to the right state. A curved arrow labeled 'Withdrawal' points from the right state to the left state.](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+**Provision**
+
+**(Not Provisioned,  
+Not Applicable,  
+Not Active,  
+Not Induced)**
+
+**(Provisioned,  
+Not Applicable,  
+Active and Operative,  
+Not Induced)**
+
+**Withdrawal**
+
+A state transition diagram with two circular states. The left state contains the text '(Not Provisioned, Not Applicable, Not Active, Not Induced)'. The right state contains the text '(Provisioned, Not Applicable, Active and Operative, Not Induced)'. A curved arrow labeled 'Provision' points from the left state to the right state. A curved arrow labeled 'Withdrawal' points from the right state to the left state.
+
+Figure 6.2: Procedure CD\_Reject
+
+![Flowchart for Procedure CD_Failure. It starts with a connector symbol, followed by a decision 'CD in progress'. If 'No', it goes to an exit connector. If 'Yes', it proceeds to 'Set negative response: forwarding failure', then 'CD Request negative response', then 'Release transaction', and finally to an exit connector.](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+### Procedure CD\_Failure
+
+1(1)
+
+Procedure in the MSC to handle Call Deflection after unsuccessful invocation
+
+Signals to/from the left are to/from the BSS
+
+```
+graph TD; Start([ ]) --> CD{CD in progress}; CD -- No --> Exit((X)); CD -- Yes --> Set[Set negative response: forwarding failure]; Set --> CDReq{CD Request negative response}; CDReq --> Release{Release transaction}; Release --> Exit;
+```
+
+Flowchart for Procedure CD\_Failure. It starts with a connector symbol, followed by a decision 'CD in progress'. If 'No', it goes to an exit connector. If 'Yes', it proceeds to 'Set negative response: forwarding failure', then 'CD Request negative response', then 'Release transaction', and finally to an exit connector.
+
+Figure 6.3: Procedure CD\_Failure
+
+![Flowchart for Procedure CD_UUS_Interaction](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+### Procedure CD\_UUS\_Interaction
+
+1(1)
+
+Procedure in the MSC to handle the interaction scenario with UUS
+
+Signals to/from the left are to/from the BSS
+
+```
+graph TD; Start([ ]) --> Step1[Set negative response: SS incompatibility]; Step1 --> Step2{CD Request negative response}; Step2 --> Step3{Release transaction}; Step3 --> End((X));
+```
+
+The flowchart illustrates the procedure for CD\_UUS\_Interaction. It begins with a start symbol (oval), followed by a process block 'Set negative response: SS incompatibility'. This is followed by a decision block 'CD Request negative response', which leads to another decision block 'Release transaction'. The process concludes with an end symbol (circle with an X).
+
+Flowchart for Procedure CD\_UUS\_Interaction
+
+Figure 6.4: Procedure CD\_UUS\_Interaction
+
+### Procedure CD\_Success
+
+1(1)
+
+Procedure in the MSC to handle  
+CD after successful invocation
+
+Signals to/from the left  
+are to/from the BSS
+
+![Flowchart for Procedure CD_Success](3ad00ce93ad9dea9ee0f47535e5355e6_img.jpg)
+
+```
+graph TD; Start([ ]) --> Decision{CD in progress}; Decision -- No --> End(( )); Decision -- Yes --> Process[CD_Notify_SS_Invocation]; Process --> Decision2{CD Request ack}; Decision2 --> Decision3{Release transaction}; Decision3 --> End;
+```
+
+The flowchart illustrates the 'Procedure CD\_Success'. It begins with a start symbol (oval with a vertical line), leading to a decision diamond labeled 'CD in progress'. If the answer is 'No', the flow proceeds to an end symbol (circle with an 'X'). If the answer is 'Yes', the flow proceeds to a process box labeled 'CD\_Notify\_SS\_Invocation'. This is followed by a decision diamond labeled 'CD Request ack', which then leads to another decision diamond labeled 'Release transaction'. Both decision diamonds lead to the same end symbol.
+
+Flowchart for Procedure CD\_Success
+
+Figure 6.5: Procedure CD\_Success
+
+![Flowchart for Procedure CD_Notify_SS_Invocation. It starts with a connector symbol, followed by a decision diamond 'SS-CSI received in SIFIC ack?'. If 'Yes', it goes to a process box 'SS Invocation Notify'. If 'No', it goes to an exit connector symbol.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg)
+
+### Procedure CD\_Notify\_SS\_Invocation
+
+1(1)
+
+Procedure in the MSC to notify the gsmSCF of the CD invocation.
+
+Signals to/from the left are to/from the gsmSCF.
+
+```
+graph TD; Start([ ]) --> Decision{SS-CSI received in SIFIC ack?}; Decision -- Yes --> Process[SS Invocation Notify]; Decision -- No --> End((X));
+```
+
+Flowchart for Procedure CD\_Notify\_SS\_Invocation. It starts with a connector symbol, followed by a decision diamond 'SS-CSI received in SIFIC ack?'. If 'Yes', it goes to a process box 'SS Invocation Notify'. If 'No', it goes to an exit connector symbol.
+
+Figure 6.6 Procedure CD\_Notify\_SS\_Invocation
+
+# --- 7 Functions of the serving VLR
+
+The functions of the serving VLR are specified in TS 23.018. The procedure specific to the CD supplementary service is specified in this subclause.
+
+## 7.1 Procedure CD\_Authorization
+
+This procedure examines the authorization related to Call Deflection.
+
+The procedure CAMEL\_Check\_CD\_Interaction is specific to CAMEL phase 2. If CAMEL phase 2 is not supported in the VLR, processing continues from the "No" exit of the test "Result=Pass?".
+
+The procedure CAMEL\_CHECK\_SII2\_CDTI is specific to CAMEL Phase 3 or higher. If CAMEL Phase 3 or higher is not supported in the VLR, processing continues from the "Yes" exit of the test "Result = Pass?".
+
+## 7.2 Procedure CAMEL\_Check\_CD\_Interaction
+
+This procedure examines whether a Translation Interaction Flag (TIF-CSI) is provided for the served subscriber.
+
+![Flowchart for Procedure CD_Authorization. It starts with a decision 'neg. resp. = CD?'. If 'No', it sets 'Result := Abort' and ends. If 'Yes', it calls 'CAMEL_CHECK_SII2_CDTI' (refer to TS 23.078). This returns a 'Result = Pass?' decision. If 'No', it ends. If 'Yes', it checks 'CD provisioned?'. If 'No', it ends. If 'Yes', it checks 'Number of mac diversions reached?'. If 'Yes', it ends. If 'No', it checks 'BAOC A&O'. If 'Yes', it sets negative response 'call barred' and ends. If 'No', it calls 'CAMEL_Check_CD_Interaction'. This returns another 'Result = Pass?' decision. If 'Yes', it goes to connector '2'. If 'No', it checks 'DTN valid?'. If 'No', it sets negative response 'number invalid' and ends. If 'Yes', it checks 'DTN is a special service code?'. If 'Yes', it sets negative response 'DTN is a special service code' and ends. If 'No', it checks 'DTN is own basic MSISDN'. If 'Yes', it sets negative response 'DTN is own number' and ends. If 'No', it goes to connector '1'. All 'set negative resp:' blocks lead to 'Result := Fail' and then end.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg)
+
+### Procedure CD\_Authorization
+
+1(1)
+
+Call Deflection related authorization
+
+DTN: Deflected-To Number  
+BAOC: Barring of All Outgoing Calls  
+A&O: Active and Operative
+
+```
+graph TD
+    Start([ ]) --> neg_resp_CD{neg. resp. = CD?}
+    neg_resp_CD -- No --> Abort[Result := Abort]
+    Abort --> End1(( ))
+    neg_resp_CD -- Yes --> CAMEL_CHECK_SII2_CDTI[CAMEL_CHECK_SII2_CDTI]
+    CAMEL_CHECK_SII2_CDTI --> Pass1{Result = Pass?}
+    Pass1 -- No --> End2(( ))
+    Pass1 -- Yes --> CD_provisioned{CD provisioned?}
+    CD_provisioned -- No --> End3(( ))
+    CD_provisioned -- Yes --> mac_diversions{Number of mac diversions reached?}
+    mac_diversions -- Yes --> End4(( ))
+    mac_diversions -- No --> BAOC_AO{BAOC A&O}
+    BAOC_AO -- Yes --> neg_resp_barred[set negative resp: call barred]
+    BAOC_AO -- No --> CAMEL_Check_CD_Interaction[CAMEL_Check_CD_Interaction]
+    neg_resp_barred --> Fail1[Result := Fail]
+    Fail1 --> End5(( ))
+    CAMEL_Check_CD_Interaction --> Pass2{Result = Pass?}
+    Pass2 -- Yes --> Connector2((2))
+    Pass2 -- No --> DTN_valid{DTN valid?}
+    DTN_valid -- No --> neg_resp_invalid[set negative resp: number invalid]
+    DTN_valid -- Yes --> DTN_special{DTN is a special service code?}
+    DTN_special -- Yes --> neg_resp_special[set negative resp: DTN is a special service code]
+    DTN_special -- No --> DTN_own{DTN is own basic MSISDN}
+    DTN_own -- Yes --> neg_resp_own[set negative resp: DTN is own number]
+    DTN_own -- No --> Connector1((1))
+    neg_resp_invalid --> Fail2[Result := Fail]
+    neg_resp_special --> Fail2
+    neg_resp_own --> Fail2
+    Fail2 --> End6(( ))
+```
+
+Flowchart for Procedure CD\_Authorization. It starts with a decision 'neg. resp. = CD?'. If 'No', it sets 'Result := Abort' and ends. If 'Yes', it calls 'CAMEL\_CHECK\_SII2\_CDTI' (refer to TS 23.078). This returns a 'Result = Pass?' decision. If 'No', it ends. If 'Yes', it checks 'CD provisioned?'. If 'No', it ends. If 'Yes', it checks 'Number of mac diversions reached?'. If 'Yes', it ends. If 'No', it checks 'BAOC A&O'. If 'Yes', it sets negative response 'call barred' and ends. If 'No', it calls 'CAMEL\_Check\_CD\_Interaction'. This returns another 'Result = Pass?' decision. If 'Yes', it goes to connector '2'. If 'No', it checks 'DTN valid?'. If 'No', it sets negative response 'number invalid' and ends. If 'Yes', it checks 'DTN is a special service code?'. If 'Yes', it sets negative response 'DTN is a special service code' and ends. If 'No', it checks 'DTN is own basic MSISDN'. If 'Yes', it sets negative response 'DTN is own number' and ends. If 'No', it goes to connector '1'. All 'set negative resp:' blocks lead to 'Result := Fail' and then end.
+
+Figure 7.1 (sheet 1): Procedure CD\_Authorization
+
+![Flowchart for Procedure CAMEL_Check_CD_Interaction. It starts with a connector symbol, leading to a decision diamond 'TIF_CSI provided'. If 'Yes', it goes to 'Result:= Pass'. If 'No', it goes to 'Result:= Fail'. Both results lead to a final connector symbol.](8307f6b04df072c9332f9987e034272c_img.jpg)
+
+### Procedure CAMEL\_Check\_CD\_Interaction
+
+1(1)
+
+Procedure in the VLR to  
+Check the Provision of TIF\_CSI
+
+```
+graph TD; Start([ ]) --> Decision{TIF_CSI provided}; Decision -- Yes --> Pass[Result:= Pass]; Decision -- No --> Fail[Result:= Fail]; Pass --> End(( )); Fail --> End
+```
+
+Flowchart for Procedure CAMEL\_Check\_CD\_Interaction. It starts with a connector symbol, leading to a decision diamond 'TIF\_CSI provided'. If 'Yes', it goes to 'Result:= Pass'. If 'No', it goes to 'Result:= Fail'. Both results lead to a final connector symbol.
+
+Figure 7.2: Procedure CAMEL\_Check\_CD\_Interaction
+
+# --- 8 Interaction with other supplementary services
+
+## 8.1 Line Identification services
+
+If the serving MSC receives an Answer message from the destination C network after the successful invocation of the call deflection supplementary service, the process MAF039 of TS 23.081 shall be performed. Refer to Process ICH\_MSC of TS 23.018 for further details.
+
+## 8.2 Call Forwarding services
+
+No impact.
+
+## 8.3 Call Waiting
+
+The MS may send a CD Request message for an incoming waiting call. Refer to procedure Process\_Call\_Waiting\_MSC of TS 23.018 for further details.
+
+## 8.4 Call Hold
+
+No impact.
+
+## 8.5 Multi Party (MPTY)
+
+No impact.
+
+## 8.6 Closed User Group
+
+The serving VLR shall perform the forwarding CUG authorisation as defined in TS 23.085 while processing a call deflection request. Refer to Process ICH\_VLR of TS 23.018 for details.
+
+## 8.7 Advice of Charge (AoC)
+
+No impact.
+
+## 8.8 Call Barring Services
+
+If a call deflection request is processed, the serving VLR shall check whether the requested deflected-to number contradicts active and operative outgoing barring programs. Refer to Procedure CD\_Authorization (figure 6.6) for details.
+
+## 8.9 Explicit call transfer (ECT)
+
+If in the originating network ECT is invoked (one call answered, the other alerting), the serving MSC shall map a redirection number parameter received in the ECT notification into the calling identity parameter of the outgoing IAM message. Refer to TS 23.091 (Interaction of Call Forwarding on mobile subscriber busy due to UDUB and explicit call transfer) for details.
+
+## 8.10 Completion of Calls to Busy Subscriber (CCBS)
+
+If a call is deflected to a NDUB destination, the serving MSC shall set the diagnostic to "CCBS not possible" when it releases the call towards the calling network. Refer to Process ICH\_MSC of TS 23.018 for further details.
+
+The serving MSC shall remove the CCBS call Indicator from the IAM message when deflecting a call.
+
+# --- 9 Interaction with other network features
+
+## 9.1 Customised Applications for Mobile network Enhanced Logic (CAMEL)
+
+If the served subscriber is provided with a Translation Information Flag (TIF-CSI) as defined in TS 23.018 the VLR shall neither perform checks regarding the validity of the deflected-to number nor perform interactions with BOIC and BOIC-exHC barring programs. Refer to Procedure CD\_Authorization for further details.
+
+## 9.2 Support of Optimal Routeing
+
+The procedures for optimal routeing of late call forwarding shall apply if the Call Deflection supplementary service is invoked. Refer to TS 23.079 for further details.
+
+# --- 10 Information stored in the HLR
+
+The following logical states are applicable for the Call Deflection service (refer to TS 23.011 for an explanation of the notation):
+
+| <b><u>Provisioning State</u></b> | <b><u>Registration State</u></b> | <b><u>Activation State</u></b> | <b><u>HLR Induction State</u></b> |
+|----------------------------------|----------------------------------|--------------------------------|-----------------------------------|
+| (Not Provisioned,                | Not Applicable,                  | Not Active,                    | Not Induced)                      |
+| (Provisioned,                    | Not Applicable,                  | Active and Operative,          | Not Induced)                      |
+
+The HLR shall store:
+
+- the logical state of the Call Deflection service (which shall be one of the valid states listed above) on a per subscriber basis.
+- the subscription option "notification to the calling party" on a per subscriber basis;  
+This subscription option takes one of the following values:
+  - no notification;
+  - notification.
+- the subscription option "MSISDN of the served subscriber can be presented to the forwarded-to subscriber" on a per subscriber basis;  
+This subscription option takes one of the following values:
+  - presentation restricted;
+  - presentation allowed.
+
+# 11 State transition model
+
+Figure 11.1 shows the successful cases of transition between the applicable logical states of the Call Deflection service. 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 and are therefore not shown in the diagram.
+
+![State transition model diagram for the Call Deflection service. It shows two states: (Not Provisioned, Not Applicable, Not Active, Not Induced) and (Provisioned, Not Applicable, Active and Operative, Not Induced). Transitions are labeled Provision and Withdrawal.](2eb23c2210154279f8013a1594fbcc5a_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> (Not Provisioned, Not Applicable, Not Active, Not Induced)
+    (Not Provisioned, Not Applicable, Not Active, Not Induced) --> (Provisioned, Not Applicable, Active and Operative, Not Induced) : Provision
+    (Provisioned, Not Applicable, Active and Operative, Not Induced) --> (Not Provisioned, Not Applicable, Not Active, Not Induced) : Withdrawal
+  
+```
+
+State transition model diagram for the Call Deflection service. It shows two states: (Not Provisioned, Not Applicable, Not Active, Not Induced) and (Provisioned, Not Applicable, Active and Operative, Not Induced). Transitions are labeled Provision and Withdrawal.
+
+Figure 11.1: State transition model
+
+# 12 Transfer of information from HLR to VLR
+
+If the provisioning state for the Call Deflection service is "Provisioned" then when the subscriber registers on a VLR the HLR shall send that VLR information about the logical state of the Call Deflection service. In this case the following additional information shall be sent to the VLR:
+
+- subscription options "notification to the calling party" and "MSISDN of the served subscriber can be presented to the forwarded-to subscriber".
+- Translation Information Flag (TIF-CSI) if contained in the CAMEL subscriber data of the served subscriber (refer to TS 23.078 for further details).
+
+If the logical state of the Call Deflection service or the value of the subscription options "notification to the calling party" or "MSISDN of the served subscriber can be presented to the forwarded-to subscriber" or the presence of the Translation Information Flag (TIF-CSI) is changed while a subscriber is registered on a VLR then the HLR shall inform the VLR of the new logical state or the new value of the subscription option or the presence of the Translation Information Flag (TIF-CSI).
+
+# 13 Information stored in the VLR
+
+For the supplementary service Call Deflection the VLR shall store the service state information, information about the subscription options "notification to the calling party" and "MSISDN of the served subscriber can be presented to the forwarded-to subscriber" and the Translation Information Flag (TIF-CSI) received from the HLR.
+
+# 14 Handover
+
+Handover will have no impact on the control procedures and the operation of the service.
+
+# Annex A (informative): Change history
+
+| Change history |           |         |       |         |             |                                                    |
+|----------------|-----------|---------|-------|---------|-------------|----------------------------------------------------|
+| TSG CN#        | Spec      | Version | CR    | <Phase> | New Version | Subject/Comment                                    |
+| Apr 1999       | GSM 03.72 | 7.0.0   |       |         |             | Transferred to 3GPP CN1                            |
+| CN#03          | 23.072    |         |       |         | 3.0.0       | Approved at CN#03                                  |
+| CN#05          | 23.072    | 3.0.0   | 001   |         | 3.1.0       | Approved at CN#05                                  |
+| CN#05          | 23.072    | 3.0.0   | 003   |         | 3.1.0       | Approved at CN#05                                  |
+| CN#06          | 23.072    | 3.1.0   | 002r1 |         | 3.2.0       | Approved at CN#06                                  |
+| CN#09          | 23.072    | 3.2.0   | 004   |         | 3.3.0       | Transfer of Procedure Check_CD_SII2 to TS 23.078   |
+| CN#09          | 23.072    | 3.2.0   | 005   |         | 3.3.0       | Handling of the Call Diversion Treatment Indicator |
+| CN#11          | 23.072    | 3.3.0   |       | Rel-4   | 4.0.0       | Release 4 after CN#11                              |
+| CN#16          | 23.072    | 4.0.0   |       | Rel-4   | 4.0.1       | References updated                                 |
+| CN#16          | 23.072    | 4.0.1   |       | Rel-5   | 5.0.0       | Release 5 after CN#16                              |
+| CN#26          | 23.072    | 5.0.0   |       | Rel-6   | 6.0.0       | Release 6 after CN#26                              |
+| CT#36          | 23.072    | 6.0.0   |       | Rel-7   | 7.0.0       | Upgraded unchanged from Rel-6                      |
+| CT#42          | 23.072    | 7.0.0   |       | Rel-8   | 8.0.0       | Upgraded unchanged from Rel-7                      |
+| CT#46          | -         | 8.0.0   | -     | Rel-9   | 9.0.0       | Update to Rel-9 version (MCC)                      |
+| 2011-03        | -         | 9.0.0   | -     | Rel-10  | 10.0.0      | Update to Rel-10 version (MCC)                     |
+| 2012-09        | -         | 10.0.0  | -     | Rel-11  | 11.0.0      | Update to Rel-11 version (MCC)                     |

marked/Rel-11/23_series/23081/raw.md

@@ -0,0 +1,1354 @@
+
+
+
+
+
+
+# Contents
+
+|                                                                                           |    |
+|-------------------------------------------------------------------------------------------|----|
+| Foreword .....                                                                            | 5  |
+| 0 Scope.....                                                                              | 6  |
+| 0.1 References .....                                                                      | 6  |
+| 0.2 Definitions and abbreviations.....                                                    | 6  |
+| 0.2.1 Definitions .....                                                                   | 6  |
+| 0.2.1.1 Definition of line identity .....                                                 | 6  |
+| 0.2.1.2 Definition of presentation and screening indicators .....                         | 7  |
+| 0.2.2 Abbreviations .....                                                                 | 7  |
+| 1 Calling line identification presentation (CLIP).....                                    | 7  |
+| 1.1 Handling of calling line identification presentation.....                             | 7  |
+| 1.1.1 Interrogation .....                                                                 | 7  |
+| 1.2 Functions and information flows.....                                                  | 8  |
+| 1.2.1 Optional capability to carry calling line identification.....                       | 17 |
+| 1.2.2 Information elements used in the messages .....                                     | 17 |
+| 1.2.3 Parameters in Send Routeing Info and Provide Roaming Number for CLI.....            | 18 |
+| 1.2.4 Messages between MSC and VLR in destination network .....                           | 19 |
+| 1.3 Information stored in the HLR .....                                                   | 19 |
+| 1.4 State transition model.....                                                           | 19 |
+| 1.5 Transfer of information from HLR to VLR .....                                         | 20 |
+| 1.6 Information stored in the VLR .....                                                   | 20 |
+| 1.7 Handover .....                                                                        | 20 |
+| 1.8 Interactions with other supplementary services .....                                  | 20 |
+| 2 Calling line identification restriction (CLIR).....                                     | 20 |
+| 2.1 Handling of calling line identification restriction .....                             | 20 |
+| 2.1.1 General .....                                                                       | 20 |
+| 2.1.2 Permanent mode .....                                                                | 21 |
+| 2.1.3 Controlling presentation of the CLI when CLIR is provisioned in temporary mode..... | 21 |
+| 2.1.4 Interrogation .....                                                                 | 21 |
+| 2.2 Functions and information flows.....                                                  | 22 |
+| 2.3 Information stored in the HLR .....                                                   | 28 |
+| 2.4 State transition model.....                                                           | 28 |
+| 2.5 Transfer of information from HLR to VLR .....                                         | 28 |
+| 2.6 Information stored in the VLR .....                                                   | 28 |
+| 2.7 Handover .....                                                                        | 29 |
+| 2.8 Interworking .....                                                                    | 29 |
+| 3 Connected line identification presentation (COLP).....                                  | 29 |
+| 3.1 Handling of connected line identification presentation.....                           | 29 |
+| 3.1.1 Interrogation .....                                                                 | 29 |
+| 3.1.2 Interactions with call forwarding supplementary services .....                      | 30 |
+| 3.2 Functions and information flows.....                                                  | 30 |
+| 3.3 Information stored in the HLR .....                                                   | 35 |
+| 3.4 State transition model.....                                                           | 35 |
+| 3.5 Transfer of information from HLR to VLR .....                                         | 35 |
+| 3.6 Information stored in the VLR .....                                                   | 36 |
+| 3.7 Handover .....                                                                        | 36 |
+| 4 Connected line identification restriction (COLR).....                                   | 36 |
+| 4.1 Handling of connected line identification restriction.....                            | 36 |
+| 4.1.1 General .....                                                                       | 36 |
+| 4.1.2 Interrogation .....                                                                 | 36 |
+| 4.2 Functions and information flows.....                                                  | 37 |
+| 4.3 Information stored in the HLR .....                                                   | 40 |
+| 4.4 State transition model.....                                                           | 40 |
+| 4.5 Transfer of information from HLR to VLR .....                                         | 41 |
+| 4.6 Information stored in the VLR .....                                                   | 41 |
+| 4.7 Handover .....                                                                        | 41 |
+
+4.8 Interworking .....41
+
+**Annex A (informative): Mapping of CLI.....42**
+
+Annex B (informative): Change history.....44
+
+# --- Foreword
+
+This Technical Specification has been produced by the 3GPP.
+
+This TS defines the stage 2 of the line identification supplementary services for the 3GPP system.
+
+The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows:
+
+Version 3.y.z
+
+where:
+
+- x the first digit:
+  - 1 presented to TSG for information;
+  - 2 presented to TSG for approval;
+  - 3 Indicates TSG approved document under change control.
+- y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc.
+- z the third digit is incremented when editorial only changes have been incorporated in the specification;
+
+# 0 Scope
+
+The present document gives the stage 2 description of the call identification supplementary services.
+
+The group line identification supplementary services are divided into the following four supplementary services:
+
+- |                                              |      |             |
+|----------------------------------------------|------|-------------|
+| - Calling line identification presentation   | CLIP | (clause 1); |
+| - Calling line identification restriction    | CLIR | (clause 2); |
+| - Connected line identification presentation | COLP | (clause 3); |
+| - Connected line identification restriction  | COLR | (clause 4). |
+
+## 0.1 References
+
+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] 3GPP TS 21.905: "3G Vocabulary".
+- [2] 3GPP TS 23.011: "Technical Realization of Supplementary Services - General Aspects."
+- [3] 3GPP TS 23.018 : "Basic Call Handling; Technical realization".
+- [4] 3GPP TS 22.081: "Line Identification supplementary services - Stage 1".
+
+## 0.2 Definitions and abbreviations
+
+### 0.2.1 Definitions
+
+#### 0.2.1.1 Definition of line identity
+
+The line identity is made up of the following information units:
+
+- The subscriber's international ISDN/MSISDN number;
+- Optionally subaddress information.
+
+For mobile originated calls, the ISDN/MSISDN shall always be provided within the network. The subaddress shall only be included if it is provided by the user (or user equipment).
+
+The calling line identity is the line identity of the calling party. The connected line identity is the line identity of the connected party.
+
+The additional calling line identity provides additional line information for the purpose of the calling line identification presentation service (CLIP). The additional connected line identity provides additional line information for the purpose of the connected line identification presentation service (COLP).
+
+For mobile originating calls the user (or user equipment) has no possibility to provide an additional line identity. For mobile terminating calls the user (or user equipment) has no possibility to provide an additional connected line identity.
+
+#### 0.2.1.2 Definition of presentation and screening indicators
+
+In addition to, or instead of, the line identity or additional line identity, the network may send a presentation indicator (PI) together with a Cause of no CLI (CoNC) and/or a screening indicator (SI) to the MS as follows:
+
+- Presentation Indicator:
+  - a) Presentation allowed;
+  - b) Presentation restricted;
+  - c) Number not available.
+- If the Presentation Indicator indicates "presentation restricted" the Cause of no CLI may give a diagnostic:
+  - a) Unavailable;
+  - b) Rejected by user;
+  - c) Interaction with other services;
+  - d) Coin line/ Pay phone.
+- Screening indicator:
+  - a) User provided, verified and passed;
+  - b) User provided, not screened;
+  - c) network provided.
+
+The screening indicator applies to the ISDN/MSISDN or the number given as additional line identity respectively.
+
+### 0.2.2 Abbreviations
+
+Abbreviations used in the present document are listed in 3GPP TR 21.905.
+
+# 1 Calling line identification presentation (CLIP)
+
+## 1.1 Handling of calling line identification presentation
+
+### 1.1.1 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 1.1.
+
+![Sequence diagram illustrating the interrogation of calling line identification presentation (CLIP). The diagram shows four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate CLIP' to MSC. 2. MSC sends 'Interrogate CLIP' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete' back to MS. The HLR is shown but not involved in this specific sequence.](4ba34b7c8f0b8799dc89462e0c71c52c_img.jpg)
+
+```
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant HLR
+    MS->>MSC: Interrogate CLIP
+    MSC->>VLR: Interrogate CLIP
+    VLR-->>MSC: Acknowledge
+    MSC-->>MS: Release Complete
+```
+
+Sequence diagram illustrating the interrogation of calling line identification presentation (CLIP). The diagram shows four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate CLIP' to MSC. 2. MSC sends 'Interrogate CLIP' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete' back to MS. The HLR is shown but not involved in this specific sequence.
+
+Figure 1.1: Interrogation of calling line identification presentation
+
+## 1.2 Functions and information flows
+
+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.
+
+![Flowchart for Process CLIP_MAF001. It starts with 'idle', followed by 'initiate handling of CLIP'. A decision 'CLIP provisioned' follows. If 'no', it goes to 'set provision indication = not provisioned'. If 'yes', it goes to 'set provision indication = provisioned'. From there, a decision 'called subscriber in HPLMN country' is made. If 'no', it goes to 'set override category = no'. If 'yes', a decision 'override category' is made. If 'yes', it goes to 'set override category = yes'. If 'no', it goes to 'set override category = no'. Both 'set override category' paths lead to 'continue call handling', which then leads to 'idle'. A note at the bottom right says 'CLIP: Calling Line Identification Presentation.'](b3baf3a29b67c7425d2562ddbc52f0cc_img.jpg)
+
+Process CLIP\_MAF001
+
+381\_12(1)
+
+Figure 1.2
+
+```
+graph TD; Start([idle]) --> Init[/initiate handling of CLIP/]; Init --> CLIP_Prov{CLIP provisioned}; CLIP_Prov -- no --> SetNotProv[set provision indication = not provisioned]; CLIP_Prov -- yes --> SetProv[set provision indication = provisioned]; SetProv --> HPLMN{called subscriber in HPLMN country}; HPLMN -- no --> SetOverrideNo[set override category = no]; HPLMN -- yes --> Override{override category}; Override -- no --> SetOverrideNo; Override -- yes --> SetOverrideYes[set override category = yes]; SetNotProv --> Continue{continue call handling}; SetOverrideYes --> Continue; SetOverrideNo --> Continue; Continue --> End([idle]);
+```
+
+CLIP: Calling Line Identification Presentation.
+
+Flowchart for Process CLIP\_MAF001. It starts with 'idle', followed by 'initiate handling of CLIP'. A decision 'CLIP provisioned' follows. If 'no', it goes to 'set provision indication = not provisioned'. If 'yes', it goes to 'set provision indication = provisioned'. From there, a decision 'called subscriber in HPLMN country' is made. If 'no', it goes to 'set override category = no'. If 'yes', a decision 'override category' is made. If 'yes', it goes to 'set override category = yes'. If 'no', it goes to 'set override category = no'. Both 'set override category' paths lead to 'continue call handling', which then leads to 'idle'. A note at the bottom right says 'CLIP: Calling Line Identification Presentation.'
+
+Figure 1.2: MAF001 Determination of calling line identification presentation subscription (VLR)
+
+![Flowchart for process CLIP_MAF002: Determination of the information for offering to the called party (destination MSC).](e6df2733626a85205c1db682e6259c46_img.jpg)
+
+process CLIP\_MAF002
+
+381\_13(1)
+
+Figure 1.3
+
+```
+
+graph TD
+    Idle1([Idle]) --> Init[initiate handling of CLIP]
+    Init --> CLIP_Provisioned{CLIP Provisioned}
+    CLIP_Provisioned -- No --> End1(( ))
+    CLIP_Provisioned -- Yes --> CLI_available{CLI available}
+    CLI_available -- No --> End2(( ))
+    CLI_available -- Yes --> CLI_received_VLR{CLI received from VLR}
+    CLI_received_VLR -- No --> Use_CLI_Signalling[Use CLI received from signalling]
+    CLI_received_VLR -- Yes --> Use_CLI_VLR[Use CLI received from VLR]
+    Use_CLI_Signalling --> PI_Restricted{PI = Presentation restricted?}
+    Use_CLI_VLR --> PI_Restricted
+    PI_Restricted -- Yes --> Cause_No_CLI[Cause of No CLI]
+    PI_Restricted -- No --> Additional_CLI_Available{additional CLI available}
+    Cause_No_CLI --> Override_Category1{override category}
+    Override_Category1 -- Yes --> Additional_CLI_Available1{additional CLI available}
+    Override_Category1 -- No --> Additional_CLI_Available2{additional CLI available}
+    Additional_CLI_Available1 -- Yes --> CLI_Override[CLI in case of override category]
+    Additional_CLI_Available1 -- No --> Pass_CLI1[pass CLI]
+    CLI_Override --> Additional_CLI[additional CLI]
+    Additional_CLI --> Pass_Additional_CLI1[pass additional CLI]
+    Additional_CLI_Available2 -- Yes --> Override_Category2{override category}
+    Additional_CLI_Available2 -- No --> PI_Restricted_Network{PI = presentation restricted by network?}
+    Override_Category2 -- Yes --> Set_PI_Restricted[Set PI = presentation restricted]
+    Override_Category2 -- No --> Set_PI_Not_Available1[Set PI = number not available]
+    Set_PI_Restricted --> Pass_CLI2[pass CLI]
+    Set_PI_Not_Available1 --> Pass_CLI2
+    Pass_CLI1 --> Continue[Continue Call Handling]
+    Pass_CLI2 --> Continue
+    Pass_Additional_CLI1 --> Continue
+    PI_Restricted_Network --> Pass_Additional_CLI2[pass additional CLI]
+    Pass_Additional_CLI2 --> Continue
+    End2 --> Set_PI_Not_Available2[set PI = number not available]
+    Set_PI_Not_Available2 --> Continue
+    Continue --> Idle2([Idle])
+  
+```
+
+CLIP: Calling Line Identification Presentation  
+CLI: Calling Line Identity  
+PI: Presentation Indicator
+
+Flowchart for process CLIP\_MAF002: Determination of the information for offering to the called party (destination MSC).
+
+Figure 1.3: MAF002 Determination of the information for offering to the called party (destination MSC)
+
+![Flowchart for Procedure Cause_of_no_CLI](5a4e62bead259c258d069fd3663ea670_img.jpg)
+
+### Procedure Cause\_of\_no\_CLI
+
+1(1)
+
+```
+graph TD; Start([ ]) --> Q1{Cause of no CLI supported?}; Q1 -- Yes --> Q2{CoNC = reject by user?}; Q1 -- No --> End(( )); Q2 -- Yes --> End; Q2 -- No --> Q3{CoNC = interworking with other services?}; Q3 -- Yes --> Set3[Set CoNC = Interworking with other services]; Q3 -- No --> Q4{CoNC = Coin line/payphone?}; Q4 -- Yes --> Set2[Set CoNC = Coin line/payphone]; Q4 -- No --> Q5{CoNC = Unavailable?}; Q5 -- Yes --> Set1[Set CoNC = Unavailable]; Q5 -- No --> End; Set1 --> End; Set2 --> End; Set3 --> End;
+```
+
+The flowchart titled 'Procedure Cause\_of\_no\_CLI' starts with an oval connector. The first decision diamond asks 'Cause of no CLI supported?'. If 'Yes', it proceeds to the next decision 'CoNC = reject by user?'. If 'Yes' to this, it ends at a circle with an 'X'. If 'No', it proceeds to 'CoNC = interworking with other services?'. If 'Yes', it goes to 'Set CoNC = Interworking with other services'. If 'No', it proceeds to 'CoNC = Coin line/payphone?'. If 'Yes', it goes to 'Set CoNC = Coin line/payphone'. If 'No', it proceeds to 'CoNC = Unavailable?'. If 'Yes', it goes to 'Set CoNC = Unavailable'. If 'No', it ends at the circle with an 'X'. All four 'Set CoNC' boxes lead to the same end connector. A note box in the top right contains 'CoNC : Cause of no CLI'.
+
+Flowchart for Procedure Cause\_of\_no\_CLI
+
+Figure 1.4: Procedure Cause\_of\_no\_CLI
+
+![SDL diagram for Procedure CLI_MT_GMSC showing a start symbol, a process box to add calling party information to the SRI, and an end symbol.](27b06ec9f42b5d727a2630f61a5f1861_img.jpg)
+
+Procedure CLI\_MT\_GMSC 1(1)
+
+```
+
+graph TD
+    Start([ ])
+    Process[ ]
+    Note[Add Calling Party  
+Number and Generic  
+Number to the SRI]
+    End((X))
+
+    Start --> Process
+    Process --- Note
+    Process --> End
+  
+```
+
+SDL diagram for Procedure CLI\_MT\_GMSC showing a start symbol, a process box to add calling party information to the SRI, and an end symbol.
+
+**Figure 1.5: Addition of line identification information to Send Routeing Info message.**
+
+#### Procedure CLI\_HLR\_Set\_CLI
+
+1(1)
+
+![Note box icon](eb22a8740f7c6a0f6ee98f16d99ed8b9_img.jpg)
+
+Note box icon
+
+![Flowchart for CLI_HLR_Set_CLI procedure](ddc7460821484f1ae2835c67955c554c_img.jpg)
+
+```
+graph TD; Start([ ]) --> D1{ }; D1 -- No --> End(( )); D1 -- Yes --> D2{ }; D2 -- No --> End; D2 -- Yes --> D3{ }; D3 -- No --> End; D3 -- Yes --> P1[Add Calling Party Number and Generic Number to the PRN]; P1 --> End;
+```
+
+The flowchart illustrates the procedure for adding line identification information. It begins with a start symbol (oval with a vertical line) leading to a decision diamond. The first decision is 'Subscriber roaming outside home country'. If 'No', the process ends at a circle with an 'X'. If 'Yes', it proceeds to the next decision diamond: 'Sending of CLI information allowed to destination NW'. If 'No', the process ends. If 'Yes', it proceeds to the third decision diamond: 'CLI information received from GMSC'. If 'No', the process ends. If 'Yes', it proceeds to a process box: 'Add Calling Party Number and Generic Number to the PRN', which then leads to the end symbol.
+
+Flowchart for CLI\_HLR\_Set\_CLI procedure
+
+Figure 1.6: Addition of line identification information to Provide Roaming Number message.
+
+![Flowchart for Procedure CLI_PRN_VLR. It starts with a connector symbol, followed by a decision diamond 'CLI Information received from HLR'. If 'No', it goes to another decision diamond 'Subscriber roaming outside home country'. If 'No' to the second diamond, it goes to a connector symbol. If 'Yes' to the second diamond, it goes to a process box 'Store CLI information', which then leads to a connector symbol. If 'Yes' to the first diamond, it also leads to the connector symbol.](a33da0f14e456f92539ce3e9b7d81f9a_img.jpg)
+
+Procedure CLI\_PRN\_VLR
+
+1(1)
+
+```
+graph TD; Start([ ]) --> D1{CLI Information received from HLR}; D1 -- No --> D2{Subscriber roaming outside home country}; D1 -- Yes --> End(( )); D2 -- No --> End; D2 -- Yes --> Process[Store CLI information]; Process --> End;
+```
+
+Flowchart for Procedure CLI\_PRN\_VLR. It starts with a connector symbol, followed by a decision diamond 'CLI Information received from HLR'. If 'No', it goes to another decision diamond 'Subscriber roaming outside home country'. If 'No' to the second diamond, it goes to a connector symbol. If 'Yes' to the second diamond, it goes to a process box 'Store CLI information', which then leads to a connector symbol. If 'Yes' to the first diamond, it also leads to the connector symbol.
+
+Figure 1.7: Storing of Line Identification in destination VLR
+
+![Flowchart for Procedure CLI_ICH_VLR_Add_CLI. It starts with a connector symbol, leading to a decision diamond 'CLI information stored in VLR'. If 'No', it goes to an exit connector. If 'Yes', it goes to a process block 'Add Calling Party Number and Generic Number to message to MSC', which then leads to an exit connector.](7efae06af3af43ffe5d4b956a679cf54_img.jpg)
+
+Procedure CLI\_ICH\_VLR\_Add\_CLI
+
+1(1)
+
+```
+graph TD; Start([ ]) --> Decision{CLI information stored in VLR}; Decision -- No --> Exit1(( )); Decision -- Yes --> Process[Add Calling Party Number and Generic Number to message to MSC]; Process --> Exit2(( ));
+```
+
+Flowchart for Procedure CLI\_ICH\_VLR\_Add\_CLI. It starts with a connector symbol, leading to a decision diamond 'CLI information stored in VLR'. If 'No', it goes to an exit connector. If 'Yes', it goes to a process block 'Add Calling Party Number and Generic Number to message to MSC', which then leads to an exit connector.
+
+Figure 1.8: Addition of line identification information to Complete Call/Process Call Waiting message.
+
+![Sequence diagrams showing information flow for calling line identification presentation. The top diagram shows a direct path from MS/TE to MSb via MSCa/LE, VLRb, and MSCb. The bottom diagram shows a more complex path involving a GMSC and HLRb for routing information before reaching MSCb and MSb.](1a827b10290f33d4fec04d0e8ef7a897_img.jpg)
+
+**Top Sequence Diagram:**
+
+- MS/TE** sends a **set-up** message to **MSCa/LE**.
+- MSCa/LE** sends a **set-up** message to **MSCb** containing **(SI+PI+CoNC+LI+aSI+aPI+aLI)**.
+- MSCb** sends an **info req** to **VLRb** (labeled **MAF 001**).
+- VLRb** sends an **info ack** to **MSCb** (labeled **MAF002**).
+- MSCb** sends a **set-up** message to **MSb** containing **(SI+PI+CoNC+LI)**.
+
+**Bottom Sequence Diagram:**
+
+- MS/TE** sends a **set-up** message to **MSCa/LE**.
+- MSCa/LE** sends a **set-up** message to **GMSC** containing **(SI+PI+CoNC+LI+aSI+aPI+aLI)**.
+- GMSC** sends an **SRI** message to **HLRb**.
+- HLRb** sends a response containing **(SI+PI+LI+aSI+aPI+aLI)** to **GMSC**.
+- GMSC** sends an **SRI ack** message to **HLRb**.
+- HLRb** sends a **PRN** message to **VLRb**.
+- VLRb** sends a response containing **(SI+PI+LI+aSI+aPI+aLI)** to **HLRb**.
+- HLRb** sends a **PRN ack** message to **VLRb**.
+- GMSC** sends a **set-up** message to **MSCb** containing **(SI+PI+CoNC+LI+aSI+aPI+aLI)**.
+- MSCb** sends an **info req** to **VLRb** (labeled **MAF 001**).
+- VLRb** sends an **info ack** to **MSCb** (labeled **MAF 002**).
+- MSCb** sends a **set-up** message to **MSba** containing **(SI+PI+CoNC+LI)**.
+
+Sequence diagrams showing information flow for calling line identification presentation. The top diagram shows a direct path from MS/TE to MSb via MSCa/LE, VLRb, and MSCb. The bottom diagram shows a more complex path involving a GMSC and HLRb for routing information before reaching MSCb and MSb.
+
+Figure 1.9: Information flow for calling line identification presentation: mobile station or fixed terminal to mobile station
+
+#### NOTE:
+
+\*\* : A subaddress may be received from the originating MS or the TE  
+ info: information SI: screening indicator aSI: additional screening indicator  
+ req: request PI: presentation indicator CoNC: cause of no CLI  
+ aPI: additional presentation indicator  
+ ack: acknowledge LI: line identity aLI: additional line identity
+
+NOTE: For mapping rules of CLI parameters refer to Annex A.
+
+### 1.2.1 Optional capability to carry calling line identification
+
+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 subclause 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 subclause is done using the stored calling line identification.
+
+### 1.2.2 Information elements used in the messages
+
+**Table 1.2.2.1: Information elements used in messages**
+
+| Information Element  | Logical Information element name | Information element Required | Information element description                                                                                                                                    |
+|----------------------|----------------------------------|------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Calling Party Number | SI                               | M                            | Calling Party Number contains screening indicator (SI), presentation indicator (PI) and line identity (LI) as mandatory information.                               |
+|                      | PI                               | M                            |                                                                                                                                                                    |
+|                      | LI                               | M                            |                                                                                                                                                                    |
+| Generic Number       | aSI                              | M                            | Generic Number contains additional screening indicator (aSI), additional presentation indicator (aPI) and additional line identity (aLI) as mandatory information. |
+|                      | aPI                              | M                            |                                                                                                                                                                    |
+|                      | aLI                              | M                            |                                                                                                                                                                    |
+| Cause of no CLI      | unavailable                      | M                            | Cause 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 user                   | M                            |                                                                                                                                                                    |
+|                      | interaction with other service   | M                            |                                                                                                                                                                    |
+|                      | coin line/payphone               | M                            |                                                                                                                                                                    |
+
+### 1.2.3 Parameters in Send Routeing Info and Provide Roaming Number for CLI
+
+**Table 1.2.3.1: Messages between GMSC and HLR**
+
+| Message            | Message sender | Information element name | Information element Required | Information element description                                                                                                                                                       |
+|--------------------|----------------|--------------------------|------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Send Routeing Info | GMSC           | -                        | -                            | Refer to 3GPP TS 23.018.                                                                                                                                                              |
+|                    |                | Calling Party Number     | C                            | In addition:<br>The information element is present if GMSC received calling party number from originating network; otherwise it shall be absent.                                      |
+|                    |                | Generic Number           | C                            | The 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. |
+
+**Table 1.2.3.2: Messages between HLR and VLR**
+
+| Message                | Message sender | Information element name | Information element Required | Information element description                                                                                                                                      |
+|------------------------|----------------|--------------------------|------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| Provide Roaming Number | HLR            | -                        | -                            | Refer to 3GPP TS 23.018.                                                                                                                                             |
+|                        |                | Calling Party Number     | C                            | In addition:<br>The 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 Number           | C                            | The 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.      |
+
+### 1.2.4 Messages between MSC and VLR in destination network
+
+**Table 1.2.4.1: Messages between MSC and VLR**
+
+| Message                     | Message sender | Information element name | Information element Required | Information element description                                                                                   |
+|-----------------------------|----------------|--------------------------|------------------------------|-------------------------------------------------------------------------------------------------------------------|
+| Complete Call               | VLR            | -                        | -                            | Refer to 3GPP TS 23.018.                                                                                          |
+|                             |                | Calling Party Number     | C                            | In addition:<br>The information element is present if it is stored in VLR; otherwise it shall be absent.          |
+|                             |                | Generic Number           | C                            | The information element is present if it is stored in VLR; otherwise it shall be absent.                          |
+|                             |                | Cause of no CLI          | C                            | The information element is present if it is stored in VLR; otherwise it shall be absent.                          |
+| Process Call Waiting        | VLR            | -                        | -                            | Refer to 3GPP TS 23.018.                                                                                          |
+|                             |                | Calling Party Number     | C                            | In addition:<br>The information element is present if it is stored in VLR; otherwise it shall be absent.          |
+|                             |                | Generic Number           | C                            | The information element is present if it is stored in VLR; otherwise it shall be absent.                          |
+|                             |                | Cause of no CLI          | C                            | The information element is present if it is stored in VLR; otherwise it shall be absent.                          |
+| Send Info for Incoming Call | MSC            | -                        | -                            | Refer to 3GPP TS 23.018.                                                                                          |
+|                             |                | Cause of no CLI          | C                            | In addition:<br>The information element is present if MSC received Cause of no CLI; otherwise it shall be absent. |
+
+## 1.3 Information stored in the HLR
+
+CLIP 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 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.
+
+## 1.4 State transition model
+
+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.
+
+![State transition model for CLIP diagram showing two states and two transitions.](81a4cbf0b3c4cbc065efdf8f800dadde_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> NotProvisioned
+    state " (Not Provisioned, Not Applicable, Not Active, Not Induced) " as NotProvisioned
+    state " (Provisioned, Not Applicable, Active and Operative, Not Induced) " as Provisioned
+    NotProvisioned --> Provisioned : Provision
+    Provisioned --> NotProvisioned : Withdrawal
+  
+```
+
+The diagram illustrates the state transition model for CLIP. It consists of two states represented by ovals. The left state is labeled "(Not Provisioned, Not Applicable, Not Active, Not Induced)". The right state is labeled "(Provisioned, Not Applicable, Active and Operative, Not Induced)". A curved arrow labeled "Provision" points from the left state to the right state. A curved arrow labeled "Withdrawal" points from the right state back to the left state.
+
+State transition model for CLIP diagram showing two states and two transitions.
+
+**Figure 1.9: State transition model for CLIP**
+
+## 1.5 Transfer of information from HLR to VLR
+
+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.
+
+## 1.6 Information stored in the VLR
+
+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 Handover
+
+Handover will have no impact on the control procedures and the operation of the service.
+
+## 1.8 Interactions with other supplementary services
+
+See 3GPP TS 22.081 [4] subclause 1.6.
+
+# 2 Calling line identification restriction (CLIR)
+
+## 2.1 Handling of calling line identification restriction
+
+### 2.1.1 General
+
+If the originating party has calling line identification restriction provisioned and it is impossible to indicate to the terminating network (due to interworking) that the number should not be presented to the terminating party, the calling line identity shall not be delivered to the terminating network.
+
+### 2.1.2 Permanent mode
+
+If the subscriber has calling line identification restriction provisioned in permanent mode, the originating party's CLI shall not be presented to the terminating party (i.e. the terminating MS or TE), unless the terminating party has calling line identification presentation provisioned with the subscription option "override category" set (see clause 1).
+
+### 2.1.3 Controlling presentation of the CLI when CLIR is provisioned in temporary mode
+
+A subscriber can have calling line identification restriction provisioned in temporary mode with one of two default values: presentation restricted or presentation allowed.
+
+If the default value is set to presentation restricted, the default handling is not to present the originating party's CLI to the terminating party (i.e. the terminating MS or TE).
+
+However, it is possible for the originating subscriber to present his CLI to the terminating party. The originating subscriber must indicate during call set-up that the CLI must be presented to the terminating party. This procedure is illustrated in figure 2.1.
+
+![Diagram of Figure 2.1: MS indicating presentation of CLI when CLIR is provisioned in temporary mode with default value 'presentation restricted'.](73dff6b45b2b9ffd384bab3235f869af_img.jpg)
+
+The diagram shows a Mobile Station (MS) on the left and a Mobile Switching Center (MSC) on the right. A horizontal arrow points from the MS to the MSC, with the text "Present CLI" written above it. Both the MS and MSC are represented by vertical rectangles with a small horizontal line at the top.
+
+Diagram of Figure 2.1: MS indicating presentation of CLI when CLIR is provisioned in temporary mode with default value 'presentation restricted'.
+
+**Figure 2.1: MS indicating presentation of CLI when CLIR is provisioned in temporary mode with default value "presentation restricted"**
+
+If the default value is set to presentation allowed, the default handling is to present the originating party's CLI to the terminating party (i.e. the terminating MS or TE).
+
+However, it is possible for the originating subscriber to restrict presentation of his CLI to the terminating party. The originating subscriber must indicate during call set-up that CLI presentation must be restricted. This procedure is illustrated in figure 2.2.
+
+![Diagram of Figure 2.2: MS invoking CLIR, when CLIR is provisioned in temporary mode with default value 'presentation allowed'.](5fbb4f0de01736f1293333e599410c99_img.jpg)
+
+The diagram shows a Mobile Station (MS) on the left and a Mobile Switching Center (MSC) on the right. A horizontal arrow points from the MS to the MSC, with the text "Restrict CLI" written above it. Both the MS and MSC are represented by vertical rectangles with a small horizontal line at the top.
+
+Diagram of Figure 2.2: MS invoking CLIR, when CLIR is provisioned in temporary mode with default value 'presentation allowed'.
+
+**Figure 2.2: MS invoking CLIR, when CLIR is provisioned in temporary mode with default value "presentation allowed"**
+
+### 2.1.4 Interrogation
+
+#### Data request
+
+The mobile subscriber can request the data of the supplementary service.
+
+In response the following information shall be given:
+
+- whether the service is provided or not;
+- if provided which mode is subscribed;
+- if subscribed to the temporary mode: which default value.
+
+This procedure is illustrated in figure 2.3.
+
+![Sequence diagram showing the interrogation of calling line identification restriction. The diagram involves four lifelines: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends 'Interrogate CLIR' to MSC. 2. MSC sends 'Interrogate CLIR' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete' back to MS. The HLR lifeline is present but not involved in this sequence.](e180f2b5fcbe8001554a7c0677cd3f82_img.jpg)
+
+```
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant HLR
+    MS->>MSC: Interrogate CLIR
+    MSC->>VLR: Interrogate CLIR
+    VLR-->>MSC: Acknowledge
+    MSC-->>MS: Release Complete
+```
+
+Sequence diagram showing the interrogation of calling line identification restriction. The diagram involves four lifelines: MS, MSC, VLR, and HLR. The sequence of messages is: 1. MS sends 'Interrogate CLIR' to MSC. 2. MSC sends 'Interrogate CLIR' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete' back to MS. The HLR lifeline is present but not involved in this sequence.
+
+**Figure 2.3: Interrogation of calling line identification restriction**
+
+## 2.2 Functions and information flows
+
+The following Mobile Additional Functions have been identified for the PLMN:
+
+### MAF003
+
+Determination of the calling line identification restriction subscription
+
+The ability of a PLMN component to determine whether the supplementary service is provisioned for the mobile subscriber. See figure 2.4.
+
+Location: VLR.
+
+### MAF004
+
+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 2.5.
+
+Location: originating MSC.
+
+The information flows are shown in figures 2.6 to 2.9.
+
+![Flowchart for Process CLIR_MAF003: Determination of calling line identification restriction subscription (VLR).](eb03559a4d92ea9ebd63ea9be663c50a_img.jpg)
+
+Process CLIR\_MAF003 381\_24(1)
+
+Figure 2.4
+
+```
+graph TD; Start([idle]) --> Init[/initiate handling of CLIR/]; Init --> Decision1{CLIR provisioned}; Decision1 -- no --> SetNotProvisioned[set provision indication = not provisioned]; Decision1 -- yes --> SetProvisioned[set provision indication = provisioned]; SetProvisioned --> Decision2{subscription option = permanent}; SetNotProvisioned --> Decision2; Decision2 -- yes --> SetPermanent[set mode indication = permanent]; Decision2 -- no --> Decision3{temporary mode default = pres. restricted}; Decision3 -- no --> ModeAllowed[mode indication = temporary (pres. allowed)]; Decision3 -- yes --> ModeRestricted[mode indication = temporary (pres. restricted)]; ModeAllowed --> Continue{continue call handling}; ModeRestricted --> Continue; SetPermanent --> Continue; Continue --> End([idle]);
+```
+
+CLIR: Calling Line Identification Restriction
+
+Flowchart for Process CLIR\_MAF003: Determination of calling line identification restriction subscription (VLR).
+
+**Figure 2.4: MAF003 Determination of calling line identification restriction subscription (VLR)**
+
+![Flowchart for process CLIR_MAF004: Determination of the presentation indicator (originating MSC).](ae53f90bb87d6d09e2d6b5278d7c338f_img.jpg)
+
+process CLIR\_MAF004
+
+381\_25(1)
+
+Figure 2.5
+
+```
+graph TD; Idle1([Idle]) --> Initiate[Initiate Handling of CLIR]; Initiate --> CLIR_Provisioned{CLIR Provisioned?}; CLIR_Provisioned -- No --> Restrict_CLI_note2{Restrict CLI? note 2}; CLIR_Provisioned -- Yes --> Permanent{Permanent?}; Restrict_CLI_note2 -- Yes --> ClearCall{{Clear Call}}; Restrict_CLI_note2 -- No --> SetPI_allowed1[Set PI = presentation allowed]; Permanent -- Yes --> Present_CLI_note1_1{present CLI? note 1}; Permanent -- No --> TempModeDefault{temporary mode default = pres. restricted?}; Present_CLI_note1_1 -- Yes --> SetPI_restricted1[Set PI = Presentation restricted]; Present_CLI_note1_1 -- No --> ErrorNotification{{Error Notification}}; TempModeDefault -- Yes --> Present_CLI_note1_2{present CLI note 1}; TempModeDefault -- No --> Restrict_CLI_note2_2{restrict CLI? note 2}; Present_CLI_note1_2 -- Yes --> SetPI_allowed2[Set PI = Presentation allowed]; Present_CLI_note1_2 -- No --> ErrorNotification; Restrict_CLI_note2_2 -- Yes --> SetPI_restricted2[Set PI = presentation restricted]; Restrict_CLI_note2_2 -- No --> SetPI_allowed2; SetPI_allowed1 --> Continue[Continue Call Handling]; SetPI_restricted1 --> Cause_of_no_CLI_CLIR1[Cause_of no_CLI_CLIR]; SetPI_allowed2 --> Continue; SetPI_restricted2 --> Cause_of_no_CLI_CLIR2[Cause_of no_CLI_CLIR]; Cause_of_no_CLI_CLIR1 --> Continue; Cause_of_no_CLI_CLIR2 --> Continue; Continue --> Idle2([Idle]);
+```
+
+Note 1: present CLI is input received from the mobile  
+Note 2: restrict CLI is input received from the mobile
+
+CLIR: Calling Line Identification Restriction  
+CLI: Calling Line Identity  
+PI: Presentation Indicator
+
+Flowchart for process CLIR\_MAF004: Determination of the presentation indicator (originating MSC).
+
+Figure 2.5: MAF004 Determination of the presentation indicator (originating MSC)
+
+![Flowchart for Procedure Cause_of_no_CLI_CLIR. It starts with a connector, then checks if 'Cause of no CLI supported?'. If 'No', it goes to a merge point. If 'Yes', it checks 'rejected by user?'. If 'Yes', it goes to 'Set CoNC = reject by user'. If 'No', it checks 'interacted with other services?'. If 'Yes', it goes to 'Set CoNC = interaction with other services'. If 'No', it checks 'coin line/ payphone?'. If 'Yes', it goes to 'Set CoNC = coin line/payphone'. If 'No', it checks 'Unavailable?'. If 'Yes', it goes to 'Set CoNC = unavailable'. If 'No', it goes to a merge point. All four 'Set CoNC' boxes lead to a common merge point, which then leads to an end connector.](26d664119ad25250780f554633444e54_img.jpg)
+
+Procedure Cause\_of\_no\_CLI\_CLIR 1(1)
+
+```
+graph TD; Start([ ]) --> Q1{Cause of no CLI supported?}; Q1 -- No --> Merge(( )); Q1 -- Yes --> Q2{rejected by user?}; Q2 -- Yes --> Set1[Set CoNC = reject by user]; Q2 -- No --> Q3{interacted with other services?}; Q3 -- Yes --> Set2[Set CoNC = interaction with other services]; Q3 -- No --> Q4{coin line/ payphone?}; Q4 -- Yes --> Set3[Set CoNC = coin line/payphone]; Q4 -- No --> Q5{Unavailable?}; Q5 -- Yes --> Set4[Set CoNC = unavailable]; Q5 -- No --> Merge; Set1 --> Merge; Set2 --> Merge; Set3 --> Merge; Set4 --> Merge; Merge --> End((X))
+```
+
+Flowchart for Procedure Cause\_of\_no\_CLI\_CLIR. It starts with a connector, then checks if 'Cause of no CLI supported?'. If 'No', it goes to a merge point. If 'Yes', it checks 'rejected by user?'. If 'Yes', it goes to 'Set CoNC = reject by user'. If 'No', it checks 'interacted with other services?'. If 'Yes', it goes to 'Set CoNC = interaction with other services'. If 'No', it checks 'coin line/ payphone?'. If 'Yes', it goes to 'Set CoNC = coin line/payphone'. If 'No', it checks 'Unavailable?'. If 'Yes', it goes to 'Set CoNC = unavailable'. If 'No', it goes to a merge point. All four 'Set CoNC' boxes lead to a common merge point, which then leads to an end connector.
+
+Figure 2.6: Procedure Cause\_of\_no\_CLI\_CLIR
+
+![Sequence diagram for Figure 2.7 showing information flow for calling line identification restriction.](90ddb84c323b956e2d50a54d3f870566_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant MSCb/LE
+    Note right of MSC: MAF 004
+    Note right of VLR: MAF 003
+    MS->>MSC: set-up  
+**
+    MSC->>VLR: info request
+    VLR-->>MSC: info acknowledge
+    MSC->>MSCb/LE: set-up  
+(SI,PI=restricted, CoNC,  
+LI:Calling party number)
+  
+```
+
+The diagram illustrates the information flow for calling line identification restriction. It involves four lifelines: MS, MSC, VLR, and MSCb/LE. The MS sends a 'set-up' message to the MSC, which includes a subaddress (\*\*). The MSC then sends an 'info request' to the VLR. The VLR responds with an 'info acknowledge'. Finally, the MSC sends a 'set-up' message to the MSCb/LE, which includes the screening indicator (SI), presentation indicator (PI) set to 'restricted', CoNC, and the line identity (LI) of the calling party number. The MSC has a message authentication code (MAC) MAF 004, and the VLR has MAF 003.
+
+Sequence diagram for Figure 2.7 showing information flow for calling line identification restriction.
+
+**Figure 2.7: Information flow for calling line identification restriction in permanent or temporary mode with the default value "presentation restricted"**
+
+NOTE: \*\*: A subaddress may be received from the MS  
+ SI: screening indicator  
+ PI: presentation indicator  
+ LI: line identity
+
+![Sequence diagram for Figure 2.8 showing information flow for allowing presentation of the CLI.](392a79ccd95e682ccd08f35ab2e64144_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant MSCb/LE
+    Note right of MSC: MAF 004
+    Note right of VLR: MAF 003
+    MS->>MSC: set-up  
+(present CLI)  
+**
+    MSC->>VLR: info request
+    VLR-->>MSC: info acknowledge
+    MSC->>MSCb/LE: set-up  
+(SI, PI=pres allowed, LI)
+  
+```
+
+The diagram illustrates the information flow for allowing the presentation of the calling line identity (CLI) when CLIR is provisioned in temporary mode. It involves four lifelines: MS, MSC, VLR, and MSCb/LE. The MS sends a 'set-up' message to the MSC, which includes the calling line identity (present CLI) and a subaddress (\*\*). The MSC then sends an 'info request' to the VLR. The VLR responds with an 'info acknowledge'. Finally, the MSC sends a 'set-up' message to the MSCb/LE, which includes the screening indicator (SI), presentation indicator (PI) set to 'pres allowed', and the line identity (LI). The MSC has a message authentication code (MAC) MAF 004, and the VLR has MAF 003.
+
+Sequence diagram for Figure 2.8 showing information flow for allowing presentation of the CLI.
+
+**Figure 2.8: Information flow for allowing presentation of the CLI when CLIR is provisioned in temporary mode with default value "presentation restricted"**
+
+NOTE: \*\*: A subaddress may be received from the MS  
+ SI: screening indicator  
+ PI: presentation indicator  
+ LI: line identity  
+ CLI: calling line identity
+
+![Sequence diagram for calling line identification presentation in temporary mode with default value 'presentation allowed'.](2ae3eae1bd80a90f192f568ae246a9a6_img.jpg)
+
+This sequence diagram illustrates the information flow for calling line identification presentation in temporary mode with the default value "presentation allowed". The participants are MS, MSC, VLR, and MSCb/LE. The sequence of messages is as follows: 1. The MS sends a "set-up" message to the MSC, with a subaddress (\*\*). 2. The MSC sends an "info request" to the VLR, identified by MAF 004. 3. The VLR responds with an "info acknowledge" to the MSC, identified by MAF 003. 4. Finally, the MSC sends a "set-up" message to the MSCb/LE, including parameters (SI, PI=pres allowed, LI).
+
+Sequence diagram for calling line identification presentation in temporary mode with default value 'presentation allowed'.
+
+NOTE: \*\*: A subaddress may be received from the MS  
+SI: screening indicator  
+PI: presentation indicator  
+LI: line identity
+
+![Sequence diagram for calling line identification restriction in temporary mode with default value 'presentation allowed'.](4cde160bcc69b7b6c81b648dd0e4252e_img.jpg)
+
+This sequence diagram illustrates the information flow for calling line identification restriction in temporary mode with the default value "presentation allowed". The participants are MS, MSC, VLR, and MSCb/LE. The sequence of messages is as follows: 1. The MS sends a "set-up" message to the MSC, containing "(restrict CLI)" and a subaddress (\*\*). 2. The MSC sends an "info request" to the VLR, identified by MAF 004. 3. The VLR responds with an "info acknowledge" to the MSC, identified by MAF 003. 4. Finally, the MSC sends a "set-up" message to the MSCb/LE, including parameters (SI, PI=restricted, CoNC, LI:Calling party number).
+
+Sequence diagram for calling line identification restriction in temporary mode with default value 'presentation allowed'.
+
+**Figure 2.9 : Information flow for calling line identification restriction in temporary mode with default value "presentation allowed"**
+
+NOTE: \*\*: A subaddress may be received from the MS  
+SI: screening indicator  
+PI: presentation indicator  
+LI: line identity  
+CLI: calling line identity
+
+## 2.3 Information stored in the HLR
+
+CLIR 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 CLIR (which shall be one of the valid states listed above) on a per subscriber basis.
+
+The HLR shall also store the subscription option "presentation mode" on a per subscriber basis.
+
+This parameter takes one of the following values:
+
+- permanent;
+- temporary (presentation restricted);
+- temporary (presentation allowed).
+
+## 2.4 State transition model
+
+The following figure shows the successful cases of transition between the applicable logical states of CLIR. 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.
+
+![State transition model for CLIR diagram showing two states and two transitions.](ead623e6a8ec701df64567695a57d01c_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> State1 : Provision
+    State1 --> State2 : Withdrawal
+    state " (Not Provisioned, Not Applicable, Not Active, Not Induced) " as State1
+    state " (Provisioned, Not Applicable, Active and Operative, Not Induced) " as State2
+  
+```
+
+The diagram illustrates the state transition model for CLIR. It consists of two states represented by ovals. The left state contains the logical state: (Not Provisioned, Not Applicable, Not Active, Not Induced). The right state contains the logical state: (Provisioned, Not Applicable, Active and Operative, Not Induced). A curved arrow labeled "Provision" points from the left state to the right state. A curved arrow labeled "Withdrawal" points from the right state back to the left state.
+
+State transition model for CLIR diagram showing two states and two transitions.
+
+Figure 2.10: State transition model for CLIR
+
+## 2.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 CLIR and the presentation mode.
+
+If the logical state of CLIR or the presentation mode is changed while a subscriber is registered on a VLR then the HLR shall inform the VLR of the new logical state of CLIR and (if the provisioning state is "Provisioned") the new presentation mode.
+
+## 2.6 Information stored in the VLR
+
+For CLIR, the VLR shall store the service state information and presentation mode received from the HLR.
+
+## 2.7 Handover
+
+Handover will have no impact on the control procedures and the operation of the service.
+
+## 2.8 Interworking
+
+The VPLMN needs to distinguish three cases in order to meet data privacy requirements in an environment where support of CLIP and CLIR is optional:
+
+- the HPLMN supports CLIR, and CLIR is provisioned for the subscriber;
+- the HPLMN supports CLIR, but CLIR is not provisioned for the subscriber;
+- the HPLMN does not support CLIR.
+
+In case a) the VPLMN must apply the CLIR subscription as indicated by the data sent by the HPLMN.
+
+In case b) the VPLMN must not apply CLIR.
+
+In case c) the VPLMN must apply an implicit CLIR subscription.
+
+To allow the VPLMN to make this distinction, the HLR and VLR behave as follows:
+
+- If the HLR supports CLIR, but CLIR is not provisioned for the subscriber, the HLR shall inform the VLR that CLIR is not provisioned.
+- If the VLR supports CLIR, but the HLR does not support CLIR, the VLR shall behave in the same way as if CLIR (temporary (presentation restricted)) was provisioned for the subscriber, i.e. the calling line identity shall not be displayed to the called subscriber unless the called subscriber has CLIR override capability. When interrogating the service status the subscriber shall be informed that CLIR (temporary (presentation restricted)) is provided to him and is active.
+
+# 3 Connected line identification presentation (COLP)
+
+## 3.1 Handling of connected line identification presentation
+
+### 3.1.1 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 3.1.
+
+![Sequence diagram illustrating the interrogation of connected line identification presentation (COLP). The diagram shows four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate COLP' to MSC. 2. MSC sends 'Interrogate COLP' to VLR. 3. VLR sends 'Acknowledge' to MSC. 4. MSC sends 'Release Complete' to MS. The HLR is shown but not involved in this specific sequence.](6a5c8326029e6290e69a5f43d6ed4548_img.jpg)
+
+```
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant HLR
+    MS->>MSC: Interrogate COLP
+    MSC->>VLR: Interrogate COLP
+    VLR-->>MSC: Acknowledge
+    MSC-->>MS: Release Complete
+```
+
+Sequence diagram illustrating the interrogation of connected line identification presentation (COLP). The diagram shows four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate COLP' to MSC. 2. MSC sends 'Interrogate COLP' to VLR. 3. VLR sends 'Acknowledge' to MSC. 4. MSC sends 'Release Complete' to MS. The HLR is shown but not involved in this specific sequence.
+
+Figure 3.1: Interrogation of connected line identification presentation
+
+### 3.1.2 Interactions with call forwarding supplementary services
+
+If the forwarding user selects the option that the calling user is not notified of the call forwarding, then the calling user shall receive no forwarding notification, and the calling user shall not receive the connected user's identity when the call is answered, unless the calling user has override capability.
+
+## 3.2 Functions and information flows
+
+The following Mobile Additional Functions have been identified for the PLMN:
+
+### MAF005
+
+Determination of the connected line identification presentation subscription
+
+The ability of a PLMN component to determine whether the supplementary service is provisioned for the mobile subscriber. See figure 3.2.
+
+Location: VLR.
+
+### MAF006
+
+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 3.3.
+
+Location: originating MSC.
+
+### MAF039
+
+Interaction of connected line identification presentation with the call forwarding supplementary services
+
+The ability of a PLMN component to determine the presentation indicator of the connected party number after invocation of a call forwarding service. See figure 3.4.
+
+Location: forwarding MSC.
+
+The information flow is shown in figure 3.5.
+
+![Flowchart for Process COLP_MAF005: Determination of connected line identification presentation subscription (VLR).](00504fc688ebcf131ccbeff94dfc9939_img.jpg)
+
+Process COLP\_MAF005 381\_32(1)
+
+Figure 3.2
+
+```
+graph TD; Start1([idle]) --> Init[/initiate handling of COLP/]; Init --> Decision1{COLP provisioned}; Decision1 -- yes --> Action1[set provision indication = provisioned]; Decision1 -- no --> Action2[set provision indication = not provisioned]; Action1 --> Decision2{calling subscriber in HPLMN country}; Decision2 -- yes --> Decision3{override category}; Decision2 -- no --> Action3[set override category = no]; Decision3 -- yes --> Action4[set override category = yes]; Decision3 -- no --> Action3; Action2 --> Decision4[/continue call handling/]; Action3 --> Decision4; Action4 --> Decision4; Decision4 --> Start2([idle]);
+```
+
+COLP: Connected Line Identification Presentation.
+
+Flowchart for Process COLP\_MAF005: Determination of connected line identification presentation subscription (VLR).
+
+**Figure 3.2: MAF005 Determination of connected line identification presentation subscription (VLR)**
+
+![Flowchart for Process COLP_MAF006 showing the determination of information for offering to the connected party. It starts with 'idle', followed by 'initiate handling of COLP', then checks if 'COLP provisioned', 'COL available', and 'presentation restricted'. Depending on these checks, it either passes additional COL, passes COL, or sets PI to 'number not available' before continuing call handling and returning to 'idle'.](e05b36c0d46549e681ce6581422c66b2_img.jpg)
+
+Process COLP\_MAF006
+
+381\_33(1)
+
+Figure 3.3
+
+```
+graph TD; idle1([idle]) --> initiate[initiate handling of COLP]; initiate --> provisioned{COLP provisioned}; provisioned -- no --> continue_handling{continue call handling}; provisioned -- yes --> available{COL available}; available -- no --> set_pi[set PI = number not available]; available -- yes --> restricted{presentation restricted}; restricted -- yes --> override{override category}; restricted -- no --> additional_available{additional COL available}; override -- yes --> additional_available; override -- no --> continue_handling; additional_available -- yes --> pass_additional1[pass additional COL]; additional_available -- no --> pass_col[pass COL]; additional_available -- yes --> additional_in_override{COL in case of override category}; additional_in_override --> additional_col[additional COL]; additional_col --> pass_additional2[pass additional COL]; pass_additional1 --> continue_handling; pass_col --> continue_handling; pass_additional2 --> continue_handling; set_pi --> continue_handling; continue_handling --> idle2([idle]);
+```
+
+COLP: Connected Line Identification Presentation.  
+COL: Connected Line Identity.  
+PI: Presentation Indicator.
+
+Flowchart for Process COLP\_MAF006 showing the determination of information for offering to the connected party. It starts with 'idle', followed by 'initiate handling of COLP', then checks if 'COLP provisioned', 'COL available', and 'presentation restricted'. Depending on these checks, it either passes additional COL, passes COL, or sets PI to 'number not available' before continuing call handling and returning to 'idle'.
+
+Figure 3.3: MAF006 Determination of the information for offering to the connected party (originating MSC)
+
+![Flowchart for Process COLP_MAF039. The process starts at an 'idle' state, proceeds to 'initiate handling of COLP', then checks if a 'connected number received'. If 'no', it goes to 'continue call handling'. If 'yes', it checks if to 'notify calling user of forwarding'. If 'yes', it goes to 'continue call handling'. If 'no', it 'set PI = presentation restricted' and then goes to 'continue call handling'. The process ends at an 'idle' state. A note defines COLP as Connected Line Identification Presentation and PI as Presentation Indicator.](b5335262987c819d7f71ce40f99cb71b_img.jpg)
+
+Process COLP\_MAF039
+
+381\_34(1)
+
+Figure 3.4
+
+```
+graph TD; idle1([idle]) --> initiate[initiate handling of COLP]; initiate --> connected{connected number received}; connected -- no --> continue{continue call handling}; connected -- yes --> notify{notify calling user of forwarding}; notify -- yes --> continue; notify -- no --> setPI[set PI = presentation restricted]; setPI --> continue; continue --> idle2([idle]);
+```
+
+COLP: Connected Line Identification Presentation.  
+PI: Presentation Indicator.
+
+Flowchart for Process COLP\_MAF039. The process starts at an 'idle' state, proceeds to 'initiate handling of COLP', then checks if a 'connected number received'. If 'no', it goes to 'continue call handling'. If 'yes', it checks if to 'notify calling user of forwarding'. If 'yes', it goes to 'continue call handling'. If 'no', it 'set PI = presentation restricted' and then goes to 'continue call handling'. The process ends at an 'idle' state. A note defines COLP as Connected Line Identification Presentation and PI as Presentation Indicator.
+
+Figure 3.4: MAF039 Interaction between COLP and call forwarding services (forwarding MSC)
+
+![Sequence diagram showing information flow for connected line identification presentation from MSa to MSb/TE via MSCa, VLRa, and MSCb/LE. The diagram includes messages like set-up, info req, info ack, and answer with various parameters (SI, PI, LI, aSI, aLI, OR1-OR5).](05eb72d372e4bf78e3d6a64949d77bcc_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MSa
+    participant MSCa
+    participant VLRa
+    participant MSCb/LE
+    participant MSb/TE
+
+    Note right of VLRa: MAF 005
+
+    MSa->>MSCa: set-up
+    MSCa->>VLRa: info req
+    VLRa-->>MSCa: info ack
+    MSCa->>MSCb/LE: set-up
+    MSCb/LE->>MSb/TE: set-up
+    MSb/TE-->>MSCb/LE: answer **
+    MSCb/LE-->>MSCa: answer (SI+PI+LI+aSI+aLI)
+    Note right of MSCa: MAF006
+    MSCa-->>MSa: answer OR1:N
+    Note right of MSCa: OR1:Y
+    MSCa-->>MSa: answer OR2:c
+    Note right of MSCa: OR1:Y
+    MSCa-->>MSa: (PI)
+    Note right of MSCa: OR1:Y
+    MSCa-->>MSa: answer OR2:b
+    Note right of MSCa: OR3:N
+    MSCa-->>MSa: (PI)
+    Note right of MSCa: OR1:Y
+    MSCa-->>MSa: answer OR2:b
+    Note right of MSCa: OR3:Y
+    MSCa-->>MSa: (SI+PI+LI)
+    Note right of MSCa: OR1:Y
+    MSCa-->>MSa: answer OR2:b
+    Note right of MSCa: OR3:Y
+    MSCa-->>MSa: (SI+PI+LI)
+    Note right of MSCa: OR1:Y
+    MSCa-->>MSa: answer OR2:b
+    Note right of MSCa: OR3:Y
+    MSCa-->>MSa: (aSI+PI+aLI)
+    Note right of MSCa: OR1:Y
+    MSCa-->>MSa: answer OR2:a
+    Note right of MSCa: OR4:N
+    MSCa-->>MSa: (SI+PI+LI)
+    Note right of MSCa: OR1:Y
+    MSCa-->>MSa: answer OR2:a
+    Note right of MSCa: OR4:Y
+    MSCa-->>MSa: (aSI+PI+aLI)
+  
+```
+
+Sequence diagram showing information flow for connected line identification presentation from MSa to MSb/TE via MSCa, VLRa, and MSCb/LE. The diagram includes messages like set-up, info req, info ack, and answer with various parameters (SI, PI, LI, aSI, aLI, OR1-OR5).
+
+**Figure 3.5: Information flow for connected line identification presentation: mobile station to mobile station or fixed terminal**
+
+NOTE: OR1: COLP provisioned Y: yes N: no  
+ OR2: Presentation Indicator Value a: allowed b: restricted c: not available  
+ OR3: Override category  
+ OR4: additional line identity available Y: yes N: no  
+ OR5: COL in case of override category a: LI b: aLI  
+ \*\*: A connected subaddress may be received from the MS  
+ info: information SI: screening indicator aSI: additional screening indicator  
+ req: request PI: presentation indicator  
+ ack: acknowledge LI: line identity aLI: additional line identity
+
+## 3.3 Information stored in the HLR
+
+COLP 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 COLP (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:
+
+- yes;
+- no.
+
+## 3.4 State transition model
+
+The following figure shows the successful cases of transition between the applicable logical states of COLP. 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.
+
+![State transition model for COLP diagram showing two states and two transitions.](40ef8b4d1d6b485e04c5edfeb6324b18_img.jpg)
+
+```
+
+stateDiagram-v2
+    state "(Not Provisioned, Not Applicable, Not Active, Not Induced)" as state1
+    state "(Provisioned, Not Applicable, Active and Operative, Not Induced)" as state2
+    state1 --> state2 : Provision
+    state2 --> state1 : Withdrawal
+  
+```
+
+The diagram illustrates the state transition model for COLP. It consists of two states represented by ovals. The left state is labeled "(Not Provisioned, Not Applicable, Not Active, Not Induced)". The right state is labeled "(Provisioned, Not Applicable, Active and Operative, Not Induced)". A curved arrow labeled "Provision" points from the left state to the right state. A curved arrow labeled "Withdrawal" points from the right state to the left state.
+
+State transition model for COLP diagram showing two states and two transitions.
+
+Figure 3.6: State transition model for COLP
+
+## 3.5 Transfer of information from HLR to VLR
+
+If the provisioning state for COLP is "Provisioned" then, when the subscriber registers on a VLR, the HLR shall send that VLR information about the logical state of COLP. 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 COLP 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 COLP. If the override category is changed and the provisioning state of COLP 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.
+
+## 3.6 Information stored in the VLR
+
+For COLP, 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".
+
+## 3.7 Handover
+
+Handover will have no impact on the control procedures and the operation of the service.
+
+# 4 Connected line identification restriction (COLR)
+
+## 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.
+
+![Sequence diagram illustrating the interrogation of connected line identification restriction (COLR). The diagram shows four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate COLR' to MSC. 2. MSC sends 'Interrogate COLR' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete' back to MS. The HLR is shown but not involved in this sequence.](1dc5e74b1032f935e1b1ea3a9c876ac6_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS
+    participant MSC
+    participant VLR
+    participant HLR
+    Note right of HLR: HLR is not involved in this sequence
+    MS->>MSC: Interrogate COLR
+    MSC->>VLR: Interrogate COLR
+    VLR-->>MSC: Acknowledge
+    MSC-->>MS: Release Complete
+  
+```
+
+Sequence diagram illustrating the interrogation of connected line identification restriction (COLR). The diagram shows four entities: MS (Mobile Station), MSC (Mobile Switching Center), VLR (Visitor Location Register), and HLR (Home Location Register). The sequence of messages is: 1. MS sends 'Interrogate COLR' to MSC. 2. MSC sends 'Interrogate COLR' to VLR. 3. VLR sends 'Acknowledge' back to MSC. 4. MSC sends 'Release Complete' back to MS. The HLR is shown but not involved in this sequence.
+
+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.
+
+![Flowchart for Process COLR_MAF040. It starts with 'idle', followed by 'initiate handling of COLR'. A decision diamond 'COLR provisioned' has 'yes' and 'no' paths. 'yes' leads to 'set provision indication = provisioned', 'no' leads to 'set provision indication = not provisioned'. Both paths merge at 'continue call handling', which leads to 'idle'. A note indicates 'COLR: Connected Line Identification Restriction.'](78ff716475b2f65bf01c3a4d02d89fc4_img.jpg)
+
+Process COLR\_MAF040 381\_42(1)
+
+Figure 4.2
+
+```
+graph TD; idle1([idle]) --> initiate[initiate handling of COLR]; initiate --> provisioned{COLR provisioned}; provisioned -- yes --> set_provisioned[set provision indication = provisioned]; provisioned -- no --> set_not_provisioned[set provision indication = not provisioned]; set_provisioned --> continue{continue call handling}; set_not_provisioned --> continue; continue --> idle2([idle]); note[COLR: Connected Line Identification Restriction.];
+```
+
+Flowchart for Process COLR\_MAF040. It starts with 'idle', followed by 'initiate handling of COLR'. A decision diamond 'COLR provisioned' has 'yes' and 'no' paths. 'yes' leads to 'set provision indication = provisioned', 'no' leads to 'set provision indication = not provisioned'. Both paths merge at 'continue call handling', which leads to 'idle'. A note indicates 'COLR: Connected Line Identification Restriction.'
+
+**Figure 4.2: MAF040 Determination of connected line identification restriction subscription (VLR)**
+
+![Flowchart for Process COLR_MAF041. It starts with 'idle', followed by 'initiate handling of COLR'. A decision diamond 'COLR provisioned' has 'yes' leading to 'set PI = presentation restricted' and 'no' leading to 'set PI = presentation allowed'. Both paths merge to 'continue call handling', which ends at 'idle'. A note defines COLR as Connected Line Identification Restriction and PI as Presentation Indicator.](6629e8a87e7552e2454b7c3e9f6d73a0_img.jpg)
+
+Process COLR\_MAF041
+
+381\_43(1)
+
+Figure 4.3
+
+```
+graph TD; idle1([idle]) --> initiate[initiate handling of COLR]; initiate --> provisioned{COLR provisioned}; provisioned -- yes --> set_restricted[set PI = presentation restricted]; provisioned -- no --> set_allowed[set PI = presentation allowed]; set_restricted --> continue{continue call handling}; set_allowed --> continue; continue --> idle2([idle]);
+```
+
+COLR: Connected Line Identification Restriction.  
+PI: Presentation Indicator.
+
+Flowchart for Process COLR\_MAF041. It starts with 'idle', followed by 'initiate handling of COLR'. A decision diamond 'COLR provisioned' has 'yes' leading to 'set PI = presentation restricted' and 'no' leading to 'set PI = presentation allowed'. Both paths merge to 'continue call handling', which ends at 'idle'. A note defines COLR as Connected Line Identification Restriction and PI as Presentation Indicator.
+
+Figure 4.3: MAF041 Determination of the presentation indicator
+
+![Sequence diagram showing information flow for connected line identification restriction from MS/TE to MSb via MSC/LE, VLRb, and MSCb.](9f6dec4d4e9fde40bce018861ef1278e_img.jpg)
+
+```
+
+sequenceDiagram
+    participant MS/TE
+    participant MSC/LE
+    participant VLRb
+    participant MSCb
+    participant MSb
+
+    MS/TE->>MSC/LE: set-up
+    MSC/LE->>MSCb: set-up
+    MSCb->>VLRb: info req
+    VLRb-->>MSCb: MAF040
+    MSCb->>VLRb: info ack
+    MSCb->>MSb: set-up
+    MSb-->>MSCb: answer **
+    MSCb->>MSC/LE: answer (SI+PI+LI)
+    Note right of MSCb: MAF041  
+OR1:N  
+OR2:a
+    MSCb->>MSC/LE: answer (SI+PI+LI)
+    Note right of MSCb: OR1:Y  
+OR2:b
+  
+```
+
+Sequence diagram showing information flow for connected line identification restriction from MS/TE to MSb via MSC/LE, VLRb, and MSCb.
+
+**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.
+
+![State transition model for COLR diagram showing two states and two transitions.](329c96049bb432e9c2cbda4e224a0c9c_img.jpg)
+
+```
+
+stateDiagram-v2
+    [*] --> State1 : Provision
+    State1 --> [*] : Withdrawal
+    state " (Not Provisioned, Not Applicable, Not Active, Not Induced) " as State1
+    state " (Provisioned, Not Applicable, Active and Operative, Not Induced) " as State2
+  
+```
+
+The diagram illustrates the state transition model for COLR. It consists of two states represented by ovals. The left state is labeled "(Not Provisioned, Not Applicable, Not Active, Not Induced)". The right state is labeled "(Provisioned, Not Applicable, Active and Operative, Not Induced)". A curved arrow labeled "Provision" points from the left state to the right state. A curved arrow labeled "Withdrawal" points from the right state back to the left state.
+
+State transition model for COLR diagram showing two states and two transitions.
+
+**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:
+
+- the HPLMN supports COLR, and COLR is provisioned for the subscriber;
+- the HPLMN supports COLR, but COLR is not provisioned for the subscriber;
+- 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 provisioned                       | *                                             | *             | *                                 | *                        | *                              | -                          | -                                  | -                              |
+| 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                |
+| <b>CLIP provisioned with override category</b> | -                                             | -             | -                                 | -                        | -                              | 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 |           |         |        |         |             |                                                               |
+|----------------|-----------|---------|--------|---------|-------------|---------------------------------------------------------------|
+| TSG CN#        | Spec      | Version | CR     | <Phase> | New Version | Subject/Comment                                               |
+| Apr 1999       | GSM 03.81 | 7.0.0   |        |         |             | Transferred to 3GPP CN1                                       |
+| CN#03          | 23.081    |         |        | R99     | 3.0.0       | Approved at CN#03                                             |
+|                | 23.081    | 3.0.0   |        | R99     | 3.0.1       | Upgrade of references from 2G to 3G                           |
+| CN#08          | 23.081    | 3.0.1   |        | R99     | 3.1.0       | Enhanced handling of presentation indicators for CLIP         |
+| CN#11          | 23.081    | 3.1.0   |        | Rel-4   | 4.0.0       | Release 4 after CN#11                                         |
+| CN#16          | 23.081    | 4.0.0   |        | Rel-5   | 5.0.0       | Release 5 after CN#16                                         |
+| CN#17          | 23.081    | 5.0.0   | 0006   | Rel-5   | 5.1.0       | Correction of 'Cause of no CLI' handling in SDLs              |
+| CN#19          | 23.081    | 5.1.0   | 0007r1 | Rel-5   | 5.2.0       | Correction to interworking between CLIP enhancement and CAMEL |
+| CN#25          | 23.081    | 5.2.0   | 0008   | Rel-6   | 6.0.0       | Editorial correction of table definition                      |
+| CT#36          | 23.081    | 6.0.0   |        | Rel-7   | 7.0.0       | Upgraded unchanged from Rel-6                                 |
+| CT#42          | 23.081    | 7.0.0   |        | Rel-8   | 8.0.0       | Upgraded unchanged from Rel-7                                 |
+| CT#46          | -         | 8.0.0   | -      | Rel-9   | 9.0.0       | Update to Rel-9 version (MCC)                                 |
+| 2011-03        | -         | 9.0.0   | -      | Rel-10  | 10.0.0      | Update to Rel-10 version (MCC)                                |
+| 2011-12        | 23.081    | 10.0.0  | 0009   | Rel-11  | 11.0.0      | CLI interactions with ACR                                     |